summaryrefslogtreecommitdiffstats
path: root/deploy/templates/virtual_environment/vms
AgeCommit message (Collapse)AuthorFilesLines
2017-09-03build, deploy: Remove obsolete Fuel@Openstack codeAlexandru Avadanii3-195/+0
JIRA: FUEL-278 Change-Id: I30c04c325de5ac97aee172386de43201988646c5 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-04-05Double allocated memory of fuel master nodeMichael Polenchuk1-2/+2
Rise up allocated memory of fuel master node for virtual envs in order to avoid swapping and improve performance of overall deployment process. Change-Id: I04b020b628a9c84f934a9d17e8be98d34fe2a085 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-11-01[virtual envs] Switch to raw imagesMichael Polenchuk3-3/+3
* use raw devices instead of qcow2 * disable i/o caching, it reduces data copies and bus traffic * set native aio instead of thread based JIRA: FUEL-201 Change-Id: I8ac728cbb5be5948080fab8ae4d3d311e0a5c09c Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-08-17Use virtio driver for fuel-master NICMichal Skalski1-1/+1
Using e1000 driver on fuel master may lead to temporarily loss of communication [1]. We can use two approaches here: * use virtio driver * install e1000-kmod package virtio driver should be sufficient for our purposes, we don't use bonding on fuel master. e1000-kmod package is available on fuel master and provide e1000 kernel module which does not introduce additional problems. This package is not installed by default but for this purpose MASTER_NODE_EXTRA_PACKAGES cmdline option can be set during fuel master installation. [1] http://docs.openstack.org/developer/fuel-docs/userdocs/release-notes/fuel_known_issues.html Change-Id: I3fc1fed5f0b9c780cd9174205a3c31dae92a180e Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-08-11Pass host cpu flags to compute guestsMichal Skalski1-0/+3
Both kvm and ovs plugins require specific cpu flags. Host-model mode will pass most of the host cpu flags to guest. If a hypervisor is not able to use the exact CPU model, libvirt automatically falls back to a closest model. JIRA: FUEL-157 Change-Id: I77ce625e118b6de51cbcdb58e4be5a6dcaecf384 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-08-10Revert "Pass host cpu flags to compute guests"Michal Skalski1-3/+0
This reverts commit 34da00c2baa6abc69a812aae4c30a82ebae561bd. Change-Id: I495fa1f71ac30e259ca63e90ca8b38dd2300d469 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-08-10Pass host cpu flags to compute guestsMichal Skalski1-0/+3
Both kvm and ovs plugins require specific cpu flags. Host-model mode will pass most of the host cpu flags to guest. JIRA: FUEL-157 Change-Id: Iff620a4b4f5948e54f6f8db01411d6659f08ec00 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-07-12Aligning machine type over Ubuntu and CentosStefan K. Berg3-3/+3
We have previously used "pc-1.0" as the qemu-kvm machine definition for virtual Fuel deploys. On Ubuntu this points to: pc-1.0 Standard PC (i440FX + PIIX, 1996) On CentOS 7 this machine definition does not exist, but there's a match in "pc": pc RHEL 7.0.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.0.0 So, finally, pc is also in Ubuntu: pc Ubuntu 14.04 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-trusty) This change is about exploring whether moving to "pc" will make the auto deploy work on both platforms with the "pc" machine type. What still needs to be done in CentOS is to create a symlink from /usr/libexec/qemu-kvm and /usr/bin/kvm though. Change-Id: I1cce52a21075950cb59b75709b12d724d759e3e6 Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-05-09Use US keyboard layout on the consolePeter Barabas3-3/+3
Change-Id: I40942c7181daf5efd1640a03471e91df82548073 Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
2016-03-01Changing 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
2016-02-25Remove apparmor for vFuelNikolas Hermanns1-2/+0
Not every CPU supports apparmor and there is no real benefit when using it only for fuel. Change-Id: Ibb3221b85d8565f718df9b087aa324d0f606bdee
2016-01-26Use 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>
2016-01-13Removing 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
2015-11-27Restructcture of the directory layoutJonas Bjurel3-0/+275
Restructure of the directory layout due to move of Fuel into it's own repo JIRA: FUEL-85 Change-Id: I3647e1992a508f29dce06a5d6c790725c527f6f5 Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>