summaryrefslogtreecommitdiffstats
path: root/patches
AgeCommit message (Collapse)AuthorFilesLines
2016-06-08Merge "Fuel deploy: timestamp for newly created images"Alexandru Avadanii1-0/+39
2016-06-08Merge "Rebase: deploy related patch series."Alexandru Avadanii28-155/+226
2016-06-04Fix: nailgun_syncdb upgrade to Fuel 9.0.1.Alexandru Avadanii1-2/+2
Armband database migrations were applied on top of Fuel 8.0, creating two heads: 43b2cb64dae6 (branchpoint) -> 11a9adc6d36a -> f9b7fd91ac19 (head) Update our change to be applied on top of Fuel 9.0.1. Change-Id: If5b2ff1aa082227cebd268a2515b78a350166598 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-06-04Rebase: ODL Fuel plugin arm64 support patch.Alexandru Avadanii1-26/+21
ODL plugin package is now arch-independent, drop arm64 hardcode. FIXME: Some arm64 hardcodes remain in place, like installing quagga package. Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-06-04Fixture: fix wrong identation (missing space)Alexandru Avadanii1-1/+1
This prevented YAML parsers from reading the Mitaka fixtures configuration file. Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-06-04Rebase: p/f-l: Update VGA defaults patch context.Alexandru Avadanii1-3/+3
Minor change upstream requires us to rebase this patch.
2016-06-04Rebase: deploy related patch series.Alexandru Avadanii28-155/+226
After change "common.py: catch stderr in exec_cmd" [1] and other unrelated changes were merged upstream, we need to rebase the complete deploy related series. While we're at it, re-export Fuel@OPNFV patches in Armband. [1] https://gerrit.opnfv.org/gerrit/#/c/14561/ Change-Id: Icbc8261c2e24e4b29e8f5f2bc83db6829219129a
2016-06-03Fuel deploy: timestamp for newly created imagesJosep Puigdemont1-0/+39
All images created are named opnfv.iso, this is not sustainable in an environment where several PODs might share the same libvirt storage pool. For this we need unique names, and the time stamp is a cheap way for now to achieve this. Change-Id: I8a7d34036898b8b4e57b23c11bee643876e1829c Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
2016-06-01Upstream: p/common.py: catch stderr in exec_cmd.Alexandru Avadanii1-40/+0
See Fuel@OPNFV change [1]. [1] https://gerrit.opnfv.org/gerrit/#/c/14561/
2016-06-01Upstream: ODL file limit patch was merged upstreamAlexandru Avadanii1-31/+0
See upstream commit [1]. [1] https://github.com/openstack/fuel-plugin-opendaylight/ commit/5012455d58ddfda5894130ca14d8fb7d6b4c8b60
2016-06-01p/Separate-armband-repo no longer needed.Alexandru Avadanii1-43/+0
Since Fuel@OPNFV switched from carrying the orig ks.cfg to a patch for this file in "Build system uplift to Fuel 9.0/Mitaka" [1], we (Armband) can now drop this patch. [1] https://gerrit.opnfv.org/gerrit/#/c/13919/
2016-05-31Rebase: Sync after Build system uplift to Fuel 9.0Alexandru Avadanii4-49/+85
Refresh patches after Fuel@OPNFV migrated to Mitaka in [1], "Build system uplift to Fuel 9.0/Mitaka". >As bootstrap_admin_node.sh has >been transitioned into an RPM (fuel-support), the lazy designer found >it more simple to patch that script during the Fuel build phase than >at the OPNFV ISO generation. The patch mechanism has been changed to >a normal context diff instead of the orig/modified file tuples >previously used. Hopefully this will require fewer manual rebases >(may the fuzz be with us!). >Also the ks.cfg patching has transitioned to a context based ordinary >patch for the same reasons, but this is as before taking place during >OPNFV ISO generation. [1] https://gerrit.opnfv.org/gerrit/#/c/13919/
2016-05-26Merge "bootstrap: Add lshw package (also in fuel-mirror)."Alexandru Avadanii2-5/+48
2016-05-26Merge "deploy: ipmi adapter: Add <port> config support."Alexandru Avadanii1-0/+74
2016-05-26deploy: ipmi adapter: Add <port> config support.Alexandru Avadanii1-0/+74
Sometimes the IPMI lanplus protocol listens on a non-standard remote port, e.g. when target nodes are interfaced through a fake IPMI BMC application that listens on multiple ports on the same IP address. Therefore, allow setting IPMI port in the DHA using a new property named `ipmiPort`, and pass it along to `ipmitool` when set. CHANGE: get_access_info now also supports specifying the IPMI port to use with `ipmitool` by configuring the `ipmiPort` property in the DHA. hp_adapter.py: updated `get_access_info` return signature with the new (unused there) `ipmiport`. Change-Id: Ibff1309b17733af1a6fc8c5008495f42d7ef084a
2016-05-24bootstrap: Add lshw package (also in fuel-mirror).Alexandru Avadanii2-5/+48
Until Ubuntu Trusty fixes the following bug on AArch64 [1]: "AArch64: slow cpuinfo due to redundant loop" we will be using a patched version of <lshw> from Armband MOS repos. This change enforces replacing the lshw from Ubuntu with our custom, patched package. [1] https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1582181 Change-Id: Ie10c7819f305accf2a2c2045b1c350880e4c25b6 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-24Fix improper patch rebaseStanislaw Kardach3-72/+87
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
2016-05-24Correct libvirt template patchStanislaw Kardach1-34/+22
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
2016-05-16Rebase: p/fuel-web: Drop obsoleted qemu doc patch.Alexandru Avadanii1-21/+0
Upstream moved documentation from local repo to fuel-docs in [1]. While looking at this patch, I think we should drop this change altogether, since qemu-user-static is not needed inside the docker builder container, at least not until we start using it for cross-builds, which is highly unlikely anyway. qemu-user-static should always be automatically installed as a dependency of fuel-agent, and NOT by explicit request. [1] https://github.com/openstack/fuel-web/commit/ eb673991cc99c5dadb251f922adb08abb40a8bad Change-Id: Iad7f659fd5ff81e92860508fad58bac519158c47
2016-05-16Rebase: WSREP rsync patchesAlexandru Avadanii2-109/+40
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com> Change-Id: Ic5cc1109df04a95a5e072ab3acb79eb89427a1e0
2016-05-16Merge "Rebase: p/fuel-library: CirrOS direct kernel boot"Alexandru Avadanii2-57/+36
2016-05-16Rebase: p/fuel-web: Add AArch64 s/Liberty/Mitaka/.Alexandru Avadanii2-115/+310
Change patch adding Liberty on aarch64 support to adding the following Openstack releases instead: - Mitaka on Ubuntu 14.04 (aarch64) - Mitaka on Ubuntu+UCA 14.04 (aarch64) Signed-off-by: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com> Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> Change-Id: Ib3f782eccb3d58786d8f99cfd10674cef214d239
2016-05-16Rebase: p/fuel-web: Disable s/Liberty/Mitaka/.Alexandru Avadanii2-24/+34
Update patch for disabling Opentack release(s). Fuel now introduced <Mitaka on Ubuntu+UCA 14.04>, so disable that too for x86_64. Change-Id: I431357bfc6edd3ae0b2567ee5b59c4a1b4deb9b2 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-16Rebase: p/fuel-main: Drop armband RPM repo patch.Alexandru Avadanii1-50/+0
Since Fuel 9.0 drops containers on Fuel master (see spec "Get rid of docker containers on the master node"), we no longer need to add the armband RPM repo config to the cobbler container for cobbler-grub-aarch64. [1] https://blueprints.launchpad.net/fuel/+spec/ get-rid-docker-containers Change-Id: Ia23482226e81f83c1eb50c239346a3686206d5bf
2016-05-16Rebase: p/f-{main,lib}: cobbler-grub-aarch64 dep.Alexandru Avadanii2-39/+35
Since Fuel 9.0 drops containers on Fuel master (see spec "Get rid of docker containers on the master node"), we need to handle the install of cobbler-grub-aarch64 in a different place. So, handle cobbler-grub-aarch64 loader install as a cobbler dependency in puppet. [1] https://blueprints.launchpad.net/fuel/+spec/ get-rid-docker-containers Change-Id: Ia42211b4d0aa54ba67862f30f8c7975d2aa09392
2016-05-16Rebase: p/fuel-main: Refresh after pkglist update.Alexandru Avadanii1-9/+9
Upstream commit: "Update package list required for building ISO" [1] [1] https://github.com/openstack/fuel-main/commit/ 18f2c14a928bf3e92ccd4d868953361bed61614b Change-Id: I59af524de7539489ad4dce12894573f8ff1ac5a5
2016-05-16Rebase: p/fuel-library: Update after 96da5b4a.Alexandru Avadanii9-106/+83
Refresh patches after: "Move openstack specific tasks to their own folder structure" NOTE: The qemu-kvm change patch (0003-Make-qemu-kvm-architecture-aware.patch) only affects RedHat systems, so it is optional, at least for the current stage. [1] https://github.com/openstack/fuel-library/commit/ 96da5b4a1eb82a76fb416d93f5249dc32e2499f2 Change-Id: Ibd1fd3f7e45d7947c90336bbe7e2ace101b5802b
2016-05-16Rebase: p/fuel-library: nailgun -> fuel module.Alexandru Avadanii2-84/+75
Upstream introduced two related changes, requiring a rebase: - Remove nailgun module [1] - Remove CentOS based bootstrap image support [2] [1] https://github.com/openstack/fuel-library/commit/ 74a68f493ff215ce8dfc67c3af6d06dd5a2db194 [2] https://github.com/openstack/fuel-library/commit/ 3e1320bfcf4a8688d4bfb577a1330121390bafc0 Change-Id: I27279a2fd76d269d482a3eb25e9dba41bc669280
2016-05-16Rebase: p/fuel-astute: Reduce patch context.Alexandru Avadanii1-3/+1
Change-Id: Ic11f7c4caa801df32d12461b39e10df8f07460a7
2016-05-16Merge "Rebase: p/fuel-agent: Update UEFI after ec71a42."Alexandru Avadanii2-19/+19
2016-05-16Merge "Rebase: p/fuel-agent: Patch context refresh."Alexandru Avadanii2-7/+3
2016-05-16Merge "Rebase: p/opnfv-fuel: Drop upstream patches."Alexandru Avadanii3-115/+1
2016-05-16Merge "Rebase: p/opnfv-fuel: Allow Fuel commit override."Alexandru Avadanii1-2/+2
2016-05-16Fix improperly exported patchesStanislaw Kardach4-2/+2
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
2016-05-15Rebase: p/fuel-library: CirrOS direct kernel bootStanislaw Kardach2-57/+36
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com> Change-Id: I12126a39c90abf8fc5bef449506e87dc190a50ee
2016-05-15Increase open file limit for OpenDaylightStanislaw Kardach1-0/+31
Upstart scripts by default do not run scripts in a shell which results in limits from `/etc/security/limits.conf` not be taken into account and results in the default value (4096) to be taken. This may prove problematic for OpenDaylight during initialization. On Cavium ThunderX we have noticed OpenFlow controller initialization failures caused by hitting this limit. OPNFV is increasing the `nofile` limit to 112640 for OpenStack services which is why I'm using this value here. Bug report filed to Fuel@OPNFV (see [1]). [1] https://jira.opnfv.org/browse/FUEL-140 Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
2016-05-13Rebase: p/fuel-agent: Update UEFI after ec71a42.Alexandru Avadanii2-19/+19
Rebase after upstream change [1]: "Grub stage1 shall be installed on all of disks" [1] https://github.com/openstack/fuel-agent/commit/ c71a424b9552c07ef1f8a068bedea9563cbe45c
2016-05-13Rebase: p/fuel-agent: Patch context refresh.Alexandru Avadanii2-7/+3
2016-05-13Rebase: p/opnfv-fuel: Drop upstream patches.Alexandru Avadanii3-115/+1
While we're at it, fix minor context in remaining patch.
2016-05-13Rebase: p/opnfv-fuel: Allow Fuel commit override.Alexandru Avadanii1-2/+2
2016-05-10Merge "Cleanup: rm TODO, fix license header."Alexandru Avadanii4-7/+7
2016-05-10Merge "UX: Fix: rtc-efi blacklist for Ubuntu targets."Alexandru Avadanii3-51/+35
2016-05-10Cleanup: rm TODO, fix license header.Alexandru Avadanii4-7/+7
While we're at it, fix default setting for net.ifnames in arm64 fixture. Also, renumber some patches to eliminate duplicate prefixes resulted from parallel development of patch sets. Change-Id: Ibd8cc1f6f8916ad79527f2060a1a2725d557b2c2
2016-05-10UX: Fix: rtc-efi blacklist for Ubuntu targets.Alexandru Avadanii3-51/+35
Previously, rtc-efi module was blacklisted in fuel-library preseed cobbler template, which is not used for Ubuntu target nodes. Fix by instead blacklisting rtc-efi in cloud-init jinja2 template. Change-Id: I325f8d1f411f51d494df7c738f1933445d996ff6
2016-05-10Merge "Increase maximum shell command timeout to 2h"Alexandru Avadanii1-0/+33
2016-05-10Increase maximum shell command timeout to 2hStanislaw Kardach1-0/+33
Since `execute_shell_command` mcagent is used for building the target image and the timeout provided in the astute task is just respected on the Astute level (on mcollective level this timeout is actually a minumum between value provided and ddl value) we need to increase it for Armband operation. Because Armband builds the target image via `qemu-debootstrap`, it can take more than 1 hour to finish the building. Therefore aside of increasing the timeout in the Astute task, the maximum timeout value for mcagent has to be increased. Change-Id: Iab94e794e36bb7e887e8f334daa46e82fe0c6f94 Signed-off-by: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com>
2016-05-10Merge "deploy/reap.py: Dump extra interfaces information."Alexandru Avadanii1-0/+90
2016-05-10Merge "UX: Update bootstrap/target build time estimate."Alexandru Avadanii2-0/+66
2016-05-09[fuel] deploy.sh: Add timeout flag on fuelJosep Puigdemont1-0/+81
Some PODs might need to increase the default timeout value. The patch introduces the -T flag to Fuel's deploy script, that can be used to set the timeout. If the flag is not given, it will look into the DEPLOY_TIMEOUT environment variable and use that value instead, otherwise the default vaule in deploy.py will be used. Change-Id: I835473190673dd8646d0da48c2dbd3bb5e13046d Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
2016-05-09deploy/reap.py: Dump extra interfaces information.Alexandru Avadanii1-0/+90
Since on AArch64, Ubuntu local mirror lacks arm64 packages (see [1]), Fuel master requires internet connectivity during deploy, and hence a way to setup such a public (extra) interface automatically. Previous commit "transplant: Generate extra interfaces config file" introduced support for passing this information via DEA (override), which may define a IFCGF_<interface> section in its 'fuel:' section, containing the necessary keys to produce a ifcfg-<interface> file, like in this example: fuel: IFCFG_ETH1: device: eth1 ipaddress: 10.0.1.10 netmask: 255.255.255.0 gateway: 10.0.1.254 In order for Network Manager to use the newly added interfaces for outgoing traffic and honor their GATEWAY setting (e.g. if we just added one public interface), the default route on admin iface (most of the time called eth0) is disabled when extra interfaces are present. FIXME: Only supports lowercase interface names, but so does Fuel, see related bug report [2]. [1] https://jira.opnfv.org/browse/ARMBAND-35 [2] https://jira.opnfv.org/browse/FUEL-136 Change-Id: Idd6fe95a5a73ec172eca17cfd96f23b1a1bc2bee Signed-off-by: Alexandu Avadanii <alexandru.avadanii@enea.com> Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>