| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Partial-Bug: #1544545
Change-Id: I292bcaeacb080ff4c5ab6b42b7d899039d6b19c4
|
|
This commit fixes a bug in kolla_checker.py where the check_volume
function will raise "TypeError NoneType object is not iterable" if
there are no existing volumes.
TrivialFix
Change-Id: Ic57c339793fa532ed8db075ba1074db75106e36d
|
|
|
|
|
|
Also add missing cinder-backup ceph.conf info
TrivialFix
Change-Id: I2b2d85c2d34908a9b11198eb51b3cf359a06bdf7
|
|
|
|
|
|
The extend_start.sh script for rsyslog is removed as it is no longer
needed. Docker no longer binds to /dev/log or /run/kolla/log
Closes-Bug: #1544545
Change-Id: Ic0a323a26ee4e9e15baf4598285844a8a4955f23
|
|
This ensures mysql works through whatever the vip is
Change-Id: Iaeb17240b90ae2f0fef081b42d4ba140dcecd972
Closes-Bug: #1536633
|
|
|
|
To allow for TLS to protect the service endpoints, the protocol
in the URLs for the endpoints will be either http or https.
This patch removes the hardcoded values of http and replaces them
with variables that can be adjusted accordingly in future patches.
Change-Id: Ibca6f8aac09c65115d1ac9957410e7f81ac7671e
Partially-implements: blueprint ssl-kolla
|
|
Change-Id: I27ca0ea75f3d6a4371c91b3cb2c7a999ec90fbc4
|
|
|
|
Make sure extend_start.sh file run to completion
Change-Id: I45f6ab1c7d1b7a21ac92bb5f0e9d82a6c135cb5f
Closes-Bug: #1545287
|
|
Part of ELK stack. Includes Dockerfiles for both Centos and Ubuntu.
Change-Id: I9f76adf084cd4f68e29326112b76ffd02b5adada
Partially-implements: blueprint central-logging-service
|
|
|
|
|
|
Rabbitmq container has moved to named volume. No need pull rabbitmq-data
image.
TrivialFix
Change-Id: I83776ce626a7e398add0f07bd855924b8632b1ae
|
|
Change-Id: I42550c57222de4ad5556e95d40bb96528bc1d085
Closes-Bug: #1533942
|
|
TrivialFix
Co-Authored-By: Ryan Hallisey <rhallise@redhat.com>
Change-Id: Ia83f642d3817116e2ba99285efc12b583f07bbd1
|
|
We are using the mount propagation in Docker 1.10.
TrivialFix
Change-Id: Ic2ef1fbce9dba217eac75f3743cef7f6ac702b00
|
|
- sets privileged: true on cinder backup container
- adds /dev/mapper to cinder-backup mounts
- this change allows the cinder backup manager to access the
cinder-volumes lvm volume group via the kernel device mapper.
Change-Id: I252ee9cadb5f06c383ac9f48d0b1b16d83037a41
Closes-Bug: #1542574
|
|
*** Requires Docker 1.10 which is released ***
Documentation will be in the next patch. You must set the following
in your docker.service daemon control file for propogation to work:
[Service]
MountFlags=shared
======================================================================
Thanks to mount propagation in Docker 1.10 we can use thin containers
finally! This is extremely useful to operators since now they can
access the network namespaces from the hosts (outside the neutron
container). But additionally it allows us to implement the VPN agent
and other services easier.
Neutron containers and the neutron role are brought into the standards
of the new Kolla. Completely with drop-root and ansible formating
updates.
The ip_wrapper.py script was (thankfully) not needed so it has been
removed from the repo.
Partially-Implements: blueprint upgrade-neutron
Change-Id: Iaf5555283240457e1912459f397a6393d886fba1
|
|
Docker 1.10 has broken the gate and this patch will correct that
breakage.
The issue comes with rsyslog. Due to a commit in Docker 1.10 [1] we
must change the way we get the log socket for rsyslog. The /dev/
folder will no longer populate as we used it. So instead we simply
make a new socket in a path we control and share that to the correct
location in the containers.
Additionally, adjust the gate for new Docker daemon.
[1] https://github.com/docker/docker/pull/16639
Partially-Implements: blueprint kolla-upgrade
Change-Id: I881a2ecdf6d7b35991e1d38a3f3e60d022d6577f
|
|
Two patches merged that did not have teh correct name for
kolla_toolbox
TrivialFix
Change-Id: I09e230e29cff496247c32bf227715bfb7caa0a95
|
|
|
|
|
|
character""
|
|
Libvirt stores some information in /run at runtime that is needed to
automatically reestablish a connection with the VM when a new
container is created. Without this information a long (and manual)
process is needed to redefine the running vms and reattach to the
running qemu process.
This mountpoint was removed as "unneeded" in the past, but it does
exist in Liberty branch enabling a no-vm-downtime upgrade.
TrivialFix
Change-Id: I2eb31c602d8d17cbd6a8e405daf4123070794843
|
|
This change breaks ubuntu
This reverts commit 04992a3de0a181a658cae2561a3a1adce313bbf1.
Change-Id: I5e38d4c4a37ee90603ad04ab4b9d03298b6b2eb2
|
|
|
|
|
|
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: Iaec726be146fd93bf1437fcd859081858b1d541d
Partially-Implements: blueprint upgrade-kolla
Implements: blueprint upgrade-mistral
|
|
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
|
|
|
|
|
|
|
|
Add back missing swift proxy server image which was removed in Swift
shared image change.
TrivialFix
Change-Id: Icf13d4a1550192f73e266a6c6aa74f604ee4e77a
|