Commit Graph

5 Commits

Author SHA1 Message Date
James E. Blair ab24e2a81f Invoke run_k8s_ansible from its directory
It relies on loading ansible.cfg from the cwd to zero out the
inventory.

Change-Id: I43a8f12eda034d132b6752df29e7b041025f4340
2019-05-07 16:03:59 -07:00
Ian Wienand 6df8caa421 Change to parent dir in run_k8s_ansible.sh
This is calling tools/cloud-to-env.py without a full path, which fails
when it's called from the run_all_script which hasn't cd'd to
/opt/system-config.  Use the old "cd to my parent dir" at the start of
the script.

Change-Id: I54a97c6942edd8a047ac679f6b0b08f0e5595f1f
2019-03-15 09:51:40 +11:00
Monty Taylor 0c4a981f73 Stop running k8s-on-openstack nested
The current code runs k8s-on-openstack's ansible in an ansible
task. This makes debugging failures especially difficult.

Instead, move the prep task to update-system-config, which will
ensure the repo is cloned, and move the post task to its own
playbook. The cinder storage class k8s action can be removed from
this completely as it's handled in the rook playbook.

Then just run the k8s-on-openstack playbook as usual, but without
the cd first so that our normal ansible.cfg works.

Change-Id: I6015e58daa940914d46602a2cb64ecac5d59fa2e
2019-02-12 18:17:46 +00:00
Monty Taylor 3703ddf4a0 Increase number of k8s nodes to 4
Change-Id: I08bc14a854e8b692abe89670c1b3661a76b1a27a
2019-02-05 18:51:38 +00:00
Monty Taylor 9cac3c6b63 Run k8s-on-openstack to manage k8s control plane
The k8s-on-openstack project produces an opinionated kubernetes
that is correctly set up to be integrated with OpenStack. All of the
patches we've submitted to update it for our environment have been
landed upstream, so just consume it directly.

It's possible we might want to take a more hands-on forky approach in
the future, but for now it seems fairly stable.

Change-Id: I4ff605b6a947ab9b9f3d0a73852dde74c705979f
2019-02-05 18:50:31 +00:00