summaryrefslogtreecommitdiffstats
path: root/patches
AgeCommit message (Collapse)AuthorFilesLines
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>
2016-05-09UX: Update bootstrap/target build time estimate.Alexandru Avadanii2-0/+66
While building for a different architecture (e.g. AArch64 on x86_64), the bootstrap/target image build may take longer, due to latency introduced by using qemu-user-static. Change-Id: I2b57aae73ccc172fea9e53867bcb66e2f950498f Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-08f_repobuild: Repeat mirror build up to ten times.Alexandru Avadanii1-0/+73
OPNFV ISO build uses fuel-mirror to create a local Ubuntu partial mirror in nailgun. Work around temporary mirror issue (e.g. during rsync) by retrying mirror build up to 10 times. Change-Id: I8afb0f55b08c1680903a09e07ac96b4d29415ed5 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-08ARMband patches for the fuel@opnfv deploy scriptsJosep Puigdemont16-0/+1271
These are a collection of patches that adapt the current Fuel deploy scripts for mainly two purposes: - Make it possible to create a Fuel VM on a remote libvirt server. We use the LIBVIRT_DEFAULT_URI environment variable to detect that. Local deploys are possible by setting this variable to 'quemu:///system', or leaving it empty. See: https://libvirt.org/remote.html for more details. - Make it possible to add additional network interfaces. For this we allow the user to pass the "-b bridge" paramter several times, and creating a new virtual NIC for each of them, in the same order they were given. This required a bit of refactoring of the code. None of the changes above should break backwards compatibility, except when indicated in the commit (search for CHANGE in the log) In addition there are some updates to the code that were deemed necessary, like the ability to retry when executing shell commands instead of directly failing, and a simplification of the DHA IPMI adapter. Change-Id: I8a0cd5b8672383decd861309328137971eaed14b Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
2016-04-29Cleanup: Kill submodules: Remove obsolete patches.Alexandru Avadanii5-43/+0
Change-Id: Ia4123727913aa401d26cbe1028f30b20b4497961 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-04-29Cleanup: Kill submodule: fuel-plugin-qemu.Alexandru Avadanii1-28/+0
Since we only build ODL plugin on arm64 for now, kill fuel-plugin-qemu submodule in armband repo. Change-Id: Ib7a6dfe7e1dbd03771e3f28d2769d54659280901 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-04-28Fix: cobbler: setup.sh: Re-add extra RPM repos.Alexandru Avadanii1-31/+19
Commit 69fd98a broke the cobbler yum config, because instead of re-adding only mos and nailgun repos with file:/// handler, it kept the docker-specific repo config from ISO build. Change-Id: I910fe639116a7ea8cb768c0371af0a84b471d0a4
2016-04-28FIXME: cobbler: setup.sh: Keep extra RPM repos.Alexandru Avadanii1-0/+62
cobbler-grub-aarch64 (arm64 specific loader) is currently distributed and added to the cobbler docker container during ISO build using EXTRA_RPM_REPOS envvar mechanism. However, since this package installs files in a mounted location, its contents are not persistent, requiring a test and eventual forced reinstall during container start. This, of course, requires the package to be available at that point, which is not currently possible, as we remove the extra RPM repository entry from yum config at the end of container build. Hacky temporary workaround: Keep extra RPM yum config after container is set up, only for cobbler. TODO: This patch should be dropped once cobbler-grub-aarch64 RPM package gets upstreamed. Change-Id: I58e39df2671d79125c68a5ec994db962c103ce01
2016-04-26f_repobuild/Makefile: Use python-debian from pip.Alexandru Avadanii1-0/+29
Currently, Ubuntu Trusty provides a broken python-debian package, that fails to parse foreign architecture (package:any) relationships. Purge debian package and let pip resolve this dependency, using a newer version from pypi. [1] http://lists.alioth.debian.org/pipermail/ pkg-python-debian-maint/2014-July/001795.html Change-Id: Iba8f6cb52ad0a92e5d8d2bee4fb066b213991a94
2016-04-26Rebase: Drop cpio symlink patch (upstream).Alexandru Avadanii2-27/+0
Drop p/fuel-main/0003-Make-cpio-accept-symlinks.patch, since this is now covered by OPNFV commit f544e41, "Correction due to changed cpio behavior". For details, see https://jira.opnfv.org/browse/FUEL-125 Change-Id: I6c04e34cb7a5af5681745f1cdd026809c65720ce
2016-04-21Increase target image build timeoutStanislaw Kardach1-0/+27
Currently we're close to 40 minutes of image building (thanks to qemu-debootstrap). If network connectivity is a bit slow (happened to me) it's easy to go over 1h limit. Therefore let's push this to 2 hours to be safer. Signed-off-by: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com>
2016-04-20Allow configuring MySQL WSREP SST providerStanislaw Kardach2-0/+174
On some arm64 platforms xtrabackup is broken due to an outdated MySQL/InnoDB code that it uses which is missing. To work around that this patch allows choosing which WSREP SST provider to use. Aside of already supported `xtrabackup-v2` and `mysqldump`, the `rsync` method has been added as it is comparable to xtrabackup in terms of speed (or is faster), has been validated to work on arm64 platforms where xtrabackup is broken and it doesn't rely on db mechanisms to perform the state transfer. This patch is tied to a patch in fuel-web that introduces configuration options for WSREP SST provider and in case nothing is specified, it will choose `xtrabackup-v2`. Signed-off-by: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com>
2016-04-20Cleanup patch-export bugsStanislaw Kardach10-24/+23
2016-04-18Merge "ceilometer: Fix libvirt-bin group name for armband."Alexandru Avadanii1-0/+46
2016-04-18Merge "target Ubuntu: Blacklist rtc-efi if not supported."Alexandru Avadanii2-0/+51
2016-04-18ceilometer: Fix libvirt-bin group name for armband.Alexandru Avadanii1-0/+46
Upstream mirrors use a custom version of libvirt, ported from Debian, while keeping the Ubuntu ceilometer package, leading to a libvirt group name mismatch between the two. Fuel-library hardcodes a deb-version test for libvirt-bin, which enforces the use of "libvirt" instead of "libvirtd" for 1.2.9 or newer libvirt-bin [1]. Armband brings its own 1.3.2 libvirt-bin package, which respects Ubuntu standard group naming ("libvirtd"), but since 1.3.2 > 1.2.9, the old group name ("libvirt") is still used. This patch extends the version checking introduced in [1]: - libvirt-bin 1.3.2 or newer will use "libvirtd" naming; - libvirt-bin 1.2.9 ... <1.3.2 will use "libvirt". [1] https://review.openstack.org/#/c/200602/8/deployment/puppet/ openstack/manifests/ceilometer.pp Change-Id: I11861e1863d7971a844c62dc08f22dbbab63b3e1
2016-04-18Fix build issue introduced by RPM repo switch.Alexandru Avadanii2-5/+44
Adding another RPM repo also requires updating ks.cfg{.orig,} in OPNFV fuel repository. Update TODO by removing obsolete entries. Also fix minor unrelated patch whitespace error. Change-Id: I6a7f271d32c5d9c58aa48658e90e1cdbb0d59fdc
2016-04-17fuel-nailgun-agent: ohai: Read L1 info w/ ethtool.Alexandru Avadanii1-0/+69
fuel-nailgun-agent uses ohai and rethtool for reading eth info, including ethernet card speed. However, current methods rely on the drivers populating the advertised and/or supported link speed lists. This is not true for all drivers, especially for some Fibers that only report the speed via ethtool when the link is up. This patch adds support for reading L1 info from ohai, which supports parsing ethtool speed starting with version amos2 [1]. [1] https://linux.enea.com/mos-repos/ubuntu/8.0/pool/main/o/ ohai/ohai_6.14.0-2~u14.04+mos1+mos8.0+amos2_all.deb Change-Id: Ic8c252e411a680af32cc68574c572434147a7e78
2016-04-17target Ubuntu: Blacklist rtc-efi if not supported.Alexandru Avadanii2-0/+51
Older ThunderX and possibly other UEFI-enabled targets do not support rtc-efi properly, so they end up filling dmesg with useless complaints about not being able to read system time. This adds a simple test for rtc-efi and blacklists it in target OS (Ubuntu) if not supported. While we're at it, rename a patch file I missed in a previous rebase and update TODO. Change-Id: Ia86b27ad50aca9b0fde50522f2bd15d329726f34