Skip to content
This repository has been archived by the owner on Apr 29, 2021. It is now read-only.

Commit

Permalink
Merge pull request #57 from NERSC/clean-up-after-converge
Browse files Browse the repository at this point in the history
Clean up after converge.  Will create an issue for creating deployment documentation.
  • Loading branch information
rcthomas authored Mar 25, 2019
2 parents f5f8a67 + 550044d commit ccb3096
Show file tree
Hide file tree
Showing 14 changed files with 0 additions and 1,437 deletions.
45 changes: 0 additions & 45 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,48 +1,3 @@
# NERSC JupyterHub Deployment

There are three Dockerfiles.

## Base Dockerfile

This is the common frame of reference for our JupyterHub installation.
While we are developing we can create this Docker image and from new images off of it for various purposes.
The base image comes from Ubuntu:16.04 and installs the NERSC fork of JupyterHub and that is about it.
If you find you need to `apt-get install` packages in derived images, think about putting them here.

JupyterHub should always come from a specific tag of our fork.
Would be nice to make it easy to adjust that.

## Dockerfile for jupyter.nersc.gov

This Dockerfile builds the setup for a Docker-based JupyterHub + Jupyter installation.
Basically the science gateway deployment right now.

## Dockerfile for jupyter-dev.nersc.gov

Dockerfile and supporting files (currently certs) for the cori login node deployment of JupyterHub.

BASE_PATH The path to the python install on the remote system
ADMINS A comma seperated list of admin usernames
SSL_KEY Path to the SSL key (if SSL should be enabled).
SSL_CERT Path to the SSL cert (if SSL should be enabled).
REMOTE_HOST Host:Port of the GSI SSH running on the remote system
HUB_API_URL URL of the HUB API (e.g. http://jupyter-dev.nersc.gov:8082/hub/api)

Probably the authenticator and SSH spawner should come from a specific tag on each repo.

## Additional setups

Other directories can be added for various testing.

## Future Work

Eventually the two derived image builds should merge into one using WrapSpawner.
This would provide a single point of entry for Jupyter at NERSC for:

* Jupyter in Spin (hub separate from notebooks and kernels though).
* Jupyter on Cori19
* Jupyter on Cori computes via reservation, interactive queue, etc.

## Scripts

These are management scripts.
34 changes: 0 additions & 34 deletions jupyter-dev-nersc/web/Dockerfile

This file was deleted.

74 changes: 0 additions & 74 deletions jupyter-dev-nersc/web/announcement.py

This file was deleted.

8 changes: 0 additions & 8 deletions jupyter-dev-nersc/web/build.sh

This file was deleted.

8 changes: 0 additions & 8 deletions jupyter-dev-nersc/web/docker-compose.yml

This file was deleted.

29 changes: 0 additions & 29 deletions jupyter-dev-nersc/web/docker-entrypoint.sh

This file was deleted.

9 changes: 0 additions & 9 deletions jupyter-dev-nersc/web/hub-scripts/flush-certs.sh

This file was deleted.

32 changes: 0 additions & 32 deletions jupyter-dev-nersc/web/hub-scripts/kill-cori.sh

This file was deleted.

27 changes: 0 additions & 27 deletions jupyter-dev-nersc/web/hub-scripts/scram-user.sh

This file was deleted.

18 changes: 0 additions & 18 deletions jupyter-dev-nersc/web/hub-scripts/test-user.sh

This file was deleted.

Loading

0 comments on commit ccb3096

Please sign in to comment.