summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-06-27Merge "Add validation check for divergent parameter definitions"Jenkins1-4/+71
2017-06-27Merge "Add non-ha env file."Jenkins1-0/+16
2017-06-27Merge "Adds service for OVS and enables ODL DPDK deployments"Jenkins10-143/+395
2017-06-27Add validation check for divergent parameter definitionsBen Nemec1-4/+71
Many of our parameters are defined in multiple templates, but currently there is no easy way of checking that all of those definitions match. It can be confusing when a parameter is defined one way in one file and another way in a different file. For example, the NovaWorkers description is: Number of workers for Nova API service. and Number of workers for Nova Placement API service. and Number of workers for Nova Conductor service. Which is it actually? All of them. That one parameter controls the workers for all of the nova services, and its description should reflect that, no matter which template you happen to look at. This change adds a check to yaml-validate.py to catch these sorts of inconsistencies and allow us to eventually prevent new ones from getting into the templates. An exclusion mechanism is included because there are some parameter definitions we probably can't/shouldn't change. In particular, this includes the network cidrs which are defaulted to ipv4 addresses in the ipv4 net-iso templates and ipv6 in the ipv6 templates. It's possible a user would be relying on one of those defaults in their configuration, so if we change it they might break. To get around that, the tool explicitly ignores the default field of those parameters, while still checking the description and type fields so we maintain some sanity. There may be other parameters where this is an issue, but those can be added later as they are found. For the moment any inconsistencies are soft-fails. A failure message will be printed, but the return value will not be affected so we can add the tool without first having to fix every divergent parameter definition in tripleo-heat-templates (and there appear to be plenty). This will allow us to gradually fix the parameters over time, and once that is done we can make this a hard-fail. Change-Id: Ib8b2cb5e610022d2bbcec9f2e2d30d9a7c2be511 Partial-Bug: 1700664
2017-06-27Merge "Provides a list of per-service ctlplane IPs to the workflows env"Jenkins5-0/+42
2017-06-27Merge "Add flag to enable/disable the HAProxy stats interface"Jenkins2-0/+9
2017-06-27Merge "Allows use of Mistral workflows during deployment steps"Jenkins7-13/+183
2017-06-27Merge "Enable DPDK on boot using PreNetworkConfig"Jenkins8-2/+109
2017-06-26Merge "Add VipMap output"Jenkins2-0/+11
2017-06-26Merge "Add split-stack environments"Jenkins6-7/+42
2017-06-26Merge "Add DeploymentSwiftDataMap parameter"Jenkins8-1/+191
2017-06-26Merge "Add os-collect-config data as an output"Jenkins9-0/+41
2017-06-26Merge "Fix descriptions on bonding templates"Jenkins9-53/+35
2017-06-26Provides a list of per-service ctlplane IPs to the workflows envGiulio Fidente5-0/+42
Adds in the execution environment of the workflow steps a list of per-service network IPs. This can be used by the workflows to execute actions against the nodes hosting a given service. Change-Id: Id7c735d53f04f6ad848b2f9f1adaa3c84ecd2fcd Implements: blueprint tripleo-ceph-ansible
2017-06-26Allows use of Mistral workflows during deployment stepsGiulio Fidente7-13/+183
Introduces a general mechanism meant to allow for the execution of workflows during the deployment steps. Services can define workflow actions to be triggered during a step in the newly added service_workflow_tasks section. The syntax is: service_workflow_tasks: step2: - name: my_action_name action: std.echo input: output: 'hello world' Implements: blueprint tripleo-ceph-ansible Depends-On: If02799e7457ca017cc119317dfb2db7198a3559f Depends-On: Ibc5707f9f06266fe84ad1dd91dcb984157871d30 Change-Id: I36a642fbc2076ad9e4a10ffc56d6d16f3ed6f27a
2017-06-26Add non-ha env file.Carlos Camacho1-0/+16
This environment file will be used to deploy an Overcloud without the use of pacemaker. Change-Id: I3a486d22b30ffdb6053b3d917dea373c1361df81
2017-06-26Merge "Make sensu-client log to file"Jenkins1-1/+11
2017-06-26Add flag to enable/disable the HAProxy stats interfaceJuan Antonio Osorio Robles2-0/+9
This was made configurable in a recent commit [1] So this flag makes it easier for deployers to use that functionality. [1] Ic68266eaf39d6803f7c3e299095578bbcfd63b88 Change-Id: Iffff20dcda53bc7237586dd240e581bcb0282844
2017-06-26Merge "Containerize Cinder-backup for HA"Jenkins1-0/+152
2017-06-25Temporarily disable containerized cinderMartin André1-2/+2
The containerized cinder service was merged a bit too soon and it caused several issues in CI. Disable it temporarily to unblock CI until it matures. Change-Id: I8c6c0ce0011fddfec1e2de798d4fc6f34ae78de2 Related-Bug: #1700333
2017-06-24Merge "Replace hardcoded 'br-ex' with NeutronPhysicalBridge parameter."Jenkins3-5/+13
2017-06-23Merge "scenario004: containerize services for CI"Jenkins1-2/+5
2017-06-23Merge "Fix manila-api volumes list"Jenkins1-0/+1
2017-06-23Merge "Enable periodic task to discover cell hosts when ironic is used"Jenkins3-0/+17
2017-06-23Replace hardcoded 'br-ex' with NeutronPhysicalBridge parameter.Dan Sneddon3-5/+13
This change uses the NeutronPhysicalBridge parameter on all roles, rather than hard-coding the "br-ex" name. Previously, there were different parameters for controller and compute roles, but since we use a unified bridge name with OVS, this is unnecessary. Change-Id: I6d9189404fae67bcc33ddc2ba3ce1b0385dd989d Closes-bug: 1669130
2017-06-23Merge "scenario002: containerize services for CI"Jenkins1-3/+4
2017-06-23Merge "Fix rpms being installed via DeployArtifactURLs"Jenkins2-2/+10
2017-06-23Merge "Fix roles dict object' has no attribute 'lower' error"Jenkins1-1/+1
2017-06-23Enable periodic task to discover cell hosts when ironic is usedDmitry Tantsur3-0/+17
Starting with the Ocata release, bare metal nodes are no longer get recognized by nova automatically. To avoid forcing users into running nova manage command each time they enroll a node, we will have to allow enable the periodic task to do so. Change-Id: I8b0afac54dc9bd51dbe2ae4f237e4de50459be0f Closes-Bug: #1697724
2017-06-23scenario004: containerize services for CIEmilien Macchi1-2/+5
Change-Id: I025ed07ce97132bce3fa7a15d170fc62e17e07a4
2017-06-23Fix manila-api volumes listJiri Stransky1-0/+1
Change-Id: Idbbff1047fbc3f664e44131770ba2849ea9d51bc Closes-Bug: #1700082
2017-06-23Merge "Configuration for containerized MySQL clients"Jenkins2-0/+67
2017-06-23Adds service for OVS and enables ODL DPDK deploymentsTim Rozet10-143/+395
In order to deploy OpenDaylight with DPDK we need to copy the DPDK config for OVS done in the neutron-ovs-dpdk service template, without enabling OVS agent for compute nodes. To do this correctly, we should inherit and openvswitch service which is a common place to set OVS configuration and parameters. Note: vswitch::dpdk config will be called in prenetwork setup with ovs_dpdk_config.yaml so there is no need to include that in the step config for neutron-ovs-dpdk-agent service or opendaylight-ovs-dpdk. Changes Include: - Creates a common openvswitch service template, which in the future will migrate to be its own service. - Renames and fixes OVS DPDK configuration heat parameters in the openvswitch template. - neutron-ovs-dpdk-agent now inherits the common openvswitch template. - Adds opendaylight-ovs-dpdk template which also inherits common ovs template. - Uses OVS DPDK config script to allow configuring OVS DPDK in prenetwork config (before os-net-config runs). This has an issue where hieradata is not present yet, so we have to redefine the heat parameters and pass them via bash. In the future this should be corrected. - Adds opendaylight-dpdk environment file used to deploy an ODL + DPDK deployment. - Updates neutron-ovs-dpdk environment file. Closes-Bug: 1656097 Partial-Bug: 1656096 Depends-On: I3227189691df85f265cf84bd4115d8d4c9f979f3 Change-Id: Ie80e38c2a9605d85cdf867a31b6888bfcae69e29 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-23Merge "Make collectd log to file"Jenkins1-3/+17
2017-06-23scenario002: containerize services for CIEmilien Macchi1-3/+4
Change-Id: I9f9a9dcf1666b5b0475bc8fae5b785747480b7d6
2017-06-23Enable DPDK on boot using PreNetworkConfigSaravanan KR8-2/+109
DPDK has to be enabled on openvswitch on the boot before configuring the network as when the network uses DPDK ports OvS should be ready to handle DPDK. Enabled DPDK via PreNetworkConfig by checking if ServiceNames contains DPDK service. Implements: blueprint ovs-2-6-dpdk Closes-Bug: #1654975 Depends-On: I83a540336c01a696780621fb2b39486a6abf0917 Change-Id: I7af4534d91e67c94ba559b78b9ac6a001e639db3
2017-06-22Merge "Revert "Blacklist support for ExtraConfig""Jenkins11-192/+7
2017-06-22Merge "scenario003: containerize services for CI"Jenkins1-5/+5
2017-06-22Merge "Specify file url when deploy-artifacts fails"Jenkins1-1/+1
2017-06-22Merge "Fixes incorrect glance api network"Jenkins2-1/+4
2017-06-22scenario003: containerize services for CIEmilien Macchi1-5/+5
Change-Id: I152f5c97d2545aa595e193218653a4b7e56c0cb6
2017-06-22Merge "Fix fallback logic in run-os-net-config.sh"Jenkins1-1/+1
2017-06-22Merge "Remove add_listen: false from Horizon hieradata"Jenkins1-1/+0
2017-06-22Merge "Test Horizon by default in multinode jobs"Jenkins1-0/+2
2017-06-22Make collectd log to fileMartin Mágr1-3/+17
- sets collectd service in container to log to file consistently with other docker services. - corrects configuration mounts Depends-On: I50289ad6657852d37abbf12938128ff9ab9e3bac Change-Id: Ibf9efbe249d67d0fa1e50fbd7dd9902a64d5a273
2017-06-22Merge "Deploy ironic-api with WSGI"Jenkins2-4/+36
2017-06-22Revert "Blacklist support for ExtraConfig"Alex Schultz11-192/+7
This reverts commit d6c0979eb3de79b8c3a79ea5798498f0241eb32d. This seems to be causing issues in Heat in upgrades. Change-Id: I379fb2133358ba9c3c989c98a2dd399ad064f706 Related-Bug: #1699463
2017-06-22Merge "Remove trailing whitespace"Jenkins0-0/+0
2017-06-21Fix descriptions on bonding templatesDan Sneddon9-53/+35
This change updates the descriptions of bond paramters in the bonded network interface templates. Previously, only OVS bond settings were mentioned, and the description for the bond options constraints had extra whitespace. This change mentions settings for Linux bonds, and removes extra spaces. Change-Id: Id50c042ae4a3b9298e8de0364e315b9f8777b79f
2017-06-21Fix fallback logic in run-os-net-config.shBen Nemec1-1/+1
The expression "${variable:-''}" with $variable unset results in a value that looks like "''", which will not pass a -z test, as I believe is intended in this code. Making the default value blank yields the correct behavior. Change-Id: I9fe98f3c69c797feb9c37da1ad8c7912a15bcecb Closes-Bug: 1699614