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

Create Azure deployment infrastructure #373

Closed
3 tasks
choldgraf opened this issue May 3, 2021 · 6 comments
Closed
3 tasks

Create Azure deployment infrastructure #373

choldgraf opened this issue May 3, 2021 · 6 comments
Labels
Enhancement An improvement to something or creating something new.

Comments

@choldgraf
Copy link
Member

choldgraf commented May 3, 2021

Summary

We currently focus much of our deployment infrastructure around Google Cloud rather than AWS or Azure. We also have a few clients that would like their hubs working on Azure. We should improve our Azure deployment infrastructure and use these use-cases as forcing functions.

The use-case we can use for this is:

The hub is currently running on Google Cloud, but they'd like us to move it to Azure whenever possible.

Acceptance criteria

We should be able to spin up an Pangeo-style hub on Azure with the same ease that we currently have with GKE.

Tasks to complete

@choldgraf choldgraf added Enhancement An improvement to something or creating something new. 🏷️ CI/CD labels May 3, 2021
@yuvipanda
Copy link
Member

We have a lot of Azure automation at github.com/utoronto-2i2c/jupyterhub-deploy/. https://github.com/utoronto-2i2c/jupyterhub-deploy/tree/staging/terraform has terraform for setting up an AKS based Kubernetes cluster with autoscaling, image repositories and an NFS server in the correct network (via ansible), and there's automated deployment with hubploy and github actions.

@choldgraf
Copy link
Member Author

@yuvipanda thanks for that info! I've added a task to the top of the list to look into those repositories for inspiration

@choldgraf
Copy link
Member Author

Now that the JIL is up and running, is this mostly an issue for documentation rather than building the infrastructure itself?

@yuvipanda
Copy link
Member

@choldgraf so #287 hasn't been merged (or marked for review) yet. I think once that's done this will be an issue of documentation

@damianavila
Copy link
Contributor

@choldgraf #287 was indeed merged but the work @yuvipanda is talking about lives in #513 AFAIK, am I correct @yuvipanda?

@yuvipanda
Copy link
Member

At this point, I think #512 and this issue completely overlap - so I'm going to close this one and develop that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An improvement to something or creating something new.
Projects
None yet
Development

No branches or pull requests

3 participants