summaryrefslogtreecommitdiffstats
path: root/patches/opnfv-fuel/upstream-backports/0004-Fuel-rework-for-multiple-libvirt.patch
AgeCommit message (Collapse)AuthorFilesLines
2017-06-28MCP: Remove all Fuel patches and pluginsAlexandru Avadanii1-1533/+0
Chances are none of the old patches / plugins can be reused as-is, so remove all of them and prepare for the switch to MCP. Change-Id: I999927a43b438d9bda9ff118731e2af4b1fa8caa Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-03-17Add copyright header to patch filesCatalina Focsa1-0/+8
JIRA: ARMBAND-236 Change-Id: I91c4956b5baa479995bff2f569a321b8a0b421c0 Signed-off-by: Catalina Focsa <catalina.focsa@enea.com>
2017-02-03Rebase: Adjust patch context for deploy configAlexandru Avadanii1-1/+6
Change-Id: I3d1b15cbfd70d726ae8b24514d2106e7e52e2524 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-01-21Uplift Armband to Fuel NewtonAlexandru Avadanii1-1/+1
[ Dan Andresan ] - puppet: database: Fix Percona XtraBackup sync [ Alexandru Avadanii ] - disable all plugins; - re-enable remote tracking; - remove "Revert: Point to specific snapshot ..."; - patch context adjustments; - obsolete "kernel-bump", linux-image-lts-xenial is now the default; - network-checker iface state check now fixed upstream [1]; - fuel-nailgun-agent hugepage size should also check /proc/meminfo; - fuel-nailgun-agent CPU detection for AArch64; - nova AArch64 hugepage support is now upstream; - obsolete Cirros Test VM direct kernel boot (by switch to AAVMF): * f-l/0001-upload_cirros-Add-direct-kernel-boot-support.patch * f-w/0001-direct-kernel-boot-for-cirros.patch - rework m1.micro RAM size patch after puppet manifest split upstream; - re-enable arch-agnostic plugins which were rebased in Fuel@OPNFV: * f_yardstick-pluginbuild * f_congress-pluginbuild - do NOT retire MySQL SST provider patch series (nack: ARMBAND-186), rebase (and keep for now) MySQL SST provider patches, as trying to use xtrabackup-v2 revelead a regression since Colorado.3.0, and these patches simplify troubleshooting a lot; - AArch64: nova: libvirt: Use host-model cpu (ARMBAND-193); - AArch64: nova: libvirt: Use pointer_model instead of use_usb_tablet; - m1.micro RAM size insufficient for TestVM with AAVMF (s/128/256/) - switch Cirros TestVM to AAVMF from direct kernel boot; - backport nova libvirt driver fix for deleting instances booted with AAVMF firmware from [2]; TODO (later): - Include ISO build time fixes for cirros_testvm in Armband package; TODO (ODL, later): - test & revise leveldb patching; - bring back Qugga patching for arm64; - configure systemd service to automatically respawn; [1] https://review.openstack.org/#/c/417373/ [2] https://review.openstack.org/#/c/357190/ JIRA: ARMBAND-29 JIRA: ARMBAND-32 JIRA: ARMBAND-63 JIRA: ARMBAND-88 JIRA: ARMBAND-116 JIRA: ARMBAND-118 JIRA: ARMBAND-186 JIRA: ARMBAND-193 JIRA: ARMBAND-194 JIRA: ARMBAND-195 JIRA: ARMBAND-196 JIRA: ARMBAND-197 Change-Id: Ia99022e364e61245d109cabab9d0ed7157b4d2f5 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> Signed-off-by: Dan Andresan <dan.andresan@enea.com>
2016-12-07Fix failed deploys on virtual pod (noha scenarios)cristinapauna1-53/+627
JIRA: ARMBAND-173 Currently only ha scenarios were successfully deployed on virtual pods The default configuration is for ha scenarios and those have 5 target nodes while on the noha scenarios there are 4. The noha scenarios failed because it was trying to parse one extra node. This patch modifies the dea and dha files for each noha scenario so that the nodes are properly configured. Change-Id: I360aeaf8dc92e0ff614367d47d74f6fa61ef2268 Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-11-27Correct previous patch on fuel reworkcristinapauna1-20/+28
Some leftover chars in https://gerrit.opnfv.org/gerrit/#/c/24901/ were keeping the deploy to work. Also, the empty folder networks was added. This folder should contain templates for virtual network config for the targets. For arm we don't need those so we leave it empty for consistency with other projects and for avoiding changing the deploy logic JIRA: ARMBAND-122 Change-Id: Id33e2efacc3ff8d3754c8b29d4bebefd0b385c41 Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-11-25Fuel rework for multiple libvirtcristinapauna1-0/+938
The current fuel arhitecture assumes that all the VMs (Jenkins slave, Fuel master and Target nodes) are all on the same server. There is code that allows the Fuel master to be on a different machine, but nothing for the Target nodes. In Enea-Arm lab we have a different server for each. This commit also adds specific templates for a virtual pod in the Enea-Arm lab. Therefore, the following changes are done: - The default libvirt URI is the machine on which the Target nodes are - The parameter libvirtUri was added in the dha.yaml file for fuel master - All virsh calls have "-c" option to explicitly specify the uri; this parameter is set only when libvirtUri is explicitly set in the yaml file - The scenarios dha override now point to the arm template files - The network templates are not needed for ARM, as the network infra is provided by the server on which the Target node VMs reside; the folder is added here just for consistency - The target nodes are created with virsh rather than quemu when the nodes are not on the same machine as Jenkins slave (similar logic to what is done for remote Fuel master) JIRA: ARMBAND-122 FIXME: remove hardcodes for - Network bridges from templates - Default pool - libvirtUri from scenario overwrite Change-Id: Ibf4744e5593f5201550115397024fd8311696074 Signed-off-by: cristinapauna <cristina.pauna@enea.com>