Test, development and Binder hubs
Those are deployments managed by Pangeo collaborators and open to everyone,
usually by Pangeo github organization public membership for the standard
Jupyterhubs, and with no restriction for Binder hubs. All of them rely
on dask-kubernetes for (auto)scaling.
Description: Flagship Pangeo JupyterHub server for scalable interactive data analysis running on Google Cloud Platform
Cloud provider: Google Cloud Platform
Jupyter Deployment: JupyterHub
Access: Need a github account part of the Pangeo organization with affiliaton set to public
|
Description: Pangeo demo and model for domain specific deployments
Cloud provider: Google Cloud Platform
Jupyter Deployment: JupyterHub
Access: Need a github account part of the Pangeo organization with affiliaton set to public
|
Description: Validation and integration environment for Pangeo platform
Cloud provider: Google Cloud Platform
Jupyter Deployment: JupyterHub
Access: Used by Pangeo core developers, need a github account and specific authorization
|
Description: Develoment environment for Pangeo platform, highly unstable
Cloud provider: Google Cloud Platform
Jupyter Deployment: JupyterHub
Access: Used by Pangeo core developers, need a github account and specific authorization
|
Description: Former flagship Pangeo JupyterHub server for scalable interactive data analysis running on Google Cloud Platform
Cloud provider: Google Cloud Platform
Jupyter Deployment: JupyterHub
Access: Soon being closed
|
Description: Flagship Pangeo BinderHub deployment running on Google Cloud Platform
Cloud provider: Google Cloud Platform
Jupyter Deployment: BinderHub
Access: Anyone, look at http://binder.pangeo.io/v2/gh/pangeo-data/pangeo-example-notebooks/master
|
Description: Developement and integration Pangeo BinderHub deployment running on Google Cloud Platform
Cloud provider: Google Cloud Platform
Jupyter Deployment: BinderHub
Access: Used by Pangeo core developers
|
Domain specific deployments
Those are designed specifically for domain use cases and communities,
allowing to customize both infrastructure and software environment
toward a particular need. If you’re interested in one of this deployment,
please contact one of its responsible.
All deployments here use standard Jupyterhub and dask-kubernetes.
Description: Pangeo platform for developing atmospheric use cases
Cloud provider: Google Cloud Platform
Access: Ask @charlesbluca and @biasuttimic on https://github.com/pangeo-data/atmos.pangeo.io-deploy/
|
Description: Pangeo platform for developing hydrologic use cases
Cloud provider: Google Cloud Platform
Access: Ask @jhamman or @bartnijssen
|
Description: Pangeo platform for developing polar use cases
Cloud provider: Google Cloud Platform
Access: Ask @NicWayand on https://github.com/NicWayand/polar.pangeo.io-deploy
|
Description: Pangeo platform for developing astronomic use cases
Cloud provider: Google Cloud Platform
Access: Ask @SimonKrughoff and @wtbarnes on https://github.com/pangeo-data/astro.pangeo.io-deploy
|
Description: Pangeo platform for developing ocean use cases
Cloud provider: Google Cloud Platform
Access: Ask @raphaeldussin on https://github.com/raphaeldussin/example.pangeo.io-deploy
|