summaryrefslogtreecommitdiffstats
path: root/xci/installer/osa/files/noha
AgeCommit message (Collapse)AuthorFilesLines
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-09-04xci: osa: Restore self-signed XCI certificateMarkos Chandras1-0/+2
This reverts commit cc583f30f881ba956fb4f1402aa4dd1608b27da2. We still need to have control over the generated certificates so lets keep creating our own. deploy-scenario:os-nosdn-nofeature installer-type:osa Change-Id: I9e730bce2dba578ca0b561b168eaf1c2eca1282d
2018-09-03Revert "xci: osa: Disable haproxy ssl configuration"Markos Chandras1-5/+2
This reverts commit 42501f0ef7e0f0729b1c780102fb9713ef383fb3. This also removes the entire SSL management code and we let the haproxy_server role generate the certificates for us. We also need to bump the openrc role to include an upstream patch which fixes the openrc template file. deploy-scenario:os-nosdn-nofeature installer-type:osa Change-Id: I9bb590c9f1d5bc63519cfb4794dc15f794cc5b07 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-07-04xci: osa: Disable haproxy ssl configurationMarkos Chandras1-1/+3
The self-signed certificates are causing troubles so until we implement a proper certificate chain in XCI we should disable the SSL endpoints. Change-Id: Ife4ef78de1569121c435a806924a3f90917fd85b Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-05-09xci: osa: Add initial dynamic inventory from PDF/IDF filesMarkos Chandras2-40/+0
The PDF and IDF files contain all the information we need for the virtual XCI deployment, so we can use it to create a dynamic inventory and get rid of all the static ones which could easily get outdated as PDF and IDF files evolve over time. This inital version of the dynamic inventory contains a lot of unnecessary generated information but we do that in order to ease the migration from static files to the dynamic inventory. The dynamic inventory will be improved in the future as we consume more and more information from the PDF and IDF files. Change-Id: Id9f07a61c67a5cffcbc18079a341e5d395020a27 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-21Use package_state:present to avoid package installation issuesFatih Degirmenci1-0/+3
Using package_state:present should give our jobs better chance to finish on time and perhaps improve the overall deployment times even. Change-Id: Ifa4e01318fe364a91c32f5326024d34c364e25c8 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-17xci: osa: Simplify OpenStack host playbooksMarkos Chandras1-0/+4
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-13xci: Fix group for the OPFNV hostMarkos Chandras1-1/+1
Ansible gets upset if we use the same name for a host and a group so add the OPNFV host to the deployment group. This fixes the following warning: [WARNING]: Found both group and host with same name: opnfv Change-Id: Idbaff712d40e8234721332aee6d10d5ba44c62ce Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-02-21xci: osa: Do not wipe cinder volumesMarkos Chandras1-0/+1
When a volume is removed, cinder will fill the entire disk with 0s. This can slow down the volume removal process. Since we do not care what happens with the volume after it's being removed, we don't need to wipe it at all. Change-Id: I5ef1b01a18cdf2694252b450ca4f1c6a37090f71 Link: https://docs.openstack.org/cinder/latest/sample_config.html Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-01-08xci: Rename 'nfvi' to 'installer'Markos Chandras7-0/+432
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>