The user variable was incorrectly in passwords.yml
The naming was inconsistent, it should be prefixed with manila_*
Removed old unused variable
TrivialFix
Change-Id: I182797fcc6d62d35174403d78d71c8ad7ddcbc43
These options have all be deprecated/removed. This switches all
options to thier proper mitaka values.
TrivialFix
Change-Id: Ica8d5ea0d48da01ee11672a32890431acd6a306d
The in-process cache for keystone tokens has been deprecated due to
"incosistent results and high memory usage" with the expectation we
switch to memcached_servers if we want to stay performant.
Add memcache_servers [cache] section to the appropriate servers as the
[DEFAULT]\memcache_servers options was deprecated.
TrivialFix
Related-Id: Ied2b88c8cefe5655a88d0c2f334de04e588fa75a
Change-Id: Ic971bdddc0be3338b15924f7cc0f97d4a3ad2440
Rabbitmq can't work with IPs, so we need to make sure that all
rabbit cluster hosts can resolve each others hostnames. We
should also require that in docs.
DocImpact
Closes-Bug: #1559158
Change-Id: I2418187138988d21da3dc3624e9cdbda891d4894
Thanks to the related-id commit we can do nova->glance snapshots. This
updates the keyrings to reflect that change.
Change-Id: I02f083aec0255e9d681bd225a11ead6f5a379366
Related-Id: If13d25b6c94e247d2505583b524ae3af9c34b5dc
This matches the current default for nova.conf. Use unmap/discard if
t is enabled on the hypervisor. This option is new for mitaka.
TrivialFix
Change-Id: Id94c05e2ec8a65c75ec82afcd4150390f8b87ee2
This type of per node configuration is required to support things like
availability zones for nova. As always, if this file doesnt exist it
doesnt get used so this change is safe.
TrivialFix
Change-Id: Iff8172af522c2c96e5f2c173b24a5dfd4d522ed2
This change will enable to lvm commands running in a container
communicate with udev process running on a host.
Partially-Implements: blueprint iscsi-lvm2-docker
Change-Id: If780710bb81adaee44ce0d291e22ce91ec6436aa
This playbook only matters for multinode since AIO can recover from
power outage without additional configuration.
DocImpact
Implements: blueprint mariadb-lights-out
Change-Id: I903c3bcd069af39814bcabcef37684b1f043391f
Minor versions of mariadb upgrade do not require full cluster stop.
Full cluster stop will need to be address during the move to 10.1 at
some time in the future.
Change-Id: Ia048a3fd4d79921f827f3b88c623d26db506bfc3
Partially-Implements: blueprint upgrade-kolla
Implements: blueprint upgrade-mariadb
This change is a "futureproofing" thing. It has already been discussed
that libvirt should not be a child of nova and should be removed out
to the base docker directory (just like openvswitch isn't a child of
neutron). That is not going to happen this cycle but when it does we
can't change the name of the volume. This updates the volumes to the
proper name of libvirtd. This is in contrast with the libvirtlogd
volume that will be needed in newton due to libvirt 1.3
Of note, the container can remain named nova_libvirt since we can
change that on the fly later without breaking instances.
This wont break liberty as named_volumes are not backported yet.
TrivialFix
Change-Id: I16cf9e1b1dbba9b5a9f5cc883494580e276d4f72
This will give more info to the user about the specific values being
set and allows us to grow this list easier.
TrivialFix
Change-Id: Iaf22bf2c9f4ab294bec0cca17699d461852109ac
TASK: [manila | Copying over manila.conf] fails while
deploying Manila ubuntu binary image with the following
error.
UnicodeEncodeError: 'ascii' codec can't encode character
u'\u2018' in position 313: ordinal not in range(128)
The reason was use of non-ascii character <``> in manila.conf.j2
which is replaced by <''> in this patch to fix the issue.
Change-Id: Ic26a5829ed700179997c7c06836fd581a67a6777
The rabbitmq-server package is upgraded to 3.5.7 in cloud-archive
so we update centos to match
The xen-utils package now needs an explict version, xen-utils-4.6 is
what is provided by cloud-archive mitaka
Libvirt 1.3 is in the ubuntu cloud-archive. This has a new daemon for
logging that needs further implementation in newton. For now, it has
been disabled within the qemu.conf
Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
TrivialFix
Change-Id: I84217824817c484b6800a64cbd7767b127a3098e
Without this option the vip will always bounce to the highest priority
node that is up. So if you reboot the highest priority node the vip
will fail to the second highest. When the highest priority node
recovers it will claim the vip again leaving you will two fail overs
rather than one.
TrivialFix
Change-Id: I4a3c6c10eee391cdbdd80c44a71a9fafd1069944
haproxy 1.6+ does not allow the formatting that was used for stats
listener. We need to adjust it to the correct syntax
TrivialFix
Change-Id: I5f0111c756d40a0cf7385e6963ebbb57adb36b35
