This is a difference between different versions of parted and since we
since we are screen scraping this is a clean solution.
backport: liberty
Change-Id: I4c441bb16cfba7f405d2a41233d0129e61715c62
Closes-Bug: #1504920
Vagrantfile is in dev/vagrant directory on repository,
so to reach the main directory, it should sync "../.."
path instead of "..".
Change-Id: I7d142c8239423f5de52de5602a732770bb1d7c6c
Closes-Bug: #1504426
For Swift, the *.json.j2 templates are looking under
{{ container_config_directory }} whereas they need to be looking in the
common location for swift which is /var/lib/kolla/swift
Change-Id: I6f0dcbc9a705b36d1d98275ba9ebc56404fe882d
backport: liberty
Closes-Bug: #1504210
THe top level dev directory is now used to store the heat and
vagrant development environments.
backport: liberty
TrivialFix
Change-Id: Ib0922b90eacaa8518aee09cdeb46f4ac0437e015
Several people over the liberty cycle committed to maintaining
compose, but it was never completed. Rather than carry compose
in our repoistory until the end of time in a broken state I propose
removing it. If someone comes along and wants to resseruct the code
and make it functional in the future, I'd be 100% open to merge a
patch in the future which reintroduces this functionality. In the
meantime it is confusing to users which ask me on a daily basis if
compose is supported which I have to go into a 10 minute monologue
about why its in the repository.
Fortunately git contains full history so we can always revert this
change at a later time if someone wants to actually fixt his code
base up and make it useable in some way. I think the proper answer
is a seperate repoistory (kolla-compose) which contains any compose
related bits.
Please consider removing since nobody is using this code and its
dead.
TrivialFix
backport: liberty
Change-Id: I8b7c39b00d1967184d363af7db86d1ff8b5e725f
Reformat local registry section. And document that the Docker config need to
be modified when building images if using local registry.
Change-Id: I51c4df499d84c8ce2a2afc3787b2d609cc0f7d7e
In https://bugs.launchpad.net/kolla/+bug/1483667, oslo.messaging
was pinned to 2.2.0. This pin is no longer necessary as this bug
has been fixed upstream.
backport: liberty
TrivialFix
Change-Id: Ica9ae41876a754291d4c6ee1235f6e69a4213463
The dockerfiles for each of these containers were hacked to force
install the most recent version of the package, even though the newer
version had a lower version number. Delorean has fixed the issue by
bumping the epoch, so the hack is no longer required.
backport: liberty
Change-Id: I8d9c071d84e53280d3cadfceb9034bb96f64f3a3
Closes-bug: #1503785
Currently we seem to be experiencing races between containers.
If another containers tries to write to rsyslog before rsyslog container
is up and running it will create /dev/log as directory,
and that will prevent rsyslog from starting.
Change-Id: I88ac27693d12e605f95e3a945fc98783516d7933
Closes-Bug: #1501694
backport: liberty
Several packages are not installed from RPM packages which are
required in order for CentOS from source to operate correctly.
This looked like sudo was failing to execute, but it was because
the dnsmasq binary was not found.
backport: liberty
Change-Id: If23cfbacd55d9089ffec442399ee0151adea923f
Closes-Bug: #1503412
Make openstack-base optimized for from source builds for RPM based
distributions.
backport: liberty
Change-Id: I5f1056ebc09fd55cd5d46da7a09331e38940d888
Implements: blueprint openstack-common-container
The which tool is installed in the base image now and this extra
install is duplicated and has no effect.
backport:liberty
TrivialFix
Change-Id: I70c3edb11f5c847063b6e4ab4f9de7184356ce57
The base image contains -d 10 in a yum command which prints unhelpful
debug output for one of the yum commands. Remove the extranous debug
output.
backport: liberty
TrivialFix
This patch is a trivial fix and is a test to set boundaries on what
a trivial fix looks like that doesn't require a bug tracker entry. If
reviewers feel a trivial fix isn't documented properly by this commit
message, please weigh in, as this is a slight suggested change to our
policy as first institued by the Magnum community and brought to my
attention by Jeff Peeler. Hopefully this compromise won't be abused :)
Change-Id: I57f00978d0baaefd73592f4ad6a655e663d83478
Our current version based upon conversations with TTX was
0.1.0. It appears now that the full API is nearly stable. It is
stable enough to call our first Liberty release 1.0.0.
The API consists of the following data:
The locations of config files passed to the container
The environment variables expected by the container
The JSON encoded file containing the copy and cmd operations
Each container in current master follows the same sytnax and
style for all of the implementations of every container that
atleast has been Ansibilized.
backport: liberty
Change-Id: I2064689ca6fd9f332ad26624e1b93f6aaa08e79b
Closes-Bug: #1503494
Pin rabbitmq to 3.5.5 for RPM platforms. This version is the latest
and sparkly with lots of bug fixes. Tested multi-node HA and everything
seems solid in comparison to the 3.3.z releases used previously.
backport: liberty
Change-Id: I53bf70175fd12ded132141aa499c73919a932cdf
Closes-Bug: #1503280
The bridge parameters should be net.bridge.* according to install
documentation at docs.openstack.org.
Change-Id: Ib29dd462e01f26e3fec48f0730ed322f2704cd8a
Closes-Bug: #1503416
The brace in string variable will not be expanded in some case.
Put conatiner name into array.
Change-Id: I2fb16e7352bd579f207efce0fb9b2565a1e7236d
Closes-Bug: #1502467
