Rename this repository to infrastructure

[yuvipanda]

This repository is called pilot-hubs, which might make you think it deploys the hubs under *.pilot.2i2c.cloud. However, it actually deploys almost all the hubs we maintain - see list under https://github.com/2i2c-org/pilot-hubs/tree/master/config/hubs.

We should rename this repository to make that clearer.

How about just infrastructure?

Tasks

• Rename pilot-hubs to infrastructure
• Update ReadTheDocs URLs
• Point infrastructure.2i2c.org to these docs
• Update references to pilot-hubs.2i2c.org or devops.2i2c.org to infrastructure.2i2c.org
  • Pilot Hubs to infrastructure in docs team-compass#267
  • Rename devops to infrastructure 2i2c-org.github.io#81
  • Pilot hubs to infrastructure docs#107
  • Rename pilot hubs to infrastructure #758

[yuvipanda]

Also what exactly are we piloting? I think we should define that and use it only in appropriate places.

[choldgraf]

For renaming this repository, it sounds good to me. infrastructure is a little bit generic but also accurate, I think. Other options could be

• 2i2c-org/deployments / 2i2c-org/deploy
• 2i2c-org/cloud
• 2i2c-org/hubs
• 2i2c-org/service
• 2i2c-org/federation

For "what are we piloting?" I think the answer is that we are piloting a few things:

• At the highest level, we are piloting a model for a Managed Hub Service for 2i2c. This entails a few different things we're trying out as a part of the pilot:
  • CI/CD infrastructure to deploy multiple independent hubs from a single source (pilot-hubs/ until we rename it)
  • Support mechanisms and processes for these hubs (e.g. FreshDesk, issues to create new hubs, etc)
  • Sales / contracting processes for bringing on new hubs
  • Sustainability models for generating resources that keeps this service running / growing
  • (not unique to the managed service): Team processes for coordinating and prioritizing our time

So in general, when I think "Our pilot", I mean the combination of things above.

[damianavila]

I like the infrastructure proposal.

So in general, when I think "Our pilot", I mean the combination of things above.

I agree with this view...
Although maybe we need to be a little bit more fine-grained and ask ourselves what we are piloting on each of those items...

[choldgraf]

Proposal

Are there any objections to the following:

• We rename this repository to infrastructure
• We point infrastructure.2i2c.org to this documentation

?

[yuvipanda]

That sounds great, @choldgraf

[choldgraf]

OK - I've renamed the repository to infrastructure, and have opened up documentation update PRs across each of our active repositories to update references. I've got a list of those PRs in the top comment (#570 (comment)) it'd be great if folks could at least give a quick look to make sure I didn't accidentally rename something incorrectly.

Question

There are some cases where pilot-hubs is hard-coded into cloud infrastructure. I believe our GCP registry has pilot-hubs in it for example. I'm not renaming anything in tfvars etc to make sure we don't mess that up. Does anybody object to just leaving that as-is for now?

[damianavila]

Does anybody object to just leaving that as-is for now?

No objections, in fact, see my comment here: #758 (comment)

[choldgraf]

this is now done!