Refactor, Streamline, Sync, Tidy up, document infrastructure

covidgraph / documentation

28 stars 8 forks source link

Refactor, Streamline, Sync, Tidy up, document infrastructure #90

Open motey opened 4 years ago

motey commented 4 years ago

At the moment we have 3 Host:

DEV - Was DEV DB but is used now for running the pipeline atm.
COMPUTE - Was the pipeline runner but is running the DEV DB now
PROD - This is used to run the PROD DB

Every instance has different directories, setups and config styles.

[ ] Define a global setup/config style
[ ] Implement this setup/config on all instances
[ ] Adapt (and improve) the documentation to these changes

motey commented 4 years ago

i am in favor of a all dockerized and traefik proxied approach and put everything in /opt/covidgraph

@mpreusse you are cool with this?

motey commented 4 years ago

i want to try to use the treafik tls+tcp-endpoint feature to prevent any need for fumbling with certificates

motey commented 4 years ago

we could git the whole config in our ~~covidgraph/steering-group~~ https://github.com/covidgraph/infrastructure-config repo

motey commented 4 years ago

@Jiros you created the steering group repo. does every team member has access to https://github.com/covidgraph/infrastructure-config ? what do we need to do to restrict access to only some team members?

motey commented 4 years ago

think i found it https://github.com/covidgraph/infrastructure-config/settings/access

Jiros commented 4 years ago

@motey Yes, that's now restricted by the look of it. The other option is to set up an Infrstructure team in Github and add people and permissions to that but there's not much difference (other than being able to mention @team in comments etc) and makes more sense for larger setups.

Also, be aware that we can't add private repos to the ZenHub board but that doesn't sound like it will be an issue here.

We can discuss custom label types that might make more sense in that repo. (e.g. Type: Server)