Age | Commit message (Collapse) | Author | Files | Lines |
|
The IDF files contain DNS information so we should respect that when
we configure the various XCI nodes. The DNS information is also a
list instead of a string so treat it as such.
Change-Id: I1c4d5eb600baaca35b2838dcafa7a75e59bf6783
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
We are using two variables which have a similar scope:
- create_image_via_dib
- use_prebuilt_images
We could use one of them and not both. create_image_via_dib is selected
because it also exists in upstream bifrost
use_prebuilt_images = false is the same as create_image_via_dib = true
use_prebuilt_images = true is the same as create_image_via_dib = false
Change-Id: Ieaab78f1dc2d199746a2b13ebc82e9dc615d92e9
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
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>
|
|
The creation or not of the IPA image does not depend on the value of the
use_prebuilt_images. This variable is intended to control the following
call to bifrost-create-dib-image role.
I added a few comments to clarify what we are doing in each call to the
bifrost-create-dib-image role
Change-Id: Id66e1a969ca279a055640481719f118744eedf38
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Deployers may want to use a different DNS server so allow them to
override the ipv4_nameserver option. If the variable is not set,
then we use the libvirt DNS if we are behind a proxy, otherwise
we default to the Google DNS.
Change-Id: I96cf63758902d4aae3d155b2e8beef650449ebc9
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
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>
|