aboutsummaryrefslogtreecommitdiffstats
path: root/deploy/templates/virtual_environment_noha
AgeCommit message (Collapse)AuthorFilesLines
2016-04-09Merge "Changing raw to qcow2 for vFuel/Controller/Compute" into ↵Jonas Bjurel3-3/+3
stable/brahmaputra
2016-04-09Changing raw to qcow2 for vFuel/Controller/ComputeNikolas Hermanns3-3/+3
A lot of diskspace is allocated although never used this commit changes to thin provisioning for the virtual enviroment. Change-Id: Ia128143a3bae9f3d85a9e749319c2f5343c1df4e (cherry picked from commit aac8573f454109c98fa2af1e5ed05c1d1b19829b)
2016-04-09Remove apparmor for vFuelNikolas Hermanns1-1/+0
Not every CPU supports apparmor and there is no real benefit when using it only for fuel. Change-Id: Ibb3221b85d8565f718df9b087aa324d0f606bdee (cherry picked from commit ca27087edd27555aa6d7992b3e754c970bc6543f)
2016-01-29Use e1000 network driver in virtual labsMichal Skalski3-9/+9
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> (cherry picked from commit 4b87e1e902e44971740ca020b164327d463d12c8)
2016-01-14Removing CPU specification from TemplatesNikolas Hermanns3-81/+0
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 (cherry picked from commit a732cb72ef59f11a0de1df4cbcb2630fa88afd8d)
2015-12-22Revert "Fix for the default virtaul enviroment template."Fatih Degirmenci1-3/+3
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
2015-12-22Fix for the default virtaul enviroment template.lmcdasm1-3/+3
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
2015-11-30Moved the noha virtual templatesStefan K. Berg10-0/+1242
This will complete the restructuring of the Fuel repo. Change-Id: If2029617dca872741d6108362a7315833ae62c4e Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>