Difference between revisions of "Containerizing StarlingX Infrastructure"
| Line 38: | Line 38: | ||
[[File:StarlingX Initial Containerized Infrastructure.png]] | [[File:StarlingX Initial Containerized Infrastructure.png]] | ||
| − | === OpenStack services === | + | === OpenStack and other services === |
* All OpenStack services currently integrated by StarlingX are planned to be containerized | * All OpenStack services currently integrated by StarlingX are planned to be containerized | ||
** Including dependencies such as MariaDB | ** Including dependencies such as MariaDB | ||
** Pike based | ** Pike based | ||
| − | * nova-api proxy from stx-nfv will be containerized | + | *** nova-api proxy from stx-nfv will be containerized |
| + | *** nova-compute will be containerized | ||
| + | *** Neutron will be containerized | ||
| + | *** cilometer-poller will be containerized | ||
| + | ** Keystone container will run in the 'openstack' namespace for the OpenStack services only | ||
* rbd-provisioner pod: enabling pvc's from the CEPH cluster | * rbd-provisioner pod: enabling pvc's from the CEPH cluster | ||
* An instance of the Fault Management service will be containerized for alarming in OpenStack | * An instance of the Fault Management service will be containerized for alarming in OpenStack | ||
| − | * | + | * Current StarlingX compute nodes are re-purposed as Kubernetes worker nodes |
| + | * OVS-DPDK is '''not''' containerized | ||
| + | ** No Helm chart is currently available | ||
| + | |||
| + | |||
| + | [[File:StarlingX Initial Containerized Infrastructure 2.png]] | ||
| + | |||
| + | == Deployment/Lifecycle Management == | ||
| − | |||
| − | |||
[[File:Containerization overview 7.png|thumb]] | [[File:Containerization overview 7.png|thumb]] | ||
Revision as of 18:09, 1 March 2019
Contents
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
Container Platform
- 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
Initial Infrastructure Containerization
Overview
- The "Flock" services with the exceptions called out later are not planned to be containerized for the initial phase
- An instance of Keystone, RabbitMQ, and PostgreSQL will remain on bare metal and will be used for the "Flock" service
- An instance of Horizon will remain on bare metal for the "Flock" services only
OpenStack and other services
- All OpenStack services currently integrated by StarlingX are planned to be containerized
- Including dependencies such as MariaDB
- Pike based
- nova-api proxy from stx-nfv will be containerized
- nova-compute will be containerized
- Neutron will be containerized
- cilometer-poller will be containerized
- Keystone container will run in the 'openstack' namespace for the OpenStack services only
- rbd-provisioner pod: enabling pvc's from the CEPH cluster
- An instance of the Fault Management service will be containerized for alarming in OpenStack
- Current StarlingX compute nodes are re-purposed as Kubernetes worker nodes
- OVS-DPDK is not containerized
- No Helm chart is currently available
