Browse Source

NFV workload to test OpenStack interoperability

Change-Id: I5532d978d6ceac732ea5da9ff3c4abcf67905793
Signed-off-by: yaohelan <yaohelan@huawei.com>
yaohelan 2 years ago
parent
commit
561e7ed68b
1 changed files with 156 additions and 0 deletions
  1. 156
    0
      doc/source/specs/spec_nfv.rst

+ 156
- 0
doc/source/specs/spec_nfv.rst View File

@@ -0,0 +1,156 @@
1
+..
2
+
3
+This work is licensed under a Creative Commons Attribution 3.0 Unported License.
4
+http://creativecommons.org/licenses/by/3.0/legalcode
5
+
6
+..
7
+
8
+==================================
9
+ Run vIMS on OpenStack with OPEN-O
10
+==================================
11
+
12
+Making a voice call is a typical scenario in telecommunication industry.
13
+To make the voice calling as a NFV workload running atop OpenStack
14
+Infrastructure, such workload consists of VNF and MANO functionality,
15
+Telco needs to leverage a MANO to deploy corresponsding network services
16
+along with underlying infrastructure.
17
+In this blueprint, we deploy the voice calling workload (vIMS and Open-O,
18
+which serves as VNF and MANO respectively) on an OpenStack infrstructure.
19
+
20
+Network Function Virtualization(NFV) is a network architecture concept that
21
+uses virtualization technology in Telco industry. Virtual Network Function
22
+(VNF) is a software implementation of network functions that can be deployed
23
+on a Network Virtualization Infrastructure(NFVI). OpenStack is a type of
24
+NFVI.
25
+
26
+Running a VNF on a NFVI is a normal way to demonstrates the ability that
27
+OpenStack supports NFV. To fulfill the goal, a MANO is needed to manage the
28
+lifecycle of VNF and orchestrate the services.
29
+OPEN-O is an open source MANO project.
30
+
31
+vIMS network is a core component of deploying VoLTE services in an LTE network
32
+and it a good candidate for showing the OpenStack deployment ability.
33
+Clearwater is an open source implementation of vIMS.
34
+
35
+
36
+Problem description
37
+===================
38
+
39
+There is no existing NFV workload running on OpenStack to test interoperability.
40
+
41
+
42
+Proposed change
43
+===============
44
+
45
+The primary changes that need to be done are as follows:
46
+
47
+* Deployment scripts to deploy the workload
48
+
49
+  * Shell script to deploy OPEN-O
50
+
51
+  * Python script to call OPEN-O to deploy vIMS
52
+
53
+  * Shell script to deploy a SIP client
54
+
55
+* Test scripts to verify the workload
56
+
57
+  * Python script to confirm OPEN-O is working
58
+
59
+  * Ruby script to confirm vIMS is working
60
+
61
+
62
+Implementation
63
+==============
64
+
65
+Assignee(s)
66
+-----------
67
+
68
+Primary assignee:
69
+  Helan Yao <yaohelan@huawei.com>
70
+
71
+Other contributors:
72
+  Zhipeng Huang <huangzhipeng@huawei.com>
73
+
74
+Milestones
75
+----------
76
+
77
+Target Milestone for completion:
78
+  Pike-1
79
+
80
+Work Items
81
+----------
82
+
83
+Prerequisites
84
+
85
+1. OPEN-O VM
86
+  * at least 4 CPUs, 64G RAM, 100G Disk
87
+  * Ubuntu 16.04
88
+2. vIMS VM * 7 nodes
89
+  * 1 CPU, 2G RAM, 2G RAM, 20G Disk
90
+  * Ubuntu 12.04
91
+3. OpenStack Keystone V2 is verified while Keystone V3 is not verified
92
+
93
+
94
+Details
95
+
96
+1. Deployment scripts development to fulfill the workload
97
+
98
+  The workload of running vIMS on OpenStack with OPEN-O
99
+
100
+  1. Deploy 1 VM by OpenStack and install the OPEN-O
101
+    * refer to the prerequisite for the VM requirement
102
+
103
+  2. Bind the OPEN-O with OpenStack
104
+
105
+    * configure OpenStack as Virtual Infrastructure Manager(VIM) by calling
106
+    OPEN-O API, which is mainly about providing OpenStack authentication
107
+    information to OPEN-O
108
+
109
+  3. Deploy the vIMS by OPEN-O
110
+
111
+    * define the Network Service Descriptor(NSD) and VNF Descriptor(VNFD) to
112
+    give the overall definition for the topology
113
+
114
+    * deploy the topology by OPEN-O
115
+
116
+      * several VMs are deployed to play different roles. A Clearwater vIMS is
117
+      consist of 7 VMs includes basic function nodes and a DNS.
118
+      * refer to the prerequisite for the VM requirement
119
+
120
+  4. Configure vIMS and get specific calling number for each OpenStack vendor
121
+
122
+    * call vIMS API to generate identification for each OpenStack vendor
123
+
124
+  5. Configure the SIP client with the calling identification
125
+
126
+    * call the SIP client API to configure
127
+
128
+  6. Show the audiences by dialing a specific number
129
+
130
+2. Test scripts to verify the deployment
131
+
132
+  * script to confirm OpenStack is working
133
+
134
+    * basic scenario to create VM along with network as API verification for
135
+    the OpenStack
136
+
137
+  * script to confirm OPEN-O is working
138
+
139
+    * basic scenario to call OPEN-O services to confirm core services are working
140
+
141
+  * script to confirm vIMS is working
142
+
143
+    * basic scenario to call vIMS services to confirm main functions are working
144
+
145
+Dependencies
146
+============
147
+
148
+- Include specific references to specs and/or blueprints in interop-workloads-specs, or in other
149
+  projects, that this one either depends on or is related to.
150
+
151
+  None
152
+
153
+- Does this feature require any new library dependencies or code otherwise not
154
+  included in OpenStack? Or does it depend on a specific version of library?
155
+
156
+  OPEN-O, Clearwater vIMS, SIP client

Loading…
Cancel
Save