Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Change-Id: Ibd522813a40a0b1c385c47e65f77b1a13c860269
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Change-Id: Ia54bd3955a3e3b534d8c4d8380de5870a106edc5
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Some eth drivers, such as those for APM X-Gene Mustang Board's NICs, do
not advertise operstate properly in sysfs, ie. it is advertised as
"unknown" whereas ethtool shows the NIC as fully functional with link
detected. This further affects "ip link show" output which is parsed
within _check_iface_ready() method.
Replace "ip link show" command with "ethtool" in order to obtain proper
results when operstate is unknown.
Launchpad bug: https://bugs.launchpad.net/fuel/+bug/1618480
Change-Id: If8e28d3720161d9ffe897b875af235561cf1062d
Signed-off-by: Stefan Sicleru <stefan.sicleru@enea.com>
|
|
|
|
Change-Id: Iaabd176f4032494c8ea40fd1264dafcac01b4a43
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I308eb1c2bfdf0fc568e7f351078cd7a3017aae4a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Most likely, when we configure an additional interface for Fuel
Master, and Network Manager is restarted, our old ssh connection
is timed out and needs to be re-established before checking
for fuel bootstrap process via ssh.exec_cmd.
Change-Id: I44589b2e8190008c8b1035d171cbb50270dfd98c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Armband build benefits (or should have) of a local mirror
for "linux.enea.com", which we used to inject into the build
system by host's "/etc/hosts".
After Armband switched to building inside docker, this change
was silently discarded by containerization.
The proposed solution uses hosts's network stack in all build
containers.
See [1] for full description.
This change simplifies the network abstraction during build by
NOT containerizing the containers' networking.
The original motivation was pointing to local mirrors via host's
"/etc/hosts", for which an alternative solution could be passing
"-v /etc/hosts:/etc/hosts".
[1] https://docs.docker.com/v1.8/articles/networking/
Change-Id: I31e3c787a432af49b4799f561669a0150668b222
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ic584d9b1eb179009256de8ccacfb7669976823c6
|
|
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Now we can kill fuel-astute submodule.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Decouple main Makefile and repository patches by moving all Fuel
component patches to a subdir, <patch-repo>.
Proposed structure of <patch-repos> dir:
- patch-repos/*.patch are intended for <fuel-main> git repo;
- patch-repos/build/repo/<fuel-module>/*.patch are intended for
<fuel-module>, e.g. "fuel-nailgun";
Full list of Fuel submodules supported by this mechanism at [1].
While at it, replace all occurences of </tmp/fuel-main> with
<FUEL_MAIN_DIR> in main Makefile and rewrite a few git/make calls
to use the "-C" arg.
NOTE: `git -C` is available starting with git 1.8.5.
ARMBAND NOTE: This patch will allow us to streamline the process
of moving patches from our repo straight to Fuel@OPNFV.
[1] https://github.com/openstack/fuel-main/blob/stable/mitaka/repos.mk
#L32-L44
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Backport fpb change submmited in [1].
[1] https://review.openstack.org/#/c/311031/
Change-Id: I02ce8c6151799e3953587fce50cbe552a5c95c50
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
See Fuel@OPNFV change [1].
[1] https://gerrit.opnfv.org/gerrit/#/c/19033/
Change-Id: I9c95a7aaec366c9e03620f1129b3cb8401385476
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Since arm64 support has been proposed straight upstream [1], we
no longer have to keep the git submodule for the yarstick repo.
[1] https://gerrit.opnfv.org/gerrit/#/c/18883/
Change-Id: Ic8a02106ed1d26012a0767fc0444b8f8d35c54aa
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Previously, Armband Makefile used to call Fuel@OPNFV Makefile
target <iso>, instead of <all>, which resulted in bypassing
using Docker for ISO building completely.
Switch to <all> Makefile target, hence bringing back Docker
as a build container.
This change justifies moving make variables to a separate spec
file, armband.mk.
While at it, enable caching of builds.
This requires Jenkins bash scripts to be updated for the ISO
build job, done in [1].
JIRA: ARMBAND-56
[1] https://gerrit.opnfv.org/gerrit/#/c/18453/
CHANGES:
- all: release (was all: build)
- Common make targets now depend on submodules-init;
- clean-build and clean-docker make targets have been replaced by:
make clean, make deepclean;
FIXME: These issues should be fixed later:
- (optional) trim local repo paths from gitinfo files
- only account for armband submodules in cache fingerprints;
- identify size mismatch culprit
Change-Id: I7d73409be44983fa21d4c09d2e07b87a33231e03
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I6a8a96caa095b20d85db2d4d418dd9cb121b12e4
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Ubuntu arm64: While keeping kernel 4.2 for Trusty
(linux-image-generic-lts-trusty), set 4.4 backported from Xenial
(linux-image-generic-lts-xenial) as default kernel for Armband ISO.
Xenial kernel 4.4 for Trusty has been tested with:
- AMD Softiron;
- APM Mustang;
- Cavium ThunderX;
While at it, remove obsoleted rtc-efi fixes.
Notes:
- keep 4.2 kernel inside the ISO;
- selecting 4.2 kernel may be done via deploy settings, by
overriding kernel flavor when calling `fuel-bootstrap`;
Related-bug: ARMBAND-48
Change-Id: Ice1f95939f0d7d9491befd20030740850b1a0e61
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Upstream change [1] requires us to to adapt our Fuel@OPNFV patches.
[1] https://gerrit.opnfv.org/gerrit/#/c/17969/
Change-Id: I9823469df575cc929e399a6025aca6066a16e98d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I78606b3dca803c7bf1d872cf067b2bd5f8a8aa91
|
|
Change-Id: I97c9c79bb342d6c7504414134649795689b5e78b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: ARMBAND-59
Change-Id: I031e1c20bcb7d5bb15b26dce18364a4994f4d0d7
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Backport from upstream proposed change [1] in Fuel@OPNFV.
[1] https://gerrit.opnfv.org/gerrit/#/c/17563/
Prereq for: ARMBAND-48
Change-Id: Ia5a2073532e578b663f8f45bfe90b9fe36df77cc
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Ubuntu arm64: While keeping kernel 4.2 for Trusty
(linux-image-generic-lts-trusty), add 4.4 backported from Xenial
(linux-image-generic-lts-xenial) to Armband ISO.
Xenial kernel 4.4 for Trusty has been tested with:
- AMD Softiron;
- APM Mustang;
- Cavium ThunderX;
While at it, remove obsoleted armband-rtc-efi-fix Debian package,
which was only needed on targets that are not compatible with 4.4,
and we plan on retiring soon.
v2->v3:
- keep 4.2 kernel instead of replacing it;
- selecting 4.4 kernel will be done via deploy settings, by
overriding kernel flavor when calling `fuel-bootstrap`;
- dropped test changes, not needed when both 4.2 and 4.4 are in;
TODO:
- switch default kernel flavor to 4.4 when all our PODs are ready;
Closes: ARMBAND-48
Change-Id: I37600f12dd01facbd552f1d2d721bc7a3e0e2750
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Previous commit which was supposed to fix the BUILD_ID being too
long mistakenly altered the submodule code for computing the
short SHA, instead of altering the Makefile.
Fixes: ARMBAND-53
Change-Id: Ib1c1b3dc9592714fd86a59ae1a64001bd2930bd3
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Previous change altered the BUILD_ID to include Armband commit info
instead of Fuel@OPNFV info, and also a marker to indicate it comes
from Armband repo.
This lead to the ISO volume ID becoming too long:
"Making ISO...
genisoimage: Volume ID string too long
make[1]: *** [iso] Error 255"
While at it, change our marker from "FUEL_AARCH64" to "ARMBAND_FUEL",
as our ISO should also support x86 in the future, not only arm64.
Fixes: ARMBAND-53
Change-Id: I52526f1f7861aca71d16d1e6b6b2a9566a6c7d3f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ia268e17a7a8b0c2c47209e47feb6f77394036283
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Upstream change [1] removed Czech mirror patch.
[1] https://gerrit.opnfv.org/gerrit/#/c/17225/
Change-Id: Id986899aa83b3cb7d228a266b1b8a8f5a942ba49
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Closes: ARMBAND-53
Change-Id: I92c1541a22a837c281d9b86f6ee8da327305884d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
In order to clean up old partitioning and boot entries on target
nodes, before removing the Fuel Master, try ssh-ing into it and
removing all environments/nodes.
This is especially important for EFI systems, where old boot
entries are left behind without a proper env delete, leading to
target nodes failing to PXE boot on Fuel Master re-install.
This change assumes that:
- all Fuel Master information is unchanged between old and new
deploy (fuel IP, password etc.);
- Fuel Master is up and running, in a sane state (target nodes
are also online), when deploy starts;
Closes: ARMBAND-51
Change-Id: I52b853b37a0d226a9cb33179f7aeb65eff74da4e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I493279d81b32a58b918f2b6caa0cf869a0caa674
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
|
|
Change-Id: Icbbba0bee68a8fe9de76dbf3c339e01da43fb3a2
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
Previous change [1] introduced the addition of an iptables rule
that was supposed to allow SSH access on all ifaces (not only
admin iface) when additional ifaces are configured.
However, Fuel installer is flushing the rules after transplant
adds our SSH config, overwriting it.
Move iptables SSH config to post-install section, as standalone
script. In order to keep the same behavior, test ifcfg-eth0
(admin interface is expected to be called eth0 by convention)
for "DEFROUTE=no" and only whitelist SSH on all ifaces if it matches.
[1] https://gerrit.opnfv.org/gerrit/#/c/16571/
Change-Id: I086b75461daa62671cad10494fe34acfd77757ae
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Change-Id: Iae462ebe89ff3bc351addd12a8f5cc5ecdef2b11
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
Change-Id: I2cd1899d82878dfece22ed546e1ff24d5387e8c1
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
Previously (in Fuel 8.0), SSH used to listen only on 10.20.0.2
(admin interface), which required editing sshd_config and restarting
SSH server for allowing SSH connections over the public IP on eth1
(just an example, which corresponds to Armband PODs use cases).
In Fuel 9.0, SSH server on Fuel Master listens on all ifaces,
but connections are filtered by iptables.
This change piggy-backs on a previous Armband addition that allows
transplant.py script to configure additional interfaces (e.g. public).
In case additional interfaces have been configured by transplant,
this change will instruct iptables to accept SSH connections on ANY
interface, not only the admin one.
Possible improvements:
- limit SSH access to admin + interfaces added by transplant instead
of ANY;
Change-Id: I0923496e1b23f6dc826c8afbbe9805956c2d4b34
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@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>
|