summaryrefslogtreecommitdiffstats
path: root/xci
AgeCommit message (Collapse)AuthorFilesLines
2019-08-01Introduction of Openstack-helm as installernikoskarandreas31-6/+1030
This patch creates a new installer tree in xci that uses openstack-helm to deploy openstack on a kubernetes cluster. USAGE: Export INSTALLER_TYPE=osh, DEPLOY_SCENARIO=k8-calico-nofeature and XCI_FLAVOR=noha or mini and run xci-deploy.sh as in documentation. deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: I212f70eb51c2a38c798c11367d2ebb8bf5f4a1de Signed-off-by: nikoskarandreas <nick@intracom-telecom.com>
2019-07-31Move to newer versions of Bifrost reposManuel Buil1-10/+10
Change-Id: Id0b7becd47534de8b80df93e85daf399bc613aec Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-07-31Remove source installManuel Buil1-3/+0
We should try to use pip ansible module as much as possible. If we use pip in the command line we run into issues when moving towards a newer version of bifrost Change-Id: Ib606e0cc0e754f0a9ca07bf7724b7f8d70976b2d Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-06-12Pin ara version to 0.16.4Nikos Mimigiannis2-1/+2
The ara module just released an update which changes how the module can be imported. As a result, the xci-deploy script immediately fails when trying to setup the virtualenv. This patch sets ara to its previous version (ara==0.16.4). Change-Id: Ic54d18dc877857389e8b36bbf2e8bf4b70bc2812 Signed-off-by: Nikos Mimigiannis <nmimi@intracom-telecom.com>
2019-03-26Bug fix: use pod4-nodeN to refer to the nodesManuel Buil1-10/+10
lfpod4 uses pod4-nodeN notation and that was missing for the kubespray deployer Change-Id: If5b0a600b65f830c96ff8888986e0ef8decaada6 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-03-26Merge "Add idf and pdf for lfpod4"Fatih Degirmenci2-0/+385
2019-03-25Add idf and pdf for lfpod4Manuel Buil2-0/+385
Change-Id: I6086d13450f95a5c901270c7d4b69a0aa127f129 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-03-25Bug fix: don't force rc=0 on first commandManuel Buil1-1/+1
When working with an interface that uses vlan, the vlan is created when executing the ifup command. As we previously execute the command: /sbin/ip addr flush dev {{ item }} it will not return code 0 because the interface does not exist yet. Consequently, the second part of the command (ifup) is never executed and the new network config is never triggered. This patch removes the requirement to get a rc=0 in the first command to run the second one. Note that /sbin/ip addr flush dev {{ item }} must be run before ifup when working with non-vlan interfaces that already have an ip, otherwise ifup fails in Ubuntu Change-Id: Ieac273a49b78104f24d4c1ba81c263b450a40a9f Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-03-25Fix bug in the inventory generatorManuel Buil1-1/+7
The dns keys should only appear in case the idf provides a dns entry for the network. Otherwise, it should not exist at all. If it exists, even if the value is empty, ansible will transform it in a variable and "item.network.dns is defined" will return true: https://github.com/opnfv/releng-xci/blob/master/xci/playbooks/roles/bootstrap-host/templates/osa/debian.interface.j2#L35 A docstring is also added to explain what is the purpose of the class Signed-off-by: Manuel Buil <mbuil@suse.com> Change-Id: Ib8afa06cecb54f384083060073fa463c7f8d313f
2019-03-25Use functest:hunter for openstack/rockyFatih Degirmenci1-1/+2
deploy-scenario:os-nosdn-nofeature installer-type:osa Change-Id: Icebfbbd151c53b9ca3f38c7fdb107cb1f51b2b3e Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2019-03-05Increase timeoutManuel Buil1-2/+2
Baremetal is failing because ironic takes long to transfer the image to the hard drive of the nodes Change-Id: Ief704e92307d1ea7fe55ee0268abae49e0126503 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-03-04Add the baremetal case to READMEManuel Buil2-1/+32
Change-Id: I3977c3d99b06b2548259e8765c262eb996ba30cf Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-02-14Fix typoManuel Buil2-1/+1
The name of the file should have baremetal not barematal Change-Id: I15d70b69943e8ce3032c76d1cd7bc7272a6b8d56 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-01-08SHA Bump for stable/rockyManuel Buil3-83/+83
Moving to the newer SHAs of stable/rocky installer-type:osa Change-Id: I89de6554d5e3bef8b2b49c6a3e621d3ca3a6f4dc Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-11-29Add network details for k8sManuel Buil1-2/+19
To read the idf when the installer is kubespray, we need the network details too Change-Id: Idb9b0a4338a224e146abc78690067659bc94c302 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-11-21Rename Ericsson POD2 PDF/IDFFatih Degirmenci2-0/+0
The PDF/IDF filenames to use during deployments in CI will be generated dynamically based on which slave the job is running on with the help of the SLAVE_NAME environment variable Jenkins injects into job environment. It will probably look like this pdf=var/pdf.yml idf=var/idf.yml if [[ "$SLAVE_NAME" !~ virtual ]]; then pdf=var/${SLAVE_NAME}-pdf.yml pdf=var/${SLAVE_NAME}-idf.yml fi ./xci-deploy.sh -i $idf -p $pdf deploy-scenario:os-nosdn-nofeature installer-type:osa Change-Id: Ief319ee36292ca888b97e4059a26337ee98dfef2 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-11-08xci: bifrost: Respect IDF DNS details during node configurationMarkos Chandras6-7/+10
The IDF files contain DNS information so we should respect that when we configure the various XCI nodes. The DNS information is also a list instead of a string so treat it as such. Change-Id: I1c4d5eb600baaca35b2838dcafa7a75e59bf6783 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-11-07Merge "[baremetal] Provide networking for suse nodes"Manuel Buil2-2/+41
2018-11-06Merge "[Baremetal] Provide networking for Ubuntu nodes"Manuel Buil2-1/+111
2018-11-06Merge "Bug fix: NFS clients pointing to wrong server"Manuel Buil1-30/+30
2018-11-06Merge "Simplify the serial config"Manuel Buil1-10/+0
2018-11-06Bug fix: NFS clients pointing to wrong serverManuel Buil1-30/+30
We are deploying the NFS server in computes. In all flavors, node2 takes the role of compute00 and thus the NFS server is in 172.29.244.12. Therefore, the openstack config for ha is wrong Change-Id: I5e82ddd670b44e291c0b866ba4fde57e74b68643 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-11-06[Baremetal] Provide networking for Ubuntu nodesManuel Buil2-1/+111
When deploying baremetal, the traffic should be segmented using the different interfaces instead of through vlans. All the config is done based on idf and pdf information. When doing non-baremetal, opnfv and nodes get the same config. When doing baremetal, opnfv and nodes get a different network config Change-Id: I23aa576bc782c7c69d511a5558827110c37b558a Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-11-06[baremetal] Provide networking for suse nodesManuel Buil2-2/+41
When deploying baremetal, the traffic should be segmented using the different interfaces instead of through vlans. All the config is done based on idf and pdf information. When doing non-baremetal, opnfv and nodes get the same config. When doing baremetal, opnfv and nodes get a different network config Apart from that, if vlan_id is defined in the name, there is no need for VLAN_ID in the interface descriptor. This simplifies things Change-Id: Iddbb90af807b43e247e5ee11fe735df9e823d4bf Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-11-05Merge "xci: files: Also collect BIFROST env variables for bug reports"Manuel Buil1-1/+1
2018-11-05xci: files: Also collect BIFROST env variables for bug reportsMarkos Chandras1-1/+1
Bifrost is exposing quite a few variables so we need to collect them as well. Change-Id: I7e7ca7a093f35a0acb53af360e58444f6c1de7e4 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-11-02Simplify the serial configManuel Buil1-10/+0
The current configuration only dumps the booting info into a file and the pty does not work (i.e. virsh console opnfv returns a failure because it cannot find a character device). After some investigations, it is apparently impossible to have both active: https://github.com/Mirantis/virtlet/issues/249 Therefore, we should remove the pty part of the xml. To connect to the VM in case of network problems, we can always use vnc. Apart from that, the console part is not necessary as libvirt will create that one for us Change-Id: I80a59163b4ba4e6bff34cb5378893201e93ddb87 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-11-02xci: Bump kubespray version to 2.7.0Markos Chandras1-3/+2
installer-type:kubespray deploy-scenario:k8-nosdn-nofeature Change-Id: I6b59df5112e9b3459bf3147557f5f22fe0fb778b Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-11-02xci: osa: Bump SHAs to the HEAD of the Rocky branchMarkos Chandras4-87/+92
Change-Id: I50c367433dc8cf8964c291c916ea939e25f638cb Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-11-01xci: Add missing update_cache statementsMarkos Chandras4-2/+5
When we install packages from the distro repos we need to make sure that the database is updated. This also takes SUSE's zypper pkg manager into consideration which can benefit from the same Ansible option. Change-Id: I7a2206bfc5827b9ccb448278759711c560bb4679 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-10-31Bug fix: Fetch vm names from idfManuel Buil4-8/+10
Currently we were taking the names of the nodes to be generated from the NODE_NAMES variable whereas ansible was fetching the names from the dynamic_inventory.py which uses idf. This resulted in problems: when doing ha, ansible was provisioning a compute as a controller and vicebersa. This patch forces create_nodes role to fetch the name from idf and thus align with the naming schema of ansible deploy-scenario:k8-calico-nofeature installer-type:kubespray Change-Id: Id1473727405701fd9ed0cb2f1394ee8676cec337 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-30Remove variable for driverManuel Buil2-2/+2
Right now, we only support ipmi hosts (either virtual or physical) and that is why our json is always describing the ipmi parameters. It does not make sense that we have a variable which would allow to change that Change-Id: I7b88aca5930a73d68342e3d4cf21f9e96286c4d7 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-30Bug fix: Wrong reference to vm_host_groupsManuel Buil1-1/+1
The variable should be host_group which is generated at line 32 and 35 Change-Id: I7add3af73198ec0638dee0c8f189a3a372a78ee8 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-26Change variable in start-new-vm.shManuel Buil1-1/+1
Since the patch: https://gerrit.opnfv.org/gerrit/#/c/63173/ The variable BIFROST_USE_PREBUILT_IMAGES has changed to BIFROST_CREATE_IMAGE_VIA_DIB. As jenkins does not trigger testing jobs when editing file in xci/scripts/, this change is done in a separate patch Change-Id: I3bc285936fae5b7514272ca0ad2418b60446e4aa Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-26Merge "SHA bump for bifrost"Markos Chandras1-9/+9
2018-10-26Merge "Reduce complexity when using bifrost roles"Markos Chandras3-4/+3
2018-10-26Merge "Bug fix: match only the scenario name"Markos Chandras1-1/+1
2018-10-26Bug fix: match only the scenario nameManuel Buil1-1/+1
Since this week we have two sfc scenarios: - os-odl-sfc - os-odl-sfc_osm When $DEPLOY_SCENARIO=os-odl-sfc, using the current code testing_role gets two values: os-odl-sfc os-odl-sfc_osm This patch adds '$' character to prevent matching scenarios which concatenate characters after $DEPLOY_SCENARIO Change-Id: Ia0782362da04e8b3ecd2ec6f13ccc8c404797fda Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-26Reduce complexity when using bifrost rolesManuel Buil3-4/+3
We are using two variables which have a similar scope: - create_image_via_dib - use_prebuilt_images We could use one of them and not both. create_image_via_dib is selected because it also exists in upstream bifrost use_prebuilt_images = false is the same as create_image_via_dib = true use_prebuilt_images = true is the same as create_image_via_dib = false Change-Id: Ieaab78f1dc2d199746a2b13ebc82e9dc615d92e9 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-26os_neutron SHA bumpManuel Buil1-1/+1
We need a commit for SFC scenario: https://github.com/openstack/openstack-ansible-os_neutron/commit/200fa4a7aaa15a6d6758418eafffe093174d2f72 Change-Id: Ia497a49a910d16eaf3c7ee896f0f75aab812bd7a Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-26SHA bump for bifrostManuel Buil1-9/+9
We need it for baremetal support in opensuse: https://github.com/openstack/bifrost/commit/0f605cd723a68e2c2bb9b30a15a08e5aba777bd5 We move all related repos from Rocky to master (problems if we SHA bump ironic, etc in Rocky while Bifrost in master) Change-Id: Icf0dd58c6fc6cc8f221d37a6ed3f3746f6577716 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-25Merge "Introduce the Barbican in XCI for SFC-HA scenario"Markos Chandras1-0/+1
2018-10-25Integrate os-odl-sfc_osm scenario into XCIVenkata Harshavardhan Reddy Allu1-0/+14
https://gerrit.opnfv.org/gerrit/#/c/63505/ The os-odl-sfc_osm scenario has been verified in the previous patchsets of this commit. This patch needs to be merged after adding OS variables to the post-deployment playbook. https://gerrit.opnfv.org/gerrit/#/c/63135/ installer-type:osa deploy-scenario:os-odl-sfc_osm Change-Id: I14e83357c9e1db6e31890b5f126b9e405e124594 Signed-off-by: Venkata Harshavardhan Reddy Allu <venkataharshavardhan_ven@srmuniv.edu.in>
2018-10-20xci: Add OS variables to the post-deployment playbookVenkata Harshavardhan Reddy Allu1-0/+1
OSM needs access to OpenStack credentials and authentication url. This patch would provide that using the xci_flavor specific user_variables.yml file. This patch is necessary to complete the initial integration of OSM. installer-type:osa deploy-scenario:os-nosdn-osm Change-Id: Ic228b323fc69ce46c8093f6dfbc116d8c71a0391 Signed-off-by: Venkata Harshavardhan Reddy Allu <venkataharshavardhan_ven@srmuniv.edu.in>
2018-10-19Introduce the Barbican in XCI for SFC-HA scenarioPanagiotis Karalis1-0/+1
The barbican OS component is introduced for SFC HA deployed scenario. The reason behind is that In HA scenarios we need Openstack Barbican to gather and store the fernet keys so Tacker can access them and be able to register new VIMs. deploy-scenario:os-odl-sfc installer-type:osa JIRA: SFC-131 Change-Id: Ife416fb2a7dc04ddadc93f962695aee4ed448501 Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com>
2018-10-18Merge "[Baremetal] Add baremetal support to create-nodes"Manuel Buil6-14/+122
2018-10-18xci: osa: Bump SHAs to the HEAD of the Rocky branchManuel Buil4-92/+91
Since Rocky, networking-odl depends on ceilometer and requires it to be installed. Therefore, all odl scenarios need to have ceilometer deployed. Once that is done, we can unfreeze n-odl repo. Besides, we need to introduce a SHA bump for neutron and ceilometer to include the latest changes to support this fix Ceilometer should be git cloned always, otherwise repo_build will fail as ceilometer is now part of requirements.txt [mchandras: Instead of just bumping selective network related roles, lets just do a complete sha bump for stable/rocky] deploy-scenario:os-odl-sfc installer-type:osa Change-Id: I81a39436e4ff648faabda4e82fce1d3f14615741 Signed-off-by: Manuel Buil <mbuil@suse.com> Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-10-18Merge "Add ODL variables to env file"Manuel Buil3-0/+31
2018-10-18Add ODL variables to env fileManuel Buil3-0/+31
ODL testcases in functest require new variables: https://git.opnfv.org/functest/tree/functest/utils/env.py#n22 Otherwise the test fails because it cannot contact ODL To find those variables, we fetch the ml2_conf.ini file from the neutron container and then we parse the values. This is only run when the scenario has odl deploy-scenario:os-odl-sfc installer-type:osa Change-Id: If175bb7642e66e151b30e1ccd1b9040aa3481d8f Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-17[Baremetal] Add baremetal support to create-nodesManuel Buil6-14/+122
Information about baremetal servers is collected for ironic to do the provisioning. Two main things are done: 1 - baremetalhoststojson.yml fills the json config file fed to ironic so that it knows how to boot the blades. In the baremetal case, the create_vm.yml playbook will only create opnfv vm. The variable vms_to_create holds that information. The variable baremetal_nodes specifies the physical nodes (empty when non baremetal deployments) 2 - For PXE to work, we create a file called baremetalstaticips that has the mapping between mac address from servers and its ip. That file is moved into the dnsmasq config directory Change-Id: I0e788db1deb50769c183b71524a68ac0b925f8aa Signed-off-by: Manuel Buil <mbuil@suse.com>