blob: 142b6cb079b8bb04eb1e0ccf68e10af4d9e449a6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) by Yingjun Li (HUAWEI) and Harry Huang (HUAWEI)
os-nosdn-openo-ha Description
===========================
Introduction
------------
Since OPNFV board expanded its scope to include NFV MANO last year,
several upstream open source projects have been created to develop
MANO solutions. Each solution has demonstrated its unique value in
specific area. Open-Orchestrator (OPEN-O) project is one of such
communities. Opera seeks to develop requirements for OPEN-O MANO
support in the OPNFV reference platform, with the plan to eventually
integrate OPEN-O in OPNFV as a non-exclusive upstream MANO. The
project will definitely benefit not only OPNFV and Open-O, but can
be referenced by other MANO integration as well. In particular, this
project is basically use case driven. Based on that, it will focus
on the requirement of interfaces/data models for integration among
various components and OPNFV platform. The requirement is designed
to support integration among Open-O as NFVO with Juju as VNFM and
OpenStack as VIM.
Currently OPNFV has already included upstream OpenStack as VIM, and
Juju and Tacker have been being considered as gVNFM by different OPNFV
projects. OPEN-O as NFVO part of MANO will interact with OpenStack and
Juju. The key items required for the integration can be described as
follows.
Scenario Components and Composition
-----------------------------------
This Scenario will deploy Open-O on jump host as orchestrator and deploy
juju in an OpenStack VM as VNFM. All Open-O service can be access through
openo_ip specified in network config file.
Scenario Usage Overview
-----------------------
This scenario has an orchestrator field to specify which orchestrator to
be used.
COMPASS installer configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The os-nosdn-openo-ha scenario in Compass4NFV has an orchestrator field.
Set orchestrator type to Open-O to install Open-O after Compass4NFV finishs
NFVI deployment and Open-O version can also be assigned in key version.
With orchestrator setting to Open-O, Compass4NFV will git clone Opera
project to perform a combined deployment. Set key vnf to clearwater if you
want to launch clearwater after Open-O launched.
os-nosdn-openo-ha scenario needs to be deployed along with Open-O included
network config file. Compass4NFV has network_openo.yml to config network for
Opera.
The Open-O related info in both scenario and network config will be synchronized
into Opera after its repository being cloned.
References
----------
For more information on the OPNFV Danube release, please visit
http://www.opnfv.org/danube
|
