Initiative

Introduction

The first release of StarlingX provided a hardened OpenStack platform
Evolution plan to move to a cloud native (Kubernetes) platform was presented at the Vancouver Summit
- Run the infrastructure including OpenStack services as containerized applications on Kubernetes
- Containerization work is planned to be done in phases having OpenStack and dependencies the initial focus

Kubernetes master configuration on two nodes with high availability (HA)
- Run on existing StarlingX nodes
- Deployed by StarlingX system configuration
Calico CNI plugin
Docker runtime
CEPH as persistent storage backend
- Leverage existing bare metal CEPH cluster
- Extend CEPH support to one- and two-node configuration
Authentication/authorization of Kubernetes APIs with Keystone
Local Docker image registry, authentication with Keystone
Helm as package manager
Airship Armada for orchestrating the deployment of multiple Helm charts (ex. OpenStack)
Initial Kubernetes hosting environment for applications, the infrastructure including OpenStack will also be containerized