| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
The install type is converted in kolla-build, so it will never
fail in dockerfile, move the check to kolla-build just above
the install type converting.
TrivialFix
Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Change-Id: I1500d3b47e909f94ea9f68c5245297733f63a70b
|
|
|
|
|
|
TrivialFix
Change-Id: I1c0a80f7781aa196023795a6381443d6835d534c
|
|
TrivialFix
Change-Id: I73f780d72fc30ff3adf3e70ed03361dcb76b451d
|
|
Change-Id: I3afb8a29c4ae2369f29e0cc94d75ff8a3c42594b
Implements: blueprint custom-repos
|
|
|
|
|
|
Adding the necessary spaces.
TrivialFix
Change-Id: I3858ed1cb978bcf8aefd4a85f7c802607876b36e
|
|
Trivial Fix
Change-Id: Ic14778bb4e894490a3b6af9471ba01ab4da94601
|
|
Partially-Implements: blueprint upgrade-kolla
Implements: blueprint upgrade-horizon
Change-Id: I11f11a684becd43cb137fe2c5694ca7e887b38ba
|
|
This is a required patch.
Kilo introduced a nova-api database but didn't use it. [1]
Mitaka now uses it and has broken booting instances. [2]
[1] https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#OpenStack_Compute_.28Nova.29
[2] https://github.com/openstack/nova/blob/df0fca62cf5324f5b6eae0fed1f88c6c9ed61c71/releasenotes/notes/request-spec-api-db-b9cc6e0624d563c5.yaml
Change-Id: If0a7f4ba4937fab8d60f5236ca00db06faa768c7
Closes-Bug: #1540579
|
|
|
|
|
|
This change is needed for clarity. We have a kolla-ansible script.
We have a kolla-mesos repo. We plan to have a kolla-ansible repo.
Already we have had far too much confusion about whether we are
talking about the container or the project. Naming this kolla-toolbox
eliminates all of that confusion and its probably a bit more accurate
of a name too.
Closes-Bug: #1541053
Change-Id: I8fd1f49d5a22b36ede5b10f46b9fe02ddda9007e
|
|
Change-Id: I5b40de377ac0323d3253f58b49318d57da347d11
Parially-Implements: blueprint enable-manila-containers
|
|
|
|
|
|
TrivialFix
Change-Id: Ib5621f21d51f05acd851801134a97bac283b6c74
|
|
|
|
|
|
|
|
Change-Id: Iaec726be146fd93bf1437fcd859081858b1d541d
Partially-Implements: blueprint upgrade-kolla
Implements: blueprint upgrade-mistral
|
|
TrivialFix
Change-Id: Ie723fb35f15be0a500b428b2b58e6b4c5321df0c
|
|
Container maybe exit after deployed. But the print_failure
never runs if the kolla-ansible run success.
This PS checks all the containers status after deploy and
failed the test if the container status is exited
TrivialFix
Change-Id: Ia461b280855eda500e143ee1d6cfd5f215eaf6fe
|
|
Change-Id: I46db4d3547b120d1ccd87a48e31b699bdd1aa1a0
Closes-Bug: #1540234
|
|
Change-Id: Iffb12c8e22724ba779e4ce80204710513875e725
Partially-Implements: blueprint upgrade-kolla
Implements: blueprint upgrade-murano
|
|
Change-Id: I98616610a2d665ba20085d3550975ea8093653fc
Partially-Implements: blueprint upgrade-kolla
Implements: blueprint upgrade-memcached
|
|
Current Swift playbook is based on the preassumption of AIO setup.
However, if one goes with default multinode setup
(ansible/inventory/multinode), it follows the P + ACO deployment model,
which proxy-server runs on controller nodes where ACO
(account/container/object services) run on storage nodes.
It will break because swift proxy-server no longer has access (it
shouldn't have) to /srv/node path. This change ensure disk mounting part
only happens on storage node. It also moves chown from proxy-server
Dockerfile to rsyncd because no matter with PACO, P+ACO or P+A+C+O
model, rsyncd is always running on each storage node.
Change-Id: I3aa20454902caa9c84d3901bb91e4e4c93ac5f34
Partially-Implements: blueprint swift-physical-disk
Closes-Bug: #1537544
|
|
|
|
|
|
|
|
|
|
Ansible installs pytz from pip which is newer then then pytz in
RDO repositories. As part of this process, it removes pytz
which corrupts the python installation in some way. This causes
further pip usage to produce a backtrace causing the kolla-toolbox
container not to build.
Mixing pip and RPM is not good.
Change-Id: I413468641bad5476cfcba61cb0e2189c31f3d682
Closes-Bug: #1545215
|
|
Add back missing swift proxy server image which was removed in Swift
shared image change.
TrivialFix
Change-Id: Icf13d4a1550192f73e266a6c6aa74f604ee4e77a
|
|
TrivialFix
Change-Id: I7ccbecddc55b26d252b92faccec94676315c3eec
|
|
Change-Id: I81413ffcaa4efb881d13fef62823d60b676e871d
Implements: blueprint docker-named-volumes
|
|
This change let Swift detect and use physical disk for storage. The
old named volume for storage isn't really useful for any serious setup.
Also updated swift-guide.rst accordingly.
Change-Id: I4f577b7b69d8bcd8b3961500946241c65a16db22
Partially-Implements: blueprint swift-physical-disk
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This adds a spec for using Heka as Kolla's log processing tool.
Change-Id: Ia786601f3f0b298c120950e2abdd6d1b71e32ba5
|
|
|
|
|
|
Steve is tired of maintaining a copr for Magnum. People bug him
all the time to update the rpm for RDO. The RDO community
has offered to take on the maintainance of the Magnum RPM. As this
RPM won't be in current-passed-ci for some time so it needs
to be pulled from current repo for the foreseeable future,
possibly nearing the release of Mitaka.
Change-Id: I9cfb02ab828251ef5bf40ca236f18b5f0f715e34
Closes-Bug: #1539325
|