Age | Commit message (Collapse) | Author | Files | Lines |
|
Not every CPU supports apparmor and
there is no real benefit when using it
only for fuel.
Change-Id: Ibb3221b85d8565f718df9b087aa324d0f606bdee
|
|
In the past virtio network driver cause problems when vlan segmentation
was used [1][2]. E1000 driver looks like safer choice.
[1] https://bugs.launchpad.net/fuel/+bug/1433593
[2] https://bugs.launchpad.net/fuel/+bug/1463316
Change-Id: I0a573e640309ad3caf2d67166cdaeaf285a6e6be
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Not all the flags are supported by
every machine. This patch removes
the specification of cpu and
lets libvirt decide what cpu
model is used.
Change-Id: I1f183560e47d58abcfe496838a815d3f3594ee1b
|
|
We need to revert this in order to be able to run virtual
deployments on Intel machine. The issue on Ericsson machine
needs to be looked into after the vacation period.
This reverts commit 6ffd176509318935eae6dd554a5fb70c255c6db3.
Change-Id: Ia0d33bee15f127016c3fda778b4327b5877f79f0
|
|
Im not sure who / how this value was changed, but when you are doing a virtual "AUTOMATED" installation, then the value needs to remain as the FUEL VM, since in a nested
environment, the idea is NOT to allow the VM's external access (only to the FUEL VM on the ADMIN network )...
If you need to have a different "virtualConfiguration", the create a new subdirectory and a alternate configuration rather than the working / default template for CI for FUEL Nested Setup
Change-Id: I6163307bac285d710a5a5c683798a3c20c609932
Signed-off-by: lmcdasm <lmcdasm@OPNFV-VNCSRV1.opnfvericsson.ca>
JIRA: 007
|
|
This will complete the restructuring of the Fuel repo.
Change-Id: If2029617dca872741d6108362a7315833ae62c4e
Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
|