summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2019-09-02Merge changes from topics "bump-kubespray", "refactor-k8s-scenarios"Fatih Degirmenci7-31/+84
* changes: Bump kubespray version to bring k8s v1.15.3 Bump ansible to 2.7.8 Refactor k8s scenario implementation
2019-09-02Promote Panagiotis Karalis as XCI committerFatih Degirmenci1-0/+5
Panos has been an active contributor to XCI, working with XCI itself and supporting Dovetail to use XCI. Some of his contributions can be seen on Gerrit and on OPNFV maillists. https://gerrit.opnfv.org/gerrit/#/q/owner:panos.pkaralis%2540gmail.com https://lists.opnfv.org/g/opnfv-tech-discuss/search?d=0&ev=false&q=panos+xci&startdate=2018-08-22&enddate=2019-08-22 Change-Id: Iada997f82836a0c5424e6bce90c31fbf1424b03c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2019-09-01Bump kubespray version to bring k8s v1.15.3Fatih Degirmenci1-3/+3
installer-type:kubespray deploy-scenario:k8-calico-nofeature JIRA: XCI-6 Change-Id: I8546feb53312cce7267a43c1c91d502326c83995 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2019-09-01Bump ansible to 2.7.8Fatih Degirmenci1-1/+1
Most recent Kubespray requires minimum 2.7.8 ansible version. installer-type:kubespray deploy-scenario:k8-calico-nofeature JIRA: XCI-5 Change-Id: I8bf790ba93849758a4d3964f4949294e1d9f396d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2019-09-01Refactor k8s scenario implementationFatih Degirmenci7-28/+81
This change updates the scenario logic for basic k8s scenarios that enables the use of various network plugins. The change simply stops copying k8s-cluster.yml over but instead operates on the existing/original k8s-cluster.yml and updates kube_network_plugin in place. This makes it easier to maintain the scenarios and more importantly unblocks us from bumping kubespray and kubernetes versions. Please note that opnfv-scenario-requirements.yml contains version and the refspec of the corresponding change in releng-xci-scenarios repo so this change must be verified properly and if it passes CI, it needs to be amended, updating k8-calico-nofeature scenario's version to master and submitted. And then the change in releng-xci-scenarios can properly be verified. https://gerrit.opnfv.org/gerrit/#/c/releng-xci-scenarios/+/68418/ installer-type:kubespray deploy-scenario:k8-calico-nofeature JIRA: XCI-20 Change-Id: I1f851d20f5f7bc256199303581b05659091fddf9 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2019-08-26Merge "Provide osh support for baremetal"Manuel Buil2-2/+75
2019-08-23Merge "Support for py3"Manuel Buil4-11/+18
2019-08-23Provide osh support for baremetalManuel Buil2-2/+75
Add osh into the idf description so that we can deploy osh in baremetal environments deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: Id0830ac4744122d149736b1d515af8a1dcbe9eb2 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-22Support for py3Manuel Buil4-11/+18
This patch provides support for py3 in the deployment host and the OPNFV VM. Some extra changes will need to happen in the future when distros disclose how they will react to the py2 expiration. * virtualbmc version is upgraded to 1.5 because 1.3 is not compatible with py3 * The dynamic inventory is slightly modified because it was using functionality that changes in py3 * pip3 check is removed as Ansible now works with py3 deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: I34178ebc357b0a299c0017d6f9e596b815c77b3b Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-22Fix bug for baremetal deploymentsManuel Buil1-3/+3
OSH cannot be deployed because the name is currently a string instead of a variable that should be interpreted by ansible deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: Ib0ec71d181d62ee1830861427ca6d4f64625fb4e Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-14Separate vxlan trafficManuel Buil2-0/+12
Currently, all traffic is going through the untagged interface. However, we are creating interfaces for the different traffic. This patch moves the private traffic (VM-VM), which normally uses vxlan tunnels, to the interface created for that deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: I680698d0bf7ab8045d4ca8f7b5bea8c1e1881d71 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-13Fix the labels for nohaManuel Buil1-1/+1
Both nodes are openstack-helm-node-class=primary. That creates problems when deploying neutron because two l3 agents and dhcp agents are deployed which sometimes results in problems deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: Id13ee3cf308f5120061176302573739d7c5a5ed3 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-12Set the correct labels for nohaManuel Buil2-14/+26
In noha mode, node1 and node2 is used for controller and compute roles. This patch changes that making node1 only controller and node2 only compute. It also modifies a bit the syntax to make it more ansible friendly deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: I3f40f59ea3c167914ea4c810f7dda60c75fb7175 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-09Fix noha deploymentManuel Buil1-3/+17
JIRA:XCI-11 noha was not passing the tempest test, however, nobody is testing that test upstream. We should use the test that it being really tested upstream deploy-scenario:k8-calico-nofeature installer-type:osh xci-flavor:noha Change-Id: I551e966e81a93120e96027b32096ec18b21bd3bd Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-08Merge "Fix problems when redeploying with osh"Manuel Buil3-8/+30
2019-08-07Fix problems when redeploying with oshnikoskarandreas3-8/+30
When deploying manually after a previous deployment, keys and fingerprints of the VMs clash with the stored ones. This patch clears the relevant files and also fixes an issue with keepalived role which failes ansible lint when already cached. deploy-scenario:k8-calico-nofeature installer-type:osh Signed-off-by: nikoskarandreas <nick@intracom-telecom.com> Change-Id: I9331a5b7d0ac66a35064dfe7f62dd78a461e570c
2019-08-07Merge "os-nosdn-nofeature can be supported by osh"Fatih Degirmenci1-0/+8
2019-08-06Merge "Remove hardcoded ips"Manuel Buil1-2/+2
2019-08-06Merge "Move variable definition to vars"Manuel Buil2-15/+18
2019-08-06Merge "Add the required dashes in yaml files"Manuel Buil6-0/+6
2019-08-06mbuil's id was wrong, and he was removed.Aric Gardner1-1/+1
The id was wrong so updating the INFO.yaml removed his rights. I have added him by hand for now. Signed-off-by: Aric Gardner <agardner@linuxfoundation.org> Change-Id: Ib8bd94cae10b2ded36d4d162bb28b2edc24ddf64
2019-08-06os-nosdn-nofeature can be supported by oshManuel Buil1-0/+8
The latest patches in xci provided support for the basic scenario os-nosdn-nofeature when using the osh installer deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: Ia37718ae73b91da223bd26715208bb3975a15998 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-06Remove hardcoded ipsManuel Buil1-2/+2
We should use the Ansible variables whenever possible instead of hardcoding values like IPs deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: Iee5f179b0b36d2fcbf9b2eca82a3c31cefd83229 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-06Move variable definition to varsManuel Buil2-15/+18
Ansible best practices recommend doing the definition of variables in the vars directory instead of directly in the tasks deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: Ia5e215f8492a901b8c75ac06ee23258249f7f09a Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-06Add the required dashes in yaml filesManuel Buil6-0/+6
deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: I0423ab27186316d40c93cce847d7cb9fa7308df1 Signed-off-by: Manuel Buil <mbuil@suse.com>
2019-08-06Merge "Update committer list for releng-xci"Manuel Buil1-15/+0
2019-08-05Support of opensuse in OSH-XCINikos Mimigiannis8-2/+50
deploy-scenario:k8-calico-nofeature installer-type:osh Change-Id: Ie198ee7e25579f1438561f71fd965518b067fe42 Signed-off-by: Nikos Mimigiannis <nmimi@intracom-telecom.com>
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-07-30Update committer list for releng-xciFatih Degirmenci1-15/+0
Yolanda, Peri, and Tianwei stepped down from the project as committers. Change-Id: Ie320028332a38e8cd323fe821cc215dff61c3931 Signed-off-by: Fatih Degirmenci <fdegir@gmail.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>