Currently, if ceilometer is enabled with glance then the
rabbitmq is non-functional, causing various glance failures
including image upload.
This is caused because:
The generated config fails to have a carriage return at the
end of the rabbit_host line, causing the following line to
be added to this entry.
rabbit_host is used rather than rabbit_hosts, where the
fromer expects a string, rather than the list that is
provided.
This also adds rabbit HA support, to be in-line with the
other services using rabbitmq.
This is resolved, by pushing the rabbit_hosts entry to be
last, meaning that a carriage return is not required.
Change-Id: I89f26d542565b98025fd9b84fc4beb5cbed364e5
Closes-Bug: 1596244
Signed-off-by: Dave Walker (Daviey) <email@daviey.com>
VM instance state (e.g., instance.xml) should be persistent
regardless of nova-libvirt container.
Change-Id: I4463d0634db2aaefde7dc2c45a144e920d9cb1ac
Closes-Bug: #1569828
This introduces a new configuration parameter neutron_enable_qos to
be able to enable the Neutron QoS service plugin.
More details about the Neutron QoS service plugin are available at:
http://docs.openstack.org/liberty/networking-guide/adv-config-qos.html
Change-Id: I8525bf4dce5f1e225f72a4e1c3760b64a36b17f6
Closes-bug: #1593183
Implements: bp netowrking-qos
When kolla_internal_vip_address didn't belong to the same network as
network_interface, the prechecks would spit out an ugly error:
Unexpected templating type error occurred on [snip]:
argument of type 'NoneType' is not iterable"
This commit fixes the check to execute properly.
Change-Id: I24a066c212c78e105a923525b131724736ac74b6
The Nova EC2 API is disabled by default, the default value
of the enabled_apis parameter in nova.conf is "osapi_compute, metadata"
The EC2 API is marked as deprecated and will be removed from Nova in
the future.
Change-Id: I6b9d66017e066cde5749be45b367194d2192ead3
Closes-bug: #1586605
Upgrade the kernel version is not acceptable for the server in most
of case. I do not see the issue when using ubuntu 14.04 default
kernel with docker aufs storage driver.
Even if there is some wrong in the aufs driver, we could recommend
the user to use other drivers, like lvm, brtfs or even overlay driver.
This reverts commit 833c1269c7941498787d49ce879be6c283728407.
Change-Id: I6ee71ecd1ca64777b874bfcc342162622643b89c
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
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
