Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
Functest requires ODL variables to run the ODL healthcheck which is
mandatory for all ODL scenarios
We require this patch to be merged first:
https://gerrit.opnfv.org/gerrit/#/c/63175/
Change-Id: Ibb95d621f952c1d921dcb175fcf6c8ad30c2e234
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Ceilometer is a dependency in the networking-odl repo and thus we
require the ceilometer component to be deployed for all the scenarios
including odl
deploy-scenario:os-odl-nofeature
installer-type:osa
Change-Id: I3281ceec07f72512fba3a804957a0f8ac36b509e
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
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>
|
|
|
|
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>
|
|
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>
|
|
If we want to have connectivity to the flat provider network in
openstack, we need this parameters
https://docs.openstack.org/openstack-ansible-os_neutron/latest/app-openvswitch.html
Change-Id: I2c747011428b87252134b9f08a9ed820110dbe68
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
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>
|
|
1. set kubenet the k8s network plugin
2. set istio_enable to true
Change-Id: I244c6c1adfb5c992e1748d198cc1d7f8271f56ee
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Change-Id: I41ba60a9f49034aa84f852baf17786f678622579
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
When doing the ansible lookup, if the variable does not exist, an empty
string is returned. That is a bug which must be fixed:
https://github.com/ansible/ansible/issues/17329
Until then, we initialize the variable
Change-Id: I92c43d15559600ff1583e1560c032377dc22793c
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
All the external scenarios are developed and maintained in corresponding
project repos under scenarios folder. In order to handle generic and external
scenarios in same way, we need to move generic scenarios into scenarios
folder in this repo.
Change-Id: I30064d3e3105a88279e40384a8efb888cc3bcc68
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|