| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
NOTE: Armband moves MaaS IPs to x.y.z.2 (from x.y.z.3) due to address
overlap with IPMI static IPs residing in the same range.
Change-Id: I2fc9539afe921d2704e7f5ff615ccd86d0914b7b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, refresh "AArch64 virtio NIC names sync" to include
changes for ODL-L3 scenario recently added in Fuel@OPNFV.
Change-Id: Ic221b330d9968204b7d4da16a26454b2cf8b88eb
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
FIXME: This should be converted into a dynamic configuration read
from the universal POD descriptor in securedlab, once that is ready.
Until then, just align the public network configuration used by the
virtual POD with the Enea lab configuration specific to arm-virtual2
(i.e. public network on 10.0.9.0/24).
NOTE: Replace the gateway at 10.16.0.1 (now 10.0.9.1) with the same
IP address as our lab's gateway (10.0.9.254), to keep both possible
network layouts in sync (using all virtual networks created via
virsh, respectively our lab's static config).
This will ensure deploys continue to work in both enviroments.
Also, since our gateway resides at 10.0.9.254, trim the DHCP pool
range for the public network to not include that address.
To pass bridge information from CI, Fuel@OPNFV deploy scripts need
some small adjustments as well.
While at it, rebase our patches on top of latest Fuel@OPNFV changes.
Change-Id: I92f01dd819ebf41b1da68d3b934fb10a23257e33
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Fix libvirt 3.x compatibility issues by explicitly setting the CPU
model to host-passthrough via virt-install.
Change-Id: I0e52cbabb0bf42b36dd2b9b5045dc18878e21884
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I99b6052a26169888c137f874889872107c7df931
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ic4066acc2716e5f3f497fba9799691e0258d3011
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- p/fuel: classes: AArch64: virtio-pci-net sync
- p/reclass-system-salt-model: Add Armband repos
- mcp/config: AArch64: Use UEFI arm64 image
Also, allow removal of VMs booted via guest UEFI (OVMF or AAVMF).
While at it, bump default vCPU number from 2 to 6.
- lib.sh: AArch64: Use VGA video mode for guests
On AArch64, there is no Cirrus video, so use VGA mode instead.
For now, we install vgabios package no matter the arch, although
it is only used on AArch64.
On Debian systems, also fix a missing link for vgabios-stdvga.bin.
Based on previous Armband work from [1].
- lib.sh: AArch64: virt-install: Use virtio-net-pci
AArch64 virt tools (i.e. libvirt) default to "virtio-mmio", instead of
"virtio-net-pci", at least before libvirt 3.x (see [2]).
Without PCI bus info, we can't really enforce a specific order for
the guest ethernet devices.
Moreover, predictable network interface naming is out of the question
with virtio-mmio, as there is no bus information to rely on.
Therefore we will enforce "virtio-net-pci" on AArch64, instead of
the default "virtio" (which translates into "virtio-mmio" currently).
- salt.sh, user-data: Add Saltstack arm64 repo
- salt.sh: Clone armband repo, apply patches from it
- classes: virtual: AArch64: virtio-pci-net sync
Since AArch64 will be using virtio-net-pci NIC model for guests,
predictable interface naming yields a slightly different scheme.
Update all configuration to reflect this.
FIXME:
- Use https for fetching Armband GPG keys!
- Revise the patching mechanism, make things more dynamic.
[1] https://github.com/opnfv/armband/blob/danube.2.0/patches/fuel-library/
arm64-bug-fixes/0002-Install-vgabios-and-link-for-aarch64.patch
[2] https://www.redhat.com/archives/libvir-list/2016-August/msg00931.html
Change-Id: If5aae22066f75732652201a78357c4931438d58d
Signed-off-by: Guillermo Herrero <Guillermo.Herrero@enea.com>
Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
Alexandru Avadanii