summaryrefslogtreecommitdiffstats
path: root/deploy/config/plugins
AgeCommit message (Collapse)AuthorFilesLines
2016-10-11[ODL] Use OpenDaylight BoronMichal Skalski1-2/+2
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-03Use tacker plugin in SFC scenarioMichal Skalski1-0/+48
JIRA: FUEL-205 verify: no-cache Change-Id: I37746bf3e490f6b707de8fe56af10f1df932908c Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-09-18Repo tidy-up + licence scrubingJonas Bjurel3-0/+24
- 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>
2016-08-12Allign odl-sfc scenarios with new plugin versionMichal Skalski1-21/+5
ODL Boron use different set of sfc features. JIRA: FUEL-169 Change-Id: I38c1e518ffbf625a68f879779c01e4abfdb1d672 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-07-27Fix configuration for kvm scenarioMichal Skalski1-0/+34
JIRA: FUEL-157 Change-Id: I5baafd4395a2d298a24cccda042d5b43824ae7a0 Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-07-04Plugin version is requiredMichal Skalski1-0/+2
Plugin version is required when plugin configuration is overwritten. Change-Id: I93af002ed5e994c90b9134f8c020a3822e81e42c Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-07-04Modify the indent in fuel-odl_0.9.0.yaml.wu.zhihui1-142/+142
Change-Id: I15bb84c35c075037df23746b75b108e2d7b90ede Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-07-01[BGPVPN] Uplift plugin to MitakaNikolas Hermanns1-0/+22
Change-Id: I9db366806ec97b44b0e537ee2d4beb3c8a968b92 Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
2016-06-30Uplift fuel and nshovs plugins configsNikolas Hermanns2-0/+194
Change-Id: I86cdef9d3e3337d1b16b9154c940f73b0a3d8567 Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
2016-06-15build and deploy onos plugin for fuel9wuwb19891-0/+38
Change-Id: I04dd8b4bdddc5678b158d7287c6ffc52d1bce135 Signed-off-by: wuwb1989 <wuwenbin2@huawei.com>
2016-04-06Enable BGPVPN_extension/SDNVPN_featureNikolas Hermanns1-0/+117
This commit includes the bugfixes and changes for BGPVPN_extensions and SDNVPN_feature of ODL. Change-Id: I9832680109edae497f7a344d5626568d3a335a15
2016-03-08[BGPVPN] Correct BGPVPN plugin fileNikolas Hermanns1-0/+22
The plugin config 0.0.2 has some missleading statements. At some point in time we should delete it and only use this one here. Change-Id: I6ceb2d2b7379ad691e4c7116ed7bc552deffc099
2016-02-17Scenario for SFCJonas Bjurel1-0/+44
Pleas carefully review this patch, especially the ODL features NOT VERIFIED DO NOT MERGE Change-Id: Ief3fa22d5fd03c17101aef4cbe7dcf88f5f14e8c Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
2016-02-16Merge "Applying ODL changes to BGPVPN scenario"Jonas Bjurel1-0/+23
2016-02-15Applying ODL changes to BGPVPN scenarioNikolas Hermanns1-0/+23
Since module substitionion does not support arrays the plugin attributes are added to the scenario file and not taken from the plugin files. In addition the bgpvpn plugin contains a fix for the instable stable/liberty branch now. Change-Id: I94ce93bbbe6596ff9417bdd8c11dc62cd2167c11
2016-02-15Rebased NFVOVS to the new plugin archJonas Bjurel1-0/+35
Change-Id: I4eb093c2fe4208975d08ffc2477e8ff04b213afd Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
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>
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>
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>
2016-01-29onos-configdongfeng1-0/+24
Change-Id: I10af719aa70dd9fde333542f507033903a6224de
2016-01-22OpenDaylight 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>
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
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>