summaryrefslogtreecommitdiffstats
path: root/xci/files/xci-destroy-env.sh
AgeCommit message (Collapse)AuthorFilesLines
2018-08-10Force remove ~/.vbmc folder in case if it doesn't existFatih Degirmenci1-1/+1
Change-Id: If87afa892a0c39d082cb1563e1c019f46b742169 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-08-10xci: xci-destroy-env.sh: Update virtualbmc pathMarkos Chandras1-9/+9
Bifrost no longer installs on the deployment host so we don't need to look into the bifrost venv for a vbmc installation. Moreover, XCI uses virtualenv by default, so we should only look there for vbmc. Finally, we should clear vbmc config files from previous deployments since that could leave artifacts behind. Change-Id: I4cd35636a65e1823c9e4ca9a7c5b17d4b103c6a2 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-06-28Use PDF to set up the XCI VMsManuel Buil1-1/+1
This patch is doing the first work item of the spec: https://github.com/opnfv/releng-xci/blob/master/docs/specs/infra_manager.rst It creates the required VMs by XCI to afterwards deploy the VIM. It does that by reading the pdf provided by the user. - It is currently assumed that the OS for the VM will be installed in the first disk of the node described by the pdf - It is assumed that the opnfv VM characteristics are not described in the pdf but in a similar document called opnfv_vm.yml - All references to csv from bifrost-create-vm-nodes were removed Change-Id: I46a85284e4ce7df21cbf66f66619b35f74251e68 Signed-off-by: Manuel Buil <mbuil@suse.com> Co-Authored-by: Markos Chandras <mchandras@suse.de>
2018-05-17xci: Wipe repositories at the beginning of the deploymentMarkos Chandras1-0/+2
We should not wipe the repositories in the localhost playbooks since it makes it somewhat hard to debug problems. We should do that at the beginning of the deployment to ensure that we start without any stale git data. Change-Id: I70b2ac77284a9ca304d6aa68dbf1654f59260dc4 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-09Redirect virsh output to /dev/null in cleanup scriptFatih Degirmenci1-4/+4
deploy-scenario:k8-nosdn-nofeature installer-type:kubespray Change-Id: I540eb8bad2f35d7029ae8a2148c431f7664fbad0 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-23xci: install: Move all pip installations to virtualenvMarkos Chandras1-1/+3
Now that all pip installations are managed in the same way we can move them inside a global virtual environment to further isolate the XCI artifacts from the rest of the system. Moreover, we further simplify the initial package installation to install everything at once instead of calling the package manager for every single package that we need. Change-Id: I6a170d2439fae8b0653f3141e0e8bb8ead67657e Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-22xci: files: xci-destroy-env.sh: Remove VMs from all flavorsMarkos Chandras1-2/+8
If we switch from one flavor to another then some VMs may left behind so we need to cleanup the VMs from all flavors. Change-Id: I8b5d400b6d543b32b9cdaff73c3d173984357012 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-20xci: Move cleanup script outside of bifrostMarkos Chandras1-0/+78
The cleanup script has grown quite a bit over time and it now does more things than cleaning up old 'bifrost' artifacts to move it to the global files directory so it can be used by all installers. Change-Id: Ibf70ff255f14e798216cedc71fb7c5f5476b964a Signed-off-by: Markos Chandras <mchandras@suse.de>