summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-01-03[XCI] move osa files into xci/nfvi/osa/fileswutianwei30-13/+14
we maybe introduce other NFVI in the future in XCI. it is necessary to put the nfvi files to corresponding directory xci/nfvi/$NFVI/files, otherwise the files directory will be confused. Change-Id: Iea98167ff0bc8d338a94fe1c064ac0ab396c53d3 Signed-off-by: wutianwei <wutianwei1@huawei.com>
2017-12-22xci: scenarios: Fix location when copying scenarios to rolesMarkos Chandras1-6/+6
The location where we were putting the scenarios was wrong as it was placing them in xci/playbooks/roles/$scenario/$scenario so in the end the Ansible couldn't find the role we were looking for. As a result, the role was never executed. Moreover, we can use the synchronize module instead of the shell which should be both faster and safer. Change-Id: I3d996652bb6a62d23e259da5674d94596dad4d8d Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-22Merge "xci: playbooks: Copy local changes to scenarios"Markos Chandras1-0/+12
2017-12-22Merge "xci: nfvi: OSA: Set 'pipefail' when SSHing on the OPNFV host"Markos Chandras1-6/+6
2017-12-22Merge "bifrost: Bump bifrost SHA"Markos Chandras2-63/+1
2017-12-22xci: playbooks: Copy local changes to scenariosMarkos Chandras1-0/+12
Make sure that any local changes to scenarios are being propagated to the checkouts. This should only happen when we are testing the 'master' branch of the scenario since it may be desirable to test a specific SHA in which case we shouldn't modify the checkout code. Change-Id: I4197f09a3e4d5a54c86905bc556b06e08948fbc2 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-22Merge "Bump sha on openstack-ansible-lxc_hosts"Markos Chandras1-1/+1
2017-12-21Bump sha on openstack-ansible-lxc_hostsTapio Tallgren1-1/+1
The commit 6b529de0315fe6cd12f6e78c00a5f2f2d3a01e28 in openstack-ansible-lxc_hosts reverts an earlier change that introduced systemd-networkd to lxc containers that run OpenStack services. This prevents the containers from being stopped (ie, lxc-stop fails until it times out), since systemd-networkd restarts. lxc-stop sends the SIGRT+3 message to the container which the container interprets as "halt". systemd-networkd conflicts with shutdown, so when the system tries to enter halt, systemd-networkd gets started again. As a result, the container does not shut down cleanly. This patch uses a version of openstack-ansible-lxc_hosts that does not use systemd-networkd in the containers. Change-Id: Ie85d2117ce2e6e8afa87810d690eab78e3b3be3d Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
2017-12-21xci: nfvi: OSA: Set 'pipefail' when SSHing on the OPNFV hostMarkos Chandras1-6/+6
We need to set the 'pipefail' option so if an SSH command fails we stop the deployment instead of silently ignoring it just because the right leg of the pipe succeeded. Change-Id: Iebc720fbd3e6e96fc7135a6cf15e3c0941974d2c Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-21Fix the parameter of scenario directorieswutianwei1-2/+2
1. the "+" and "'" will be part of the string in the path parameter of ansible. So the directories we create are not right. we need remove these char. 2. it miss the "{{" in ansible variable Change-Id: I30c9804450588c63f5f18c63c1d90cd869fad90e Signed-off-by: wutianwei <wutianwei1@huawei.com>
2017-12-21Merge "xci: OSA: Move all the OSA specific playbooks to the NFVI directory"Markos Chandras13-40/+228
2017-12-21xci: OSA: Move all the OSA specific playbooks to the NFVI directoryMarkos Chandras13-40/+228
Move all the playbooks that only make sense for OpenStack-Ansible deployments to the NFVI/OSA directory where they belong. This further disassociates XCI from OSA. Change-Id: Iab8b6dc81d9025a1d85608a98fb1eee0f1c6a69f Signed-off-by: Markos Chandras <mchandras@suse.de> Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-21xci: playbooks: Fix conditional for scenario/flavor factMarkos Chandras1-1/+1
We need to use proper jinja2 code to set the fact properly. Change-Id: I903233c0e059edf2af973ea9c08b8bd80795e1a9 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-20Merge "Rename variable OPNFV_SCENARIO to DEPLOY_SCENARIO"Fatih Degirmenci6-16/+16
2017-12-20bifrost: Bump bifrost SHAMarkos Chandras2-63/+1
Bump the bifrost SHA so we can get rid of the testvm.xml.j2 template which has now made it upstream. Change-Id: Ia9cdd999a5702f37125d38e0ba68bb31920d2117 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-20Merge "Pin os_heat role to the version with working policy"Fatih Degirmenci1-1/+1
2017-12-19Pin os_heat role to the version with working policyFatih Degirmenci1-1/+1
Upstream change modifying policy.json results in failures with several heat test case failures with functest healthcheck. https://review.openstack.org/#/c/526306/ Using the policy.json from the earlier commit seems to solve the failures which is this https://git.openstack.org/cgit/openstack/openstack-ansible-os_heat/commit/?id=0b3eb9348d55d6b1cf077a2c45b297f9a1be730d Change-Id: Iaac0911e73743d1b628cc8d4abe460a0a2a66a84 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-19Rename variable OPNFV_SCENARIO to DEPLOY_SCENARIOFatih Degirmenci6-16/+16
Rest of the OPNFV projects use the variable DEPLOY_SCENARIO so XCI should be aligned with them as well even though OPNFV_SCENARIO fits better than DEPLOY_SCENARIO. Change-Id: Id48c41fa8a1fa9493cfc7a4906f64b6d8ed27d64 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-19Update osa version files for master branch as wellFatih Degirmenci1-3/+3
This is needed in order to update the files before we attempt to run osa-periodic job. Change-Id: Ied5a53c294fd753039a6f79fa0ebce24b515cdba Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-18Merge "Increase ram of XCI VM and change disk cache type for all VMs"Fatih Degirmenci6-7/+7
2017-12-18Merge "bifrost: Set vCPU model to 'host-passthrough'"Markos Chandras2-0/+64
2017-12-18Merge "Add tacker to the list of components to install"Markos Chandras1-0/+1
2017-12-18Merge "xci: Move OpenStack-Ansible out of the main script"Markos Chandras3-182/+204
2017-12-18bifrost: Set vCPU model to 'host-passthrough'Markos Chandras2-0/+64
The default CPU model of QEMU GenuineIntel/QEMU Virtual CPU is not the best option for vCPU in terms of performance. As such, lets use the real host CPU. This has also been submitted upstream and the template should be removed once the upstream patch has been merged and the SHA for bifrost is bumped. Change-Id: I23d86933604c290d5650b73f420972d0a2b23dc8 Link: https://review.openstack.org/#/c/528677/ Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-18Increase ram of XCI VM and change disk cache type for all VMsFatih Degirmenci6-7/+7
These options seem to help with the functest execution within XCI VM. Change-Id: I3b9b6b02fc571feb42543025f8ab179c6db18e0a Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-15Add tacker to the list of components to installManuel Buil1-0/+1
Tacker is already part of the upstream setup-openstack.yml but as releng-xci overwrites it, tacker does not get deployed. Adding it to the setup-openstack.yml of releng-xci does not disturb the other scenarios as it will only be deployed when the tacker container is defined which only happens when deploying odl-sfc Change-Id: Ifd76fc49369c114c55e966eb20658d82c99e14cb Signed-off-by: Manuel Buil <mbuil@suse.com>
2017-12-15xci: scripts: start-new-vm: Use host-passthrough to use the real host CPUMarkos Chandras1-1/+1
The host-passthrough mode will allow the VM to use all the host cpu features so it should provide the best possible CPU performance. Change-Id: I6ecd0363d046aaefa08f9e97144aa9ca9f1afae5 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-15xci: Move OpenStack-Ansible out of the main scriptMarkos Chandras3-182/+204
In preparation for supporting more NFVIs in XCI, we need to make the main script NFVI agnostic. Right now, our NFVI is being deployed using bifrost+OSA so we keep bifrost in the main script since the hardware provisioning is NFVI agnostic (at least for now) but we move OSA to its own directory. This should allow more NFVI to plug into XCI by simply providing a nfvi-deploy.sh script. The user can select the preferred NFVI using the XCI_NFVI variable. Change-Id: Ieeacd3b22a64d363feff5d43ff23a80c39038837 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-14Merge "xci: Add flavor information for scenarios"Markos Chandras2-1/+32
2017-12-14Merge "xci: scripts: vm: Use virtio for disk and network I/O"Markos Chandras1-1/+1
2017-12-14xci: Add flavor information for scenariosMarkos Chandras2-1/+32
Scenarios may not support all XCI flavors so record that information per scenario basis. This will resolve failures when we try to deploy a scenario that doesn't support the selected flavor. JIRA: RELENG-338 Change-Id: I5f73b139ee6c1831896aa32147c4dc1368673d92 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-14xci: scripts: vm: Use virtio for disk and network I/OMarkos Chandras1-1/+1
This ensures that the virtio paravirtualization driver is used for both disk and network I/O which should provide the best performance since we no longer need to emulate a real bus or driver. Change-Id: Ic46a38f51b06cb4b848d87d890d23fec022b2f15 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-14xci: Drop AIO specific playbookMarkos Chandras2-46/+4
The configure-opnfvhost playbook which is used for all flavors except AIO can also be used for AIO if it's adapted to not configure networking on the host and also do not fail if there aren't any OSA variables files available so lets do all that in order to avoid duplicating code across flavors. Change-Id: I58379d8b52094294b9349494753ffcdd44982013 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-14Merge "xci: Fix checkout location for OpenStack-Ansible"Markos Chandras6-48/+50
2017-12-13xci: Fix checkout location for OpenStack-AnsibleMarkos Chandras6-48/+50
The OPENSTACK_OSA_PATH only makes sense on localhost. As such, when we use it on playbooks that operate on remote hosts, the result is not predictable. However, we rsync the entire releng-xci repository to the opfnv host so we can make everything predictable by simply clone everything in advance in the .cache directory. That directory is then rsync'd to the opnfv host. As such, we can repurpose the OPENSTACK_OSA_PATH to point to the path into the OPNFV host. Moreover, all external repositories are being cloned to .cache/repos so we can eliminate some variables in order to simplify the code. Finally, we bring back the ability to use an external OSA repository for development purposes. Change-Id: Ieef3e22ae2085f6735185634d555cfc0d4b69b39 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-13xci: Reduce noise during bootstrappingMarkos Chandras3-29/+24
There is too much noise when XCI is cloning repositories, installing packages etc so lets make the console output somewhat more readable. Change-Id: I15667e0349f943ad5488daf0e3cea9336c9166d1 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-12xci: Restore the OPNFV_SCENARIO variableMarkos Chandras1-0/+1
The variable was accidentally removed in ab3c9ad0f9a4 so bring it back. Change-Id: I48e4b8dd68969c8e5336e5e571a73f037fb65988 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-12Merge "Move contents of os-nosdn-ovs into os-nosdn-nofeature"Markos Chandras11-20/+41
2017-12-12Merge "Adapt to updated REST URL for OpenDaylight"Markos Chandras1-1/+1
2017-12-12Move contents of os-nosdn-ovs into os-nosdn-nofeatureFatih Degirmenci11-20/+41
This change fixes the scenario os-nosdn-nofeature by moving directories/files from os-nosdn-ovs to os-nosdn-nofeature. The contents of the files and variables are also either adjusted or removed in order to prevent impacts on CI. Change-Id: Icfde27f413c8f93d097f9f262c8cb1230b7fe59d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2017-12-12Connect sfc-odl scenario with xciManuel Buil2-0/+5
Change-Id: I5a3f533f61b6572d8070fe5f0a306ef9d418ced8 Signed-off-by: Manuel Buil <mbuil@suse.com>
2017-12-12Merge "bifrost: destroy-env.sh: Clean dib images by default"Markos Chandras1-2/+2
2017-12-12Merge "xci: Ensure we are in the root directory for bug reports"Markos Chandras1-0/+1
2017-12-12Merge "xci: Use local playbooks for XCI deployments"Markos Chandras10-170/+101
2017-12-12Merge "xci: playbooks: provision-vm-nodes: Simplify the provision VM playbook"Markos Chandras2-29/+1
2017-12-12Adapt to updated REST URL for OpenDaylightPeriyasamy Palanisamy1-1/+1
Change-Id: Iae7ca106174c09a73bc72075dca0a753c2280f20 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2017-12-11bifrost: destroy-env.sh: Clean dib images by defaultMarkos Chandras1-2/+2
The destroy-env.sh script is meant to clean the entire environment including the dib images that were built in a previous run. However, this step was only executed if requested exclicitly leaving old artifacts behind. As such, lets switch the default value in order to remove these images as expected. Change-Id: If3b91a621df50931ef3d666737cbc3bbea5d34b9 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-11xci: Ensure we are in the root directory for bug reportsMarkos Chandras1-0/+1
During the XCI deployment we change directories in too many places. As a result of which, when something breaks, we may be outside the releng-xci checkout directory so we need to enter it again for all the git commands to work. Change-Id: I6adcff396fc5d7cce8bb07353dec26b76b1825a4 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-11xci: Use local playbooks for XCI deploymentsMarkos Chandras10-170/+101
Previously, we used to clone the releng-xci repository under a directory in /tmp, copy our changes to that repository and then run the xci-deploy.sh script from it. However, this made things far too complex for deployers and developers since some playbooks were used from the local repo whereas others were used from teh /tmp checkout. By running everything from our local repository simplifies things a lot since we can directly test our changes and also reduces the code we have in our playbooks. Change-Id: If16aa51b2846c170676df82d25cb90e26b1568b2 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-11xci: Make it easier to use OpenStack-Ansible stable branchesMarkos Chandras2-1/+15
It seems it is desirable for projects to use stable OpenStak-Ansible and OpenStack releases in general. However, merely overriding OPENSTACK_OSA_VERSION doesn't work because role requirements and OpenStack services have to be adapted too. Despite the Documentation warning users about this, seems like nobody remembers to read and do the necessary steps. However, this leads to numerous invalid bug reports due to this stable/master mix. Lets try to help improving this situation by doing all the necessary ground work if we detect that we are using a stable branch. Change-Id: I2ba5d7e7942109973b6a6523aae2c01b65e61fe7 Signed-off-by: Markos Chandras <mchandras@suse.de>