summaryrefslogtreecommitdiffstats
path: root/xci/installer/osa/files/setup-openstack.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-10-19Introduce the Barbican in XCI for SFC-HA scenarioPanagiotis Karalis1-0/+1
The barbican OS component is introduced for SFC HA deployed scenario. The reason behind is that In HA scenarios we need Openstack Barbican to gather and store the fernet keys so Tacker can access them and be able to register new VIMs. deploy-scenario:os-odl-sfc installer-type:osa JIRA: SFC-131 Change-Id: Ife416fb2a7dc04ddadc93f962695aee4ed448501 Signed-off-by: Panagiotis Karalis <pkaralis@intracom-telecom.com>
2018-10-18xci: osa: Bump SHAs to the HEAD of the Rocky branchManuel Buil1-0/+1
Since Rocky, networking-odl depends on ceilometer and requires it to be installed. Therefore, all odl scenarios need to have ceilometer deployed. Once that is done, we can unfreeze n-odl repo. Besides, we need to introduce a SHA bump for neutron and ceilometer to include the latest changes to support this fix Ceilometer should be git cloned always, otherwise repo_build will fail as ceilometer is now part of requirements.txt [mchandras: Instead of just bumping selective network related roles, lets just do a complete sha bump for stable/rocky] deploy-scenario:os-odl-sfc installer-type:osa Change-Id: I81a39436e4ff648faabda4e82fce1d3f14615741 Signed-off-by: Manuel Buil <mbuil@suse.com> Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-02xci: Make few of OpenStack-Ansible components optionalMarkos Chandras1-0/+2
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-01-08xci: Rename 'nfvi' to 'installer'Markos Chandras1-0/+27
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>