path: root/build/opnfv-environment.yaml
AgeCommit message (Collapse)AuthorFilesLines
2018-04-18Adding NovaMigrationTarget serviceRicardo Noriega1-0/+1
Live migration fails due to this missing service in the compute role JIRA: APEX-564 Change-Id: I13d69673204f6157dcbce31507aaa132f8c4ecce Signed-off-by: Ricardo Noriega <>
2018-02-23Merge "barometer: fix barometer apex build"Tim Rozet1-1/+1
2018-02-13Adds barbican service to deploymentTim Rozet1-0/+2
This service is required for creating encrypted volumes for storage. JIRA: APEX-531 Change-Id: Ied5ea1d6921ef96c1a352dba523d6f37245608e2 Signed-off-by: Tim Rozet <>
2018-02-07barometer: fix barometer apex buildMaryam Tahhan1-1/+1
apex-tripleo-heat-templates: I3250b57316b4ec85e0558f1b512f6f3ed7c349fb apex-puppet-tripleo: I95698d69c58e0c36ae88cc2687073a05b514592c Change-Id: I5f33cd2a2842051a77c89cb11f97e8e37d1d0185 Signed-off-by: Maryam Tahhan <>
2017-11-16Migrates Apex to PikeTim Rozet1-15/+25
JIRA: APEX-544 Change-Id: Ibee2068e782da75268ed76beb36ccb5dcd1847d6 Signed-off-by: Tim Rozet <>
2017-11-06Adds ability to deploy from upstream openstackTim Rozet1-0/+9
To deploy with upstream openstack branch, use new deploy setting 'os_version'. A default scenario file for nosdn with pike has been included in this patch. If 'os_version' is a version other than the default version for this OPNFV release, then upstream is used. In order to use upstream with the current OS version use '--upstream' argument to the deploy command, to force an upstream deployment. Also include '-e upstream-environment.yaml' to use default upstream deployment settings. Supports nosdn and odl-nofeature deployments. Change-Id: Ic07e308827b449637b4e86cdd086434e4de2fb69 Signed-off-by: Tim Rozet <>
2017-10-10Cleaning up yamllint warningsDan Radez1-1/+0
apex/tests/config/inventory-virt-1-node.yaml 1:1 warning missing document start "---" (document-start) apex/tests/config/inventory-virt.yaml 1:1 warning missing document start "---" (document-start) build/opnfv-environment.yaml 6:3 warning comment not indented like content (comments-indentation) Change-Id: Ice888464d09831066bb6cd0ac94fbd290b142088 Signed-off-by: Dan Radez <>
2017-09-29Fixes nova migrationTim Rozet1-6/+26
Nova migration was failing in rally sanity test. Looking at the keys nova is configured with, the newlines in the private key were being converted to spaces in hieradata, thus making the key invalid. This patch corrects the yaml so it is multiline data. Also, corrects the parameter being set to the right THT parameter and adds sshd service to the control/compute roles which is required for migration to work. JIRA: APEX-525 Change-Id: Ic57db5c0b27df2e1f584f3c1a379e067291d892d Signed-off-by: Tim Rozet <>
2017-09-27Merge "Fixes BgpVpn service name and tht fixes"Feng Pan1-1/+1
2017-09-26Fix Neutron data_plane_status extension pathCarlos Goncalves1-1/+2
This way is easier to patch than patching file neutron.egg-info/entry_points.txt, plus this feature is backported to Ocata so it's temporary and only applicable for Euphrates. From Pike we can move it back to 'data_plane_status' as it was before. Change-Id: I1c2ebc55e782463793e7a8e463cc17fdf899457a Signed-off-by: Carlos Goncalves <>
2017-09-26Fixes BgpVpn service name and tht fixesTim Rozet1-1/+1
BgpVpn service was spelled incorrectly and there were syntax issues with the corresponding heat templates. apex-tripleo-heat-templates: If39072c687dcfb3fcb5c2dab33ecc3755b3396df Change-Id: I94155f4a32af2338bcd58afe3fb602860346a555 Signed-off-by: Tim Rozet <>
2017-09-22Fixes missing bgpvpn service on controllerTim Rozet1-0/+1
Change-Id: I943fc99d539aca9bc66204a75dbd2ae8fa7033fd Signed-off-by: Tim Rozet <>
2017-09-14Cleaning up yamllint warningsDan Radez1-6/+6
yamllint output: build/baremetal-environment.yaml 1:1 warning missing document start "---" (document-start) build/opnfv-environment.yaml 6:3 warning comment not indented like content (comments-indentation) 14:4 warning missing starting space in comment (comments) 123:1 warning comment not indented like content (comments-indentation) 128:1 warning comment not indented like content (comments-indentation) 156:1 warning comment not indented like content (comments-indentation) config/deploy/os-odl-fdio-dvr-ha.yaml 1:1 warning missing document start "---" (document-start) config/deploy/os-odl-fdio-dvr-noha.yaml 1:1 warning missing document start "---" (document-start) config/network/network_settings_v6.yaml 225:6 warning missing starting space in comment (comments) Change-Id: I3985ce0b6740ce4694b5d75b477cb03c3dc49c28 Signed-off-by: Dan Radez <>
2017-08-11Add os-odl-fdio-dvr supportFeng Pan1-0/+1
apex-tripleo-heat-templates: I6a83c9e2deeb0df9a3ab09a707c9c64aa84da55e apex-puppet-tripleo: I2025e3157b97b376b63002003ca17c7206aba546 JIRA: APEX-466 Change-Id: Iedb75994d35b5dc1dd5d5ce1a57277c8f3729dfd Signed-off-by: Feng Pan <>
2017-08-10Remove extra VPP interface from fdio-nosdn scenariosFeng Pan1-0/+2
Also set NeutronNetworkVLANRanges for daily environment. JIRA: APEX-502 Change-Id: I0a53ad8b0bce7a721104b84a2aa7ea38c510a7e7 Signed-off-by: Feng Pan <>
2017-08-09Enables SFC scenariosTim Rozet1-0/+1
apex-tripleo-heat-templates: I230b31dc9ed0ecc5046064628ba2f2505e589522 apex-puppet-tripleo: Icd433ddc6ae7de19a09f9e33b410a362c317138a Change-Id: I0b17b4e86eb90b949bd62f7e73944adad77ef1a3 Signed-off-by: Tim Rozet <>
2017-08-04Add support for nosdn-ovs-dpdk scenarioFeng Pan1-3/+4
Change-Id: I31fca214b7d16cecc261137567fa7ecf63abfe04 Signed-off-by: Feng Pan <>
2017-08-01Merge "Adds Barometer service"Tim Rozet1-0/+1
2017-07-31Adds Barometer servicejhinman11-0/+1
Adds Barometer service as a deploy option to Compute nodes by specifying barometer as true in deploy settings. Barometer packages are installed only for x86_64. Adds scenarios os-nosdn-bar-ha and os-nosdn-bar-noha. Add scenarios to opnfv-apex-common.spec. Temporarily remove references to snmp packages. apex-tripleo-heat-templates: I397d2557639c87ab8afacd076a5b9fd7c056dce7 apex-puppet-tripleo: I878ff8d1e0a8b96f3380bb77f168cd5a4c3f6543 Puppet module is at: Change-Id: Ic087c2052f7849ee2cf6c63224558c2b36a8ca1f Signed-off-by: jhinman1 <>
2017-07-29Add support for fdio scenariosFeng Pan1-6/+6
Add support for the following scenarios: - os-odl-fdio-ha - os-odl-fdio-noha - os-nosdn-fdio-noha - os-nosdn-fdio-ha apex-tripleo-heat-templates: If11092e6581445a70e63c8f6c48518698b3cc8fc apex-puppet-tripleo: If498c41d706c8f14a5b0bbee64cb4d26cd78c2d0 apex-os-net-config: If7a2c6119bf613f1fc8846237b077cd8f0e26015 Change-Id: Id3fdd09f6e0d2b7666d08c0dc7802165797eefdc Signed-off-by: Feng Pan <>
2017-07-19Backport Neutron port data plane statusCarlos Goncalves1-0/+8
JIRA: APEX-444 JIRA: DOCTOR-102 Change-Id: Idc40aa549fb1aae077a9e6b84225833a9c7c5b72 Signed-off-by: Carlos Goncalves <>
2017-05-10Adding yamllint to build checksDan Radez1-15/+17
- making formatting changes to yaml files to meet yamllint checks Change-Id: Id48a8446512943e908e61dc00bbe6c033af27775 Signed-off-by: Dan Radez <>
2017-05-09Updating Apex to OpenStack OcataDan Radez1-25/+21
- power management updated to virtualbmc, pxe_ssh is deprecated - removing custom tacker build - removing custom congress build - disabling yum update in undercloud on the cli instead of in a patch - Undercloud is direct kernel booted now, there are no kernel and initrd in the disk image from upstream - remove OpenDaylight previous to Carbon JIRA: APEX-433 JIRA: APEX-432 JIRA: APEX-431 Change-Id: I6963f16e65eacade5607a3082b58b6150331406c Signed-off-by: Dan Radez <>
2017-04-13add onos deployment stepsbobzhou1-0/+3
opnfv-tht-pr: 128 opnfv-puppet-tripleo-pr: 23 Change-Id: Ib99f7e3968ed03bd86ca0de9c6c37c9871921486 Signed-off-by: bobzhou <>
2017-04-03Merge "Euphrates Docs update w odl scenario name cleanups"Dan Radez1-1/+1
2017-03-30Add core pinning settings for VPPFeng Pan1-0/+4
Also updated os-net-config to enable VPP service on startup, as well as updating show interfaces command. JIRA: APEX-407 os-net-config-pr: 6 opnfv-tht-pr: 129 Change-Id: I77c590e966d2532d894ec96bb60ffdf914a90f6d Signed-off-by: Feng Pan <>
2017-03-30Euphrates Docs update w odl scenario name cleanupsDan Radez1-1/+1
- updating docs to reference Euphrates - removing the odl_l2-nofeature scenario, it's obsolete - renameing odl_l3 to odl, it's default for odl now - adding symlinks to files to _l3 files so CI doesn't break will remote those once CI is updated to use new names Change-Id: I9f2646fc5dac443042c5f4be8cca7d2df5dca663 Signed-off-by: Dan Radez <>
2017-03-27Adding OVN as an SDN option to ApexDan Radez1-0/+1
JIRA: APEX-129 opnfv-tht-pr: 111 opnfv-puppet-tripleo-pr: 18 Change-Id: I71de5802ed476b6f78ad5a718ac15d9aec9a6a1d Signed-off-by: Dan Radez <>
2017-03-24Fixes OVS DPDK scenariosTim Rozet1-0/+3
This fixes nosdn OVS DPDK scenarios to work with OVS 2.6. It also adds support for the ODL DPDK scenario. OVS DPDK configuration is done during preconfig on compute nodes. All nodes make use of first boot script to get kernel params like hugepages. The network settings are modified to use real nic names for the virtual network settings file. This is required due to a timing bug with os-net-config and using first-boot script. The network settings file also contains the UIO driver to use with DPDK. JIRA: APEX-314 opnfv-tht-pr: 117 Change-Id: I46b6fca71ecec38981968133ba2411f64d7c6445 Signed-off-by: Tim Rozet <>
2017-03-15Add networking-vpp ML2 supportFeng Pan1-0/+3
opnfv-tht-pr: 113 opnfv-puppet-tripleo-pr: 16 os-net-config-pr: 5 Change-Id: I0c34889db27fd71e1b73e860850b81a08707c324 Signed-off-by: Feng Pan <>
2017-03-10Add support for odl_l3-fdioFeng Pan1-2/+2
This patch adds support for ODL L3 FDIO scenario. Introduces a new deploy settings parameter, odl_routing_node, to indicate the routing node's hostname. This parameter will only be used for this scenario. Change-Id: I8df3eb701299007761c6cec42c4ca318b124a0b8 opnfv-tht-pr: 108 os-net-config-pr: 4 Signed-off-by: Feng Pan <>
2017-02-22Adding congress support back into DanubeDan Radez1-0/+1
opnfv-tht-pr: 97 opnfv-puppet-tripleo-pr: 10 Change-Id: Idfc109fc984f20b096a23d12864a027146a9c74c Signed-off-by: Dan Radez <>
2017-02-18Add support for odl-fdio scenarioFeng Pan1-5/+8
Changes: - Kernel parameters are now set through first-boot.yaml during deployment. No custom images will be built. Note that all nodes will be configured the same way, we only use compute's kernel parameter settings currently (from deploy settings file) - Add support for VPP interface type in network settings file, it is now possible to specify vpp_interface type and uio_driver for tenant nic in network settings file. A new example config, network_settings_vpp.yaml is added. - Add support for odl_l2-fdio scenario. Limitations: - Physical NIC names must be specified in network settings file, numbered nic names such as nic1 are not supported for fdio scenarios. - The same kernel parameters will be configured for all nodes. The paramters will be taken from compute kernel parameter section in deploy settings file. opnfv-tht-pr: 104 opnfv-puppet-tripleo-pr: 12 os-net-config-pr: 3 Change-Id: Ie9d6151e6e58d11da3c66fbcabe4a0886c3fa152 Signed-off-by: Feng Pan <>
2017-02-13Adding tacker support back into DanubeDan Radez1-0/+1
opnfv-tht-pr: 98 opnfv-puppet-tripleo-pr: 11 Change-Id: I971bb2c94eb9500c81b25adf5019fd02f8e90053 Signed-off-by: Dan Radez <>
2017-02-10Adding gluon to the Build and DeploysystemGeorg Kunz1-0/+1
In order to make gluon really deployable some more things need to be done: - Add pull request 103 which add yaml files which point to gluon puppet - Rename the scenario to odl-gluon similar to bgpvpn scenario - Add tht of gluon to JIRA: APEX-379 opnfv-tht-pr: 103 opnfv-puppet-tripleo-pr: 13 Change-Id: I3ccfb5a279f1df21c4da79fc47039b3c0b6e5495 Signed-off-by: Nikolas Hermanns <> Signed-off-by: Georg Kunz <>
2017-02-07Add gluon scenario config fileNikolas Hermanns1-0/+1
This patch adds first version of gluon scenario config file, as well as introducing etcd service in puppet-fdio and T-H-T. JIRA: APEX-379 opnfv-tht-pr: 96 opnfv-puppet-tripleo-pr: 9 Change-Id: Icef29520d093e005dba9cbc5cf0e3fd1ed893cf4 Signed-off-by: Nikolas Hermanns <>
2017-01-12Fixes default floating ip poolTim Rozet1-0/+2
We need the default pool to match the default external network we create so that using nova to create floating ip pools without specifying the newtwork will work in temptest tests. JIRA: APEX-380 Change-Id: Icbd8c3a3810bd93d71e9e5954c587455165a8445 Signed-off-by: Tim Rozet <>
2016-11-18Fixes external network creationTim Rozet1-6/+6
Without specifying the provider network type or physical network results in the default tenant network type being used upon external network creation (for us this means vxlan). Previously this worked fine because Neutron L3 agent and ODL L3 would assume to use br-ex. This is no longer true in ODL new nettvirt, and needs to be explicitly flat along with the correct physical network. Also includes minor fix for Manila service naming that was fixed upstream. JIRA: APEX-300 Change-Id: If5d467a811baafe01b725dd530938482fdd3fd03 Signed-off-by: Tim Rozet <>
2016-11-11Migrate to stable/newtonTim Rozet1-10/+107
os-odl_l2_nofeature is now deprecated since new netvirt only supports odl_l3. JIRA: APEX-299 Change-Id: I3557ecb85fa4cd11bba96aa9410e56a8e8cceb00 Signed-off-by: Tim Rozet <>
2016-08-23Adds workaround to fix dhcp metadataTim Rozet1-0/+1
JIRA: APEX-236 Change-Id: If237340529f2b9898d91c420b004770e0f883ce0 Signed-off-by: Tim Rozet <>
2016-08-17Fixes dhcp metadataTim Rozet1-0/+2
JIRA: APEX-236 opnfv-tht-pr: 59 Change-Id: Ic8fad4abb3846c57d218b2b23ef44750a644fe73 Signed-off-by: Tim Rozet <>
2016-08-09Enables storing events in ceilometer notificationTim Rozet1-0/+2
JIRA: APEX-225 Change-Id: Idd1d7ec895be2812475c086ea4ba67f7acae3003 Signed-off-by: Tim Rozet <>
2016-07-26Merge "Add nova ssh key for vm resize"Tim Rozet1-0/+6
2016-07-22Fix tackerMichael Chapman1-1/+1
opnfv-tht-pr: 49 JIRA: APEX-210 Change-Id: I9ed97588e8ae70d8ded6d2939c6a62d38393d8de Signed-off-by: Michael Chapman <> Signed-off-by: Tim Rozet <>
2016-07-21Add nova ssh key for vm resizeMichael Chapman1-0/+6
SSH keys for the nova account are required for the nova resize functionality. A new pair of keys is generated for each deploy. In addition, host keys are populated and a shell is provided to the nova user on all compute nodes via puppet. opnfv-tht-pr: 43 Change-Id: Ibde6877d279bc0b87553301fbce44975286cb092 JIRA: APEX-147 Signed-off-by: Michael Chapman <>
2016-07-20Adding tacker supportDan Radez1-0/+1
opnfv-tht-pr: 34 opnfv-puppet-tripleo-pr: 4 JIRA: APEX-126 Change-Id: I050e7ae2e94779c1886f670841aa4e2dec4aa8d2 Signed-off-by: Dan Radez <>
2016-07-20Merge "Makes flavor consistent in virtual/baremetal deploys"Dan Radez1-1/+2
2016-07-19Allows specifying domain name for overcloud/undercloudTim Rozet1-0/+1
Can be set by setting domain_name in network_settings. Defaults to dummy JIRA: APEX-183 JIRA: APEX-182 Change-Id: Ib7c279a1c8432b8635f72e5cc667f16b9cd65159 Signed-off-by: Tim Rozet <>
2016-07-18Makes flavor consistent in virtual/baremetal deploysTim Rozet1-1/+2
Changes include: - Fixes bug where baremetal control nodes would deploy to ironic nodes labeled 'compute', and cause deployment failure - Makes virtual deployments also use flavor types when deploying JIRA: APEX-205 Change-Id: I84e1a6d1e2ccc3391ad2b4e34ea6ca62d480d64f Signed-off-by: Tim Rozet <>
2016-07-12Adds nova policy for server host status via ownerTim Rozet1-0/+5
JIRA: APEX-196 Change-Id: I21f63e69ecc4d5b979ed4780c6e92e3ad272b8d7 Signed-off-by: Tim Rozet <>