summaryrefslogtreecommitdiffstats
path: root/xci/playbooks
AgeCommit message (Collapse)AuthorFilesLines
2018-01-31Merge "deploy kubernetes in XCI"Fatih Degirmenci1-0/+100
2018-01-31deploy kubernetes in XCIwutianwei1-0/+100
This commit introduces kubespray into XCI. k8s install currently assumes k8s install and OpenStack install cannot coexist. If XCI_INSTALLER is set to "kubespray" and DEPLOY_SCENARIO is set to "k8-nosdn-nofeature" the xci-deploy.sh would install kubernetes instead of OpenStack. The version of kubernetes is beta release v1.9.0 currently according to the master of kubespray it only support the ubuntu now. Opensuse and centos still need to develop and test. This patch create the directory xci/installer/kubespray, the related files of kubespray would be placed to it. The xci/installer/$installer/playbooks/configure-localhost.yml was moved to xci/playbooks/configure-localhost.yml as a common yaml file. You can modify some parameters according your need in xci/installer/kubespray/files/k8s-cluster.yml to deploy cluster. When deploying kubernetes, it would download the kubespray to releng-xci/.cache/repos/kubespray. If your flavor is Ha, it will download haproxy_server and keepalived to xci/playbook/roles, which setup haproxy service for kubernetes. Change-Id: I24d521a735d7ee85fbe5af8c4def65f37586b843 Signed-off-by: wutianwei <wutianwei1@huawei.com>
2018-01-29Adapt to change in functestManuel Buil1-0/+1
Functest requires to read the variable TEST_DB_URL from the env. variables: https://gerrit.opnfv.org/gerrit/#/c/49757/ Change-Id: Idbfc2df989f5b2a8e6ddd2d9a9a70526dd9bf1f4 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-01-26xci: run-functest: Add required functest packagesMarkos Chandras1-0/+7
The package requirements are the same across distros so we simply hardcode them in the task. Fixes the following problem: fatal: [opnfv]: FAILED! => {"changed": true, "cmd": "/root/run-functest.sh", "delta": "0:00:09.150226", "end": "2018-01-26 14:01:18.758704", "failed": true, "rc": 125, "start": "2018-01-26 1 4:01:09.608478", "stderr": "/root/run-functest.sh: line 14: wget: command not found Change-Id: Ib07acac18f8ece1111ee0706766f32005d0ac1da Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-01-24xci: Integrate functestFatih Degirmenci5-11/+19
This change integrates functest in most easiest and messy way to get it up and running to bring functest into CI. The reason for this is that there are strange failures during functest healthcheck and it is important to look into those rather than beautifying how functest is integrated at this phase. Change-Id: I42e993be4aa15da022fa1e0069338447780f177e Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-01-22Merge "xci: get-opnfv-scenario-requirements.yml: Check if facts are set"Markos Chandras1-2/+5
2018-01-19xci: get-opnfv-scenario-requirements.yml: Check if facts are setMarkos Chandras1-2/+5
When the user selects an invalid combination then some facts may not be set so the deployment may fail in a crypt way like in the following case fatal: [localhost]: FAILED! => {"failed": true, "msg": "The conditional check 'deploy_scenario_installer' failed. The error was: error while evaluating conditional (deploy_scenario_installer): 'deploy_scenario_installer' is undefined\n\nThe error appears to have been in '/home/opnfv/releng-xci/xci/playbooks/get-opnfv-scenario-requirements.yml': line 114, column 11, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n when: item.installer == XCI_INSTALLER\n - set_fact:\n ^ here\n"} Change-Id: I931376d99bb178b15c4a9a71d47b48b01b858e4e Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-01-15Create CentOS networking configurationTapio Tallgren3-0/+48
Change-Id: If8c0de44c313fdc22b1c7443b12d42769035c5b0 Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
2018-01-15Rename centos.yml to redhat.yml in configure-nfs/varsTapio Tallgren1-0/+0
'redhat' as a ansible_os_family covers both the RedHat distros and CentOS. Change-Id: I2ab56024d2c0f1f40a014a236cfd94ef38daad04 Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
2018-01-08xci: Rename 'nfvi' to 'installer'Markos Chandras1-9/+9
Using 'installer' to describe the tool that will deploy the foundations of a particular XCI scenario is more appropriate than NFVI which normally describes both the physical and virtual resources needed by an NFV deployment. Change-Id: Ib8b1aac58673bf705ce2ff053574fd10cb390d71 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-01-03xci: Record distribution and NFVI information for scenariosMarkos Chandras1-6/+28
A scenario may only support certain NFVIs or distributions so we need a mapping with all these things so we know what can be tested and where. Change-Id: Ibf1b640b762085f58627e05e1d2ca13edfc4d716 Signed-off-by: Markos Chandras <mchandras@suse.de>
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-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-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 Chandras5-340/+0
2017-12-21xci: OSA: Move all the OSA specific playbooks to the NFVI directoryMarkos Chandras5-340/+0
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-19Rename variable OPNFV_SCENARIO to DEPLOY_SCENARIOFatih Degirmenci2-8/+8
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-14Merge "xci: Add flavor information for scenarios"Markos Chandras1-0/+20
2017-12-14xci: Add flavor information for scenariosMarkos Chandras1-0/+20
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: Drop AIO specific playbookMarkos Chandras1-0/+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 Chandras3-37/+38
2017-12-13xci: Fix checkout location for OpenStack-AnsibleMarkos Chandras3-37/+38
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 Chandras1-0/+12
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-12Merge "Move contents of os-nosdn-ovs into os-nosdn-nofeature"Markos Chandras2-12/+32
2017-12-12Move contents of os-nosdn-ovs into os-nosdn-nofeatureFatih Degirmenci2-12/+32
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 Buil1-0/+4
Change-Id: I5a3f533f61b6572d8070fe5f0a306ef9d418ced8 Signed-off-by: Manuel Buil <mbuil@suse.com>
2017-12-11xci: Use local playbooks for XCI deploymentsMarkos Chandras5-135/+76
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: playbooks: provision-vm-nodes: Simplify the provision VM playbookMarkos Chandras1-26/+1
The provision-vm-nodes playbook is only responsible for running bifrost to provision the XCI virtual machines. As such, drop all the extra tasks that this playbook performed in order to simplify it. This also drops the XCI_EXTRA_VARS_PATH variable since it had a rather obscure usage and there is not much value in passing inventory information outside of XCI. All these will be handled in the scenarios themselves. Change-Id: If5cb381a3d1e101100eb04478d80fb3045cdfaf8 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-05Merge "xci: Allow variable overrides from external scenarios"Markos Chandras1-1/+3
2017-12-04Merge "xci: playbooks: Copy scenarios instead of symlinking them"Markos Chandras1-5/+3
2017-12-01xci: Allow variable overrides from external scenariosMarkos Chandras1-1/+3
All scenarios are being cloned to XCI_SCENARIOS_CACHE so look there for the various override files. This will allow external scenarios to influence the XCI environment. Change-Id: I39a48ce55baaa29d09737ce6232867ef1165f099 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-01Merge "integrate inband os-odl-nofeature scenario"Markos Chandras1-0/+4
2017-11-30integrate inband os-odl-nofeature scenarioPeriyasamy Palanisamy1-0/+4
Change-Id: I4ea6b421a24f41ea3ca925ea98d961e1a34e7876 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2017-11-30xci: playbooks: Copy scenarios instead of symlinking themPeriyasamy Palanisamy1-5/+3
Previously, the scenarios were symlinked from the checked out location to {{ playbook_dir }}/roles. However, the symlinks were pointless since they only exist in our local releng-xci directory. The roles much also be present in OPNFV_RELENG_PATH which is the place where the deployment happens. We use 'rsync' to copy our local releng-xci directory to the remote one so our roles can be automatically be placed there if we copy them instead of symlinking them. Change-Id: I735db71eedfaa51d7196761aa2af8329d86cb775 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com> Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-11-30Merge "xci: Drop OPNFV_RELENG_DEV_PATH variable"Markos Chandras3-9/+3
2017-11-29Make sure the docker service is startedManuel Buil1-0/+6
We are installing the docker package but not checking if it is started The service name for the three distros is the same but I still added the variable in each distro variables file to keep best practices Change-Id: I0c73069ea7edc366e824cf39d14d24d1416fd6c3 Signed-off-by: Manuel Buil <mbuil@suse.com>
2017-11-29xci: Drop OPNFV_RELENG_DEV_PATH variableMarkos Chandras3-9/+3
The OPNFV_RELENG_DEV_PATH variable was used to point to a releng-xci development repository. However, people normally set the current directory as the development one and they almost always want to test the current code in XCI. Using an secondary releng-xci tree as development repo is a very obscure case and it normally complicates things. As such, let drop this option and always use the current repository for development purposes. Change-Id: If111bf29a32a5f6ea28694f191645af0c6a87abc Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-11-23Integrate inband os-nosdn-ovs scenarioPeriyasamy Palanisamy1-0/+5
Change-Id: I9253edf028fce571e04f9f82103a94952e05d2d4 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2017-11-23Merge "Use RUN_TEMPEST global env"Fatih Degirmenci1-0/+8
2017-11-22Use RUN_TEMPEST global envVictor Morales1-0/+8
The RUN_TEMPEST global environment has been defined in *user-vars* but never used in the playbooks. This change pretends to enable the use of that value. Change-Id: I49ca092546494c0cdcb015a549828bf79fa5f889 Signed-off-by: Victor Morales <victor.morales@intel.com>
2017-11-22Add br-vlan-veth to the br-vlan bridge in openSUSEManuel Buil1-0/+2
br-vlan-eth was created but not added to any bridge, therefore floating ips were not working as it was impossible for the OVS in the compute to get the ARP messages coming from the gateway of the public network Change-Id: Ia0828b7e96359dc10012ac52bf0e5d4f2c5419cb Signed-off-by: Manuel Buil <mbuil@suse.com>
2017-11-22Remove the share flagManuel Buil1-1/+1
When creating the external network for functest testing purposes, it does not need to be shareable between tenants because functest uses routers and floating ips. Therefore, better remove it to avoid confusion Change-Id: I18a1fd34a52ddae2527ee3580a9d1a2b649e61b6 Signed-off-by: Manuel Buil <mbuil@suse.com>
2017-11-17playbooks: configure-opnfvhost: Be explicit when copying user filesMarkos Chandras1-1/+1
The flavors may contain deployment specific user_variables.yml files so we should only copy the generic one in the common tasks and leave the rest for scenarios to copy them if necessary. Change-Id: I39e3e090dc40d4f13bb42028a24e8574e19cf6dd Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-11-14Merge "Fix permissions on SUSE network script"Fatih Degirmenci1-0/+1
2017-11-14Merge "Integrate ceph in XCI"Markos Chandras4-0/+76
2017-11-09Fix permissions on SUSE network scriptManuel Buil1-0/+1
We were not getting the eth12 interface in the computes because the network-config-suse file did not have executable rights: -rw-r--r-- 1 root root 300 Nov 9 14:40 network-config-suse Change-Id: Ia796123b331b67bc442d3506b944f0430f7a5f32 Signed-off-by: Manuel Buil <mbuil@suse.com>
2017-10-26Integrate ceph in XCIwutianwei4-0/+76
Openstack ansible support to deploy ceph. The purpose of this patch is to configure the ceph, just like we configure other openstack components. The default is to not deploy ceph. If you want to deploy ceph you just need to export XCI_CEPH_ENABLED=true before running xci-deploy.sh. When deployed successfully, the openstack storage will use ceph. Change-Id: Ifd8d16fdce2914b6316842e72bbfd93228ea059d Signed-off-by: wutianwei <wutianwei1@huawei.com>
2017-10-19xci: playbooks: Add generic playbook for scenarios to plug their rolesMarkos Chandras2-0/+11
The new bootstrap-scenarios.yml playbook is aimed to be used by scenarios to configure themselves right before we proceed with the bootstrapping. This way we can avoid having scenario specific stuff into the generic code. Change-Id: I3026013719a50458c65405439712270f25f569ff Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-10-19xci: Clone all XCI scenarios in advance similar to a-r-rMarkos Chandras2-0/+69
In order to plug the scenarios' roles properly, we need to have all roles physically present in advance. As such, add a opnfv-scenario-requirements.yml file which can be used to populate the roles directory with all the scenarios. Change-Id: I0cdadb63849e4565c31559817660d23217879053 Signed-off-by: Markos Chandras <mchandras@suse.de>