Age | Commit message (Collapse) | Author | Files | Lines |
|
Project: fuel 6c498c04a9843bcc99dc94650e5d0b31490dfa1b
Download deployment config after modification
Modified network or interface configurations were not reflected in
the deployment config, resulting in faulty node configurations.
Change-Id: I4ca20702c0171e7995f2b4f46317557ec9d5beac
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
Project: fuel 2498bbb0354fd7abbbb408810f419c2999c23a31
Auto deploy corrections for Fuel 9.0
- The auto deployer's detection of nodes being up corrected as "fuel node"
now returns "1" instead of "True" to denote that the node is up.
- The location of bootstrap_admin_node.sh has changed so the detection of
whether the Fuel node installation needed a correction for the deployer
not to throw an exit code and terminate prematurely.
- Small fix: deploy.py is now executable (just a chmod change).
Change-Id: I8fed7bafe6912f8b4278619bbdaa16577a82737b
Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
|
|
Project: fuel 0ac1af6354f57c389b407cb1ea1e0365027704a6
docs: Mitaka Build req: Add p7zip-full.
Build system uplift to Fuel 9.0/Mitaka now requires `7z` cmd utility
also on the builder host (not only inside docker containers), so
document this as a prereq in the build instructions.
[1] https://gerrit.opnfv.org/gerrit/#/c/13919/
Change-Id: Icb57ac58c499272fce0a27bb2d25383e933c7814
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Project: fuel 74454885828f33629f0355616017b67768bc7bd8
Clean up after ourselves
Change-Id: Id7579ef618b8cd922de325d9dc1c0b7a6c5587a7
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
Project: fuel 1378a27086272efec083778dd52fb27511b88167
A small edit for the uplift to Mitaka from Liberty
Signed-off-by: Daiel Smith <daniel.smith@ericsson.com>
JIRA:0
|
|
Project: fuel 3b8db706acb60b680bcf220bd0236d5efcc66d07
common.py: catch stderr in exec_cmd
When running commands with exec_cmd(), the stderr of the command is
sent to /dev/null and ignored, and only stdout is retrieved. Thus, when
a command fails and check is enabled, only the output of stdout is
presented to the user, which normally holds no information about the
error.
In this patch we retrieve stderr, and when an error occurs, an exception
is raised with that message.
Fixes https://jira.opnfv.org/browse/FUEL-142
Change-Id: I3940e1a43963a6abec362481b1d4ce7bd7cb816d
Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com>
|
|
Project: fuel ec0c7698cd363b71694ca33e87f65fc382acda8d
Build system uplift to Fuel 9.0/Mitaka
Switching to Fuel 9.0/Mitaka for the build system.
Overhaul of the patching mechanism. 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.
Patch naming made more descriptive.
The reaping mechanism has been slightly modified due to a change in
the naming of the node files when these are generated by the Fuel CLI.
IMPORTANT 1: The package cache mechanism is currently disabled, it is
only possible to install Fuel with a direct internet connection. This
will be fixed in a later change set!
IMPORTANT 2: All plugins has been disabled! As you have re-certified
your plugin with Fuel 9.0, please re-enable it in build/Makefile!
Change-Id: Ia918d16a74b68f89d178e06befe6e8a7a9367bf9
Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
|
|
Project: fuel ebb5b355ba542fc22b8f96f952439251d4b2c90b
Remove residual Lab & configuration DEA and DHA from the unprotected Fuel repo
This needs testing!!!!
On a follow-up release, this also needs rebasement, the libvirt templates
are still in here - they shouldnt, sinse we dont want Lab specific
configs in the Fuel repo.
NOT VERIFIED
DO NOT MERGE
Change-Id: I069ced81b886405463f27f37a6ec78e3748b37b7
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
|
|
|
|
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
|
|
Project: fuel 370cf3546e2f5e3a7afa69b4f306bd7c90d44397
More rigorous Fuel environment check
get_env() used to raise an unhandled exception when reap.py was run on a
Fuel node which didn't yet have an environment set up.
Change-Id: I07c37db2d80e416d26fa4fb4907f4e438f1c44e5
Signed-off-by: Peter Barabas <peter.barabas@ericsson.com>
|
|
|
|
|
|
|
|
Project: fuel b0b2e869cae884aaed305f2984701dc813a469ec
docs/install-instr: Add target specific cfg sect.
Fuel 8.0 adds support for setting up "Offloading Modes" for
target nodes.
Document how this features should be used (and why/when it's
necessary), and also its common limitation of not being applied
during Verify Networks step (see related Fuel bug report [1]).
While at it, fix minor reference to branch in git tag checkout
instructions, as we'd be in detached HEAD and not on a new branch.
[1] https://jira.opnfv.org/browse/FUEL-134
[Alexandru.Avadanii@enea.com]
Only minor edits and prepared for upstreaming, this is mostly
based on previous work from Florin.
Change-Id: If7a8ca44541903dbeb6db36bc64fe56b132165cb
Signed-off-by: Florin Dumitrascu <florin.dumitrascu@enea.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
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>
|
|
I've added submodule name to `patch-import` target to make it easier to
spot in which submodule does patch import fail.
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
|
|
|
|
Project: fuel 439f684991c36f61483b12134a8c981f78f0e473
Remove coexistence configuration from post script
This is not more needed as the config comes from FUEL ODL plug-in
Change-Id: Ie09a52ac3919ac641924d41431dc000910e6d4f4
Signed-off-by: Manuel Buil <manuel.buil@ericsson.com>
|
|
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
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
Change-Id: Ic5cc1109df04a95a5e072ab3acb79eb89427a1e0
|
|
|
|
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
|
|
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>
|
|
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
|
|
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
|
|
Upstream commit:
"Update package list required for building ISO" [1]
[1] https://github.com/openstack/fuel-main/commit/
18f2c14a928bf3e92ccd4d868953361bed61614b
Change-Id: I59af524de7539489ad4dce12894573f8ff1ac5a5
|
|
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
|
|
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
|
|
Change-Id: Ic11f7c4caa801df32d12461b39e10df8f07460a7
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
Change-Id: I12126a39c90abf8fc5bef449506e87dc190a50ee
|
|
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>
|
|
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
|
|
Rebase after upstream change [1]:
"Grub stage1 shall be installed on all of disks"
[1] https://github.com/openstack/fuel-agent/commit/
c71a424b9552c07ef1f8a068bedea9563cbe45c
|
|
|
|
While we're at it, fix minor context in remaining patch.
|
|
|
|
Since fuel-plugin-opendaylight and fuel are OPNFV components,
they do not have a stable/mitaka branch, so use master for them.
Change-Id: Ie8ae0e458953bae7006e0d411b4680f20b87a13c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- edit image with unexisting plugins on AArch64;
- change "BIOS" references to "UEFI" and add note(s) about
required firmware support;
- add warning about bootstrap image build fuelmenu config;
Change-Id: I5bcf208dcb0c95e9c09f4da0bd4e861e19d34cc0
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Document workaround for xtrabackup issues on AArch64 controllers.
Change-Id: I126c730f751f09a4d75ac345d9b889df9414de2d
|
|
Fuel 8.0 adds support for setting up "Offloading Modes" for
target nodes.
Document how this features should be used (and why/when it's
necessary).
While at it, fix minor reference to branch in git tag checkout
instructions, as we'd be in detached HEAD and not on a new branch.
Change-Id: If7a8ca44541903dbeb6db36bc64fe56b132165cb
|