aboutsummaryrefslogtreecommitdiffstats
path: root/ci/environments
AgeCommit message (Collapse)AuthorFilesLines
2017-02-07implement a collectd composable serviceLars Kellogg-Stedman1-0/+4
The collectd composable service permits an operator to configure collectd metrics collection as part of the overcloud install. Depends-on: I03cfbd96778a76125d18e2ca2f48d96e292608de Change-Id: I143565329f5128f15cc39c9b62a6b242666383ab
2017-02-02CI: enable debug on multinode and upgrade jobEmilien Macchi2-0/+2
We're running TripleO CI jobs outside TripleO projects (nova, gnocchi, etc), folks need more debug to be helpful. Change-Id: I512ad89d9ac82ae62f9cbe7d0029fb1ac7445cc9
2017-01-31Use common directory in CI scenario for net-configMathieu Bultel1-2/+2
The multinode_major_upgrade scenario is using an external directory for net-config. Moving this to the internal directory in tht common/ Change-Id: I41692d2ddb9fbd2002fd7910933ab4edff74f33e
2017-01-27multinode/upgrade: set heat::rpc_response_timeout to 600Emilien Macchi1-0/+1
Continue the work done on https://review.openstack.org/#/c/423302/ Change-Id: I931534e0ec33e131809186f74068eb479d38a0f9
2017-01-27Use os-net-config in multinode jobsEmilien Macchi5-10/+10
Full credits to James Slagle, author of this code in TripleO CI: https://review.openstack.org/#/c/409346 This patch adds a new template for configuring networking on the Overcloud nodes using os-net-config in multinode jobs. Previously we were not using os-net-config at all. Also updates the multinode.yaml environment to use this network config template. The IP of each subnode is used when the vxlan tunnels are configured in OVS, given that, each node needs its own unique network configuration. To accomodate that, the templates makes use of the network_config_hook function to influence run-os-net-config.sh This patch is just the first step to totally switching to os-net-config in multinode jobs. The devstack-gate code is still in use to bootstrap the initial networking on the undercloud and subnodes. That will be switched over in subsequent patches. Change-Id: I6efa71eb23109d0b3b480061135c572ab89f5981 Co-Authorized-By: James Slagle <jslagle@redhat.com> Implements: blueprint multinode-ci-os-net-config
2017-01-27Merge "Adds SSH Banner text into sshd_config"Jenkins1-0/+10
2017-01-26ci: import multinode_major_upgrade.yaml from tripleo-ciEmilien Macchi1-0/+46
So we can version it between releases like we do with scenarios. Change-Id: I3e3aa5d4fa7e03d1f4483bf42fcff17386b58709
2017-01-26Adds SSH Banner text into sshd_configLuke Hinds1-0/+10
Allow use of ooo template to populate banner text into /etc/issue Change-Id: If5b2da9415f10652a0a64503b2da4b63d1018640 Depends-On: Ie9f8afdfa9930428f06c9669fedb460dc1064d5e Closes-Bug: #1640306
2017-01-25Merge "Add ec2-api service"Jenkins1-0/+2
2017-01-24Import multinode + pingtest from tripleo-ciEmilien Macchi2-0/+124
* Import multinode-3nodes roles data * Import multinode * Import tenantvm_floatingip pingtest We are importing these files from tripleo-ci because they contain some informations that need to be versionned (TripleO services, data binding, etc), specific to TripleO versions. Change-Id: I9d4ab144f98e8bd46cad2c29411d1270f6469b91
2017-01-24Add ec2-api serviceSven Anderson1-0/+2
This change adds the ec2api service using the tripleo::profile::base::nova::ec2api profile. The deprecated nova-cert service is not supported, and therefore the RegisterImage action is not supported either. Change-Id: I2510fd4ed935d8423216fff9ce3adf2d69c9c804 Depends-On: If4b091e1ca02f43aa9c65392baf8ceea007b7cfb
2017-01-18Merge "Remove Glance Registry service"Jenkins4-4/+0
2017-01-17Nova Placement API composable serviceEmilien Macchi4-0/+4
Add support to deploy Nova Placement API service in TripleO. Change-Id: Ie41ebc362a0695c8f55419e231100c63007405ed
2017-01-16Remove Glance Registry serviceEmilien Macchi4-4/+0
Glance registry is not required for the v2 of the API and there are plans to deprecate it in the glance community. Let's remove v1 support since it has been deprecated for a while in Glance. Depends-On: I77db1e1789fba0fb8ac014d6d1f8f5a8ae98ae84 Co-Authored: Flavio Percoco <flaper87@gmail.com> Change-Id: I0cd722e8c5a43fd19336e23a7fada71c257a8e2d
2017-01-06scenario001: add Panko testingEmilien Macchi1-0/+2
Panko has been introduced in TripleO but is not tested yet. Adding it on scenario001 with other telemetry services. Depends-On: If2f6559a7d76b26fa9b0a3ecfa2e2101aae93e3c Change-Id: Ic76f1cb36ee05e22cfda1fff8ad3f0ec18acf617
2016-12-11Decouple swift-proxy from ceilometerDan Prince3-0/+3
This patch updates the swift-proxy base profile so that we now explicitly set the rabbit_port. This allows us to remove the use of puppet-ceilometer default settings in the puppet-tripleo modules change ID here: I8d9f69f5e9160543b372bd9886800f16f625fdc6 It also adds a new boolean parameter that allows the end user to disable the swift ceilometer pipeline by setting SwiftCeilometerPipelineEnabled to false. This two settings allow Swift to once again be installed on a machine without configuring Ceilometer. Depends-On: Id1584df5e5bb90f8087ae25eecc4834179b6fc21 Change-Id: Ief5399d7ea4d26e96ce54903a69d660fa4fe3ce9 Related-bug: #1648736
2016-12-02Merge "scenario001: deploy Cinder with RBD backend"Jenkins1-0/+4
2016-12-02Merge "Add Zaqar to scenario002"Jenkins1-1/+4
2016-12-02Merge "scenario001: deploy Ceph"Jenkins1-3/+24
2016-12-02Merge "Implement scenario004 with Ceph Rados Gateway scenario"Jenkins1-0/+62
2016-12-01Merge "scenario003: configure Keystone tokens with Fernet provider"Jenkins1-0/+1
2016-12-01scenario001: deploy Cinder with RBD backendEmilien Macchi1-0/+4
Improve scenario001 with Cinder + RBD coverage. Also remove Barbican bits, we don't deploy Barbican in scenario001, but 002. Change-Id: Ib9cadbefcb3ddcdb4812f47ff5496e74b2bd888d
2016-12-01scenario003: configure Keystone tokens with Fernet providerEmilien Macchi1-0/+1
Improve scenario003 to configure Keystone tokens with Fernet provider. Scenario001 and scenario002 will still deploy uuid for now. Change-Id: I8c671d0371b2c3590b58b9623bb0df0b0c625a5b
2016-12-01Implement scenario004 with Ceph Rados Gateway scenarioEmilien Macchi1-0/+62
Like Puppet OpenStack CI, implement scenario004 with Ceph RGW scenario, where Glance uses it as a image storage backend. Change-Id: If055ca225c456a738c5726ef1e76a4a4f9c566a8
2016-12-01scenario001: deploy CephEmilien Macchi1-3/+24
Add Ceph to scenario001 and use it as a backend for Nova, Glance and Gnocchi. Change-Id: I29065d4b2ac39db40984873fda550d7adbe904fe
2016-12-01Merge "Make scenario template paths relative"Jenkins1-5/+5
2016-11-30Add Zaqar to scenario002Brad P. Crochet1-1/+4
Install Zaqar into the overcloud and create a queue with OS::Zaqar::Queue in order to test the Zaqar composable service. Change-Id: I9027d17fa3d75e6c3e23d6636642abadac8730ac Depends-On: Ia5ca4fe317339dd05b0fa3d5abebca6ca5066bce
2016-11-30Merge "Add Mistral to scenario003"Jenkins1-0/+6
2016-11-30Make scenario template paths relativeBrad P. Crochet1-5/+5
To make local testing of scenario patches easier, this changes the paths to the templates under test to be relative to the scenarios. Change-Id: I12a45ee917c214a071f5de1e28f632dbf7d1fe9d
2016-11-30Add Mistral to scenario003Brad P. Crochet1-0/+6
Install Mistral into the test overcloud and create a workflow to verify the Mistral installation. This does not currently actually execute the workflow. It merely tests that it can be created. Change-Id: Ia03a605bcfd92498bf299d3042dca7c9932f5b63 Depends-On: Id5ff9cb498b5a47af38413d211ff0ed6ccd0015b
2016-11-29Test encrypted volumes in scenario002Juan Antonio Osorio Robles1-0/+2
This effectively adds barbican-api to the deployment in scenario002 and uses it to provide encrypted volumes for cinder that a nova instance boots from in the test. Change-Id: I132e346755fb49c9563247b4404be06b97f77872
2016-11-25Import TripleO CI environments from tripleo-ciEmilien Macchi3-0/+147
Import TripleO CI environments from tripleo-ci into THT for some reasons: 1) THT is branched while tripleo-ci is not. Having them here would allow to make scenarios able to evolve over the releases without adding more scenarios. 2) Help our developers to run TripleO CI scenarios themselves from THT by exposing the templates here. The whole discussion is here: http://lists.openstack.org/pipermail/openstack-dev/2016-November/107816.html Change-Id: I3527a64c0c8f56ca77115d32849fa23fe710112d