summaryrefslogtreecommitdiffstats
path: root/xci/installer/osa/files
diff options
context:
space:
mode:
authorFatih Degirmenci <fdegir@gmail.com>2018-06-24 01:04:10 +0200
committerFatih Degirmenci <fdegir@gmail.com>2018-08-09 12:31:08 +0200
commit09cee3636fee20ba551e211c60f6e9942079cfb9 (patch)
tree4383cefd36c36d2a714614b5d6493489f8807464 /xci/installer/osa/files
parent21d793a1af489d8e68ad933adf7dfe10988344a4 (diff)
Integrate os-nosdn-osm scenario
This change integrates os-nosdn-osm scenario. The installation of OSM is done as post-deployment. This is achieved by the addition of the new playbook named post-deployment.yml in scenario role folder. This mechanism is available for all OpenStack scenarios. If anything needs to be done for a specific scenario as part of the post-deployment, it can be achieved by creating playbook post-deployment.yml. If post-deployment.yml exists in scenario role, the framework will run it once the regular deployment playbooks are run successfully. If the file does not exist, it will be skipped. The location of the post-deployment.yml is releng-xci-scenarios/<scenario>/role/<scenario>/tasks/post-deployment.yml This is only implemented for OpenStack scenarios currently and similar mechanism is needed for K8S scenarios as well which will be implemented in a separate change. installer-type:osa deploy-scenario:os-nosdn-osm Change-Id: I16780abffca39699eb2f38f662479f0e4d551504 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
Diffstat (limited to 'xci/installer/osa/files')
0 files changed, 0 insertions, 0 deletions