Added centos, ubuntu, oraclelinux.
Not added other base distros are not
well maintained currently.
Change-Id: Icb1c12dde2ff005068f1b0f36693049f9ea30f52
Closes-Bug:#1569265
new cleanup-host script removes kolla-build.conf
in /etc/kolla directory which contains the build
configuration for building images.
This should be preserved.
Change-Id: I20fbf3f8a2400a5e048ba55beb0c8e1ec849d8a3
Related-Bug:#1561055
Due to lack of /var/cache/swift directory, swift services
are unable to access /var/cache/swift/container.recon file.
Closes-Bug: 1569182
Change-Id: Ifc4763d40256e43f51728e1dd4b3986c4f0ba0fc
neutron-plugin-linuxbridge and neutron-plugin-openvswitch package
is useless and removed in Mitaka on Ubuntu
Change-Id: Ia156d58410198af969f579cd5e7461c31ea63408
Closes-Bug: #1568281
Updates to ensure commands run in the swift containers
are done as the 'swift' user rather than root.
Change-Id: I8c5a12e24b9940200241dbe09d6bde8f1cc1cf05
Closes-Bug: #1553895
Co-Authored-By: Serguei Bezverkhi <sbezverk@cisco.com>
As suggested it was created the variable KOLLA_SERVICE_NAME to identify
the container service name through PS1 shell variable.
This method it was previously discussed in IRC.
https://goo.gl/k7AdEg
The other option it was usage hostname param in kolla_docker, but
currently docker does not support it due this issue:
https://github.com/docker/compose/issues/2460
The final result is like this:
$ docker exec -it heka /bin/bash
(heka)[heka@kolla-control /]$
$ docker exec -it mariadb /bin/bash
(mariadb)[mysql@kolla-control /]$
More details can be accessed through this link
http://paste.openstack.org/show/493689/
Closes-Bug: #1557454
Change-Id: I6aab8d640a8ebb17baa9d6d4f1edd6e331674713
In the gate, it is possible for /etc/hostname to not have a valid
SELinux security conext. So, reset them to default before we update
the hostname to avoid:
TASK: [Assign hostname]
failed: [node1] => {"failed": true}
msg: Command failed rc=1, out=, err=Could not set property: Access
denied
Closes-Bug: #1568047
Change-Id: Ie30c8437b310d1ea5bc75307375c255131dfe934
Needed-By: I2ff5fbb315832b8cf07c93d0dd0cdaacd958631e
Make sure that all the sevices will attempt to
connect to the database an infinite about of times.
If the database ever disappears for some reason we
want the services to try and reconnect more than just
10 times.
Closes-bug: #1505636
Change-Id: I77abbf72ce5bfd68faa451bb9a72bd2544963f4b
The comment was confusing and not explaining what the real issue is
when binding erlang to an IPv4 address.
Change-Id: I819ea137fa37c0b2711efb1e7cb1e518ae26b9ab
Related-Bug: #1562701
Heat development environments don't work at all.
As such document this so folks avoid them unless they want to
work on making them better.
Change-Id: Ibe3296660d30ccc24213c272ef379e6d3e2c21f2
Please refer to the Closes-Bug identifier for detailed information
pertaining to this issue.
Closes-Bug: #1562701
Change-Id: I77563930e14e11ea48e7edfef0bff80002279381
This fix adds a check of Rabbitmq's image version during the upgrade.
The container gets restarted only when the image version is different.
Change-Id: Ie038845c0c8fff1ac51b7cbf21e1b593229c2c0e
Closes-Bug: #1558832
This partially implements iscsi and lvm2 support for cinder
in Kolla. Adds iscsid and tgtd docker containers.
Change-Id: I7fb48c954e578772b90a2aa619c8bcfa990b3ae8
Partially-Implements: blueprint iscsi-lvm2-docker
Kolla deployment creates /etc/kolla folder on a target host
with multiple configuration files. In some scenarios,
the presence of these files prevent successful deployment
of certain services especially when their configuration parameters
have been changed on the deployment host.
Change-Id: Iefd544b50fc90b7f00d6e137bc14ab4807ef7c0f
Closes-Bug: #1561055
