- Discussion of Terratoolserve:
- One centralized server for all Clowder instances
- One Terratoolserve per Clowder instance – problematic for Kubernetes
- For the demo: run a tool server as a system daemon
- Quotas are not enforced now
- Apictl is not using go api bindings (ala swagger client)
- IRods integration with a single server is OK, but craig will confirm with Jon
- Demo has been moved to Weds – Jon and David L asked to attend
- Make videos, in case things go wrong
- Installer process tasks: GUI, Apiserver, Kubernetes, etc.
- Building our own Kuberenetes binaries + containers
- Realistic development environment: emulates full cluster deploy including loadbalancing
- Workshop tutorial
- Every participant gets a CoreOS VM
- ssh into the box – dummy credentials
- What is the image? CoreOS X
- Docker run -it ndslabs/ndsdev bash
- Pulls image
- kube-up
- ndslabs-up (apiserver, gui, load default specs)
- login/ndslabctl/kubectl/docker
- Show how to add a service and run it
- Write docker file, build image, push the image (need a dockerhub account)
- Write NDSLAbs service spec, load and test that spec
- Run the service via apictl or UI, start stop, interact with the endpoints (upload data/etc)
- Assumption
- hostPath volumes (no one will have OpenStack credentials)
- Each participant will have a laptop with SSH capability and browser
- Will continue to use NodePort
- VMs: Access will be terminated when – end of workshop (end of week)
- Every participant gets a CoreOS VM
- Will still try to integrate Prometheus?
- What is a complete local environment?
- What are the requirements:
- Docker v1.9; adequate RAM and HDD (8GB, as much HD as images you want to run)
- System requirements
- We don't understand the requirements, so we need to identify them
- Bootup scripts pushed into container or tarfile
- What are the requirements:
Overview
Content Tools