summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2016-02-03Fix some words spellingsvenkatamahesh7-7/+7
Trivial Fix Change-Id: Ic14778bb4e894490a3b6af9471ba01ab4da94601
2016-02-03Playbook for horizon upgradeJeffrey Zhang1-0/+4
Partially-Implements: blueprint upgrade-kolla Implements: blueprint upgrade-horizon Change-Id: I11f11a684becd43cb137fe2c5694ca7e887b38ba
2016-02-02Create nova-api databaseSamYaple5-0/+44
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
2016-02-02Merge "Fix Swift for multinode P+ACO deployment"Jenkins6-8/+12
2016-02-02Merge "Add an ansible role for mongodb"Jenkins19-3/+183
2016-02-02Rename kolla_ansible to kolla_toolboxSamYaple39-60/+60
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
2016-02-02Fix manila permsSamYaple1-2/+2
Change-Id: I5b40de377ac0323d3253f58b49318d57da347d11 Parially-Implements: blueprint enable-manila-containers
2016-02-02Merge "Playbook for upgrade mistral"Jenkins3-16/+24
2016-02-02Merge "Validate that all the containers are started"Jenkins1-8/+12
2016-02-02Remove unexisting data_files in setup.cfgÉric Lemoine1-2/+0
TrivialFix Change-Id: Ib5621f21d51f05acd851801134a97bac283b6c74
2016-02-02Merge "Playbook for upgrade memcached"Jenkins1-0/+4
2016-02-02Merge "Playbook for upgrade murano"Jenkins3-16/+24
2016-02-02Merge "fix miss rabbitmq config when hostname include special character"Jenkins1-2/+2
2016-02-02Playbook for upgrade mistralAllen Gao3-16/+24
Change-Id: Iaec726be146fd93bf1437fcd859081858b1d541d Partially-Implements: blueprint upgrade-kolla Implements: blueprint upgrade-mistral
2016-02-02Fix wrong behavior when the source is a directoryAntoine Roux1-1/+1
TrivialFix Change-Id: Ie723fb35f15be0a500b428b2b58e6b4c5321df0c
2016-02-02Validate that all the containers are startedJeffrey Zhang1-8/+12
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
2016-02-02fix miss rabbitmq config when hostname include special characterweiyu1-2/+2
Change-Id: I46db4d3547b120d1ccd87a48e31b699bdd1aa1a0 Closes-Bug: #1540234
2016-02-02Playbook for upgrade muranoAllen Gao3-16/+24
Change-Id: Iffb12c8e22724ba779e4ce80204710513875e725 Partially-Implements: blueprint upgrade-kolla Implements: blueprint upgrade-murano
2016-02-02Playbook for upgrade memcachedAllen Gao1-0/+4
Change-Id: I98616610a2d665ba20085d3550975ea8093653fc Partially-Implements: blueprint upgrade-kolla Implements: blueprint upgrade-memcached
2016-02-02Fix Swift for multinode P+ACO deploymentQiu Yu6-8/+12
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
2016-02-01Merge "Removed unused containers from gate build"Jenkins1-5/+4
2016-02-01Merge "Rework log output if pull fails"Jenkins1-7/+19
2016-02-01Merge "Convert rabbitmq to named volume"Jenkins2-18/+11
2016-02-01Merge "Fix missing swift proxy server image in pull action"Jenkins1-0/+7
2016-01-29Make kolla-toolbox container build on CentOS binSteven Dake1-1/+2
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
2016-01-30Fix missing swift proxy server image in pull actionQiu Yu1-0/+7
Add back missing swift proxy server image which was removed in Swift shared image change. TrivialFix Change-Id: Icf13d4a1550192f73e266a6c6aa74f604ee4e77a
2016-01-29Removed unused containers from gate buildSamYaple1-5/+4
TrivialFix Change-Id: I7ccbecddc55b26d252b92faccec94676315c3eec
2016-01-29Convert rabbitmq to named volumeSamYaple2-18/+11
Change-Id: I81413ffcaa4efb881d13fef62823d60b676e871d Implements: blueprint docker-named-volumes
2016-01-30Detect and use physical disks for Swift storageQiu Yu3-62/+95
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
2016-01-29Merge "Update cleanup-containers to remove manila containers"Jenkins1-0/+1
2016-01-29Merge "Update ceph-mon keyrings"Jenkins2-0/+8
2016-01-29Merge "Update all bootstraps to use Label"Jenkins14-3/+37
2016-01-29Merge "Add labels to docker module"Jenkins1-0/+23
2016-01-29Merge "Cleanup mariadb and make compatiable with mesos"Jenkins4-18/+22
2016-01-29Merge "Re-generate the compressed css and js on every horizon start"Jenkins2-4/+14
2016-01-29Logging with Heka specÉric Lemoine2-0/+927
This adds a spec for using Heka as Kolla's log processing tool. Change-Id: Ia786601f3f0b298c120950e2abdd6d1b71e32ba5
2016-01-29Merge "Enable find_disks module to match by filesystem label"Jenkins1-17/+59
2016-01-29Merge "Use rdo magnum instead of sdake's copr for magnum"Jenkins1-15/+2
2016-01-28Use rdo magnum instead of sdake's copr for magnumVikas Jain1-15/+2
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
2016-01-28Update all bootstraps to use LabelSamYaple14-3/+37
Add bootstrap label to all bootstrap containers to ensure that when the a new container is launched a difference is seen between it and the bootstrap container since we cannot rely on ENV variables for this. This only affects mariadb at this stage, but it is needed to ensure rabbitmq works when we switch to named volumes. Change-Id: Ia022af26212d2e5445c06149848831037a508407 Closes-Bug: #1538136
2016-01-28Add labels to docker moduleSamYaple1-0/+23
With the switch to named volumes we run into a few situations where we cannot bootstrap volumes like we used to. This labels param will fix that as the next patchset shows. Change-Id: Ia93166dd204c5c0d1a0eb9ffeb6d0aba486e269a Partially-Implements: blueprint docker-named-volumes
2016-01-28Cleanup mariadb and make compatiable with mesosSamYaple4-18/+22
There is no reason to have a hostname-unique pidfile in the container as we currently have. This posed problems with kolla-mesos reusing the same script. Since there is no reason for this pidfile to be configurable in path _at_ _all_, we hardcode the path. Additionally, we adjust the file perm change to only update the perms on the folder if it is not already properly set. This also incorperates a kolla-ansible file in the bootstrap process which follows our other container techniques of using the idempotent creation of a volume in the bootstrap process (see nova) TrivialFix Related-Bug: #1538136 Change-Id: I2380529fc7146a9603145cdc31e649cb8841f7dd
2016-01-28Update cleanup-containers to remove manila containersMauricio Lima1-0/+1
Change-Id: Ie7a53396b03ce4e472b5e810a02ccdfc9bd8aacd Partially-Implements: blueprint enable-manila-containers
2016-01-28Update ceph-mon keyringsSamYaple2-0/+8
Since the fetch script fetched _all_ keyrings from the ceph-mon container, the ceph-mon container must contain all keyrings. This setup works AIO but was broken on multinode because the ceph-mon container did not have the radosgw keyring. This issue affects every multinode install regardless of using the radosgw or not. TrivialFix Change-Id: Ie416de1a5275862da6d77ef0dd174e85e499fc0f
2016-01-29Remove the machine-id which cause nova-compute raise exceptionJeffrey Zhang1-1/+2
Change-Id: I3cfb239e6f99e7079b2781b06550fa627fcb8998 Closes-Bug: #1539064
2016-01-28Use trusts in heat.confMichal Rostecki2-4/+18
Change-Id: Ie91b3498e9f9d0d74a502ba6945db531ef967516 Closes-Bug: #1492736
2016-01-28Merge "Add the missed stub upgrade.yml"Jenkins1-0/+1
2016-01-28Merge "Fix swift build issue"Jenkins1-0/+13
2016-01-28Merge "Remove the libvirt socket"Jenkins1-7/+2
2016-01-28Fix swift build issueSamYaple1-0/+13
Swift updates and new deps are needed, here is one Closes-Bug: #1538377 Change-Id: Ibb890c73e462113c5aa29ab12637a9115bb51240
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-08 05:33:20 +0000