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

Already on GitHub? Sign in to your account

Bring your own computing power #60

Open
betatim opened this Issue Mar 7, 2016 · 3 comments

Comments

Projects
None yet
2 participants
Owner

betatim commented Mar 7, 2016

Watch getcarina/carina-oauth#2 and carolynvs/howtowhale#1. Once carina has oauth and @carolynvs gets the auth and spawner into the respective jupyter/*repos we should get in on the action by add a drop down menu to our spawner form that allows people to choose where to launch their container.

Owner

betatim commented Apr 6, 2016

carolynvs/howtowhale is now live: https://howtowhale.com (click "try docker"). We need to up our game to integrate this bring your own compute idea into everware.

Awesome work by @carolynvs!

HOT! I'm excited to see this in action elsewhere.

I should have the oauth doc for Carina up this week and then next week I plan on submitting the CarinaAuthenticator and CarinaSpawner to the Jupyter project. You can subscribe to carolynvs/howtowhale#7 to know when that's complete or please feel free to copy those classes from howtowhale until it's accepted upstream.

Owner

betatim commented Apr 7, 2016

We need to do some spec'ing here. We should preserve the decoupling of what auth system we use and the spawner. For example we use the GitHub oauth token to fork&push, so we can't switch to CarinaAuth without breaking that. We should also plan ahead for when others provide something like carina does. Ideally we'd offer the user a choice on the spawner page:

Do you want to use:

  • carina credentials
  • upload a auth zipfile for X
  • spin up EC2 container service and then docker there
  • ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment