aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-06-07Merge "Convert puppet and docker steps to ansible"Jenkins8-99/+83
2017-06-07Merge "Stop/disable l3 agent in docker service upgrade_tasks"Jenkins1-0/+5
2017-06-07Stop/disable l3 agent in docker service upgrade_tasksSteven Hardy1-0/+5
This service is missing the task to stop/disable the service on the host prior to it being started in a container. Change-Id: I33d70d32c3b55e1f2738441f57c74b007e7bd766 Closes-Bug: #1695017
2017-06-07Merge "Updated from global requirements"Jenkins1-1/+1
2017-06-07Merge "Fix upgrade tasks to use correct service name"Jenkins2-2/+2
2017-06-06Updated from global requirementsOpenStack Proposal Bot1-1/+1
Change-Id: I124d7f5bb0e662585a034668cd82ef1fa6db2fa1
2017-06-06Merge "Container-specific variants of scenarios 001-004"Jenkins5-4/+369
2017-06-06Merge "Fix CephPoolDefaultSize typo"Jenkins1-1/+1
2017-06-06Merge "Containerize HAProxy for the non-ha case"Jenkins2-0/+112
2017-06-06Fix upgrade tasks to use correct service namePradeep Kilambi2-2/+2
Change-Id: I149ca7cdd939ed7c1767a416bb9569ada163e820 Closes-bug: #1696089
2017-06-06Convert puppet and docker steps to ansibleSteven Hardy8-99/+83
Replace the multiple SoftwareDeployment resources with a common playbook that runs on all roles, consuming the configuration data written via the HostPrepAnsible tasks. This hopefully simplifies things, and will enable re-running the deploy steps for minor updates (we'll need some way to detect a container should be replaced, but that will be done via a follow-up patch). Change-Id: I674a4d9d2c77d1f6fbdb0996f6c9321848e32662
2017-06-06Merge "Update metric processing delay default"Jenkins2-1/+5
2017-06-06Containerize HAProxy for the non-ha caseDamien Ciabrini2-0/+112
This change implements an initial container for haproxy in the non-HA case (aka when the container is not spawn by pacemaker). We tested this using a stock kolla haproxy container image and we were able to get haproxy running on a container with net=host correctly. Change-Id: I90253412a5e2cd8e56e74cce3548064c06d022b1 Co-Authored-By: Michele Baldessari <michele@acksyn.org> Depends-on: I51c482b70731f15fee4025bbce14e46a49a49938 Closes-Bug: #1668936
2017-06-05Merge "Fix the constraints for THT params NeutronDpdkCoreList and HostCpusList"Jenkins1-4/+4
2017-06-05Merge "Example environment file to use Neutron BGPVPN driver with ODL"Jenkins1-0/+12
2017-06-05Merge "Remove nova placement config for compute service node on upgrade"Jenkins1-18/+0
2017-06-05Merge "Release 7.0.0.0b2"Jenkins1-1/+1
2017-06-05Release 7.0.0.0b2Emilien Macchi1-1/+1
Change-Id: Ie8010969443324dc76be8ade8edc1390b073345b
2017-06-04Update metric processing delay defaultPradeep Kilambi2-1/+5
This helps with processing the backlog, so lets update the default out of the box. Change-Id: I06d4ca95f4a1da2864f4845ef3e7a74a1bce9e41
2017-06-04Merge "Containerize Redis for HA"Jenkins1-0/+140
2017-06-04Containerize Redis for HADamien1-0/+140
This service allows configuring and deploying Redis containers in a HA overcloud managed by pacemaker. The containers are managed and run by pacemaker. Inside there is pacemaker_remote which will invoke the resource agent managing galera. The resources themselves are created via puppet-pacemaker inside a short-lived container used for this purpose (mysql_init_bundle). This container needs to use the 'docker_config' section to invoke puppet (as opposed to 'docker_puppet_tasks'), because due to the HA composability each resource creation needs to happen on the bootstrap node of that service and 'docker_puppet_tasks' will only run on the controller/primary role. Co-Authored-By: Michele Baldessari <michele@acksyn.org> Closes-Bug: #1692924 Depends-On: Ia1131611d15670190b7b6654f72e6290bf7f8b9e Change-Id: Ie045954fcc86ef2b3e4562b6f012853177f03948
2017-06-03Merge "Containerize clustercheck galera monitor for HA deployments"Jenkins1-0/+103
2017-06-03Merge "Containerize HAProxy for HA"Jenkins1-0/+116
2017-06-03Merge "Containerize RabbitMQ for HA"Jenkins1-0/+159
2017-06-03Merge "Containerize MySQL for HA"Jenkins1-0/+180
2017-06-03Merge "Modify vhost user socket directory's default value in environment file"Jenkins2-1/+7
2017-06-03Merge "Add support for linuxbridge agent"Jenkins5-0/+95
2017-06-02Merge "Server blacklist support"Jenkins8-8/+166
2017-06-02Merge "Add sshd service to containerized compute role"Jenkins2-0/+2
2017-06-02Merge "Upgrade gnocchi without skip-storage"Jenkins1-1/+1
2017-06-02Fix CephPoolDefaultSize typoAlex Schultz1-1/+1
Ie9bdd9b16bcb9f11107ece614b010e87d3ae98a9 improperly used CephPoolDefaultSite for the puppet-ceph-devel environment. The correct configuration item is CephPoolDefaultSize. Change-Id: If3a23f8d000061da62e4a7565a7fb6cf1ac97a4a
2017-06-02Merge "Handle upgrading cinder-volume under pacemaker"Jenkins1-0/+15
2017-06-01Increase default for NovaReservedHostMemory to 4096Sven Anderson2-1/+5
Idle compute nodes are found to already consume ~1.5GB of memory, so 2GB is a bit tight. Increasing to 4GB to be on the safe side. Also see https://bugzilla.redhat.com/show_bug.cgi?id=1341178 Change-Id: Ic95984b62a748593992446271b197439fa12b376
2017-05-31Server blacklist supportJames Slagle8-8/+166
Adds the ability to blacklist servers from all SoftwareDeployment resources. The servers are specified in a new list parameter, DeploymentServerBlacklist by the Heat assigned name (overcloud-compute-0, etc). implements blueprint disable-deployments Change-Id: I46941e54a476c7cc8645cd1aff391c9c6c5434de
2017-05-31Fix the constraints for THT params NeutronDpdkCoreList and HostCpusListKarthik S1-4/+4
This fix needs to be backported to ocata. Change-Id: I5938761efa4f56e576f41929e0bc12df246ac81a Signed-off-by: Karthik S <ksundara@redhat.com> Closes-Bug: #1694703
2017-05-31Upgrade gnocchi without skip-storagePradeep Kilambi1-1/+1
When gnocchi-upgrade run, we need to ensure storage is upgraded so we initialize the necessary storage sacks. Closes-bug: #1693621 Change-Id: I84e4fc3b6ad7fd966c4097a29678a0fd5b7a20a5
2017-05-31Merge "Containerized nova-compute working with Deployed Server"Jenkins2-0/+91
2017-05-30Merge "Enable arp_accept for all interfaces"Jenkins2-0/+11
2017-05-30Merge "Change database sync timeout from 300 to 900 in low-memory-usage ↵Jenkins2-0/+8
environment file."
2017-05-30Merge "docker bootstrap service commands"Jenkins11-28/+36
2017-05-29ceilometer-expirer: remove the crontab during upgradeEmilien Macchi1-5/+17
When running disabled/ceilometer-expirer.yaml, we want to remove the crontab that used to run ceilometer-expirer binary in periodic way. Let's use Puppet to remove this crontab. We can't easily use Ansible tasks this time, because the Ansible cron module can only remove Crontabs previously managed by Ansible: https://docs.ansible.com/ansible/cron_module.html#examples In this case, Puppet will erase the crontab in Pike. In Queens, we'll be able to remove these environments files since we wouldn't need it anymore. Change-Id: Idb050c3b281d258aea52d6a3ef40441bb9c8bcbe
2017-05-29Containerized nova-compute working with Deployed ServerJiri Stransky2-0/+91
When using the Deployed Server feature, we rely on Puppet to install packages. But nova-compute/libvirt puppet is running in a container, so it cannot install anything on the host. We rely on virtlogd on the host, so we need to install it there some way. This patch uses host_prep_tasks for that, conditionally based on the EnablePackageInstall stack parameter value. Also multinode-container-upgrade.yaml env is copied as multinode-containers.yaml, to remove the naming confusion, as the environment file can be used for more than just upgrades. The old env file will be removed once we make the upgrade job use the new one (catch 22 type of issue). Change-Id: Ia9b3071daa15bc30792110e5f34cd859cc205fb8
2017-05-26Merge "Add RoleNetHostnameMap output"Jenkins1-1/+13
2017-05-26Add sshd service to containerized compute roleOliver Walsh2-0/+2
This adds the sshd puppet service to the containerized compute role All other roles already include this service from the defaults roles data, it is only missing from the compute role. As the sshd service runs on the docker host, this must remain as a traditional puppet service. NB the sshd puppet service does not enable sshd, it just enables the management of the sshd config via t-h-t/puppet. Closes-bug: #1693837 Change-Id: I86ff749245ac791e870528ad4b410f3c1fd812e0
2017-05-26Merge "Store role_data in an OS::Heat::Value resource"Jenkins1-8/+16
2017-05-26Merge "Add heat environment for disabling all telemetry services"Jenkins1-0/+20
2017-05-26Merge "Add ignore_projects to filter gnocchi events"Jenkins1-0/+8
2017-05-26Container-specific variants of scenarios 001-004Jiri Stransky5-4/+369
Add container-specific variants of scenarios. These variants are supposed to be temporary, as their only purpose is to allow us CIing the scenarios with containers while we don't have pacemaker containerized yet. Once we can deploy and upgrade containerized deployment with pacemaker, these should be deleted and normal scenarios should be used. Alternative approach would be to edit the scenarios on the fly within the CI job, to remove the pacemaker parts, which would be more DRY, but perhaps more surprising when trying to debug issues. Change-Id: I36ef3f4edf83ed06a75bc82940152e60f9a0941f
2017-05-26Handle upgrading cinder-volume under pacemakerAlan Bishop1-0/+15
Add upgrade tasks for cinder-volume when it's controlled by pacemaker: o Stop the service before the entire pacemaker cluster is stopped. This ensures the service is stopped before infrastructure services (e.g. rabbitmq) go away. o Migrate the cinder DB prior to restarting the service. This covers the situation when puppet-cinder (who otherwise would handle the db sync) isn't managing the service. o Start the service after the rest of the pacemaker cluster has been started. Closes-Bug: #1691851 Change-Id: I5874ab862964fadb68320d5c4de39b20f53dc25c
2017-05-26Merge "Align optional services with optional services-docker"Jenkins2-0/+2