Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The deploy-tools image assumes that you are deploying CoreOS instances. This choice is arbitrary, but there are many assumptions in the deploy-tools component that are bound to the OS choice. Different providers make different OS decisions.  Kubernetes seems to lean toward Fedora and Debian. GCE itself is Debian. Azure Ubuntu, etc. This may not be important if we can rely on Kuberenetes deployment provided by each commercial cloud provider.

...

Other storage includes mounted volumes for /var/lib/docker and /var/lib/kubelet.

REST API Server/CLI

Dedicated etcd

We no longer rely on the Kubernetes etcd service, and provide our own that runs within the cluster.

SMTP Server / Relay

We now provide an in-cluster SMTP relay that can be configured to use Google credentials. This makes it very simple to use your Google credentials to send verification / approval / support e-mails.

REST API Server/CLI

Labs Workbench provides a thin REST interface over Kubernetes. Basic operations include: authentication, account management (register, approve, deny, delete), service management (add/update/remove), application instance management (Labs Workbench provides a thin REST interface over Kubernetes. Basic operations include: authentication, account management (register, approve, deny, delete), service management (add/update/remove), application instance management (add/update/remove/start/stop/logs), console access. The primary purpose of the REST API is to support the Angular Web UI. The API depends on Kubernetes API, etcd, Gluster for shared volume support, and SMTP support.

Web UI

The Web UI is an Angular JS a monolithic AngularJS application that interfaces with the REST API.

...

Commercial cloud providers provide their own monitoring tools, e.g., GCE Monitoring.

...

Monitoring.

Docker cache

The Labs Workbench system deployed via deploy-tools includes a local Docker cache to minimize network traffic for image pulls

Private Docker registry

The Labs Workbench system deployed via deploy-tools includes a local Docker cache to minimize network traffic for image pullsprivate Docker registry to privately share images within your cluster without needing to share them out to Docker Hub

  • This will need to be tested

Automated Testing 

The Angular Web UI includes a facility for executing automated Selenium smoke tests.

...

  • Deployment process needs to be generalized to support more environments than OpenStack and likely more OSes than CoreOS
  • Volume/storage will not work on cloud providers
  • Potentially allow for Web UI customization
  • Better custom catalog support
  • Confirm ingress (including DNS/TLS) support with Commercial providers
  • We should work towards adding options for some of the above components, to reduce minimal deployment size

Other thoughts

  • TERRA-REF case:
    • We can imagine a couple of cases.  First, TERRA-ref as a full install with a system catalog and user catalogs.  Second, TERRA-REF as a user of the current system with a custom catalog and no individual user namespaces.  We could also have a TERRA-REF data provider to get data into containers.
  • Cyverse case:
    • Similarly, we can imagine a Cyverse user launching notebooks in the current system with a Cyverse data provider (FUSE, iRODS, etc)
    • Or a full install of Workbench by Cyverse

...