Open
Description
Add Jupyterhub deployment to Unity Marketplace and Management Console Interface
Acceptance Criteria:
- Jupyterhub is not deployed automatically to a venue until explicitly selected
- Jupyter node is configurable (number of instances, types)
- Market place entry and artifacts are created (See U-CS)
- Deployment form Management Interface can be done to a project venue
- Deployment integrates with Venue API Gateway (e.g. venue httpd backend)
- Deployment is linked with Unity A&A / cognito
- Health check endpoint is available and defined in marketplace entry
- Data Bucket is readable from Jupyter Venue after deployment (Requires a data bucket created from U-DS)
- NEW Gherkin Test case(s) added to System Test DURING THE PLANNING - how will we test the marketplace feature. Is it manual? or can it be automated?
- NEW Gherkin Test case(s) implementation added to System Test during PI. If automated, these must implement the above test cases(s)
Work Tickets:
- JupyterHub Integration into Unity Marketplace: Understand and Test Manual deployment as-is unity-cs#489
- JupyterHub Integration into Unity Marketplace: Refactor IAC code for marketplace deployments unity-cs#490
- JupyterHub Integration into Unity Marketplace: Create Marketplace JSON unity-cs#491
- JupyterHub Integration into Unity Marketplace: Create Gherkin Test Case for Manual Deployment of JH in MC unity-cs#497
- more coming..
Metadata
Metadata
Assignees
Type
Projects
Status
Done