Moves templates and template_definitions to the new
directory structure.
Change-Id: I42e4d2bd056f3d8082ef51ef599d917f2fe82960
Paritially-Implements: blueprint bay-drivers
Moved all the swarm templates and template_definition code
to the magnum/drivers folder.
Moved base template_definition classes to drivers/common
folder
Change-Id: Ieff57f0f47835c35d9f17c3d7d1b7e6a40907462
Partially-Implements: blueprint bay-drivers
Co-Authored-by: Spyros Trigazis <strigazi@gmail.com>
Initialization of variables: KUBE_PROTOCOL and KUBE_CONFIG is
done inside if/else for better readability and maintainability.
Change-Id: I37dfe57cc1328f1531233d11667a020bb3e0de5b
Partial-Bug: #1500850
Bay_create_timeout default is 0 and means that magnum create bay
without timeout. But heat create stack with timeout absolutely.
So it is impossible to create bay without timeout. And I had send
a patch which allow heat to create stack without timeout, but the
core of heat did not agree with it.
The patch is: https://review.openstack.org/#/c/334138/
Change-Id: Iebc9915dcf2894a2dbed912244a2c7c308b4d9d7
Closes-bug: #1590636
This section of the user guide describes how to create and
install a new bay driver. It includes the directory structure,
naming convention, required and optional components, and an
example.
The following will be added later:
- Sample driver
- Installation guide
Co-Authored-By: Murali Allada <murali.allada@rackspace.com>
Partially implements: blueprint user-guide
Change-Id: I68c997c959406f8eeb627683d73ae3818134ca87
Currently Magnum fails to delete certificates when barbican
cert manager is used. The code was copied from neutron-lbaas and
they have different usecase. In our case, certificate is managed by
Magnum not users, so we should delete certificates when deleting bay.
So this patch deletes all the certs related to a bay.
Change-Id: I5aab01641b9447153911680c5f68e5fe2c5a1409
Closes-bug: #1587033
Ironic template needs to specify fixed subnet name/ID.
And also user sometimes want to build his cluster on
his network which he built.
This patch adds fixed_subnet field to baymodel to specify
fixed subnet which bay will build on.
Change-Id: Ia21ad6e3e1472a0d078d08369ef62601034fcc17
Partial-Implements: blueprint magnum-baremetal-full-support
Added unit tests to test_types.py and test_magnum_service.py. Also, lines
containing abstract methods and 'pass' were being counted in the coverage
metrics, so those were added to the coveragerc.
Change-Id: I4af7005453b8f843b640661a972b3f1689ed7dd0
Partial-Bug: #1511667
Currently when we create a Bay, magnum is not enough to prevent bay creation failure,
due to Invalid discovery url can be referenced and there're no check toward it. We
should check the discovery url before creating bay, a 400 Invalid will be raised if
the discovery url is invalid:
1.the discovery url should be a correct url of etcd cluster.
2.the discovery url should have suitable cluster size.
Change-Id: Ib75f9f2aade18b16dd46035efe139311faf93e1e
Baymodel section
This section explains the parameters defined in the baymodel,
along with the values expected and the usage.
Partially implements: blueprint user-guide
Change-Id: I7cf1a2c9110b8ad777aac5e14d46c2323cbcc9f3
After the recent move [1] of diskimage-buidler elements
the permissions where changed making the files non-executable.
Make them executable again.
[1] I98051da7e9c8f7943fb5fe2109989d66b4b03736
Change-Id: I8dc819470c3089beb62a76364d4b6b4ba6e12d34
master_lb_enabled is a boolean field that determines if a bay's master
nodes should be load balanced. Defaults to False.
Change-Id: Icf8317432dec70c99c29a3af9edb0499bfd2439d
Partially-Implements: blueprint decouple-lbaas
1. Any existing docker storage driver configuration will not
allow us to apply ours from the heat templates. So, clean
existing configurations.
2. Remove docker storage driver configuration from
diskimage-builder elements.
3. Simplify, devicemapper configuration. It's unnecessary to
pass DOCKER_STORAGE_OPTIONS manually. docker-storage-setup does
it for us and the result is the same.
4. Improve comments in docker storage drivers configuration.
Change-Id: Ia413fe674421a70c68dc3930209970a16b5bfdc4
Add a parameter 'slaves_to_remove' that lists resources to be
removed on stack update. The value will be passed to
removal_policies of the 'mesos_slaves' resource group.
Change-Id: I18fcd0be962dd7414329dcfcad8bb4c79958ee9a
Partially-Implements: blueprint mesos-smart-bay-scale-down
