aboutsummaryrefslogtreecommitdiffstats
path: root/ci/environments/scenario001-multinode.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-02-13Add missing TripleO services to ci/multinodeEmilien Macchi1-0/+2
Add: - OS::TripleO::Services::TripleoPackages - OS::TripleO::Services::TripleoFirewall to the CI environments, so we can test Firewalling and also TripleO packages upgrades. Change-Id: I5d39c7a332a4c376fb4d6ee9463d27f481b6a0d0
2017-02-10adding Congress SupportDan Radez1-0/+2
Depends-On: Ic74ccd5fa7b3b04ca810416e5160463252f17474 Implements: blueprint congress-service-integration Change-Id: Ie60540c340c0eb71ff376aba65507a8bb3e909b6 Signed-off-by: Dan Radez <dradez@redhat.com>
2017-02-09Adding Tacker SupportDan Radez1-0/+2
Depends-On: Ide0e60f3b7a3733788af4337c1c39b4a956c876f Depends-On: I3d6bbc05644e840395f87333ec80e3b844f69903 Depends-On: Idf6abcb7fe766546cb362ad4afe54f4bccd9c994 Implements: blueprint tacker-service-integration Change-Id: Ibddc81561f6e6ba671bd01a9251c57d3ad67ba8c Signed-off-by: Dan Radez <dradez@redhat.com>
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-01-27Use os-net-config in multinode jobsEmilien Macchi1-2/+2
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-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-18Merge "Remove Glance Registry service"Jenkins1-1/+0
2017-01-17Nova Placement API composable serviceEmilien Macchi1-0/+1
Add support to deploy Nova Placement API service in TripleO. Change-Id: Ie41ebc362a0695c8f55419e231100c63007405ed
2017-01-16Remove Glance Registry serviceEmilien Macchi1-1/+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-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-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-11-25Import TripleO CI environments from tripleo-ciEmilien Macchi1-0/+56
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