aboutsummaryrefslogtreecommitdiffstats
path: root/ci/environments
AgeCommit message (Collapse)AuthorFilesLines
2017-06-20Test Horizon by default in multinode jobsBen Nemec1-0/+2
Horizon is a pretty core service for the overcloud, so we should test it in the gate jobs. The TripleoFirewall service is also included so the Horizon ports get opened correctly. Change-Id: I844b6eee547f9b4aa8e0935ab2e1e458f7a9e960
2017-06-12Remove deprecated multinode-container-upgrade.yamlJiri Stransky1-70/+0
This has been renamed to multinode-containers.yaml to reflect that the scenario isn't upgrade-specific. Change-Id: I151792700475643a4088d98eb5e1bd7248e260cd Depends-On: Ib04e2ccb330d73df464ad97a20908f20426a4249
2017-06-06Merge "Container-specific variants of scenarios 001-004"Jenkins5-4/+369
2017-05-31Merge "Containerized nova-compute working with Deployed Server"Jenkins1-0/+70
2017-05-29Containerized nova-compute working with Deployed ServerJiri Stransky1-0/+70
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-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-25Include mongodb in scenario002 jobPradeep Kilambi1-0/+1
Since we disable mongodb by default, zaqar needs it in sceanio002 job. Lets explicitly include it so it doesnt fail with: Error while evaluating a Function Call, Could not find data item mongodb_node_ips in any Hiera data file and no default supplied at /etc/puppet/modules/tripleo/manifests/profile/base/zaqar.pp Change-Id: I8f66def467d0c0175ad76f2ba5256b6a431934a8
2017-05-23Merge "Remove osd_pool_default_min_size to allow Ceph cluster to do the ↵Jenkins2-0/+2
right thing by default"
2017-05-22Remove osd_pool_default_min_size to allow Ceph cluster to do the right thing ↵Keith Schincke2-0/+2
by default The default value is 0 which has the minimum number be caluclated based on the replica count from osd_pool_defaut_size. The default replica count is 3 and the calculated min_size is 2. If the replica count is 1 then the min_size is 1. ie: min_size = replica - (replica/2) Add CephPoolDefaultSize parameter to ceph-mon.yaml. This parameter defaults to 3 but can be overriden. See puppet-ceph-devel.yaml for an example Change-Id: Ie9bdd9b16bcb9f11107ece614b010e87d3ae98a9
2017-05-22Add Neutron L2 Gateway service to scenario 004Carlos Camacho1-1/+6
This submission installs the Neutron L2 Gateway service in the scenario 004. This is only to check that the service is installed correctly no sanity check is running yet. Change-Id: I421802e9aa1a9f192860a6d72b4bb7c729666c3a
2017-05-19Update the template_version alias for all the templates to pike.Carlos Camacho1-1/+1
Master is now the development branch for pike changing the release alias name. Change-Id: I938e4a983e361aefcaa0bd9a4226c296c5823127
2017-05-15Fix absolute paths in scenario001-multinode.yamlSteven Hardy1-2/+2
All paths should be relative as we should not rely on the package location - this can easily be overridden via --templates, and this is exactly what we do for the upgrades job, where this will break because we'll include the wrong (newer) version of these services when deploying the older pre-upgrade overcloud. Change-Id: Id8aea09305c0857253c44477945e34377cca64ca
2017-05-15Merge "multinode-container-upgrade.yaml usable for mixed upgrade"Jenkins1-0/+8
2017-05-11Deprecate Ceilometer ExpirerPradeep Kilambi1-1/+0
We dont need expirer unless we have collector and standard storage enabled. Lets turn it off by default and make it an optional service. In upgrade scenario, we will kill the process and stop the expirer, unless explicitly enabled. Change-Id: Icffb7d1bb2cf7bd61026be7d2dcfbd70cd3bcbda
2017-05-10multinode-container-upgrade.yaml usable for mixed upgradeJiri Stransky1-0/+8
We need Docker service mapping defined and set to OS::Heat::None so that we can reuse multinode-container-upgrade.yaml service list both for initial deployment and for the upgrade. The upgrade will not be broken by this as its env files are being passed later on the command line, and they'll take priority and effectively enable the Docker service on upgrade. Another change we need for mixed upgrade is to add the TripleoPackages service, which will take care of updating RPMs on the bare metal and prevent docker installation from failing with outdated puppet-tripleo ("Could not find class ::tripleo::profile::base::docker"). Related-Bug: #1685795 Closes-Bug: #1689772 Change-Id: Idb6917f22d0e9f74f8853972c6a08bffb01be410
2017-05-02Merge "Deprecate ceilometer collector"Jenkins1-2/+0
2017-04-26Upgrade failure when service parameter is changed for PankoApiSaravanan KR1-0/+1
scenario001 env in ocata has mapped PankoApi locally and it has been removed master scenario001 env file. In tripleo.sh upgrade command, both old (ocata) and new (master) env files are included, because of which new service file is not used, as it has been removed. This change is to add the PankoApi mapping back to scenario001 env file for now. Actual fix will be remove old env file from upgrade command of tripleo.sh. Partial-Bug: #1685759 Change-Id: I4a8ee38d990a1980eea6ec63f2780357d040ded4
2017-04-25Deprecate ceilometer collectorPradeep Kilambi1-2/+0
Ceilometer collector is deprecated in Pike release. Do not deploy by default. Instead use the pipeline yaml to configure the publisher directly. Closes-bug: #1676961 Change-Id: Ic71360c6307086d5393cd37d38ab921de186a2e0
2017-04-24Merge pre|post puppet resources into pre|post config.Carlos Camacho6-12/+12
The [Pre|Post]Puppet resources were renamed in https://review.openstack.org/#/c/365763. This was intended for having a pre/post deployment steps using an agnostic name instead of being attached to a technology. The renaming was unintentionally reverted in https://review.openstack.org/#/c/393644/ and https://review.openstack.org/#/c/434451. This submission merge both resources into one, and remove the old pre|post hooks. Closes-bug: #1669756 Change-Id: Ic9d97f172efd2db74255363679b60f1d2dc4e064
2017-04-19SSHD Service extensionsLuke Hinds7-0/+8
This change implements a MOTD message and provides a hash of sshd config options which are sourced to the puppet-ssh module as a hash. The SSHD puppet service is enabled by default, as it is required for Idb56acd1e1ecb5a5fd4d942969be428cc9cbe293. Also added the service to the CI roles. Change-Id: Ie2e01d93082509b8ede37297067eab03bb1ab06e Depends-On: I1d09530d69e42c0c36311789166554a889e46556 Closes-Bug: #1668543 Co-Authored-By: Oliver Walsh <owalsh@redhat.com>
2017-04-18Merge "Non-ha multinode environment for container upgrade job"Jenkins1-0/+61
2017-04-13Merge "Add Docker to services list in multinode CI environments"Jenkins7-0/+8
2017-04-12Non-ha multinode environment for container upgrade jobJiri Stransky1-0/+61
Non-working containers upgrade CI is caused by the fact that all multinode jobs deploy pacemaker environments. Currently we cannot upgrade Pacemakerized deployments anyway (containerization of pacemakerized services is WIP), upgrades have only been tested with non-Pacemaker deployments so far. We need a new environment which will not try deploying in a pacemakerized way. When pacemaker-managed services are containerized, we can change the job to upgrade an HA deployment (or single-node "HA" at least), and perhaps even get rid of the environment file introduced here, and reuse multinode.yaml. Change-Id: Ie635b1b3a0b91ed5305f38d3c76f6a961efc1d30 Closes-Bug: #1682051
2017-04-11Add Docker to services list in multinode CI environmentsJiri Stransky7-0/+8
We need the service to be present to run jobs involving containers. Note that this is effectively a no-op for the current CI jobs, as by default the Docker service is mapped to OS::Heat::None. Docker will actually be deployed only if environments/docker.yaml is included in the deploy command. Change-Id: I97a35e30e428ff64feeb411bf63dbb7aa54f9829
2017-04-07Add BGPVPN services to scenario004Carlos Camacho1-0/+4
This submission will enable the BGPVPN API on scenario004. This addition to scenario004 does not provide any sanity check for the Neutron API extension. At this stage is meant to install the required packages and prerequisites, configure the extension and having the services started correctly. In the README.rst file, this is displayed as neutron-bgpvpn, so for further integrations should be added as neutron-<extension_name> for an easier reading. Depends-On: I4d0617b0d7801426ea6827e70f5f31f10bbcc038 Depends-On: I2be0fab671ec1a804d029afc6dc27d19a193b064 Change-Id: I6c257417a9231c44e13535bc408d67d2a3cacbf8
2017-04-06Adds service for managing securettylhinds1-0/+9
This adds the ability to manage the securetty file. By allowing management of securetty, operators can limit root console access and improve security through hardening. Change-Id: I0767c9529b40a721ebce1eadc2dea263e0a5d4d7 Partial-Bug: #1665042 Depends-On: Ic4647fb823bd112648c5b8d102913baa8b4dac1c
2017-04-06Merge "Remove "Core" Service from the CI Environment file"Jenkins1-2/+0
2017-04-06Merge "Add monitoring agents deployment to CI"Jenkins1-0/+5
2017-04-06Remove "Core" Service from the CI Environment fileSaravanan KR1-2/+0
OS::TripleO::Services::Core is still referenced in the CI roles enviornment file. Because of which CI is failing when service template is modified. Removing the obsolete service. Closes-Bug: #1680043 Change-Id: I168452fa5c2e6d6d8fdf829b9b02996d9ca5532a
2017-04-06Merge "Add logging agents deployment to CI"Jenkins1-0/+6
2017-04-04Add monitoring agents deployment to CIMartin Mágr1-0/+5
This patch enables deployment of sensu-client service in scenario001. Depends-On: I4895e3b6d3d0e2c12c083133e423cafeecbafe88 Depends-On: Ibabd4688c00c6a12ea22055c95563d906716954d Change-Id: I377811878712b7615c38094ecbf55dcc67d9ddd5
2017-03-30Add logging agents deployment to CIMartin Mágr1-0/+6
This patch enables deployment of fluentd service in scenario001. Depends-On: Ibabd4688c00c6a12ea22055c95563d906716954d Change-Id: Ib24a67f9068efb60b754590503a503344ab1f1df
2017-03-29Add ceilometer ipmi agentPradeep Kilambi1-0/+1
Closes-Bug: #1662679 Change-Id: I3446d59b89d43859caedd2be4583099374944379
2017-03-13Remove unnecesary code to enable panko-apiCarlos Camacho1-1/+0
We are already enabling panko-api by default `https://github.com/openstack/tripleo-heat-templates/blob/34c46241cda3be567017943560d218ced3bbdc03/overcloud-resource-registry-puppet.j2.yaml#L226` so there is no need to have the environment file or the resource in the ci environment template. Change-Id: I6af6e2196a77320c8d3b5914d161a795b007151a
2017-02-28Merge "Add upgrade support for Horizon"Jenkins1-0/+1
2017-02-28Add upgrade support for HorizonEmilien Macchi1-0/+1
Change-Id: I91c3c93c1571288daa78b6d24b0aa9824a2bb5c4
2017-02-28Configure SSL connection for MySQL client via client config fileJuan Antonio Osorio Robles1-0/+1
This uses the mysql client configuration file to configure if SSL should be used for the connection if SSL in the internal network is enabled. Change-Id: Ifd1a06e0749a05a65f6314255843f572d2209067
2017-02-27Deploy CI scenarios with PacemakerEmilien Macchi5-7/+54
Pacemaker is now deployed by default and it would be great to have it tested for all scenarios to deploy real environments used in production. Change-Id: Iff879cd641f6207644b1b6309a6ec4129f1a255a
2017-02-25multinode_major_upgrade: enable PacemakerEmilien Macchi1-0/+1
To improve testing coverage in upgrade CI job, add Pacemaker. Change-Id: I855ed15642e28cdfda5a7cbd6ff6d01b591dff7e
2017-02-23Merge "multinode/upgrade: add nova services to environment"Jenkins1-0/+7
2017-02-22Merge "Update ci environment for multinode jobs to support Ceph"Jenkins1-0/+6
2017-02-22multinode/upgrade: add nova services to environmentEmilien Macchi1-0/+7
Add Nova services to the environment that deploys the upgrade Ci job. Change-Id: I4b98b433e5c56a35e42ba34c2f2e663a4cb79580
2017-02-20Merge "Make the DB URIs host-independent for all services"Jenkins7-0/+7
2017-02-17Make the DB URIs host-independent for all servicesMichele Baldessari7-0/+7
When fixing LP#1643487 we added ?bind_address to all DB URIs. Since this clashes with Cellsv2 due to the URIs becoming host dependent, we need a new approach to pass bind_address to pymysql that leaves the DB URIs host-independent. In change Iff8bd2d9ee85f7bb1445aa2e1b3cfbff1f397b18 we first create a /etc/my.cnf.d/tripleo.cnf file with a [tripleo] section with the correct bind-address option. In this change we make sure that the DB URIs will point to the added file and to the specific section containing the necessary bind-address option. We do introduce a new MySQLClient profile which will hold all this more client-specific configuration so that this change can fit better in the composable roles work. Also, in the future it might contain the necessary configuration for SSL for example. Note that in case the /etc/my.cnf.d/tripleo.cnf file does not exist (because it is created via the mysqlclient profile), things keep on working as usual and the bind-address option simply won't be set, which has no impact on hosts where there are no VIPs. Co-Authored-By: Damien Ciabrini <dciabrin@redhat.com> Change-Id: Ieac33efe38f32e949fd89545eb1cd8e0fe114a12 Related-Bug: #1643487 Closes-Bug: #1663181 Closes-Bug: #1664524 Depends-On: Iff8bd2d9ee85f7bb1445aa2e1b3cfbff1f397b18
2017-02-17Switch to net-config-multinodeEmilien Macchi4-8/+8
Because of this bug: https://bugs.launchpad.net/tripleo/+bug/1661412 We are unable to upgrade from Newton. Until we figure this out, let's re-enable the previous SoftwareConfig. Change-Id: I966b96c50224656b152045c97aa23b9495618a18
2017-02-17Merge "Deploy Manila with CephMDS in scenario004"Jenkins1-8/+27
2017-02-16Update ci environment for multinode jobs to support CephGiulio Fidente1-0/+6
Adds the CephMon and CephOSD services on the Controller role so that we can test Ceph if the services are enabled via registry. Change-Id: I73ee5380b88bf7643ba425a0c833922e330ecade
2017-02-16CI fix broken references to multinode-core.yamlSteven Hardy2-2/+37
This isn't needed for the single-node upgrade test, but it is required for the 3-nodes job (which won't work because the referenced file doesn't currently exist). Change-Id: I78bd5c804284219a71b13dba21fd1188ca854fca
2017-02-14Deploy Manila with CephMDS in scenario004Giulio Fidente1-8/+27
Adds the Manila and CephMDS services into scenario004 and a few resources in the pingtest to test the Manila deployment. Also adds Pacemaker to scenario004 which is needed for ManilaShare. Co-Authored-By: jprovazn@redhat.com Depends-On: Ia2ece0163a3c25eb28bc0b471cd1797d52fe4e3c Change-Id: I70515c5b9ce2668a684649ecd40421b69078ee83 Related-Bug: #1644784
2017-02-13Add missing TripleO services to ci/multinodeEmilien Macchi4-0/+8
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