Age | Commit message (Collapse) | Author | Files | Lines |
|
Some mirrors are misbehaving, for instance due to flood protection,
which makes them unreliable. This change re-introduces the possibility
to blacklist them locally.
Change-Id: I7840ac0a622f2997395e54911685f9eea393dee4
Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
|
|
Change-Id: I3ee9e5afa416af9e6a90b77f03ed9258c6bd4b1b
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
|
|
ArmbandFuel@OPNFV uses Fuel@OPNFV git repo as a submodule, so
its .git dir is located outside work tree root (F_GIT_ROOT).
Allow this setup by parsing `git rev-parse --git-dir` intead of
harcoding git dir path.
Fixes: FUEL-200
Change-Id: Ia7f3b23e9333356fe05b9ed0565218f2c7ec8eba
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
isoinfo -i lists the following information for Fuel@OPNFV ISO:
"Data preparer id: 86aafaf5454a846c417848bb94f264c4420160f3"
where the SHA hash is Fuel git repo HEAD SHA.
For Armband's build system, using only the Fuel commit ID is not
enough to fully describe the state of the source code, as patches
are also applied to other fuel modules (as git submodules).
Instead, a pointer to a valid Armband commit ID should be used.
However, Armband overrides OPNFV_GIT_SHA to the Armband git repo
commit hash, so the ISO metadata should also reflect this.
While at it, allow product name to be overriden, to signal the
commit ID should be looked up inside the Armband repository.
Change-Id: I33ad490f1afe28c1d439dda40e39cee1955e0ac2
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: If0f5b268848439aa9d2abee099bbd985abd53d5c
Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
|
|
|
|
This change reworks support for cloning (fetching) and patching all
Fuel components (fuel-library ... fuel-ui, see [1] for full list),
both outside the ISO build process (for development purposes, like
testing OPNFV patches apply cleanly to each component), and during
the ISO build.
The implementation relies heavily on git submodules and patches,
so backporting pending upstream gerrit changes, as well as adding new
out-of-upstream-tree patches, should be trivial.
Also, since without tracking remotes the repos rarely change, leverage
the in-place OPNFV build caching mechanism to drastically reduce the
number of git clones during each build.
The mechanism is detailed more in-depth in the JIRA ticket [3], and
it's merely a rehash of the submodule handling in Armband, implemented
initially by Stanislaw Kardach <stanislaw.kardach@cavium.com>.
Pros (+ new features):
- OPNFV patches for Fuel components can be applied (imported) or
developed (exported) outside of the ISO build process;
- git repo caching reduces the number of external pulls;
- reuse the same fuel-* componets in ALL targets
e.g. fuel-mirror used to employ 2 slightly different git trees;
- one step closer to Fuel/Armband merge (lots of steps left though);
Cons:
- adds a lot complexity to solve a non-problem (handling the repos
is fine in the current form, for the current goals);
However, patching <fuel-astute> or <fuel-agent> seems to be
quite complicated with the current mechanism, as env vars
override our locally patched repos for these components).
The proposed change should eliminate this issue completely.
CHANGE:
Aligned divergent fuel-mirror in ISO vs local repo build by
applying the 302 redirect fix ("Fixed handling http redirects") [2]
on top of 9.0.1 tag in fuel-mirror repo, and using that for both.
This obsoleted the followking mk file:
- build/f_isoroot/f_repobuild/config.mk
CHANGE:
Removed unused make target `get-fuel-repo` from build/config.mk.
FIXME:
Remote tracking is currently deactivated for all branches.
Change this when remote HEAD should be tracked instead,
e.g. during Newton rebase.
[1] https://github.com/openstack/fuel-main/blob/stable/mitaka/repos.mk#L32
[2] https://review.openstack.org/#/c/334882/
[3] https://jira.opnfv.org/browse/FUEL-200
TODO: Extend build/f_repos/README.md with info about:
- branch changes;
- tag bumps;
- patching now supports subdirs;
v5 -> v6:
* Added support for nesting patches in subdirs, to be used for feature
groups and related changes across submodules.
E.g. Upcoming multiarch EFI support could go in:
- .../f_repos/patch/fuel-agent/multiarch-efi/...;
- .../f_repos/patch/fuel-astute/multiarch-efi/...;
While Armband patches could go in:
- .../f_repos/patch/fuel-agent/armband/...;
- .../f_repos/patch/fuel-astute/armband/...;
etc.
v6 -> v13:
* fix wrong tag used for VERSION dump;
* fix wrong tag used for patches-export;
* move OPNFV_TAG to main config.mk and use it in FUEL_*_COMMIT;
* only run `patches-import` when patches changed / not yet applied;
* only run `clean` for stale `.cacheid` (avoid re-applying patches);
* allow git submodule path/name to be different (FIXED);
* put-cache should only run when artifact is not already cached;
* `git am`: use 3-way merge so already applied patches are gently
skipped (useful for upstreaming patches from Armband);
* Properly support nested patch dirs;
* Colorize the output a little;
JIRA: FUEL-200
Change-Id: I9dbdd9b3022896d4497d21be8dacc859730db489
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
The previous change adding support for OPNFV build tag reuse
added the get/put-cache functionality to `build/docker` just
for detecting env var changes between tag creation and current build.
Obviously, when building outside CI, it is up to the end user to
force a docker rebuild when env vars change (this was the behavior
before the tag reuse support too).
An alternative approach would be removing get/put-cache completely,
if we consider the env vars (http proxy related) never change for
CI cached builds (seems to be true, worst case we wait 1 day for
the tag to expire when it happens).
This change just fixes the original intended behavior in tag reuse.
JIRA: FUEL-204
Change-Id: I14666994bc334012a5198a64a4a24cd4962e4bd6
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
JIRA: FUEL-205
This change integrates https://github.com/openstack/fuel-plugin-tacker
to the Fuel project.
Change-Id: I51b1bdeeb678e55b85393f6a9f8180fc79322e8f
Signed-off-by: George Paraskevopoulos <geopar@intracom-telecom.com>
|
|
During CI build loops, the workspace is freshly fetched,
so '.docker' make target is built each time.
Reuse existing 'opnfv.org/ubuntu-builder:14.04' tag if present, but
enforce a configurable lifespan for this tag (currently 1 day), so
it does not get stale.
JIRA: FUEL-204
Change-Id: I8d1bd81f3e5e81068e9586c9bea9f43b3327eb38
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Fix setting bgpd password with puppet
* Enable G1 garbage collector
* Adding caching possiblity
* Add firewall resource that opens BGP ports
Change-Id: I8f779ba7356acf52967e594a1a213edf192962fc
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
|
|
Meanwhile we're investigating the issues with Ubuntu repo mirror selection,
we will hardcode the Ubuntu repo mirror
Change-Id: I776bd3a8a72dc87e00052e8ff965de1134293c7a
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Change-Id: I6db0bfaab5462a9a8f8de64bc1b088607d407bab
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: I420cd75ce2749d438e340f72c3af65c28137fb8a
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
JIRA: FUEL-171
Change-Id: Iead815ba2da76493f108ad71bc32cff265302b55
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Whitewash the geographically "close" mirrors against the list of
fully synced mirrors - we've had a few instances of getting bad
mirrors which would break the script.
All credit goes to:
https://askubuntu.com/questions/39922/how-do-you-select-the-fastest-mirror-from-the-command-line
... and we should perhaps use the netselect tool as well somewhere down
the line, but this fixes the most urgent problem.
Change-Id: Ia61a2bd78657b28019f57fc1962d410e754e6d2a
Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
|
|
- Added licences and (c) to files not complying to Licence and (c) policies.
- Removed example templates not having correct licence claims and no longer being rellevant.
- Removed the Vagrant deployment method as it is not used, not rebased/up to date and not holding correct license claims.
Strategies used:
- Machine generated are not assigned an licence text, the licence follow from the source.
- Generated patch files are not assigned an licence text, the licence follow from the source.
Change-Id: I9763f076eae51fbb2d4e5cb8cacfa4bb6cf338cc
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Get all gcc/compile options to conform to corei7 arch.
JIRA: FUEL-186
Change-Id: I5ce76631aac9174c69362f96f71e26285fc95842
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Pull in "Update flavors mem_page_size"
Change-Id: I3e285cefee561dbbc02eb9ab7d2e9c01eef2742a
Signed-off-by: Billy O'Mahony <billy.o.mahony@intel.com>
|
|
It should fix problems with vm communication through floating IPs.
Change-Id: Icadc71f2b99c28715c15389e59111272a21440fb
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Change-Id: Id2405bc3b636178791428b9bab739fdaa0f094a2
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Try to allocate enough hugepages for all NUMA nodes.
JIRA: FUEL-186
Change-Id: Idcdf6ab616dfbd9ef1104be8d1667421221ea5f2
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
JIRA: FUEL-189
Change-Id: I54854e4cc87f0c0e9e348e18131aa88b70e30054
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: I2cf5df2f0469f21f64e0e7d11740058639f68697
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
|
|
make iso generates:
libisofs: WARNING : File "/ubuntu/pool/main/libj/\
libjs-twitter-bootstrap-datepicker/libjs-twitter-bootstrap-\
datepicker_1.3.1+dfsg1-1~u14.04+mos1_all.deb" can't be added
to Joliet tree, because its path length is larger than 240
At the end this package is missing in latest ISO.
NOTE: This issue is only triggered on certain kernels during build.
Closes-bug: FUEL-190
Change-Id: I21f7f1cbe3f64317d2feb66e371611a654cf30f8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Rsync protocol was used for creating local mirrors, but now we only need
http connection. This requirement can be problematic for environments
which are behind proxy and can lead to build failures when rsync is not
allowed.
Change-Id: I4efcf500fd0c25de5fdb87307e7210cc4a96714d
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
For SFC scenario we need to use ODL Boron. Since it is not yet released
there is no persistent location for a tarball. Use opnfv artifacts to
store Boron build which include required changes.
Change-Id: I43e35dbdf5ca0160d48a1adc817db071fd5db85d
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Change-Id: I175178cdcbab52ac024157d2c5707fd7e1236dd4
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.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.
[1] https://github.com/openstack/fuel-main/blob/stable/mitaka/repos.mk
#L32-L44
Change-Id: I5e4adc7285054777c3898592ed48482ccd2b706f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: FUEL-186
Change-Id: Id44a786f69d78b378fbabea2c70ab1ca78651729
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
* changes:
build: cache: Consider UBUNTU_ARCH in .cacheid
repo mirror: Allow multi-arch local mirrors
|
|
* changes:
build: Allow MIRROR_MOS_UBUNTU override
build: Allow PLUGINS override
|
|
JIRA: FUEL-185
Change-Id: Id14d30154b63abc915a0cd55835bb72cee862dde
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Usually UBUNTU_ARCH is not changed inside the same repository,
but we should consider this case anyway for future merging
Armband and Fuel@OPNFV repositories/build systems.
This applies to all Fuel plugins and the local repo.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Instead of using BUILD_FUEL_PLUGINS, which was intended for manual
overrides of the Fule@OPNFV plugin list, allow PLUGINS to be
preset to a custom list, which we will provide via Armband
Makefile spec.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Original patch from Stan, signed by me for upstreaming.
This patch allows specifying multiple architectures via UBUNTU_ARCH in
form of a list of space separated architectures. The first architecture
in the list is considered primary and will be used for building all the
deb packages by fuel-main. Additional architectures are added to allow
targets of other architectures to use the mirror.
NOTE: this imposes a requirement that all packages built are arch
independent (which is true so far).
[ Alexandru Avadanii ]
Reworked for applying on top of Fuel@OPNFV.
Pass UBUNTU_ARCH to Docker containers.
Change-Id: Ibc4ae03223545383813ac58ec34d44c1f97b4694
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
This NIC is used on Ericsson CI POD2
JIRA: KVMFORNFV-45
JIRA: FUEL-171
Change-Id: I44576b399b6195ccc1e64dfc0b04e239ced8acc7
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Some users where confused if the change we are doing
here is a change to ODL or the fuel-plugin-opendaylight.
So renaming helps for more understanding.
Change-Id: I886d7be3db995f37f9451c06ee22c16d540254e1
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
When running functes ODL crashes in the middel
and is not starting again. Investigtion
showed that it is due to insufficient memory
of the java vm.
Change-Id: I18cda9ed5bed91e72fd91aaf0efa02c5e1a3c8d1
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
Remove the workaround marked by "# fix me" mentioned in commit id:
e8928f93b50df3ecb11942ab754bae848c082c6a, since the issue (some files
generated during kvmfornfv building are owned by "root") already
resolved in fuel-plugin-kvm build process.
Change-Id: I5efb60173b9974f6fba25f04da1f4b1f53207b1a
Signed-off-by: davidjchou <david.j.chou@intel.com>
|
|
Move kernel installation to main phase of deployment which may reduce
problems with mcollective agent after node reboot.
JIRA: KVMFORNFV-45
JIRA: FUEL-171
Change-Id: I48308471f9336b73cde238ff055433f030395e19
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|