Mybinder.org-deploy: Pointing `mybinder.org` to the beta deployment

[choldgraf]

Hey all - @yuvipanda and I have been mulling this over for a while now, and we think that it's time to point mybinder.org to the beta deployment. I recently changed the page so that "beta" is up there in big letters, so it'll be clear that this isn't a finished-release. However, at this point the beta deployment is far more stable than the old version of binder, and ready for a soft launch.

Just opening this issue here in case @willingc or @minrk have suggestions otherwise...I feel like this should be a group decision.

Unless somebody objects, the plan is to make this switch as soon as I can figure out billing details with the new Moore grant (which are currently awaiting a response from Berkeley campus shared services). That'll probably be settled by early next week.

[minrk]

👍 to updating

[minrk]

Related: will we have prod & beta & staging here, or just rename beta to prod?

[willingc]

:+1:

[choldgraf]

sounds good!

we'll eventually rename beta to prod, not sure if that'll happen now or later but sometime it will :-)

btw - @yuvipanda brought up a good point that the two of us tend to have conversations about this stuff at BIDS or in non-public channels. We'll both be better about keeping our discussions about binder/jhub in the gitter channel / github repos!

[yuvipanda]

In #43 I'll probably do a bunch of changes here - specifically, I want to have staging and prod to be different clusters as well (currently they're the same cluster) and maybe even different projects (for better isolation & security). I'll rename the branches then. Hopefully that'll happen next week!

[willingc]

btw - @yuvipanda brought up a good point that the two of us tend to have conversations about this stuff at BIDS or in non-public channels. We'll both be better about keeping our discussions about binder/jhub in the gitter channel / github repos!

That would be very helpful. Otherwise, we have no idea or context on what you are trying to accomplish and why.
cc/ @fperez @ellisonbg @minrk

[ellisonbg]

+1

On Fri, Oct 6, 2017 at 1:44 PM, Carol Willing [e-mail]
wrote:

btw - @yuvipanda https://github.com/yuvipanda brought up a good point
that the two of us tend to have conversations about this stuff at BIDS or
in non-public channels. We'll both be better about keeping our discussions
about binder/jhub in the gitter channel / github repos!

That would be very helpful. Otherwise, we have no idea or context on what
you are trying to accomplish and why.
cc/ @fperez https://github.com/fperez @ellisonbg
https://github.com/ellisonbg @minrk https://github.com/minrk

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterhub/mybinder.org-deploy/issues/49#issuecomment-334865265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0KCNs3m1xV4jPsnRQAMtnCQws9Vpks5sppEZgaJpZM4PuR9W
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
[email protected] and [email protected]

[choldgraf]

Hey all, @yuvipanda and I are planning on doing this on Wednesday of this week. This is for two reasons:

1. The beta deployment is ready for wider use, and is much, much more functional than the current mybinder.org
2. I found out last week that Jeremy really needs us to start paying the bill for Binder, which means we need to switch over the google project owners so we can start paying for this off of the Moore grant.

Pinging this group in case anyone has thoughts on this.

cc @willingc @minrk @fperez @Carreau @yuvipanda @mpacer (or anybody else I'm missing)

[ellisonbg]

Sounds good! To keep things exciting I am giving a talk at 4pm on Wednesday
;-) I would normally demo binder during such a talk, but I can check in
shortly beforehand to see if that is viable.

On Mon, Oct 23, 2017 at 11:15 AM, Chris Holdgraf [e-mail]
wrote:

Hey all, @yuvipanda https://github.com/yuvipanda and I are planning on
doing this on Wednesday of this week. This is for two reasons:

1. The beta deployment is ready for wider use, and is much, much more
   functional than the current mybinder.org
2. I found out last week that Jeremy really needs us to start paying
   the bill for Binder, which means we need to switch over the google project
   owners so we can start paying for this off of the Moore grant.

Pinging this group in case anyone has thoughts on this.

cc @willingc https://github.com/willingc @minrk
https://github.com/minrk @fperez https://github.com/fperez @Carreau
https://github.com/carreau @yuvipanda https://github.com/yuvipanda
@mpacer https://github.com/mpacer (or anybody else I'm missing)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterhub/mybinder.org-deploy/issues/49#issuecomment-338749490,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0MF9UgTdYcKsI36JcPe8cFDo0WScks5svNfcgaJpZM4PuR9W
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
[email protected] and [email protected]

[choldgraf]

ah - IMO we should make this switch out of peak hours, so maybe evening to late-evening time PST, depending on whether that fits w/ @yuvipanda 's schedule

[ellisonbg]

I think this sounds good, don't feel like you need to transition before my
talk - later Wed is fine.

On Mon, Oct 23, 2017 at 12:48 PM, Chris Holdgraf [e-mail]
wrote:

ah - IMO we should make this switch out of peak hours, so maybe evening to
late-evening time PST, depending on whether that fits w/ @yuvipanda
https://github.com/yuvipanda 's schedule

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterhub/mybinder.org-deploy/issues/49#issuecomment-338775694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0PiJizMIhBS7st-WfVq78YaT5I2zks5svO2ZgaJpZM4PuR9W
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
[email protected] and [email protected]

[yuvipanda]

The steps to transition are:

1. Create new projects (binder-prod and binder-staging)
2. Do #83. This sets up two entirely new binderhubs
3. Switch staging DNS entries over, make sure everything is going ok
4. Switch over beta.mybinder.org to the new hub, but not hub.beta.mybinder.org. This lets people who are already running continue running, but new users get on the new infrastructure
5. Once the old hub is drained, kill it.

FIN

[Carreau]

Depending on when you decide to do the transition I can be around.

[yuvipanda]

@choldgraf it looks like we've to manually request a quota increase - the default quota for google cloud is only 24 cores, which is pretty small. https://cloud.google.com/compute/quotas is the procedure to ask for a quota bump, we should do it sooner than latter so we are ready to move when time comes.

[minrk]

I think everything here is done except for draining and shutting down the binder-testing project, is that right?

[yuvipanda]

It is, @minrk! I've shut down most of the compute in the binder-project, will finish cleanup later this week!

[yuvipanda]

Going to close this now since this is done, and instead open a different issue!