summaryrefslogtreecommitdiffstats
path: root/xci/infra/bifrost/infra-provision.sh
AgeCommit message (Collapse)AuthorFilesLines
2018-10-15[Baremetal] Modify interaction with bifrost rolesManuel Buil1-3/+11
Change some of the variables when calling opnfv-virtual.yml and baremetal=true: 1 - We want to configure DHCP mapping between ip and mac when doing baremetal. The create-nodes role will generate a file with that mapping for us (baremetalstaticips) 2 - Don't download the standard IPA image but build one with Fedora (only one that works in ericsson-pod2) when doing baremetal 3 - Wait for the blade to complete its booting. Its ssh port becomes available with the IPA provision but that is not the final state. We need to wait until the required distro gets installed. When not doing baremetal, this is fine as the VMs boot very fast with the chosen distro but for baremetal it takes a while (ericsson-pod2 servers take around 2 minutes to finish all BIOS booting). The playbook wait-for-baremetal.yml does this. Change-Id: I5536517209ff7f46ec034554d29566707778e397 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-10-03[Baremetal] - Change roles and playbooks namesManuel Buil1-2/+2
A few playbooks and the create-vm-nodes role should change the name to reflect the new reality once the baremetal patches are merged. The playbooks that must change the name are: - xci-prepare-virtual.yml - xci-create-virtual.yml Change-Id: Iaed1f93561fa9d39c7916e0643a5445cdddf4f97 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-09-21Add idf and pdf to the xci-create-virtual.ymlManuel Buil1-0/+2
This patch complements this other: https://gerrit.opnfv.org/gerrit/#/c/62575/2 We require the pdf and the idf (when doing baremetal) in the create-vm role, so we should propagate that variable to the playbook that triggers those roles Change-Id: I15806d386db4e6b11192829f2dbc61662bffec2b Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-06-28Use PDF to set up the XCI VMsManuel Buil1-5/+63
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-03-20xci: Move cleanup script outside of bifrostMarkos Chandras1-4/+0
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>
2018-03-20Add initial support for multiple infra deployersMarkos Chandras1-0/+25
bifrost is currently the only way to deploy the infrastructure but in the future other solutions will be added so we need to do some preparation for XCI integration. Change-Id: I961dd42157c924d88747074ddba6a318f8b537ac Signed-off-by: Markos Chandras <mchandras@suse.de>