Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
3 tasks
motey opened this issue Aug 5, 2020 · 6 comments
Open
3 tasks

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

motey opened this issue Aug 5, 2020 · 6 comments
Assignees
Labels
Priority: High This issue should be dealt with as soon as possible Status: Suggested This issue is a suggestion for doing something new or different in CovidGraph Tag: Infrastructure This issue is about infrastructure

Comments

@motey
Copy link
Member

motey commented Aug 5, 2020

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 motey added Priority: High This issue should be dealt with as soon as possible Tag: Infrastructure This issue is about infrastructure labels Aug 5, 2020
@motey
Copy link
Member Author

motey commented Aug 5, 2020

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
Copy link
Member Author

motey commented Aug 5, 2020

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

@motey
Copy link
Member Author

motey commented Aug 5, 2020

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

@motey
Copy link
Member Author

motey commented Aug 5, 2020

@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
Copy link
Member Author

motey commented Aug 5, 2020

@Jiros
Copy link
Contributor

Jiros commented Aug 5, 2020

@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)

@motey motey changed the title Refactor, Streamline, Sync, Tidy, document up infrastructure Refactor, Streamline, Sync, Tidy up, document infrastructure Aug 6, 2020
@motey motey added the Status: Suggested This issue is a suggestion for doing something new or different in CovidGraph label Aug 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High This issue should be dealt with as soon as possible Status: Suggested This issue is a suggestion for doing something new or different in CovidGraph Tag: Infrastructure This issue is about infrastructure
Projects
None yet
Development

No branches or pull requests

3 participants