summaryrefslogtreecommitdiffstats
path: root/xci/playbooks/get-opnfv-scenario-requirements.yml
AgeCommit message (Collapse)AuthorFilesLines
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-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-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 Degirmenci1-4/+4
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-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-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-12Move contents of os-nosdn-ovs into os-nosdn-nofeatureFatih Degirmenci1-9/+29
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-05Merge "xci: Allow variable overrides from external scenarios"Markos Chandras1-1/+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-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-10-19xci: Clone all XCI scenarios in advance similar to a-r-rMarkos Chandras1-0/+61
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>