aboutsummaryrefslogtreecommitdiffstats
path: root/deploy/config/plugins
AgeCommit message (Collapse)AuthorFilesLines
2016-02-12Fix for the KVM4NFV scenariosJonas Bjurel1-0/+34
- The qemu plugin has been rebased to the newer plugin framework vesion. The scenarios need to be rebased accordingly VERIFIED READY TO MERGE Change-Id: I4d74d1e94b12763f33d7731d5899a724bedcb0ce Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com> (cherry picked from commit e4520f628c47b37aa75e9980dcfd187199962e62)
2016-02-04Correcting license and copyright terms throughout the repoJonas Bjurel7-0/+63
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> (cherry picked from commit f9e50fa686599ff4a7e94805279820d3cdfefbc4)
2016-01-29Rebasement of Fuel8 deployment configuration files and scenariosJonas Bjurel1-0/+82
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> (cherry picked from commit c43ed292f38dd9d26ee1efb02f0871501aa64dc9)
2016-01-29onos-configdongfeng1-0/+24
Change-Id: I10af719aa70dd9fde333542f507033903a6224de (cherry picked from commit 970db3c06849fb149b4844fc66d971994088c243)
2016-01-29OpenDaylight plugin for brahmaputra releaseMichal Skalski1-53/+71
Include new version of fuel-plugin-opendaylight. Changes in this version: - Support MOS 8.0. - Move ODL installation and configuration to main phase of deployment. - L3 traffic managed by ODL possible when vxlan tunneling is used. - Include snapshot of OpenDaylight Beryllium, stable version not available at this moment. - Get rid of hardcoded configuration related to specific ODL version. Now plugin is more elastic and should support a broader number of ODL versions. - odl_network_scheme function overrided standard network scheme so custom network templates are not required. - ODL is no longer patched to use br-floating bridge JIRA: FUEL-58 Change-Id: Ie3542e285a064c37d1edb6751c4853a5e7594478 Signed-off-by: Michal Skalski <mskalski@mirantis.com> (cherry picked from commit 3778f82dfe7afe258a9584f72f82ac2ee6e8d92b)
2016-01-14Adding fuel-bgpvpn-plugin and ScenarioNikolas Hermanns1-0/+13
To use the bgpvpn fuel plugin configs where added and a first scenario using it is added Change-Id: Id3c65abe39e1945f6a451c523732a513b01db696 (cherry picked from commit 76aa5bd1daf9568ab91f7586b0627062ffb26fb0)
2016-01-08A simple method to separate configuration for base fuel, plugins, PODsJonas Bjurel4-0/+125
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> (cherry picked from commit 7fd2619e0df370fa832eeff00790bcaa52dc4ffc)