aboutsummaryrefslogtreecommitdiffstats
path: root/scenarios/os-nosdn-osm
AgeCommit message (Collapse)AuthorFilesLines
2018-10-30OSM: use full_install_osm.sh script to install from masterVenkata Harshavardhan Reddy Allu1-1/+1
To install OSM from master branch we need to use full_install_osm.sh and specify the branch. installer-type:osa deploy-scenario:os-nosdn-osm Change-Id: I64dc0d643d02094c9acae6ed064763ff5004342e Signed-off-by: Venkata Harshavardhan Reddy Allu <venkataharshavardhan_ven@srmuniv.edu.in>
2018-10-26Register OpenStack as VIM to OSMVenkata Harshavardhan Reddy Allu4-0/+41
This patch creates osmrc file and registers the OpenStack as VIM to OSM. TODO: Currently we don't have a suitable way to find out the functioning status of OSM as soon it was installed. So we pause the execution of playbook for 2 minutes and then register OpenStack as VIM. As soon as healthchecks are added to Docker containers(upstream), we'll use them to identify the functioning status of OSM and modify the existing task. installer-type:osa deploy-scenario:os-nosdn-osm Change-Id: Ic38bd2c142f8b1c19bff125f08bab198c423fe5d Signed-off-by: Venkata Harshavardhan Reddy Allu <venkataharshavardhan_ven@srmuniv.edu.in>
2018-10-20xci: Use master branch of devopsVenkata Harshavardhan Reddy Allu1-4/+1
Till now we usually clone the osm-devops repo of v4.0.1 and run the OSM installer file from it. v4.0.1 isn't stable anymore. OSM (upstream) has moved to release branch model (v4.0 is the stable one now). Since the integration will be completed with another patch, we can move to the master branch. https://gerrit.opnfv.org/gerrit/#/c/63129/ installer-type:osa deploy-scenario:os-nosdn-osm Change-Id: I40a7ae3762774bb615638d575814ab13845ac844 Signed-off-by: Venkata Harshavardhan Reddy Allu <venkataharshavardhan_ven@srmuniv.edu.in>
2018-08-30Merge "Bring in the files from base scenario into os-nosdn-osm"Fatih Degirmenci5-4/+644
2018-08-21Add OSM variables to os-nosdn-osm scenarioFatih Degirmenci1-1/+6
OSM variables are currently in releng-xci. This change adds them to the scenario itself so they can be configured directly within the scenario. Another change will be send to remove corresponding variables from releng-xci repo. Change-Id: I33067954f53d21651e8b2d508fe25ac8eb4d9cb5 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-08-21Bring in the files from base scenario into os-nosdn-osmFatih Degirmenci5-4/+644
This change brings in the files from the base scenario os-nosdn-nofeature into os-nosdn-osm so the scenario becomes self-contained without requiring us to introduce a new mechanism to deploy the base scenario first and then do additional stuff for the child scenario. deploy-scenario:os-nosdn-osm installer-type:osa Change-Id: Ie14b25fac8a58b01f2ee1e5e89673fbd4ae931cf Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-08-08Create os-nosdn-osm scenarioFatih Degirmenci7-0/+178
The tasks added by this change - configure opnfv host by installing required OSM packages, configuring lxd and lxd bridge, making devuser member of lxd and docker groups - clone OSM devops repo and checks out specific version - execute install_osm.sh script with certain arguments to ensure script runs unattended The installation of OSM is based on https://osm.etsi.org/wikipub/index.php/OSM_Release_FOUR#Install_OSM_Release_FOUR Change-Id: I8897288f7d0cadc4931ca21de13a4f4418fff7a8 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>