| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The current configuration only dumps the booting info into a file and
the pty does not work (i.e. virsh console opnfv returns a failure
because it cannot find a character device). After some investigations,
it is apparently impossible to have both active:
https://github.com/Mirantis/virtlet/issues/249
Therefore, we should remove the pty part of the xml. To connect to the
VM in case of network problems, we can always use vnc.
Apart from that, the console part is not necessary as libvirt will
create that one for us
Change-Id: I80a59163b4ba4e6bff34cb5378893201e93ddb87
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
opnfv vm requires connectivity to two physical interfaces of the host.
These interfaces are:
1 - admin, where DHCP requests will arrive from blades to do PXE boot
2 - mgmt, which connects to the mgmt of the blades to do the ansible
configuration
To achive this, it is required:
1 - Two libvirt networks that connect to two different linux bridges.
The important physical interfaces are connected to them. The
interfaces name is fetched from the idf
2 - Two templates representing the new libvirt networks
(net-mgmt.xml.j2 and net-admin.xml.j2)
3 - Two interfaces defined in vm.xml.j2
Change-Id: I9037aa36802cfde44717b9394bab79b22d7dfaab
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
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>
|
Manuel Buil