Date: Fri, 29 Mar 2024 03:35:42 -0500 (CDT)
Message-ID: <598649634.314.1711701342626@os-confluence.ncsa.illinois.edu>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_313_218749938.1711701342626"
------=_Part_313_218749938.1711701342626
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Use cases
Developer installa=
tion
After experiencing Labs Workbench via the public demo instance or at a w=
orkshop, developers will want to install a local instance to get their hand=
s dirty, understand the architecture and possible integration points with t=
heir systems. We currently offer two approaches to installing Labs Wo=
rkbench: ndslabs-startup git repo or deploy-tools Ansible playbooks.
- Putting ourselves in the shoes of a developer new to Labs Workbench, ar=
e there changes we would make to simplify the local installation? For examp=
le, adding support for laptop-deploys with DNS Masq.
- What environments should we support (Linux, Mac, Windows, VMs etc.
- Should we continue to use HyperKube or move to another model (e.g., Min=
ikube)?
- Should we combine ndslabs-startup and deploy-tools into a single contai=
ner to launch labs workbench?
Labs Workbench Beta
The Labs Workbench beta instance deployed at SDSC is currently configure=
d with 11 instances, 28 vcpus, 196GB RAM, and 1.2 TB storage. This includes=
ops instance, master, loadbalancer, LMA, two compute nodes, 4 GFS servers,=
monitoring and backup. Using UC internal pricing, this service will cost a=
n estimate ~$2,100 per month or ~$25,000 per year to run at SDSC under the =
current configuration.
- How can we minimize resource requirements and cost while maximizing ela=
sticity and reliability?
- Can we support deployment into other environments (e.g., AWS/GCE)? &nbs=
p;
- How can we support deploying labs on existing Kubernetes installations?=
TERRA-REF
The TERRA-REF project manages 200TB of data on the ROGER system. Data is=
accessible via Globus, Clowder, GPFS mount to ROGER batch compute resource=
s, and NFS mount to ROGER/Nebula OpenStack resources. The TERRA-REF p=
roject includes a "tool launcher" service that supports launching Docker co=
ntainers to analyze data via the Clowder API and mounted directly via NFS. =
The "tool launcher" is being replaced by Labs Workbench. Labs W=
orkbench was also used to support the TERRA-REF Phenome 2017 workshop. On a=
n average day, Labs Workbench will need to support ~5-10 active users. &nbs=
p;During workshops, Labs Workbench will need to support ~30 simultaneous us=
ers.
- How can we minimize resource requirements and cost while maximizing ela=
sticity and reliability?
Users have the option to deploy Kubernetes in a variety of environments:=
https://kubernetes.io/docs/getting-start=
ed-guides/
- Minikube/Ubuntu LXD
- Hosted solutions: =20
- GCE
- AWS
- Azure Container Service
- Local solutions=20
- Can/should we support any of these options? What changes would be requi=
red to do so?
Tasks
- Explore deployment of Labs Workbench on laptop or single instance VM. A=
re there changes we can make to improve the user's experience? What environ=
ments can/should we support?=20
- NDS-756 - Explore improvements fo=
r laptop and single-node installation (1) Resolved
- NDS-761 - Explore improvements fo=
r laptop and single-node installation (2) Closed
- NDS-762 - Explore improvements fo=
r laptop and single-node installation (3) Resolved
- See Developer/Single-node installation
- Define minimal cluster configuration for current Labs Workbench with ab=
ility to scale up/down to support TERRA-REF use case.=20
- NDS-757 - Define minimal cluster =
configuration (1) Closed
- NDS-763 - Define minimal cluster =
configuration (2) Resolved
- NDS-764 - Define minimal cluster =
configuration (3) Resolved
- See Minimal Workbench Configuration
- Explore deployment of Labs Workbench on GCE. What changes are req=
uired?=20
- NDS-759 - Explore deploying Labs =
Workbench on GCE Resolved
- See Labs=
Workbench on GKE
- Explore deployment of Labs Workbench on AWS. What changes are required?=
=20
- See NDS-760 - Explore deployin=
g Labs Workbench on AWS Resolved
- See Labs=
Workbench on AWS
- Explore deployment of Labs Workbench on Azure. What changes are require=
d?=20
- See NDS-765 - Explore deployin=
g Labs Workbench on Azure Resolved
- See La=
bs Workbench on Azure
- Explore deployment of Labs Workbench on system deployed with kubeadm. W=
hat changes are required?=20
- See NDS-766 - Explore deploying Labs=
Workbench via kubeadm Resolved
- See Labs Workbench via Kubeadm
- See Multi Node Kubernetes developer environment - using VBox/Vagrant/CoreOS<=
/a>
- Explore latest options for deploying Kubernetes on OpenStack. What meth=
ods would we recommend? Explore deploying Labs Workbench on these environme=
nts. What changes would be required?=20
- See NDS-767 - Explore deployin=
g Labs Workbench using Kubernetes OpenStack support Resolved
- See Labs Workbench on OpenStack
------=_Part_313_218749938.1711701342626--