Age | Commit message (Collapse) | Author | Files | Lines |
|
This commit includes the bugfixes and changes
for BGPVPN_extensions and SDNVPN_feature of ODL.
Change-Id: I9832680109edae497f7a344d5626568d3a335a15
(cherry picked from commit 2bebed7722fe1311cd1bc4199368db16dfad9a26)
|
|
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
(cherry picked from commit 9cd38d96acee7e165faca1724f586e568498da7b)
|
|
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>
(cherry picked from commit fd28ff15dcf266c93c230b84d5b0eac152320c7c)
|
|
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
(cherry picked from commit ad8a87e29afa370207224975841420a29b408ea1)
|
|
Change-Id: I4eb093c2fe4208975d08ffc2477e8ff04b213afd
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
(cherry picked from commit 6dd9f2cda829e3e86a177c7b9b5cf8ca742bf2f7)
|
|
- 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)
|
|
Change-Id: Ic2039bfd4fe23851197e92cce060397b54c891f0
Signed-off-by: Stefan K. Berg <stefan.k.berg@ericsson.com>
(cherry picked from commit dcd792692b565be488eb4fdadb1654bf2c2161e4)
|
|
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)
|
|
Change-Id: I386113113a7f3d754f66c2a359ef4a5d18176f47
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
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)
|
|
Change-Id: I10af719aa70dd9fde333542f507033903a6224de
(cherry picked from commit 970db3c06849fb149b4844fc66d971994088c243)
|
|
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)
|
|
Change-Id: I47a5e2b3bc0e74c44256c6733e331b89889cf9c7
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
(cherry picked from commit 218381cdc6073510d7ee280c1a5f54e56b25b051)
|
|
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)
|
|
Replaces:
- https://gerrit.opnfv.org/gerrit/#/c/5999/
- https://gerrit.opnfv.org/gerrit/#/c/6003/
Description:
- Onos scenarios updated with needed dea and dha overrides, no scenario
specific information in other config files such dha, dea_base, dea_pod
override, etc.
- Added a virtual POD for Huawei-china specific needs, i.e. DNS and NTP.
- Small fix in deploy-conf.py
Change-Id: I85fe2fc4e9ec5fe0bc98ae7b399f2e49af6450f9
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
(cherry picked from commit 283bf98d087afd9073632340800e745f5a8d8de2)
|
|
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)
|