Browse Source

Improved the doc by following latest comments

Change-Id: I1e88d3602614397a53438f20bfc4d284fe049df8
Signed-off-by: yaohelan <yaohelan@huawei.com>
yaohelan 2 years ago
parent
commit
c58a9ae41c
1 changed files with 43 additions and 36 deletions
  1. 43
    36
      doc/source/specs/spec_nfv.rst

+ 43
- 36
doc/source/specs/spec_nfv.rst View File

@@ -12,21 +12,23 @@ http://creativecommons.org/licenses/by/3.0/legalcode
12 12
 Making a voice call is a typical scenario in telecommunication industry.
13 13
 To make the voice calling as a NFV workload running atop OpenStack
14 14
 Infrastructure, such workload consists of VNF and MANO functionality,
15
-Telco needs to leverage a MANO to deploy corresponsding network services
15
+Telco needs to leverage a MANO to deploy corresponding network services
16 16
 along with underlying infrastructure.
17 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.
18
+which serves as VNF and MANO respectively) on an OpenStack infrastructure.
19 19
 
20 20
 Network Function Virtualization(NFV) is a network architecture concept that
21 21
 uses virtualization technology in Telco industry. Virtual Network Function
22 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.
23
+on a Network Virtualization Infrastructure(NFVI). Virtualized Infrastructure
24
+Manager(VIM) is responsible for controlling and managing the NFVI resources.
25
+OpenStack is a VIM.
25 26
 
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.
27
+Running a VNF on a NFVI with the help of VIM is a normal way to demonstrate
28
+the ability that OpenStack supports NFV. To fulfill the goal, a MANO is needed
29
+to manage the life-cycle of VNF and orchestrate the services.
29 30
 OPEN-O is an open source MANO project.
31
+https://www.open-o.org/
30 32
 
31 33
 vIMS network is a core component of deploying VoLTE services in an LTE network
32 34
 and it a good candidate for showing the OpenStack deployment ability.
@@ -50,13 +52,11 @@ The primary changes that need to be done are as follows:
50 52
 
51 53
   * Python script to call OPEN-O to deploy vIMS
52 54
 
53
-  * Shell script to deploy a SIP client
54
-
55 55
 * Test scripts to verify the workload
56 56
 
57 57
   * Python script to confirm OPEN-O is working
58 58
 
59
-  * Ruby script to confirm vIMS is working
59
+  * Python script to confirm vIMS is working
60 60
 
61 61
 
62 62
 Implementation
@@ -82,13 +82,13 @@ Work Items
82 82
 
83 83
 Prerequisites
84 84
 
85
-1. OPEN-O VM
85
+1. VM to host OPEN-O containers
86 86
   * at least 4 CPUs, 64G RAM, 100G Disk
87
-  * Ubuntu 16.04
87
+  * Ubuntu 14.04
88 88
 2. vIMS VM * 7 nodes
89 89
   * 1 CPU, 2G RAM, 2G RAM, 20G Disk
90 90
   * Ubuntu 12.04
91
-3. OpenStack Keystone V2 is verified while Keystone V3 is not verified
91
+3. SIP client to make the call
92 92
 
93 93
 
94 94
 Details
@@ -97,50 +97,57 @@ Details
97 97
 
98 98
   The workload of running vIMS on OpenStack with OPEN-O
99 99
 
100
-  1. Deploy 1 VM by OpenStack and install the OPEN-O
100
+  1. Deploy OPEN-O docker containers on the host
101
+
101 102
     * refer to the prerequisite for the VM requirement
102 103
 
103
-  2. Bind the OPEN-O with OpenStack
104
+  2. Create security group and add security rules to allow icmp, tcp and ucp ports
105
+
106
+  3. Deploy a VM on OpenStack and install Juju
107
+
108
+  4. Connect Juju to OPEN-O
109
+
110
+    * set up the Juju VNFM web service developed by OPEN-O
111
+    * enable the VNFM service in OPEN-O via OPEN-O Restful API
112
+
113
+  5. Connect OPEN-O with OpenStack
104 114
 
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
115
+    * configure OPEN-O to use OpenStack as its VIM. This can be done by providing
116
+    the OpenStack authentication information to the orchestrator.
108 117
 
109
-  3. Deploy the vIMS by OPEN-O
118
+  6. Deploy the vIMS by OPEN-O
110 119
 
111 120
     * define the Network Service Descriptor(NSD) and VNF Descriptor(VNFD) to
112 121
     give the overall definition for the topology
113 122
 
114 123
     * deploy the topology by OPEN-O
115 124
 
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
125
+      * several VMs are deployed to play different roles. A detailed architecture of
126
+      Clearwater vIMS can be referred here
127
+      http://www.projectclearwater.org/technical/clearwater-architecture
123 128
 
124
-  5. Configure the SIP client with the calling identification
129
+      * refer to the prerequisite for the VM requirement
125 130
 
126
-    * call the SIP client API to configure
131
+  7. Create user on vIMS and get specific calling number for each OpenStack vendor
127 132
 
128
-  6. Show the audiences by dialing a specific number
133
+    * call vIMS API to generate authentication and calling number for each 
134
+    OpenStack vendor
129 135
 
130 136
 2. Test scripts to verify the deployment
131 137
 
132
-  * script to confirm OpenStack is working
138
+  OPNFV Functest project has test cases to verify OpenStack, OPEN-O and vIMS deployment.
139
+
140
+  * test cases to confirm OpenStack is working
133 141
 
134
-    * basic scenario to create VM along with network as API verification for
135
-    the OpenStack
142
+    * healthcheck test cases are run to make sure OpenStack is working
136 143
 
137
-  * script to confirm OPEN-O is working
144
+  * test cases to confirm OPEN-O is working
138 145
 
139
-    * basic scenario to call OPEN-O services to confirm core services are working
146
+    * to call OPEN-O services to confirm core services are working
140 147
 
141
-  * script to confirm vIMS is working
148
+  * test cases to confirm vIMS is working
142 149
 
143
-    * basic scenario to call vIMS services to confirm main functions are working
150
+    * to call vIMS services to confirm main functions are working
144 151
 
145 152
 Dependencies
146 153
 ============

Loading…
Cancel
Save