Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • freedesktop freedesktop
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 83
    • Issues 83
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • freedesktop.org
  • freedesktopfreedesktop
  • Issues
  • #206
Closed
Open
Created Nov 05, 2019 by Emma Anholt@anholtMaintainer

Create VPC peering setup for google runners

Right now the Mesa runners are hitting fd.o through the external IP. However, they're in the same zone and we could reduce both of our egress costs (while improving network perf) by having a peering VPC for the runner to talk to so that we just used google-internal IPs.

I don't feel confident in working on this as I don't want to disrupt fd.o, but if we had a thing for me to plug into the google side to start using it, I'd love to.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking