| 1 |
On Wed, Sep 16, 2020 at 11:44 AM Alec Warner <antarus@g.o> wrote: |
| 2 |
> |
| 3 |
> - repomirror-ci and all the CI stuff is on infra because mgorny is also on infra! It's not like we set his stuff up for him; instead we gave him access to all the infra repos and he had to write his own puppet configs and whatnot. The benefit of course is that anyone on infra can bump the stuff and login to the machines and debug...but its not exactly a low bar. |
| 4 |
> .. |
| 5 |
> I think traditionally it's been a slog for non-infra people to get infra to host much of anything and due to difficulties with the all-or-nothing approach we take with infra credenteials; can really set a high bar to host much of anything these days. |
| 6 |
|
| 7 |
Seems like a way to improve this would be better documentation and a |
| 8 |
DIY infra testing platform. |
| 9 |
|
| 10 |
First, document how to prepare a service for infra hosting. Maybe |
| 11 |
provide an example service. |
| 12 |
|
| 13 |
Second, publish a tarball of a container/chroot that basically |
| 14 |
simulates an infra host for testing purposes. Provide instructions on |
| 15 |
how to configure/run it. Make it easy - edit this config file to |
| 16 |
point to your repo, put the name of your service/host here, etc. |
| 17 |
|
| 18 |
Anybody developing a service could then just follow the instructions |
| 19 |
and then test out their service in a similar environment to what infra |
| 20 |
uses. Nobody needs to be trusted with any credentials. Nobody needs |
| 21 |
access to any special repos. They can run the container on their own |
| 22 |
host, and point it at their favorite git repo hosting service. |
| 23 |
|
| 24 |
Once it is working all they need to do is give the link to their |
| 25 |
repo/etc to infra. Infra can then fork it and host it. The |
| 26 |
maintainer can submit pull requests as needed to infra. |
| 27 |
|
| 28 |
-- |
| 29 |
Rich |
Archives