airship
/
maas
Code Issues Proposed changes
Kubernetes deployment artifacts for Canonical's MaaS.
94 Commits 1 Branch 0 Tags 3.4 MiB
Smarty 54.3%
Dockerfile 28.9%
Makefile 5.7%
Shell 5.6%
Python 5.5%
Go to file
indra 361b13342e Added filename to logging message format for 
troubleshooting purpose
 This change is related to Maas
   Here are the Change ID's for other airship componets
     Shipyard- I09348ab7ac78700badcff557a82049660ac9f5c6
     Airflow- If8fd5983fd589ddf07b960d38e0081cfb0237003
     Deckhand- I2763ae7ea62e78c9dd89659f97b149ab000d0ebb
     Drydock- I88c8cd6a56771cf6e97cfa874dc63963e247a890
     Armada- I5edd13d2a2c06f844bef1595e045208f53af4e71
     Promenade- Ibbbf65ad815fb8c9e6ede468eda12bec863bc474

Change-Id: I61e4daaac5b6c01dbe59b6d11e343c2b77483cbf
 		2019-02-05 16:59:51 +00:00
charts/maas (chart) rackd pod readiness check 2019-01-30 16:55:42 -06:00
images (fix) Give systemd service access to env 2019-01-25 11:22:59 -06:00
tools Added filename to logging message format for 2019-02-05 16:59:51 +00:00
.gitignore Add .gitignore to repo 2018-08-22 21:24:27 -05:00
.gitreview Update .gitreview for openstack infra 2018-05-17 19:48:42 +01:00
.zuul.yaml (zuul) Add Docker image jobs 2018-06-08 05:38:15 -05:00
LICENSE Initial commit 2017-10-19 11:42:23 -05:00
Makefile Minor: meaningful default label 2018-11-08 19:32:19 +01:00
README.md Add image cache sidecar 2017-12-04 12:50:30 -06:00

README.md

MaaS Helm Artifacts

This repository holds artifacts supporting the deployment of Canonical MaaS in a Kubernetes cluster.

Images

The MaaS install is made up of two required imags and one optional image. The Dockerfiles in this repo can be used to build all three. These images are intended to be deployed via a Kubernetes Helm chart.

MaaS Region Controller

The regiond Dockerfile builds a systemD-based Docker image to run the MaaS Region API server and metadata server.

MaaS Rack Controller

The rackd Dockerfile builds a systemD-based Docker image to run the MaaS Rack controller and dependent services (DHCPd, TFTPd, etc...). This image needs to be run in privileged host networking mode to function.

MaaS Image Cache

The cache image Dockerfile simply provides a point-in-time mirror of the maas.io image repository so that if you are deploying MaaS somewhere without network connectivity, you have a local copy of Ubuntu. Currently this only mirrors Ubuntu 16.04 Xenial and does not update the mirror after image creation.

Charts

Also provided is a Kubernetes Helm chart to deploy the MaaS pieces and integrates them. This chart depends on a previous deployment of Postgres. The recommended avenue for this is the Openstack Helm Postgres chart but any Postgres instance should work.

Overrides

Chart overrides are likely required to deploy MaaS into your environment

  • values.labels.rack.node_selector_key - This is the Kubernetes label key for selecting nodes to deploy the rack controller
  • values.labels.rack.node_selector_value - This is the Kubernetges label value for selecting nodes to deploy the rack controller
  • values.labels.region.node_selector_key - this is the Kubernetes label key for selecting nodes to deploy the region controller
  • values.labels.region.node_selector_value - This is the Kubernetes label value for selecting nodes to deploy the region controller
  • values.conf.cache.enabled - Boolean on whether to use the repo cache image in the deployment
  • values.conf.maas.url.maas_url - The URL rack controllers and nodes should use for accessing the region API (e.g. http://10.10.10.10:8080/MAAS)

Deployment Flow

During deployment, the chart executes the below steps:

  1. Initializes the Postgres DB for MaaS
  2. Starts a Pod with the region controller and optionally the image cache sidecar container
  3. Once the region controller is running, deploy a Pod with the rack controller and join it to the region controller.
  4. Initialize the configuration of MaaS and start the image sync
  5. Export an API key into a Kubernetes secret so other Pods can access the API if needed