summaryrefslogtreecommitdiffstats
path: root/build
AgeCommit message (Collapse)AuthorFilesLines
2017-01-16build/Makefile: deepclean: make grep more strictAnders Roxell1-1/+1
Check if the docker image is named only 'ubuntu' and tag 14.04 JIRA: FUEL-245 Change-Id: I4dc58a295925cc64a1d5c52393e1c172d42f8a6e Signed-off-by: Anders Roxell <anders.roxell@enea.com>
2017-01-13Add congress plugin to build targetsMichael Polenchuk1-1/+1
Change-Id: I370f454880914b78609e0a8f778de4bee93a8553 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2017-01-11Build congress plugin as part ob building ISOFedor Zhadaev2-0/+103
JIRA: FUEL-230 Change-Id: I315a9ed955cafa68a2454c30daac9dbf41f76e05 Signed-off-by: Fedor Zhadaev <fzhadaev@mirantis.com>
2017-01-05Merge "Enable ceilometer collectd"Ruijing Guo3-15/+16
2017-01-02Rebase to ovs 2.6.x and NSHGuo Ruijing1-1/+1
1. rebase to latest ovs without NSH 2. rebase to ovs 2.6.1 with NSH Change-Id: I5481422e55fc65f48b78b4779119d9ff19868a91 Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2016-12-28Minor fix for yardstick pluginEdwin Zhai1-1/+1
Fix installation dependency and authentication failure. Change-Id: Ib15ecccaefd1e0214edd2e1d1f52ab3f9ed99f3a Signed-off-by: Edwin Zhai <edwin.zhai@intel.com>
2016-12-28Merge "Rework processorcount limits to os_workers"Alexandru Avadanii1-0/+284
2016-12-27Enable ceilometer collectdGuo Ruijing3-15/+16
1. ceilometer collectd basic functionality can work 2. will update config.mk after review #26213 is merged Change-Id: I3a115f20b176dbee93ce5d72c580c83d6b721382 Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2016-12-27build: plugins: Allow plugin env var overrideAlexandru Avadanii1-1/+1
Newton uplift [1] silently disabled env var overrides for the PLUGINS var, breaking Armband plugin selection. Proposed fix: only set this var when not already set. [1] https://gerrit.opnfv.org/gerrit/#/c/23433/ JIRA: ARMBAND-118 Change-Id: I143fc79de26cc9a3b66a177ca905984989bf4a9d Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-12-26Rework processorcount limits to os_workersMichael Polenchuk1-0/+284
JIRA: FUEL-227 Change-Id: I9186a1b0e0ef86c2efa322805c302f02c832e10f Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-12-22Merge "Reduce ceilometer memory usage"Alexandru Avadanii1-0/+30
2016-12-20Enable yardstick in D releaseGuo Ruijing2-2/+2
Change-Id: Ie9efd6a01b483e3e0797c19708cd1ca793f609d6 Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2016-12-20build: select_ubuntu_repo: break on errAlexandru Avadanii2-5/+9
Stop ISO build process if no sane Ubuntu mirrors are available, instead of continuing with an empty URL, which is bound to fail later. While at it, skip re-assesing the output of select_ubuntu_repo.sh if the URL var already is set. Also, stderr and stdout were both captured in UBUNTU_MIRROR_URL, so disable debug by default, and only print debug info in case no valid mirror is found. v2 -> v3: - allow "One hour behind" mirror state to be considered, since we already accept "Six hours behind" mirrors; JIRA: FUEL-240 Change-Id: I791942da234304528ff5cae1891415602e1a62b2 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-12-19Reduce ceilometer memory usageMichael Polenchuk1-0/+30
JIRA: FUEL-227 Change-Id: Ia18064299da7c056cb247c2f7f350e5532f2f587 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-12-15Merge "Restart sshd service instead of reload"Fedor Zhadaev1-1/+1
2016-12-14Restart sshd service instead of reloadMichael Polenchuk1-1/+1
In the middle of fuel master node bootstrap the reload of sshd service accidentally is losing main process pid, so restart it. JIRA: FUEL-237 Change-Id: I89023177e71cb6da4b9d6beff5083d345cf66db8 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-12-12build: f_repos: Re-enable Armband specific patchesAlexandru Avadanii2-0/+83
JIRA: ARMBAND-183 Change-Id: Ie43f8f9080241add1cb9d5312c774916baee0bee Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-12-09Merge "Turn kvm-plugin back on"Fedor Zhadaev2-3/+3
2016-12-08Point to latest repos of fuel 10/newtonMichael Polenchuk2-25/+5
Since swarm tests have been enabled against 10.0 so get the latest repositories into build. Change-Id: Ie24e51dbc2e80ef61dd9d892cd0083a594fd289e Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-12-08Turn kvm-plugin back onMichael Polenchuk2-3/+3
Change-Id: I7c46f263ec584b09b6022d9e961ae3c44c642954 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-12-02Enable vsperf in D releaseGuo Ruijing2-2/+2
Change-Id: Ibb5ed6a6d5dfb206388257367a66f5d758b2da9f Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2016-11-29build/f_repos: Fix remote tracking, pin N HEADsAlexandru Avadanii11-2/+1
Fix two issues that went undetected until now: - remote tracking variable does not properly evaluate in CI, since there is no HEAD reference; - git submodules references still point to master branch(es) commits, although .gitmodules configure the remote tracked branch correctly; JIRA: FUEL-234 Change-Id: I96dc704e2cfe98f2e93d5fa7d7dd261e7f151238 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-11-29Turn on remote tracking of submodulesMichael Polenchuk1-3/+1
JIRA: FUEL-234 Change-Id: I916cc94f58df2f2227384c73eda556f448ac50b5 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-11-17Turn ovs-plugin onMichael Polenchuk2-3/+3
The ovs-plugin has been rebased to fuel 10/newton. Change-Id: I23d9f33b005ec139862e4a53b70987706ae98198 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-11-15Uplift to Fuel 10.0/NewtonStefan K. Berg33-962/+117
Build working, automated deploy working (simple test cases only). All plugins disabled, so is the generation of the local ISO cache. Both need to be re-enabled after merge of this uplift. All patches wiped, pertinent ones need to be re-enabled after the merge of this uplift. Change-Id: I978a3d4ed25a45a4b88a6e35693baac597b162c2 Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-10-31Split out public_vip_ping taskMichael Polenchuk1-11/+27
Split out public_vip_ping task to avoid race condition when ping_checker resource might be started up on controllers before a primary one. JIRA: FUEL-217 Change-Id: I3c11e8403d4e1c53a7f0eac07c71f59584882332 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-10-27Shift public ping checker into deployment stageMichael Polenchuk1-0/+110
Avoid public vip failover at the end of post-deployment by moving ping_checker resource into deployment stage. Also pingd constraint has been changed to be based on score. If all the nodes failed to ping the default gw, the resource ain't stopped and remains on the last node where it was. JIRA: FUEL-212 JIRA: FUEL-217 Change-Id: I09329474cf13958499ac99bfbdf9c9055c9bcb55 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-10-27Merge "Update cirros image"Jonas Bjurel6-19/+48
2016-10-24Align globals workers_max key limitMichael Polenchuk1-5/+14
JIRA: FUEL-212 Change-Id: Ie8c50d515bffbb39deb44c32da42079b4181edd3 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-10-24Merge "[OVS] Update flavors key with large mem_page_size"Ruijing Guo1-1/+1
2016-10-21[OVS] Update flavors key with large mem_page_sizeMichael Polenchuk1-1/+1
Repoint to the "Update flavors mem_page_size" from stable/9.0 branch of plugin. Change-Id: I91d6a770faa9ee2d078b7f1ccccb7d61525ad923 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-10-20Update cirros imageMichael Polenchuk6-19/+48
To properly handle source routing passing by dhcpd inside instance get latest cirros image. JIRA: FUEL-202 Change-Id: Icd44ebbdd7b4aa0cb55c080e614616a7b0198c0f Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-10-20Rework processorcount limits to os_workersMichael Polenchuk1-0/+423
JIRA: FUEL-212 Change-Id: I1c5b8fe123406f1a96c5432d91a9ee5806c7cf62 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-10-19Merge "Import fuel-infra.org key"Michal Skalski1-0/+2
2016-10-17Point to specific snapshot of mos repositoriesMichal Skalski2-3/+5
Fuel 9.1 was released, it is a first time when new version of Fuel is distributed through the same repositories as previous one, point to specific snaphost of mos ubuntu repo to prevent mixing packages. Change-Id: I64bb52657ce476b0c1fdc8e858231ad751ba12b1 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-10-17Merge "Re-introduce mirror blacklisting"Michal Skalski1-3/+23
2016-10-14Merge "Compile DPDK to use basic cpu features"Ruijing Guo1-1/+1
2016-10-12Merge "ci, build/f_repos: Minor UX improvements"Alexandru Avadanii4-7/+41
2016-10-12Merge "[ODL] Use OpenDaylight Boron"Michal Skalski1-4/+3
2016-10-11ci, build/f_repos: Minor UX improvementsAlexandru Avadanii4-7/+41
After Armband rework landed of top of `build/f_repos` mechanism [1], the following minor UX improvements can also be applied to Fuel's f_repos: - set SHELL to "/bin/sh" (we don't use any bash-isms); - improve "From SHA..." removal for exported patches; - force checkout of root tag commit during clean; - silence progress during git clone (cleaner logs); - support git older than 1.8.4 in `make clean` (fix Armband deploy); FIXME: Pass TERM as Docker env var until [2] is fixed in Docker 1.13. v4 -> v5: * Moved `export TERM` to Releng, where it actually belongs [3]; * Fixed Armband deploys fail [4] by adjusting `make clean`; [1] https://gerrit.opnfv.org/gerrit/#/c/22791/ [2] https://github.com/docker/docker/issues/9299 [3] https://gerrit.opnfv.org/gerrit/#/c/22933/ [4] https://build.opnfv.org/ci/view/armband/job/\ fuel-deploy-armband-baremetal-daily-master/57/consoleText Fixes: FUEL-200 Change-Id: I80e3074f8659769e21f5b56f07c34c7a5de727bc Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-10-11[ODL] Use OpenDaylight BoronMichal Skalski1-4/+3
ODL Boron will be used in all scenarios except bgpvpn beacuse vpnservice was removed in this release, we still will use Beryllium for this scenario. This change only replace Beryllium with Boron, it does not use any new features like odl-netvirt-openstack. Change-Id: I95264cc97f5b9e922ab3fb7dc024724d9fb83e9c Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-10-11Re-introduce mirror blacklistingStefan K. Berg1-3/+23
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>
2016-10-11Compile DPDK to use basic cpu featuresGuo Ruijing1-1/+1
Change-Id: I3ee9e5afa416af9e6a90b77f03ed9258c6bd4b1b Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
2016-10-10Merge "build: Use OPNFV_GIT_SHA for ISO preparer ID"Alexandru Avadanii3-4/+8
2016-10-09build/f_repos: Allow out-of-tree .git dirAlexandru Avadanii2-2/+3
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>
2016-10-08build: Use OPNFV_GIT_SHA for ISO preparer IDAlexandru Avadanii3-4/+8
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>
2016-10-06Improving robustness of repo mirror selectionStefan K. Berg1-39/+81
Change-Id: If0f5b268848439aa9d2abee099bbd985abd53d5c Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-10-06Merge "build: Use git submodules for Fuel git repos"Alexandru Avadanii28-102/+455
2016-10-05build: Use git submodules for Fuel git reposAlexandru Avadanii28-102/+455
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>
2016-10-04build/docker: CI: no tag reuse on env var changeAlexandru Avadanii1-1/+1
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>