summaryrefslogtreecommitdiffstats
path: root/xci/config/env-vars
AgeCommit message (Collapse)AuthorFilesLines
2019-09-01Bump ansible to 2.7.8Fatih Degirmenci1-1/+1
Most recent Kubespray requires minimum 2.7.8 ansible version. installer-type:kubespray deploy-scenario:k8-calico-nofeature JIRA: XCI-5 Change-Id: I8bf790ba93849758a4d3964f4949294e1d9f396d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2019-09-01Refactor k8s scenario implementationFatih Degirmenci1-1/+1
This change updates the scenario logic for basic k8s scenarios that enables the use of various network plugins. The change simply stops copying k8s-cluster.yml over but instead operates on the existing/original k8s-cluster.yml and updates kube_network_plugin in place. This makes it easier to maintain the scenarios and more importantly unblocks us from bumping kubespray and kubernetes versions. Please note that opnfv-scenario-requirements.yml contains version and the refspec of the corresponding change in releng-xci-scenarios repo so this change must be verified properly and if it passes CI, it needs to be amended, updating k8-calico-nofeature scenario's version to master and submitted. And then the change in releng-xci-scenarios can properly be verified. https://gerrit.opnfv.org/gerrit/#/c/releng-xci-scenarios/+/68418/ installer-type:kubespray deploy-scenario:k8-calico-nofeature JIRA: XCI-20 Change-Id: I1f851d20f5f7bc256199303581b05659091fddf9 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2019-08-01Introduction of Openstack-helm as installernikoskarandreas1-0/+6
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>
2019-03-25Use functest:hunter for openstack/rockyFatih Degirmenci1-1/+2
deploy-scenario:os-nosdn-nofeature installer-type:osa Change-Id: Icebfbbd151c53b9ca3f38c7fdb107cb1f51b2b3e Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-09-18Switch to Functest HunterFatih Degirmenci1-0/+1
A new var FUNCTEST_VERSION is introduced to jobs to control the version to use for Functest. Change-Id: Ice7aa9f910db2353ce3d0bef198bef9fa3efe9fd Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-09-14xci: Drop custom XCI certificatesMarkos Chandras1-2/+0
OSM requires a CA even when we create a self-signed certificate. We don't actually need to do that since HAproxy and friends can create the whole chain for us, so we can finally get rid of this playbook. installer-type:osa deploy-scenario:os-nosdn-nofeature Change-Id: I14a3adbe3492cd6c562c5167c42dd45756e8e3dd Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-08-30xci: Bump Kubespray SHA and sync Ansible versionsFatih Degirmenci1-2/+2
This change - bumps kubespray version to 8b3ce6e418ccf48171eb5b3888ee1af84f8d71ba, taking Kubernetes version from 1.10.2 to 1.10.4. - pins Ansible version used by Kubespray to same Ansible version as the rest. The var kept as is in case if we need to pin Kubespray to a different Ansible version in future. installer-type:kubespray deploy-scenario:k8-calico-nofeature Change-Id: Iefbe82f0b9b10296e4362bca07630047c56630ac Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-08-30xci: Bump OSA and bifrost SHAsMarkos Chandras1-2/+4
This change - bumps OSA SHA to b9d9269528ecbe04b2638a73c2b0f49839f27422 - bumps bifrost SHA to 0d0cfd908d10a670668619c575fd338d1ff328b7 - Pins Ansible to 2.5.8. OSA is using 2.5.5 which has a bug in the pause module so we need to use something newer. Change-Id: Idf05bbef880db11de4a41464ae5080aa21a0613c Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-08-21Move OSM variables to os-nosdn-osm scenarioFatih Degirmenci1-1/+0
This change removes OSM variables from releng-xci repo since they are declared in os-nosdn-osm scenario itself in releng-xci-scenarios repo. In order for this change to be verified, below change must be submitted. https://gerrit.opnfv.org/gerrit/#/c/61205/ installer-type:osa deploy-scenario:os-nosdn-osm Change-Id: I9f3a1dbdfecfb2bb08cc215758bdc52aefcdf697 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-08-21xci: Bump OSA and bifrost SHAsFatih Degirmenci1-1/+4
This change - bumps OSA SHA to cbfdb7dc295ff702044b807336fab067d84a3f20 (mostly based on Rocky RC1) - bumps bifrost SHA to c1c6fb7487d5b967624400623fd35aabf303b917 - pins Ansible to 2.4.6.0 - switches to ollivier/functest-healtcheck since OS is bumped to Rocky Change-Id: Icc14e3e794b489dafd78b426c54051a3732ccb1a Signed-off-by: Fatih Degirmenci <fdegir@gmail.com> Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-08-09Integrate os-nosdn-osm scenarioFatih Degirmenci1-0/+1
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>
2018-05-16xci: kubespray: Switch kubespray to dynamic inventoryMarkos Chandras1-2/+2
The kubespray installer contains one inventory per flavor. We can get rid of these files and use the dynamic inventory similar to OSA. Moreover, we extend the dynamic inventory to read additional group variables per flavor if necessary. This way we can still pass additional information to inventory on per-flavor basis. This also fixes a typo in the 'IDF' file. We also need to bump Ansible for kubespray since the version we were using is having troubles with dynamic inventories. Change-Id: Ic58101555f81aec5fee3c193608440aa89bbe445 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-18Merge "Export OPENSTACK_REQUIREMENTS_VERSION"Fatih Degirmenci1-0/+2
2018-04-11Set additional variables for functestFatih Degirmenci1-2/+11
CI_LOOP, NODE_NAME, and BUILD_TAG are needed for logging info to console. FUNCTEST_MODE and FUNCTEST_SUITE_NAME are important for stating what level of testing we do for verify and merge jobs. Change-Id: Iaa5499155b4b94a1cfc6b5c70fe6f8f7417502a6 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-04-11Export OPENSTACK_REQUIREMENTS_VERSIONVictor Morales1-0/+2
The hash value for the OpenStack requirements project is consumed for other projects which can be out of the openstack-ansible scope. This change creates the OPENSTACK_REQUIREMENTS_VERSION variable using the openstack_services.yml value as default one. Change-Id: I4544bcc3f14c107aab8ebba1dced1ba203f07f68 Signed-off-by: Victor Morales <victor.morales@intel.com>
2018-03-14Merge "xci: config: evn-vars: Dynamically determine the Ansible version"Markos Chandras1-1/+1
2018-03-12xci: config: evn-vars: Dynamically determine the Ansible versionMarkos Chandras1-1/+1
There is no good reason why we should pin the Ansible version without the ability to override it. OpenStack Ansible is doing a great work testing Ansible releases as early as possible so we could benefit from that work and use whatever Ansible our pinned OSA uses. Change-Id: I4677dbefc68f7140417ece34d013ca9674baab43 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-12Combine vars setting installer type in INSTALLER_TYPEFatih Degirmenci1-1/+1
Change-Id: I330bc036f901d4ba61bc94ee6e085cadf54b4d8b Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-02-22xci: config: env-vars: Allow git urls overridesMarkos Chandras1-7/+11
It's useful to be able to pick alternative git repositories for the deployment. This facilitates testing in-flight features or simply save some bandwidth by keeping internal mirrors. Change-Id: I3eb2e48da1e91f6a52bb3ba14c22f0902c6cd777 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-01-31deploy kubernetes in XCIwutianwei1-0/+5
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>
2018-01-08xci: Rename 'nfvi' to 'installer'Markos Chandras1-1/+1
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-03[XCI] move osa files into xci/nfvi/osa/fileswutianwei1-1/+1
we maybe introduce other NFVI in the future in XCI. it is necessary to put the nfvi files to corresponding directory xci/nfvi/$NFVI/files, otherwise the files directory will be confused. Change-Id: Iea98167ff0bc8d338a94fe1c064ac0ab396c53d3 Signed-off-by: wutianwei <wutianwei1@huawei.com>
2017-12-19Rename variable OPNFV_SCENARIO to DEPLOY_SCENARIOFatih Degirmenci1-1/+1
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-13xci: Fix checkout location for OpenStack-AnsibleMarkos Chandras1-3/+5
The OPENSTACK_OSA_PATH only makes sense on localhost. As such, when we use it on playbooks that operate on remote hosts, the result is not predictable. However, we rsync the entire releng-xci repository to the opfnv host so we can make everything predictable by simply clone everything in advance in the .cache directory. That directory is then rsync'd to the opnfv host. As such, we can repurpose the OPENSTACK_OSA_PATH to point to the path into the OPNFV host. Moreover, all external repositories are being cloned to .cache/repos so we can eliminate some variables in order to simplify the code. Finally, we bring back the ability to use an external OSA repository for development purposes. Change-Id: Ieef3e22ae2085f6735185634d555cfc0d4b69b39 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-12xci: Restore the OPNFV_SCENARIO variableMarkos Chandras1-0/+1
The variable was accidentally removed in ab3c9ad0f9a4 so bring it back. Change-Id: I48e4b8dd68969c8e5336e5e571a73f037fb65988 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-12-12Move contents of os-nosdn-ovs into os-nosdn-nofeatureFatih Degirmenci1-1/+0
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-11xci: Use local playbooks for XCI deploymentsMarkos Chandras1-2/+14
Previously, we used to clone the releng-xci repository under a directory in /tmp, copy our changes to that repository and then run the xci-deploy.sh script from it. However, this made things far too complex for deployers and developers since some playbooks were used from the local repo whereas others were used from teh /tmp checkout. By running everything from our local repository simplifies things a lot since we can directly test our changes and also reduces the code we have in our playbooks. Change-Id: If16aa51b2846c170676df82d25cb90e26b1568b2 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-11-23Integrate inband os-nosdn-ovs scenarioPeriyasamy Palanisamy1-0/+1
Change-Id: I9253edf028fce571e04f9f82103a94952e05d2d4 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2017-09-16xci: xci-deploy.sh: Configure dib so VMs match the hostMarkos Chandras1-5/+0
In preparation for adding SUSE support, we need to configure the dib build process to build images which match the host's OS. Change-Id: I4944245d526f916b2033abc5d219fa7a69db54ab Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-09-15xci: env-vars: Bump Ansible version to 2.3.2.0Markos Chandras1-3/+4
Now that bifrost uses virtual env for Ansible we can go ahead and bump the Ansible version to match the one from OSA so we can make use of the latest features. Furthremore, we stop passing ANSIBLE_VERBOSITY to the command line since it's an environment variable so Ansible already knows about it. Change-Id: I52d9a211fc0ced1f7830f6945b2943f35d38109b Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-09-14Generate and use certificates for OSAYolanda Robla1-0/+3
Instead of making OSA to generate self signed certs, bring our own and pass them. By this way we will be able to trust in that certs, and start consuming OpenStack easily. It will also generate proper openrc file to source it and start consuming the cloud properly. Change-Id: Ic72a8b05e6efb222926fc5fa0800e033b2dbd22f Closes-Bug: RELENG-266 Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
2017-08-16Refactor releng/prototypes/xci to releng-xci/xci in the codeDave Urschatz1-2/+3
These changes are needed as part of migrating xci from releng repo to the releng-xci repo. They cover: - README updates - Re-point configuration from releng/prototypes to releng-xci The changes have been tested as follows: - XCI_FLAVOR=aio - OPENSTACK_OSA_VERSION=adfaa66d6108f87599e0595591b39cad2c8fb658 xci: aio has been installed real 107m5.310s user 11m50.180s sys 4m11.152s ubuntu@rack-IRA2-SymKloudBlade4:~/releng-xci/xci$ Change-Id: I8fd86c2442ee3a7c6996eedb6510dbc6eebd30b0 Signed-off-by: Dave Urschatz <dave.urschatz@cengn.ca>
2017-08-11prototypes: xci: Make CLEAN_DIB_IMAGES variable configurableMarkos Chandras1-1/+0
The CLEAN_DIB_IMAGES variable determines whether the /httpboot or /tftpboot directories will be removed before running the xci-deploy script. This forces XCI to re-create the target OS images. We moved this variable from env-vars to user-vars since this is something that users normally want to tweak in their deployments. Change-Id: Ia48bd63979e3837aab7e47c906c2501e7c7dd0e1 Signed-off-by: Markos Chandras <mchandras@suse.de>
2017-08-11xci: Introduce XCI_LOOP variable to control what to do properlyFatih Degirmenci1-0/+1
XCI has different jobs/loops to run - patchset verification jobs (currently bifrost and osa in future) - periodic jobs (bifrost and osa) - daily jobs (for OPNFV platform deployment and testing) The same scripts/playbooks used by XCI will also be used by developers. We need to do different things depending on the context the scripts and playbooks are executed. - periodic jobs will use latest of everything to find working versions of the components. (periodic osa will use unpinned role requirements for example) - daily jobs will use pinned versions in order to bring up the platform and run OPNFV testing against it. (daily deployment will use pinned versions and role requirements for example) - developers might choose to use pinned versions or latest Depending on what loop we are running, we need to do things differently in scripts and playbooks. This variable will help us to do this in easy way. We can of course do pattern matching of the job name but it will not work if the scripts are used outside of Jenkins. The default loop for non-Jenkins execution is set to daily as we want developers to use working versions unless they change it to something else intentionally. Change-Id: Iff69c77ae3d9db2c14de1783ce098da9e9f0c83d Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-08-11xci: Configure daily job to use xci scriptsFatih Degirmenci1-0/+1
Daily jobs are now switched to using xci-deploy.sh script together with the environment variables, playbooks, and so on. These jobs do not set any version for any of the component as the point with these jobs is to test the platform itself, not the tools. DIB related stuff is still left as parameters to deploy job for SUSE and CentOS jobs so we can override what is set by xci depending on the distro. Change-Id: I5a5292e6bae8fdd052858108db409e8d495fbf24 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-08-11xci: Create playbook to destroy, create and provision VM nodesFatih Degirmenci1-0/+3
This change moves preparation (cloning repos, combining opnfv/bifrost with openstack/bifrost), destroying and creating VM nodes from the script into a separate playbook. This requires the host to have ansible installed. The version of ansible to install using pip currently matches to what bifrost uses but it is hardcoded and needs to be fixed properly. The reason for having this as a playbook to simplify the script and increase the reuse. This playbook will be used for - developer sandbox - periodic bifrost jobs to run against latest on given branch and promoting bifrost sha1 to pin later on - daily jobs to run using pinned versions of bifrost Change-Id: I033f12290dfea19d4c74be80eea7203211c0369e Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-08-11xci: Rename the deployment host to opnfvFatih Degirmenci1-1/+1
Reflect the changes to other impacted files as well. Change-Id: I106f4e47fe5c75d288f4878fe6ec9f8ff39c652e Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-08-11xci: Add/update variables to tool, user, and flavorsFatih Degirmenci1-3/+8
Updates - RAM allocations for the flavors mini and noha increased to 12GB. - Distro variables introduced to tool as it will be used by the CI and the developers. - LOG_PATH and RUN_TEMPEST are now available in user variables. Change-Id: I4a73d7b79761d81f605cdb3fa9771ca40e9f9f02 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-08-11xci: Enable node provisioning and shuffle/rename stuffFatih Degirmenci1-0/+12
This change enables node provisioning using bifrost based on the chosen flavor. Other changes include - move flavor specific stuff (playbooks, inventory, vars) into their own folders so it is easier to copy them over. - rename flavors and get rid of xci from them. - introduce env-vars to keep variables that are not really user variables. Please note that this patch contains empty files and so on due to still trying to find best way to structurei things. Apart from this, there will probably be lots of duplications here and there which will be taken care of once things settle. Change-Id: I04a5d422e5b018439bafea5e68e65255ae38d22b Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>