airship/maas
Code Issues Proposed changes
Kubernetes deployment artifacts for Canonical's MaaS.
193 Commits 1 Branch 0 Tags 3.5 MiB
Smarty 54.3%
Dockerfile 28.9%
Makefile 5.7%
Shell 5.6%
Python 5.5%
840b482373
Go to file
Phil Sphicas 840b482373 Fix Docker image build jobs 
Update the deb-docker path to fix the docker image build jobs.

Change-Id: Ia6f427af61827ffff15b6c9b246809fae37cc26a
2021-05-10 05:20:53 +00:00
.github Update Airship vulnerability link 2020-05-18 21:26:25 +00:00
charts/maas Allow additional preseed overrides 2021-02-12 06:29:10 +00:00
images Respect USE_PROXY=true for image builds 2020-06-11 15:22:09 +00:00
tools Fix Docker image build jobs 2021-05-10 05:20:53 +00:00
.gitignore Add .gitignore to repo 2018-08-22 21:24:27 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:52:21 +00:00
.zuul.yaml Added YAML file linting to maas 2020-01-16 16:36:53 +00:00
LICENSE Initial commit 2017-10-19 11:42:23 -05:00
Makefile (cache) Configurable Ubuntu release 2019-09-27 19:19:46 +00: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