aboutsummaryrefslogtreecommitdiffstats
path: root/deploy/config/dea_base.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-05-03Revert "Revert "Select the fastest mirror of repos""Michael Polenchuk1-3/+3
This reverts commit 7785a18f592ecd6eeb307b7bc2f5b134e8e07221. https://bugs.launchpad.net/fuel/+bug/1669751 has been resolved. Change-Id: I009cf6cba8aaa7ff2ae625c5067aa4d1570e4793 JIRA: FUEL-261 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2017-03-31Update Host OS NTP Servers to pool.ntp.orgCatalina Focsa1-3/+3
Old *.fuel.pool.ntp.org values are no longer accessible Change-Id: I0879dbd6a262491b4dc9f24d77fb87a007cbaec8 Signed-off-by: Catalina Focsa <catalina.focsa@enea.com>
2017-03-03Enable experimental features by defaultMichael Polenchuk1-0/+2
JIRA: FUEL-260 Change-Id: I2235a876ffd8a403548b380fe28b62c67b0b43ea Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2017-03-02Revert "Select the fastest mirror of repos"Michael Polenchuk1-3/+3
This reverts commit fc94d23c7780bab8d14ecf7f04603c2c1d4aa7d3. Since connectivity_tests doesn't support "mirror" method. Change-Id: I1fa0a8fafbce0dec271fed67b3599efd40d5cac0 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2017-03-02Select the fastest mirror of reposMichael Polenchuk1-3/+3
apt-get supports a "mirror" method that will automatically select a closest mirror based on geographical location. Change-Id: I15d345de759e616a705abcdec3588ea4b9409d0a Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2017-02-02f_repobuild: Temporary: Use public mirrors in CIAlexandru Avadanii1-0/+18
Offline mirrors need a second look before they can be used alone, i.e. without the public mirrors. Until we sort out all offline mirror issues, add public ones too. JIRA: FUEL-250 Change-Id: I18700f10b6fa49b541ad7bda085bc7a64f80d992 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-01-30f_repobuild: Use packetary to build partial mirrorAlexandru Avadanii1-14/+2
Packetary [1] will replace fuel-mirror in upstream Fuel. fuel-mirror is using packetary under the hood already, so the transition should not be too hard. Adapt OPNFV Ubuntu partial mirror build: - obsolete opnfv-config.yaml (packetary uses CLI args for this); - new opnfv_config.yaml will hold old ubuntu.yaml data, split at build runtime into: * mos_<arch>_mirror.yaml - MOS mirror cfg, only for deps analysis; * ubuntu_<arch>_mirror.yaml - Ubuntu mirror cfg, for pkgs download; * ubuntu_<arch>_packages.yaml - Ubuntu packages to download; While the consumers of our mirror still use `debootstrap`, which only supports the "main" repo component, make sure the "main" package set is complete, in the scope of: * ubuntu_<arch>_mirror_main.yaml - Ubuntu [main only] mirror; * ubuntu_<arch>_packages_main.yaml - Ubuntu packages for [main]; New workflow (executed for EACH architecture): 1. Collect bootstrap package deps from <fuel_bootstrap_cli.yaml>; 2. Collect all fixture release pkgs from fuel-web's <openstack.yaml>; 3. Add OPNFV extra pkg deps from "opnfv_config.yaml" (based on old fuel-mirror) Currently, this is based on old fuel-mirror's <fuel-mirror/contrib/fuel_mirror/data/ubuntu.yaml>, holding a hardcoded list of package deps; plus eventual extra OPNFV packages, like additional kernels, bootloaders etc. Since we now inspect MOS repos for deps with packetary, this old list should be easy to throw away as soon as we confirm each item is directly required by another, already existing package in the mirror. For now, keep the old list as safety net for missing deps. NOTE: Dependencies up to and including this group should also be satisfiable from Ubuntu "main" repo component only. 4. Append plugin dependencies to the package list; 5. Run `packetary unresolved` for MOS repos, gathering MOS deps that should be fetched from Ubuntu. The new packages will be appended to the predefined list from old "ubuntu.yaml"; 6. Run `packetary clone` to download all required pkgs for the partial Ubuntu mirror. 7. IF repo component merging is disabled, run `packetary clone` only on Ubuntu[main] repo components to download any (still) missing dependencies for `debootstrap`, which only looks at this component, and not the whole mirror. 8. IF repo component merging is enabled, run first `dpkg-scanpackages` to filter out old duplicate versions of packages, then run `packetary create` to merge all repo comps into a single "main". v1 -> v2: - multiarch support (activated via UBUNTU_ARCH envvar); - fixed debootstrap missing deps in "main" component of Ubuntu mirror; - factored out some hardcodes into variables/functions; - add .gitignore file; - move generated config files to "opnfv_config" subdir; - add arm64 Ubuntu repo URL (ports.ubuntu.com is separated from the main Ubuntu mirror, archive.ubuntu.com, which only holds x86 pkgs); v3 -> v4: - introduce env var "MIRROR_UBUNTU_MERGE" to control local mirror repo-component merging into a single "main"; - enable mirror repo-component merging by default, edit fuel_bootstrap_cli.yaml accordingly; v4 -> v6: - edit dea_base to use only main mirror; - fix duplicated logs; - remove `-q` flag for `create`; v6 -> v7: - rebase for Newton fuel_bootstrap_cli.yaml (s/trusty/xenial/); - include OPNFV plugin deps in local Ubuntu mirror; - add `vgabios` dependency, required for arm64 guest firmware; - remove all fuel-mirror references; - merge old fuel-mirror pkglist to OPNFV pkglist; - update packetary commit to include upstream bugfixes [2, 3]; v7 -> v11: - re-enable f_repobuild after Newton rebase; - fix leftover "trusty" ref to "xenial"; - force f_repobuild rebuild to bypass cache (by editing Makefile); - extend f_repobuild .cacheid to include scripts and OPNFV config; v11 -> v12: - fix install/install.sh old refs to "trusty"; - fix out of date select_ubuntu_repo.s refs to "trusty"; v12 -> v16: - fix leftover mos9.0 / fuel-mirror references; - fix most issues reported by `pylint opnfv_mirror_ubuntu.py`; v16 -> v18: - Sync fuel_bootstrap_cli.yaml with settings.yaml.sample from 10.0: [4] Stub pass for "Get root password for build image from settings" [5] Sync pkg list with "Switch to Ubuntu Xenial" [6] "Add puppet and daemonize to default packages list" [7] "Delete kernel debug related parameter for performance" [8] "Add to bootstrap image dependencies for network checker" - Remove obsolete Trusty kernel images from pkg lists; - Don't break when plugins set is empty; - Fix missing "vim" package, which was resolved using secondary provider packages like GUI-enabled vim flavors; The proposed fix is quite sensitive, also cutting the final mirror size in half (!), and allowing us to remove a previous hacky workaround (re-running packetary only for main). - Remove "main"-only packetary run (hacky), since the new fix for "vim" also takes care of packetary solving dependencies from "universe". - Add OPNFV blacklisting to workaround "upstart" package being installed, together with "systemd" (having them both installed confuses puppet); - Currently in testing in Armband as part of [9]: * bootstrap and target image building works from offline mirror; * systemd is used instead of upstart; * full deploy is not yet confirmed, due to some AArch64 specifics we are in the process of fixing; NOTE: Without filtering out old package verisons using `dpkg-scanpackages`, bootstrap build cannot solve all deps. FIXME: Repo component merging is sort of slow, since packetary insists on copying the source files to the destination dir even if they are pointing to the same repo. FIXME: Packetary `create` uses a different directory scheme for the created mirror than the upstream Ubuntu, e.g.: [p] mirrors/ubuntu/pool/main/l/lvm2_2.02.98-6ubuntu2_amd64.deb [U] mirrors/ubuntu/pool/main/l/lvm2/lvm2_2.02.98-6ubuntu2_amd64.deb This disencourages creating the "merged" mirror in the same location as the source partial mirror. [1] https://wiki.openstack.org/wiki/Packetary [2] https://review.openstack.org/#/c/392936/ [3] https://review.openstack.org/#/c/392937/ [4] https://review.openstack.org/#/c/277353/ [5] https://review.openstack.org/#/c/345516/ [6] https://review.openstack.org/#/c/344909/ [7] https://review.openstack.org/#/c/400165/ [8] https://review.openstack.org/#/c/415912/ [9] https://gerrit.opnfv.org/gerrit/#/c/26157/ [10] https://review.openstack.org/#/c/420815 JIRA: FUEL-218 JIRA: FUEL-223 JIRA: ARMBAND-169 JIRA: ARMBAND-185 Change-Id: If2ee86f348b7683c83bfaf686baba4f1b8f555f0 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-12-15Add dkms package into initial pkgs listMichael Polenchuk1-0/+2
OVS-plugin requires DKMS installed to operate on. Also plugin yamls have been updated. Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com> Change-Id: I037b88fdf335e513d5f4e726c3daff9358397776
2016-12-05Disable public ping_checker by default on CIMichael Polenchuk1-1/+1
Change-Id: Ib0a24b7f0d5afa80bf7d05bf6fc035debb510a9e Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-11-16Update dea_base with newton versionMichael Polenchuk1-29/+230
Change-Id: I08c2be408af19df648f3538bfb1948f6ddae0180 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-09-16Enable ci off-line deploymentJonas Bjurel1-21/+3
Updated dea_base to use locak repo mirrors for off-line deployment NOT TO BE PART OF COLORADO.1 Change-Id: Ia8e2d716570267ed9a9e06e253b6a7b258ee26eb Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
2016-06-14Fixing erroneous hypervisor typeStefan K. Berg1-1/+1
A "qemu" snuck in instead of "kvm". Change-Id: Ibe704103cd1bab6e127a31d08d53f53518033539 Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-06-13Modification of deployment config for Fuel 9 and ELX labStefan K. Berg1-106/+254
Change-Id: I380087889cda079a56c8cea3acc13145dcd49046 Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-05-31A small edit for the uplift to Mitaka from LibertyDaiel Smith1-1/+1
Signed-off-by: Daiel Smith <daniel.smith@ericsson.com> JIRA:0
2016-02-05Switching to using local package mirror for installationStefan K. Berg1-21/+3
Change-Id: Ic2039bfd4fe23851197e92cce060397b54c891f0 Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
2016-02-04Correcting license and copyright terms throughout the repoJonas Bjurel1-2/+11
Please review this carefully! Strategy: 1) No strict research on copyright/who did what (if you want it changed contact the Fuel team or Jonas Bjurel) 2) Licence statements will not be added to the following file types: - Patch files or orig files for patches - Config files generated by ordinary tools, like libvirt/visrsh - GIT dierctive file - Other auto-generated files Change-Id: I48504c6f27925445dc44683a27a575bcab78d828 Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
2016-01-29Rebasement of Fuel8 deployment configuration files and scenariosJonas Bjurel1-51/+134
Note: - Lab configurations removed - Most of the POD configuration files resides in the securedlab repo - The securedlab repo is very restricive, cause it carries Lab internal secrets TODO: - Ericsson virt is not yet rebased - Intel virt is not yet rebased - LF-POD2 is not yet rebased - Deployment scenarios for vsperf, NFVOVS, NFVKVM, ONOS, VSPERF, BGPVPN is not yet rebased NOT VERIFIED DO NOT MERGE Change-Id: I59d96acb26c06abf60c254fae8ea2ced332e5884 Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
2016-01-08A simple method to separate configuration for base fuel, plugins, PODsJonas Bjurel1-0/+597
and deployment/test scenarios READY TO MERGE! Replaces: https://gerrit.opnfv.org/gerrit/#/c/3995/ Abstract -------- This deployment framework relies on a configuration structure, providing base installer configuration, per POD specific configuration, plugin configuration, and deployment scenario configuration. - The base installer configuration resembles the least common denominator of all HW/POD environment and deployment scenarios (These configurations are normally carried by the the installer projects in this case (fuel@OPNFV). - Per POD specific configuration specifies POD unique parameters, the POD parameter possible to alter is governed by the Fuel@OPNFV project. - Plugin configuration - providing configuration of a specific plugin. these configurations maintain there own namespace and are normally maintained by collaborative projects building Fuel@OPNFV plugins - Deployment scenario configuration - provides a high level, POD/HW environment independent scenario configuration for a specific deployment. It defines what features/plugins that shall be deployed - as well needed overrides of the plugin config as well as the base installer-, POD/HW environment- configurations. Objects allowed to override is governed by the Fuel@OPNFV project. Executing a deployment ---------------------- deploy.sh must be executed locally at the target lab/pod/jumpserver A lab configuration structure must be provided - see the section below. It is straight forward to execute a deployment task - as an example: sudo deploy.sh -b file:///home/jenkins/config -l ericsson-1 -p pod-2 -s os_odl-l2_no-ha -i file:///home/jenkins/MyIso.iso -b and -i arguments should be expressed in URI style. The resources can thus be local or remote. Feedback -------- Please give feed-back before I'm going to far on a wrong tangent Implemented scenarios so far: ----------------------------- - os_ha - os_no-ha - os_odl-l3_ha - os_odl-l3_no-ha - os_odl-l2_ha - os_odl-l2_no-ha - os_onos_ha - os_onos_no-ha - os_kvm_ha - os_kvm_no-ha - os_ovs_ha - os_ovs_no-ha - os_kvm_ovs_ha - os_kvm_ovs_no-ha VERIFIED READY TO MERGE JIRA: FUEL-35 Change-Id: I94a9b477d8ed4ee8057c16d8f20fe543f7ecc20d Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>