summaryrefslogtreecommitdiffstats
path: root/xci/installer/osa/playbooks
AgeCommit message (Collapse)AuthorFilesLines
2018-04-30xci: Remove intermediate scenarios tasks fileMarkos Chandras1-1/+9
Now that the scenario role is recorded as a local fact, we can include the role directly directly so we don't need the the intermediate file anymore. deploy-scenario:os-nosdn-nofeature installer-type:osa Change-Id: Ia3c5658826f115538b2a103d987ee8f33d3048b9 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-27xci: Add XCI OSA variables fileMarkos Chandras1-0/+1
We can use an XCI specific YAML file to add OSA options which are common across flavors. Right now, it only overrides the default openSUSE mirror to use a more stable one. Change-Id: Iae7d542787ead33be1e64cdeda60761aa401cfde Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-17xci: osa: Fix OpenStack-Ansible bootstrapMarkos Chandras1-0/+1
Commit 269b5fc033b1ee8d14d9d4694f4f0d3765866c0a ("xci: installer: osa: Fix status report when bootstrapping OSA") removed the 'chdir' parameter by accident and this broke the OpenStack-Ansible bootstrapping. This patch brings the missing parameter back. Change-Id: I0ecfa0eb4c91a9f1dfa2d86a8a50bacdbd224533 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-13xci: installer: osa: Fix status report when bootstrapping OSAMarkos Chandras1-3/+0
Fixes the following ansible-lint warning [WARNING]: While constructing a mapping from /home/devuser/releng- xci/xci/installer/osa/playbooks/configure-opnfvhost.yml, line 113, column 7, found a duplicate dict key (args). Using last defined value only. We also remove the changed_when value since we now use 'args' to get proper status report. Change-Id: I382e3183b66e590462fbcb8663d53cade0e5d92c Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-10Merge "xci: osa: Move SSL certification tasks to a new file"Manuel Buil1-19/+4
2018-04-10xci: osa: Fix conditional for copying OSA files to OPNFV hostMarkos Chandras1-3/+3
The conditional was wrong since it was being treated as a string instead of actually evaluating it as a boolean value. Change-Id: I59802f467a77ae755886e4cc389c2406e9d17d4c Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06xci: osa: Move SSL certification tasks to a new fileMarkos Chandras1-19/+4
The tasks for creating and managing the XCI SSL certificates can be shared between installers so move them to a common file. Change-Id: I9df82517e737681420429a992aa8d68e78528fd4 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06Merge "xci: osa: Fix task status when bootstrapping OpenStack-Ansible"Markos Chandras1-0/+4
2018-04-04xci: osa: Fix task status when bootstrapping OpenStack-AnsibleMarkos Chandras1-0/+4
The bootstrap script from the OpenStack-Ansible repository creates several things in /opt/ansible-runtime and /usr/local/bin so we can check if the final 'openstack-ansible' symlink exists in order to report a proper status for that task and even skip if everything is prepared already. Change-Id: I4ca3a733746f8d757aa1156b533e4b4de90188e6 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-04xci: osa: Use Ansible modules to create ssl certificatesMarkos Chandras1-24/+21
Ansible already provides modules to create ssl certificates so we can use these instead of running the openssl commands directly. Moreover, we can drop all the tasks which create the ssl directories since there are being created by the openssl package which also creates the appropriate symlinks. Finally, there is no need to generate the certificate on localhost if only the OPNFV host consumes it, so move these steps to the appropriate playbook. Change-Id: I0045945c502013be3d76440876e894a44a092690 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-03xci: osa: Move tasks for managing SSH keys to a new fileMarkos Chandras2-60/+4
The tasks that manage the SSH keys are common across hosts and also common across different installers. As such, lets move them to a new file so we can share them more easily. Change-Id: If235877394f224a47a2f2b8de748a2330eabcec1 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-28xci: osa: Simplify tasks for copying OSA configuration filesMarkos Chandras1-65/+48
We can use a loop to copy all these files instead of multiple tasks. This simplifies the playbook quite a bit. Change-Id: I5f0d387ac090d81fc577b5ebeaeb6131e75cffa1 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-28xci: Use proper Ansible modules to manage SSH keysMarkos Chandras2-42/+66
We can use the 'user', 'slurp' and 'authorized_key' modules to manage the various SSH configurations across the hosts instead of using command line tools. Change-Id: I2dde4d584fc336e267868607d5a58f5ee2c1feed Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-26xci: playbooks: Fixes various ansible-lint warningsMarkos Chandras1-16/+43
In preparation for adding support for the 'ansible-lint' tool we fix various problems in our playbooks to make the tool happy before we make it mandatory. Some of the problems that are fixed here are - [ANSIBLE0011] All tasks should be named - [ANSIBLE0012] Commands should not change things if nothing needs doing - [ANSIBLE0013] Use shell only when shell functionality is required - [ANSIBLE0010] Package installs should not use latest installer-type:osa deploy-scenario:os-nosdn-nofeature Change-Id: I66c759d3932a414b81b2846393d2d98ce80c0b6d Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-22Merge "xci: osa: Configure the ARA callback plugin on OPNFV host"Fatih Degirmenci1-0/+21
2018-03-22xci: osa: Configure the ARA callback plugin on OPNFV hostMarkos Chandras1-0/+21
The OSA deployment is driven by the OPNFV host so we need to install and configure the ARA plugin there as well. Change-Id: Ib583f5771a8c2da7531f0a42612d7c0b34fb4898 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-22Move bootstrap-scenarios.yml to common playbooks directorywutianwei2-28/+1
Move bootstrap-scenarios.yml from installer/osa/playbooks/bootstrap-scenarios.yml to playbooks/bootstrap-scenarios.yml as a common playbook. So we can use this file to bootstarap k8s-* scenarios, instead of creating a new file under installer/kubespray/playbooks/bootstrap-scenarios.yml Change-Id: Ic31ee00e1a0863f48fb86298d7c00fa8420fa28a Signed-off-by: wutianwei <wutianwei1@huawei.com>
2018-03-21Clean up opnfv ansible vars and switch to lowercaseFatih Degirmenci3-48/+48
This change removes the variables that are not used in any of the playbooks/roles from opnfv ansible vars. Apart from that, all caps ansible vars replaced with lowercase ones and impacted playbooks/roles are updated. installer-type:osa deploy-scenario:os-nosdn-nofeature Change-Id: I99ebdc155b3903176ac5940b64cef0c0f3aa0f0d Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-20Add proxy supportVictor Morales2-0/+34
In some cases the XCI development environment can be located behind a corporate proxy resulting in a additional layer to consider to configure. These changes pretend to include proxy support for all linux distros in all the posible flavors. Change-Id: Iab469268809ac471d09e244bb3ccd83de1a41b88 Signed-off-by: Victor Morales <victor.morales@intel.com>
2018-03-17Merge "xci: osa: Simplify OpenStack host playbooks"Fatih Degirmenci2-35/+17
2018-03-17xci: osa: Simplify OpenStack host playbooksMarkos Chandras2-35/+17
The configure-targethost playbook is configuring all the OSA hosts so we can simplify all that by introducing a new 'openstack' host group with the controller and the compute nodes and configure all of them in parallel. Change-Id: I21f8709e7649b041575dab45fc4e070aa01e0a6f Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-17xci: osa: Drop haproxy workaroundMarkos Chandras1-6/+0
There is no reference on the actual upstream problem so lets assume this is fixed and drop the workaround we had locally. Change-Id: I3f71ea2e6fdc67e342f014e572f74760a78d3816 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-16xci: Copy XCI environment to deployment hostsMarkos Chandras2-0/+9
The XCI hosts may need some of the XCI env variables to perform certain tasks so dump the XCI environment to /root/xci.env file and make that available to every host on the deployment. Change-Id: I286a01ca7da8ff206438c261798167f5e4daf7f2 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-13xci: Merge configure-network and syncronize-time rolesMarkos Chandras2-10/+4
Those roles were too small and only used as part of the host bootstrapping process. As such, we merge them into a common 'bootstrap-host' role which can be used to prepare the hosts after the initial deployment Change-Id: Ifc84cf40b98ced91b31aae699dc28e9642380550 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-12Merge "Combine vars setting installer type in INSTALLER_TYPE"Fatih Degirmenci1-1/+1
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-03-12xci: Drop the python-crypto dependencyMarkos Chandras1-3/+0
The upstream pw-token-gen tool doesn't need python-crypto anymore since e9f957861b4160640f6debb2b939084ec43b43b2 ("Make pw-token-gen.py more random") so we no longer need to install that package. Change-Id: Ib53f246db999ff8ecfed2e3f62143c780c483fbd Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-10xci: OSA: Ensure proper constrains are applied to pip installationsMarkos Chandras1-0/+2
We need to make sure that the pip packages that we install are compatible with the OSA components. Change-Id: I87e80dc9b8fb862d9f9039d835b0908f752de3ca Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-10xci: Move functest required packages to the functest roleMarkos Chandras1-16/+6
The docker packages that we install in the OPNFV VM are needed by functest so add them to the related role. Change-Id: I6ebe76fd030859f757d41ecf20c30ab76888ee9c Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-02xci: Make few of OpenStack-Ansible components optionalMarkos Chandras1-4/+5
Ironic and Horizon are not quite needed for a functional deployment and they are not currently required by functest so we can remove them from the default deployment. Change-Id: I171483f7b774951f84687529e98cb519afa48043 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-01os-odl-bgpvpn scenario supportPeriyasamy Palanisamy1-0/+4
- 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>
2018-02-23xci: osa: configure-opnvhost: Set time in the opnfv nodeMarkos Chandras1-0/+2
Set the time properly in the opnfv node like we do for the target hosts Change-Id: I97d9f875dbb37db3cedd87e5915bc5b5f9a7a0ad Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-01-31deploy kubernetes in XCIwutianwei1-75/+0
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 Chandras5-0/+342
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>