Sloop type/site is a minimalistic approach to Airship with reduced
requirements towards hardware and external dependencies while keeping
all the functional features.
Major differences compared to reference site airship-seaworthy
- Two bare-metal server setup with 1 control, and 1 compute.
Most components are scaled to a single replica and doesn't carry
any HA as there is only a single control plane host.
- No requirements for DNS/certificates.
HTTP and internal cluster DNS is used.
- Ceph set to use the single (root) disk. This generally
provides minimalistic no-touch ceph deployment.
No replication of ceph data (single copy).
- Simplified networking (no bonding).
Two network interfaces are used by default (flat PXE, and DATA network
with VLANs for OAM, Calico, Storage, and OpenStack Overlay)
- Generic hostnames used (airsloop-control-1, airsloop-compute-1) that
simplifies generation of k8s certificates
- Usage of standard Ubuntu 16.04 GA kernel (as oppose to HWE)
This updates chart configuration overrides for the monitoring
services, as well as adds missing secrets, charts and service
accounts for other exporters that have now been enabled
This updates the Elasticsearch and Fluent-logging charts to use
the most recent configuration keys in their values overrides, and
also introduces support for the ceph-rgw s3 api for use for
Elasticsearch snapshot repositories
- Add tenant ceph manifests in globals
- Add reference overrides for site in airship-seaworthy
- Re-purpose 4th control as an additional compute to total 3.
This allows to maintain proper ceph replication
- Update disk layout to use partitions for journals
This adapts manifests to be in line of using git reference
for refering to global/secrets repos instead of versioned folders.