Age | Commit message (Collapse) | Author | Files | Lines |
|
The latest patches in xci provided support for the basic scenario
os-nosdn-nofeature when using the osh installer
deploy-scenario:k8-calico-nofeature
installer-type:osh
Change-Id: Ia37718ae73b91da223bd26715208bb3975a15998
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
deploy-scenario:k8-calico-nofeature
installer-type:osh
Change-Id: Ie198ee7e25579f1438561f71fd965518b067fe42
Signed-off-by: Nikos Mimigiannis <nmimi@intracom-telecom.com>
|
|
This patch creates a new installer tree in xci that uses
openstack-helm to deploy openstack on a kubernetes cluster.
USAGE: Export INSTALLER_TYPE=osh, DEPLOY_SCENARIO=k8-calico-nofeature
and XCI_FLAVOR=noha or mini and run xci-deploy.sh as in documentation.
deploy-scenario:k8-calico-nofeature
installer-type:osh
Change-Id: I212f70eb51c2a38c798c11367d2ebb8bf5f4a1de
Signed-off-by: nikoskarandreas <nick@intracom-telecom.com>
|
|
https://gerrit.opnfv.org/gerrit/#/c/63505/
The os-odl-sfc_osm scenario has been verified in the previous
patchsets of this commit. This patch needs to be merged after
adding OS variables to the post-deployment playbook.
https://gerrit.opnfv.org/gerrit/#/c/63135/
installer-type:osa
deploy-scenario:os-odl-sfc_osm
Change-Id: I14e83357c9e1db6e31890b5f126b9e405e124594
Signed-off-by: Venkata Harshavardhan Reddy Allu <venkataharshavardhan_ven@srmuniv.edu.in>
|
|
using kubespary to deploy the istio, kubespary support to deploy istio
installer-type:kubespray
deploy-scenario:k8-nosdn-istio
Change-Id: Id8c04936187c89fafa921dada382a0e9e11aab27
Signed-off-by: wutianwei <wutianwei1@huawei.com>
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
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>
|
|
The flavor all-in-one (aio) hasn't been maintained well and
the stability of it is in question. This change disables the
flavor aio and sets the default flavor to mini.
It is important for XCI to enable the aio back in order to help
users who want to try XCI but don't have big enough machine to
go for bigger flavors. However, we need to verify all flavors
for acceptable user experience so the flavor can only be enabled
back once this happens.
Change-Id: I053c8fec78876dea71439f1f1bd737a105254ad4
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Put OpenStack scenarios and Kubernetes scenarios together.
installer-type:kubespray
deploy-scenario:k8-canal-nofeature
Change-Id: I6a47b0b3703e30ac9a2be53012687217a085ee88
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I73a7c58a27c9018d0b131dc3c8bb65da91488c35
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I5f18e1060cb45246a15584fdd69c6c6bd3427001
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
deploy-scenario:os-odl-nofeature
installer-type:osa
Change-Id: I33e10589092ee1027fa2f27fc3c000a0031eaf38
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
deploy-scenario:os-odl-sfc
installer-type:osa
Change-Id: I583c8620f29b0735a52c64309d2113f56d38be1e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
The releng-xci scenarions have been moved to their own repository so we
delete the copies from the releng-xci repository and also update the
opnfv-scenario-requirements to point to the new repository.
deploy-scenario:os-nosdn-nofeature
installer-type:osa
Change-Id: I1b7b3182a5e0c5b346c00b5734fd0cd3fdd5c98b
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
It is important to test and pin the versions tagged by the projects
to ensure we have a single version of XCI with pinned versions of the
scenarios for all the projects are recorded.
Same exercise will be done for all the scenarios and then scenarios will
be unpinned from the tags to let the development continue.
deploy-scenario:os-odl-bgpvpn
installer-type:osa
Change-Id: I9350bc53fa87836ad36259b259edf506dd99790a
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
openSUSE is supported in kubespray so we add it to the
k8s-canal-nofeature scenario.
installer-type:kubespray
deploy-scenario:k8-canal-nofeature
Change-Id: I626e98beef220f724ae72329be42b959a03ce87b
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
openSUSE is supported in kubespray so we add it to the
k8s-calico-nofeature scenario.
installer-type:kubespray
deploy-scenario:k8-calico-nofeature
Change-Id: I1ffa972b7bb1f949645bb585d2a8688cf4580342
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
installer-type:kubespray
deploy-scenario:k8-flannel-nofeature
Change-Id: Ie47efe4759b2cf52421cd2edf5e7817442b0026f
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
installer-type:kubespray
deploy-scenario:k8-calico-nofeature
Change-Id: Ief8557149fd47faab43f8f4bedcf6466dac2275f
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
In the past, there were cases where the Git mirrors were
out of sync with Gerrit which caused the use of outdated
repos. This change switches all scenarios to Gerrit.
Apart from that, it also aligns the urls across all scenarios.
Change-Id: I5301630a71446df8668f16c81bf26d81bcea8031
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
add the k8-nosdn-noeature and k8-canal-nofeature roles under scenarios directory
run different roles to configure the k8s-cluster according to the deploy scenario
installer-type:kubespray
deploy-scenario:k8-canal-nofeature
Change-Id: Ia96b01f79fb058e045c5b7d9d9aecb7f15a21e63
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Add experimental support for openSUSE until the upstream PR
is accepted
installer-type:kubespray
deploy-scenario:k8-nosdn-nofeature
Change-Id: Icd3698d882d249a18be77560ba0ba52159893816
Link: https://github.com/kubernetes-incubator/kubespray/pull/2380
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
- Integrate XCI with outband od-odl-bgpvpn role
- Install python-neutronclient on opnfv vm for the
openstack bgpvpn specific cli commands
Change-Id: Ib737349e2b2429bd366881f1e3657daf8c5c30ac
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
Kubespray already supports the CentOS distribution so make the
necessary changes to allow it to work in XCI.
Change-Id: I3cf1db055a5fd563b107b46456bc3e18eeafb3ab
Co-authored-by: Markos Chandras <mchandras@suse.de>
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
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>
|
|
Changes that make it possible to run XCI on CentOS:
- Remove the check on xci-deploy.sh script that exists on RedHat family
(including CentOS) and making the error into a warning.
- Add centos to a distro in opnfv-scenario-requirements
Change-Id: Ief6f1e50d8c7c9d8787641827e57682a6e0549e4
Signed-off-by: Tapio Tallgren <tapio.tallgren@nokia.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: I4ea6b421a24f41ea3ca925ea98d961e1a34e7876
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
Change-Id: I9253edf028fce571e04f9f82103a94952e05d2d4
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
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>
|