Decomission `2i2c-aws-us` cluster

[yuvipanda]

This cluster now has only hubs internal to 2i2c that barely get any use. We should decomission this cluster and save ourselves both money and infrastructure organizational complexity.

particularly, this means the 'showcase' hub (which doesn't actually have all the features we have, and i also suggest showcasing direct community's hubs instead) will go away.

Definition of Done

• 2i2c-aws-us cluster is gone

[agoose77]

I can surface at this stage that I think we do use showcase -- some people use it to do work, and others for demos. I know at one point we spoke about using it to build a comprehensive set of demos, too.

[yuvipanda]

For demos, I'd rather have us use specific community's hubs to describe specific demos, rather than one omnibus hub - no actual communities use omnibus hubs. And if there's some specific kind of work that isn't deployed, I'd say it should be a hub dedicated for it, primarily so we don't get regular alerts for it that we need to investigate (https://2i2c-org.pagerduty.com/incidents/Q3341C4NN1S9M1?utm_campaign=channel&utm_source=slack is what triggered this).

What kind of work is being done with this cluster / account?

[jmunroe]

Caveat to my comments below: I don't have capacity to champion defining what showcase could mean. If @colliand as BDL sees a roll for a showcase hub as a sales asset, we should keep it. If it is not useful, then we should get rid of it.

--

I am ok tearing down 2i2c-aws-us if there is the intention of, eventually, spinning up something that does in fact showcase was a hub is.

Using a community's hub for demoing, sales work, or internal 2i2c use is something that would make be uncomfortable since we would be asking another community to pay for cloud costs that do not directly benefit that community.

Also, exposing community information to prospective buyers sounds like something we should be avoiding. I disagree with using specific communities hub for our sales process.

I also agree that showcase today does not have all of the features we offer. I think the solution is to extend it so that we it does showcase the features we want to show.

My opinion is that we should have a cluster for demoing, sales work, that has multiple hubs (example: a JupyterHub with persistent storage, a JupyterHub with no persistent storage, a BinderHub, something else?) to serve a reference for what we mean by each of those hubs.

[yuvipanda]

As part of responding to an alert, I have decomissioned just the dask-staging hub in #7194. That's currently unused. I'll merge that if there are no objections to getting rid of that hub.

[colliand]

Let's decommission and revisit questions around infrastructure for demos more systematically later. I approve of this request. Thanks Yuvi and James for including me in this process.