The verbose parameter is deprecated and should not be used. This
solves the following issue:
Option "verbose" from group "DEFAULT" is deprecated for removal.
Its value may be silently ignored in the future
TrivialFix
Change-Id: Ifb04c3f396a96b6917637af3a90a3ddb1599e29d
I just thought I'd dash off a quick patch and change the underscore
to a dash.
Change-Id: Ib34cfc8039de01be7e37176648482f9815ac3848
Closes-Bug: #1589734
This patch enable wsrep_notify_cmd to rename haproxy user in haproxy_blocked
when the node is not ready to serve and restore it when ready.
Change-Id: I4f49960d7ff2fa689d6ea730b2574f16f083edc1
Closes-Bug: 1578752
Closes-Bug: 1587752
Generic, cinder, nova and neutron session aren't needed in
manila-api and manila-scheduler. It's only needed in manila-share container.
Closes-Bug: #1576823
Change-Id: Iad3054e00621b5fe7273213e1d85b54bcca2ba4a
The traceback is logged also and will be helpful when the
library failed. We can get which line is failed from the log.
TrivialFix
Change-Id: Ia417232007e2f34c83d2e7cad6ed08dee49ce836
Ansible 2.1.0 has lots of change and the plugin is not compatible
between 2.0.0 and 2.1.0. This change fix the gap.
* fix the signature change for _make_tmp_path in ansible 2.1.0
* fix the common_options in the kolla_docker.py
Change-Id: I05f5f05581c8bd625cd868fa0db549d0c60a7043
Closes-Bug: #1586018
Previously, kolla did not support neutron lbaas functionality.
Only Lbaasv2 is supported in Mitaka. Additional information can
be found here:
http://docs.openstack.org/mitaka/networking-guide/adv-config-lbaas.html
Magnum uses Neutron Lbaas to provide high availability to COE API
and Etcd endpoints within a bay. Therefore, Neutron Lbaas is required
for Kolla to support Magnum.
Co-Authored-By: Serguei Bezverkhi <sbezverk@cisco.com>
Partial-Bug: #1551992
Change-Id: I05360b7c447c601fcb3c2b6b2a913ef5cc0f3a1b
This will solve the following issue when running the
kolla-ansible cleanup command:
[WARNING]: Consider using file module with state=absent rather
than running rm
Closes-bug: #1586406
Change-Id: I366b6f27e697b24c6c54882c08afe4048803b4e8
This will resolve the following deprecation warning:
Using bare variables is deprecated. Update your playbooks so
that the environment value uses the full variable syntax. This
feature will be removed in a future release.
Partial-bug: #1586404
Change-Id: I9086d3f9e7904836e72e6df2fefaa084e5229f7e
All the images follow the same naming schema where the container
name is part of the ansible variable name. Currently, the
kolla_toolbox container is named ansible_image_full. Change
this to match what the container name is.
Could impact operators who are specifying ansible_image_full
in globals.yml.
TrivialFix
Change-Id: I9f0cbe4bd69ce17489310a1f5734a254e6ebe27b
An operator may want to specify the location of custom config
files so that kolla can detect their location and merge
them with the default configs generated.
Partially implements: blueprint multi-project-config
Change-Id: Ibfb38d07a36dfa7fe25381adc34cc1d3cbe7d1e1
Give outside projects the ability to consume kolla-ansible as a
config generation mechanism by allowing for the developer to define
a directory structure within /etc/kolla that fits a project's needs.
For example, kolla-kubernetes does not define configuration in terms
of serivces, but in terms of pods (groups of services).
Partially implements: blueprint multi-project-config
Change-Id: If08443aefcaf5fa5604b243b39a6a2d54e431cff
Since Mitaka, Neutron does the right job to calculate and advertise
correct MTU to instances, out of the box [1].
[1] https://review.openstack.org/#/c/302165/
TrivialFix
Change-Id: I71a6dc5b56c2c1fb9db757df77a56feababdc039
This change makes each step of the kolla deployment aware
of the port database was configured to listen on.
It defaults mariadb_port to database_port.
Change-Id: I8e85d5732015afc0a5481cb33e0b629fdfa84a1b
Closes-Bug: #1576151
DocImpact