Craig Willis
For the TERRA-REF project, I'm currently using Hyperkube. I did this because I want a minimal install with minimal OpenStack resources (cost/complexity). This is not just a developer instance, it will run as the primary instance for the project as a replacement for the toolserver. I think we can define a process for migrating from single-node to multi-node through etcd export and filesystem copy.
For a non-Hyperkube installation that scales, the minimal configuration is:
* 1 master/controller, 1 compute
I'd like to see us handle storage separately. If the project wants home directory, they can deploy NFS or Gluster, either an existing node or deploying new NFS/GFS instances.
David Raila
For a non-Hyperkube installation that scales, the minimal configuration is:
* 1 master/controller, 1 compute
Minimal Gluster configuration: simple replication? (instead of 2x2 striped and replicated)
Mike Lambert
Option 1: Hyperkube
- Minimal configuration: single-node
- Optional one-way migration path to scalable multi-node cluster
- Recommended for single-tenant / small-scale testing
- Does not support scaling up
Use Cases supported:
- Platform Exploration / Customization / Extension
- Development / Testing of Labs Workbench Services
Option 2: Ansible
- Minimal configuration: 1 master + 1 compute
- Optional: dedicated loadbalancer node
- Optional: dedicated glfs nodes
- Optional: dedicated LMA node
- Recommended for multiple tenants / large-scale testing or production use
- Supports scaling up and down, as needed
Uses:
- Workshops, hackathons, demos, etc
- Production use, defined as: "One or more real users are consuming the system or API"