Create a dev instance of the QHub deployment

NASA-IMPACT / veda-qhub

Other

0 stars 0 forks source link

Create a dev instance of the QHub deployment #5

Closed abarciauskas-bgse closed 1 year ago

abarciauskas-bgse commented 1 year ago

We have a deployment of QHub which currently resides at veda-analytics.delta-backend.com using https://github.com/nasa-impact/veda-qhub and deployed to the UAH AWS environment under the project name "aimee-qhub".

We want to deploy another instance of this to act as our dev environment. Then we will have a dev environment for testing out changes and a "demo" environment for live demos.

Note we plan to call these jupyter-demo.delta-backend.com and jupyter-dev.delta-backend.com

Acceptance criteria:

[ ] A running instance of QHub in the UAH account under the domain jupyter-dev.delta-backend.com that is accessible to members of this team.

abarciauskas-bgse commented 1 year ago

@jpolchlo @j08lue moved this into "Ready to be refined" since it sounds like this hasn't been started. I thought it would be good to have 2 instances of qhub in our dev UAH AWS account to develop upon but do you still agree @j08lue ?

j08lue commented 1 year ago

I thought it would be good to have 2 instances of qhub in our dev UAH AWS account to develop upon but do you still agree

Yes, it would be great to have two instances: one (DEMO) that is stable enough for ad-hoc demos and some test users and one (DEV) that we can break and rebuild as we please.

It is not urgent, but would be great to close this. Going from one deployment to two also helps identify issues with the config or reproducibility issues.

j08lue commented 1 year ago

Now that we have a DEMO instance of QHub JupyterHub (https://github.com/NASA-IMPACT/veda-architecture/issues/108), maybe the second one should actually be DEV, following my previous conception:

DEMO is basically for staging, unless we want three deployments.

So let us rename everything here from staging to dev, i.e. also deploy under jupyter-dev.delta-backend.com. Ok, @abarciauskas-bgse?

abarciauskas-bgse commented 1 year ago

That works for me @j08lue - so just to clarify we can keep jupyter-demo.delta-backend.com and then we should also create a "dev" instance (not yet deployed)?

j08lue commented 1 year ago

Yes, please. 😄

This is my plan of deployments in table form:

From here: https://almanac.io/docs/analytics-platform-IuyArwIh2xn9ThmJkJ1sjLTh3PYMi3Mk#83dfa147-291c-45a4-979c-3f459d688e06

abarciauskas-bgse commented 1 year ago

This table is super helpful thank you!

j08lue commented 1 year ago

No dev deployment planned, as the main deployment we will work with is the SMCE 2i2c one and externally provided services such as MAAP.