Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I2cd1899d82878dfece22ed546e1ff24d5387e8c1
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
For some reason, our docker sandbox builder already has dh-systemd
when checking for "fuel-agent" build-deps, and therefore skips
adding it as a build dep inside the chroot, leading to debuild fail.
Backporte upstream fix for this from [1].
[1] https://review.openstack.org/#/c/325210/
Change-Id: Ieece9b2250bd91e688bd0f203240da5234930558
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Iea330d6d778ff5034e1e801d20fa74485e302a95
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Fuel@OPNFV just added the Yardstick plugin.
This plugin is a little different, instead of breaking fuel plugin
code apart from the contents (i.e. fuel-plugin-yardstick separate
from yardstick itself), it holds both fuel plugin metadata and
actual yardstick code in the same repo.
So far, yardstick plugin code itself is arch-independant and should
not be touched.
TODO:
- add yardstick patches for arm64 until we can validate Yardstick;
- submit patches added locally in Armband to upstream
(Yardstick@OPNFV);
Change-Id: I24bc8858b92c9bdd529a64de833d7b98c06a6ade
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I986bfb5ae549321a0696f945d24ccb1b6b198f96
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Move fuel-main patching to opnfv-fuel, preparing for upstreaming
this to Fuel@OPNFV.
Drop fuel-main submodule!
Change-Id: I12b995f37701658dca1d1a212ede029d0e03231c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Rebase conflicting patches due to format change.
Change-Id: Ia9d1f9c0cad77da7b95e8ec4b62324953ef3ce9c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Skip parsing comment lines in ifcfg-ethX files at reap, e.g.:
Change-Id: Ide6b2111619f7558f1434fda5cd254b842cef0ae
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I9442f217d2f840382b40f6eae77ddb9ae2ddbadc
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
Change-Id: I3702648583983ac7afcfef7a9556fcd33e984457
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I3c7bd7f9be85078783a2e95dfe480cffc08534d1
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I158c58cb01112d2113a75dd425275cf9531d49fc
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I927bb36b0ac4628630f90649027441a895c6f774
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
This is highly unlikely to be upstreamed in any other form than this.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
IMPORTANT:
Drop `fuel-astute` submodule, and patch it instead during the Fuel
Master node bootstrapping process, using an OPNFV post.d script.
Luckily, this fits well with the recently added script that prepares
FM for cross-building.
One step closer to un-forking.
Change-Id: Ia612e0ad4077b16baf54f1b9ebf9d207daca0be4
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
ARMBAND NOTE(S):
- This is a bug fix + a new feature (arch list in a file on FM)
- This is overengineered because:
* we want to move patching to post-ISO creation, OPNFV style;
* easier integration with Fuel@OPNFV, using post-install scripts;
* prepare for true multiarch support on Fuel Master;
IMPORTANT:
This commit introduces the following file on Fuel Master,
containing the list of arch supported for target nodes:
</etc/fuel_openstack_arch>.
This file is created AFTER pre.d OPNFV scripts are ran, also by
bootstrap_admin_node.sh, BEFORE the post.d scripts are executed.
NOTE: Arch format is the same used by dpkg (e.g.: "amd64 arm64")
Based on the number of foreign architectures we should support
(the list of archs in /etc/fuel_openstack_arch minus native arch),
we determine whether cross-builds are expected, in which case
binfmt support should be functional during first Fuel Master boot.
Since systemd-binfmt service has a series of preconditions for
starting, which are tested early during first boot, some of them
are NOT YET true (e.g. no binfmt handlers are present before
qemu-user-static package is installed), so the service is not
automatically started. Of course, this only affects the first boot.
Finally, this commit adds an OPNFV post-install script in
/opt/opnfv/bootstrap/post.d, which starts systemd-binfmt service.
Change-Id: I6dbe4b3ac5a2fd076881d6778ff66b82bb6c7379
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Backport upstream pending patch
"Build local mirrors for stable/mitaka" from [1].
Minor rebase for two other patches after applying this series.
[1] https://gerrit.opnfv.org/gerrit/#/c/15259
Change-Id: I362e08be3460d711de064a487fdcc8c76fc69af9
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Update patch `deploy/reap.py: Dump extra interfaces information.`
after upstream change was merged [1].
[1] https://gerrit.opnfv.org/gerrit/#/c/15275/
Change-Id: I9fd74775030732cc0759610228fa80a0cec72352
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Upstream change [1] made this patch obsolete.
While at it, update related patch context after same change.
[1] https://gerrit.opnfv.org/gerrit/#/c/14385/
Change-Id: I21753e4dafdd0ab83c5eac37f394aa704bbe236b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Upstream removed all mirrors but usa and cz, and changed
its default to mirror.fuel-infra.org in [1].
This allows us to drop patching of fuel-main/config.mk
with the Czech mirror.
If needed, USE_MIRROR=cz can be specified as an env var.
FIXME: Remove when Fuel@OPNFV pulls change and deals with it.
[1] https://github.com/openstack/fuel-main/commit/
751d502cfe15d9c9df0ee89530ac3b0b73aa1638
|
|
|
|
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
|
|
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>
|
|
See Fuel@OPNFV change [1].
[1] https://gerrit.opnfv.org/gerrit/#/c/14561/
|
|
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/
|
|
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/
|
|
|
|
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
|
|
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>
|
|
While we're at it, fix minor context in remaining patch.
|
|
|
|
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
|
|
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: Ia4123727913aa401d26cbe1028f30b20b4497961
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
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
|
|
|
|
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
|
|
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.
armband-rtc-efi-fix validates rtc-efi can be used on the system,
otherwise it rmmods rtc_efi kernel module via rcS script.
This patch hardcodes the addition of armband-rtc-ef-fix package during
bootstrap image build.
NOTES:
This could be later removed or, if other fixes need to be delivered
like this, grouped in a meta package.
Target OS (Ubuntu) still needs to be handled, preferably by blacklisting
rtc-efi module and rebuilding initramfs during provisioning.
Fuel 9.0 moved default package list to openstack.yaml fixture, see [1].
[1] https://github.com/openstack/fuel-web/commit/
4ee42effe27694bd231663e3d0f10c0c42877177
Change-Id: I57d632e3915058bbb1fc56b3a7fbd5d15787f9d9
|
|
While we're at if, fix whitespace errors in affected patches.
Change-Id: Ic14e3e13f9503ab4b9307e55c731825b8a33da3b
|
|
Change-Id: If0d4c64742d0984f32c7c68bc903332ceea656e9
|
|
|