airship
/
maas
Code Issues Proposed changes
maas/charts/maas
History
Phil Sphicas d79b355188 MAAS chart: reduce syslog startup spam 
When the MAAS syslog pod starts, it polls continuously until the log
file exists, generating a message every 10 seconds. However, rsyslogd
won't create the file until it receives the first message, which could
take a while.

This change will create an empty file if none exists prior to starting
the rsyslogd service.

Previous comments indicate some concerns about a race condition, and it
is possible that there are some circumstances when the file may go away
and come back, so the polling loop is left in place.

Change-Id: Ic56faf718038c5d17ab9353399a94ec74e91f8d0
 		2019-11-17 06:22:29 +00:00
..
templates MAAS chart: reduce syslog startup spam 2019-11-17 06:22:29 +00:00
Chart.yaml (zuul) Basic zuul gates 2018-06-01 11:57:45 -05:00
README.rst Move MaaS chart into maas repo 2017-10-25 14:02:38 -05:00
requirements.yaml Move MaaS chart into maas repo 2017-10-25 14:02:38 -05:00
values.yaml Merge "Allow to configure service network policy" 2019-09-27 10:29:27 +00:00

README.rst

openstack-helm-addons/maas

This chart installs a working version of MaaS on kubernetes.

Quickstart ~~~~~~~~~

This chart requires a postgresql instance to be running.

To install postgresql:

helm install postgresql --namespace=maas

Note: Postgresql may take a short time to reach the ‘Running’ state. Verify that postgresql is running:

# kubectl get pods -n maas
NAME                         READY     STATUS        RESTARTS   AGE
postgresql-0                 1/1       Running       0          1m

To deploy your MaaS chart:

helm install maas --namespace=maas

To verify the helm deployment was successful:

# helm ls
NAME            REVISION        UPDATED                         STATUS          CHART
opining-mule    1               Mon Feb 13 22:20:08 2017        DEPLOYED        maas-0.1.0
sweet-manatee   1               Mon Feb 13 21:57:41 2017        DEPLOYED        postgresql-0.1.0

To check that all resources are working as intended:

# kubectl get all --namespace=maas
NAME                            READY     STATUS    RESTARTS   AGE
po/maas-rack-3238195061-tn5fv   1/1       Running   0          11m
po/maas-region-0                1/1       Running   0          11m
po/postgresql-0                 1/1       Running   0          34m

NAME                 CLUSTER-IP       EXTERNAL-IP   PORT(S)           AGE
svc/maas-region-ui   10.105.136.244   <none>        80/TCP,8000/TCP   11m
svc/postgresql       10.107.159.38    <none>        5432/TCP          34m

NAME                       DESIRED   CURRENT   AGE
statefulsets/maas-region   1         1         11m
statefulsets/postgresql    1         1         34m

NAME                           DESIRED   SUCCESSFUL   AGE
jobs/region-import-resources   1         1            11m

NAME               DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deploy/maas-rack   1         1         1            1           11m

NAME                      DESIRED   CURRENT   READY     AGE
rs/maas-rack-3238195061   1         1         1         11m