Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|