summaryrefslogtreecommitdiffstats
path: root/deploy/config/dea_base.yaml
AgeCommit message (Collapse)AuthorFilesLines
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>