Newer
Older
Dimitrios Giannopoulos
committed
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
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="author" content="Openslice.io">
<link rel="canonical" href="http://openslice.io/develop/catalogs/">
<link rel="shortcut icon" href="../img/favicon.ico">
<title>Service Catalogs - Openslice</title>
<link href="../css/bootstrap.min.css" rel="stylesheet">
<link href="../css/font-awesome.min.css" rel="stylesheet">
<link href="../css/base.css" rel="stylesheet">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.8.0/styles/github.min.css">
<link href="../css/version-select.css" rel="stylesheet">
<script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.8.0/highlight.min.js"></script>
<script>hljs.highlightAll();</script>
</head>
<body>
<div class="navbar fixed-top navbar-expand-lg navbar-dark bg-primary">
<div class="container">
<a class="navbar-brand" href="..">Openslice</a>
<!-- Expander button -->
<button type="button" class="navbar-toggler" data-toggle="collapse" data-target="#navbar-collapse">
<span class="navbar-toggler-icon"></span>
</button>
<!-- Expanded navigation -->
<div id="navbar-collapse" class="navbar-collapse collapse">
<!-- Main navigation -->
<ul class="nav navbar-nav">
<li class="dropdown">
<a href="#" class="nav-link dropdown-toggle" data-toggle="dropdown">Overview <b class="caret"></b></a>
<ul class="dropdown-menu">
<li>
<a href=".." class="dropdown-item">Introduction</a>
</li>
</ul>
</li>
<li class="dropdown active">
<a href="#" class="nav-link dropdown-toggle" data-toggle="dropdown">Getting Started <b class="caret"></b></a>
<ul class="dropdown-menu">
<li>
<a href="../deployment/" class="dropdown-item">Deployment/Installation</a>
</li>
<li>
<a href="../nfvoconfig/" class="dropdown-item">NFV Orchestrator Configuration</a>
</li>
<li>
<a href="./" class="dropdown-item active">Service Catalogs</a>
</li>
<li>
<a href="../nfvcatalogs/" class="dropdown-item">NFV Catalogs</a>
</li>
<li>
<a href="../lcm/" class="dropdown-item">LCM Rules</a>
</li>
<li>
<a href="../architecture/consumingServicesFromExternalPartners/" class="dropdown-item">Consuming Services From External OSS</a>
</li>
<li>
<a href="../service_inventory/" class="dropdown-item">Service Inventory</a>
</li>
<li>
<a href="../alarms_actions/" class="dropdown-item">Alarms and Actions</a>
</li>
</ul>
</li>
<li class="dropdown">
<a href="#" class="nav-link dropdown-toggle" data-toggle="dropdown">Design & Architecture <b class="caret"></b></a>
<ul class="dropdown-menu">
<li>
<a href="../architecture/architecture/" class="dropdown-item">Architecture</a>
</li>
<li>
<a href="../architecture/messagebus/" class="dropdown-item">Message bus</a>
</li>
<li>
<a href="../architecture/osom/" class="dropdown-item">OSOM</a>
</li>
<li>
<a href="../architecture/oauth/" class="dropdown-item">Authentication</a>
</li>
<li>
<a href="../architecture/tmfapi/" class="dropdown-item">TMF API</a>
</li>
<li>
<a href="../architecture/nfvapi/" class="dropdown-item">NFV API</a>
</li>
<li>
<a href="../architecture/tmfweb/" class="dropdown-item">TMF WEB</a>
</li>
<li>
<a href="../architecture/nfvweb/" class="dropdown-item">NFV WEB</a>
</li>
<li>
<a href="../architecture/issuemgt/" class="dropdown-item">Issue management</a>
</li>
<li>
<a href="../architecture/centrallog/" class="dropdown-item">Central logging</a>
</li>
</ul>
</li>
<li class="dropdown">
<a href="#" class="nav-link dropdown-toggle" data-toggle="dropdown">Contributing <b class="caret"></b></a>
<ul class="dropdown-menu">
<li>
<a href="../contributing/developing/" class="dropdown-item">Developing</a>
</li>
</ul>
</li>
</ul>
<ul class="nav navbar-nav ml-auto">
<li class="nav-item">
<a href="#" class="nav-link" data-toggle="modal" data-target="#mkdocs_search_modal">
<i class="fa fa-search"></i> Search
</a>
</li>
<li class="nav-item">
<a rel="prev" href="../nfvoconfig/" class="nav-link">
<i class="fa fa-arrow-left"></i> Previous
</a>
</li>
<li class="nav-item">
<a rel="next" href="../nfvcatalogs/" class="nav-link">
Next <i class="fa fa-arrow-right"></i>
</a>
</li>
<li class="nav-item">
<a href="https://github.com/openslice" class="nav-link">openslice</a>
</li>
</ul>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-md-3"><div class="navbar-light navbar-expand-md bs-sidebar hidden-print affix" role="complementary">
<div class="navbar-header">
<button type="button" class="navbar-toggler collapsed" data-toggle="collapse" data-target="#toc-collapse" title="Table of Contents">
<span class="fa fa-angle-down"></span>
</button>
</div>
<div id="toc-collapse" class="navbar-collapse collapse card bg-secondary">
<ul class="nav flex-column">
<li class="nav-item" data-level="1"><a href="#catalogs-and-templates" class="nav-link">Catalogs and Templates</a>
<ul class="nav flex-column">
<li class="nav-item" data-level="2"><a href="#createdesign-a-service-specification" class="nav-link">Create/Design a Service Specification</a>
<ul class="nav flex-column">
</ul>
</li>
<li class="nav-item" data-level="2"><a href="#manage-a-service-specification" class="nav-link">Manage a Service Specification</a>
<ul class="nav flex-column">
</ul>
</li>
<li class="nav-item" data-level="2"><a href="#assign-a-service-specification-to-service-categories-and-publish" class="nav-link">Assign a Service Specification to Service Categories and Publish</a>
<ul class="nav flex-column">
</ul>
</li>
<li class="nav-item" data-level="2"><a href="#retireremove-a-service-specification" class="nav-link">Retire/Remove a Service Specification</a>
<ul class="nav flex-column">
</ul>
</li>
<li class="nav-item" data-level="2"><a href="#consume-and-expose-service-specifications-from-other-service-catalogues" class="nav-link">Consume and expose Service Specifications from other Service Catalogues</a>
<ul class="nav flex-column">
</ul>
</li>
</ul>
</li>
</ul>
</div>
</div></div>
<div class="col-md-9" role="main">
<h1 id="catalogs-and-templates">Catalogs and Templates</h1>
<p>The Openslice Service Catalogue (accessible through the API or Services portal) contains the representation of Service Specifications, either created from the provider defining service attributes, or by supporting the GSMA Generic Slice Templates (GST) as well as the VINNI Service Blueprint. The following scenarios are supported by the Openslice Service Catalogue.</p>
<h2 id="createdesign-a-service-specification">Create/Design a Service Specification</h2>
<h3 id="first-import-some-resources-as-resource-facing-services-rfss">First Import some Resources as Resource Facing Services (RFSs)</h3>
<p>If you have any NSDs as NFV artifacts, import them through the UI menu (Import from NSD list). Then an NSD is imported as a resource and an RFS automatically is created. RFSs then later are used to design a Customer Facing Service Specification</p>
<h3 id="createdesign-a-customer-facing-service-specification">Create/Design a Customer Facing Service Specification</h3>
<p>Customer Facing Service Specification are the services offered to customers.
You can create a new Service Specification from the menu. The services created through the UI are Customer Facing Services (CFS). Usually you create a CFS as a bundle and then you include Service Specification Relationships with RFSs or/and CFSs.</p>
<p>Any Service Specification Characteristics from the RFS are copied to the CFS specification. A CFS can include multiple RFS or/and CFSs.
For example you can create a CFS spec called "A 5G Service" which is a bundle of two other services (include them in Service Specification Relationships) such as 5G eMBB Slice and a Customer VPN. So when the user orders "A 5G Service" services from 5G eMBB Slice and a Customer VPN will be created during the order.</p>
<h3 id="initial-configuration-for-osm-deployment">Initial configuration for OSM deployment</h3>
<p>if you have an initial configuration that needs to be applied in the NSD deployment, then you go to the RFS (or CFS) and in Service Specification Characteristics go and edit the OSM_CONFIG characteristic.
You can add in the Service Characteristic Value, in the Value field something like the following example which gives a floating IP to a VNF:</p>
<pre><code>{ "nsdId": "e855be91-567b-45cf-9f86-18653e7ea", "vimAccountId": "4efd8bf4-5292-4634-87b7-7b3d49108" , "vnf": [ {"member-vnf-index": "1", "vdu": [ {"id": "MyCharmedVNF-VM", "interface": [{"name": "eth0", "floating-ip-required": true }]}]}]}
</code></pre>
<p>or a more complex example (beautify it first if you want to view it, but in the parameter OSM_CONFIG must be minified like the example):</p>
<pre><code>{"nsdId":"e855be91-567b-45cf-9f86-18653e7","vimAccountId":"4efd8bf4-5292-4634-87b7-7b3d491","vnf":[{"member-vnf-index":"1","vdu":[{"id":"haproxy_vdu","interface":[{"name":"haproxy_vdu_eth1","floating-ip-required":true}]}]}],"vld":[{"name":"pub_net","vim-network-name":"OSMFIVE_selfservice01"},{"name":"management","vim-network-name":"OSMFIVE_selfservice01"},{"name":"lba_net","vim-network-name":"lba_net","vnfd-connection-point-ref":[{"member-vnf-index-ref":"1","vnfd-connection-point-ref":"haproxy_private","ip-address":"192.168.28.2"}]},{"name":"backend_net","vim-network-name":"backend_net","vnfd-connection-point-ref":[{"member-vnf-index-ref":"3","vnfd-connection-point-ref":"haproxy_public","ip-address":"192.168.20.2"}]},{"name":"lb_sb_net","vim-network-name":"lb_sb_net","vnfd-connection-point-ref":[{"member-vnf-index-ref":"3","vnfd-connection-point-ref":"haproxy_private","ip-address":"192.168.28.2"}]},{"name":"breaking_point_Spain","vim-network-name":"sb_repo_net"},{"name":"breaking_point_Greece","vim-network-name":"5TONICexternal"}],"additionalParamsForVnf":[{"member-vnf-index":"2","additionalParams":{"target_IP":"192.168.20.2"}},{"member-vnf-index":"4","additionalParams":{"target1_IP":"192.168.21.2","target2_IP":"10.154.252.10"}}]}
</code></pre>
<p>You can leave the Alias and Unit of Measure as is. Check also the is Default.</p>
<h3 id="day-2-primitive-actions">Day 2 Primitive Actions</h3>
<p>NFVOs like OSM allow to perform actions while a service is running, for example change attributes or make actions on a specific VNF. To design this do something similar to the following example:</p>
<ul>
<li>Go to the RFS related to the NSD that contains VNFs with primitives</li>
<li>create a characteristic named Primitive::<primitive> , e.g. Primitive::touch</li>
<li>select Value Type: ARRAY</li>
<li>add Service Characteristic Value: i) alias=primitive, value=<primitivename> (e.g. touch), ii) alias=member_vnf_index, value=<vnf index> (e.g. 1), iii) add the params that the user will change in alias the name of param and in value an initial value (e.g. alias=filename, value=myfile.txt)</li>
</ul>
<p>In the above example, when the service is running and the user goes to service inventory to MODIFY it, changes the value of the alias=filename, value=myfile.txt, to value =secondfile.txt. Then inside the VNF a file will be created called secondfile.txt</p>
<h3 id="generic-slice-templates-gst">Generic Slice Templates (GST)</h3>
<p>(Offered only as a design for now. THere is no direct implementation to NFV)
On October 16th 2019 GSMA published NG.116 Version 2.0 which defines the Generic Network Slice Template (GST). GST is a set of attributes that can characterise a type of network slice/service. GST is generic and is not tied to any specific network deployment. Here is a list of the various attributes of the template:</p>
<ul>
<li>Availability</li>
<li>Area of Service</li>
<li>Delay tolerance</li>
<li>Deterministic communication</li>
<li>Downlink throughput per network slice</li>
<li>Downlink throughput per UE</li>
<li>Energy efficiency</li>
<li>Group communication support</li>
<li>Isolation level</li>
<li>Location based message delivery</li>
<li>Maximum supported packet size</li>
<li>Mission critical support</li>
<li>MMTel support</li>
<li>NB-IoT support</li>
<li>Network Slice Customer network functions</li>
<li>Number of connections</li>
<li>Number of terminals</li>
<li>Performance monitoring</li>
<li>Performance prediction</li>
<li>Positioning support</li>
<li>Radio spectrum</li>
<li>Reliability</li>
<li>Root cause investigation</li>
<li>Session and Service Continuity support </li>
<li>Simultaneous use of the network slice</li>
<li>Slice quality of service parameters</li>
<li>Support for non-IP traffic </li>
<li>Supported access technologies </li>
<li>Supported device velocity </li>
<li>Synchronicity</li>
<li>Terminal density </li>
<li>Uplink throughput per network slice </li>
<li>Uplink throughput per UE</li>
<li>User management openness</li>
<li>User data access </li>
<li>V2X communication mode</li>
</ul>
<p>Openslice offers the GST in a format that is machine readable and aligned with the TMF SID model. Here is a tentative approach in JSON : <a href="https://github.com/openslice/org.etsi.osl.tmf.api/blob/master/src/main/resources/gst.json">https://github.com/openslice/org.etsi.osl.tmf.api/blob/master/src/main/resources/gst.json</a></p>
<p>Providers can clone a GST as e NEST directly in Openslice Web portal and the adjust the default attributes to their Service Specification</p>
<h3 id="5g-vinni-service-blueprint">5G-VINNI Service Blueprint</h3>
<p>(Offered only as a design for now. THere is no direct implementation to NFV)
5G-VINNI Service Blueprint is a special Service Specification defined by teh 5G-VINNI project. Many details can be found in document <a href="https://zenodo.org/record/3345612">https://zenodo.org/record/3345612</a></p>
<p>5G-VINNI Service Blueprint is a reusable self-contained specification of required network slice service (instances). As described in GST mapping VINNI-SB is also machine readable. </p>
<p>Here is a tentative approach in JSON : <a href="https://github.com/openslice/org.etsi.osl.tmf.api/tree/master/src/main/resources/vinnisb">https://github.com/openslice/org.etsi.osl.tmf.api/tree/master/src/main/resources/vinnisb</a></p>
<p>5G-VINNI SB has many commonalities with GST as well as it offers Testing as a Service attributes.</p>
<p>Next figure presents the high-level object model of a 5G-VINNI service blueprint.</p>
<p>The 5G-VINNI SB as a first prototype approach is conceived as a CFS of a ‘bundle’ of services. It has some characteristics, like name, description, service type (eMBB, etc) and others. The constituent services are:</p>
<ul>
<li>A “Service Topology” Service Specification which is related to a Network Service Resource topology (a Logical Resource Spec). It is considered at this stage as an RFS but is subject to change in future</li>
<li>A “VINNI SB Service Requirements” Service Specification which is related to Service requirements. This is very similar to GST. It is considered at this stage a CFS.</li>
<li>A “VINNI SB Service Exposure Level 1” Service Specification which contains characteristics for service exposure on level 1 ( see D3.1 for details). It is considered at this stage a CFS.</li>
<li>A “VINNI SB Service Exposure Level 2” Service Specification which contains characteristics for service exposure on level 2. It is considered at this stage a CFS.</li>
<li>A “VINNI SB Service Exposure Level 3” Service Specification which contains characteristics for service exposure on level 3. It is considered at this stage a CFS.</li>
<li>A “VINNI SB Service Exposure Level 4” Service Specification which contains characteristics for service exposure on level 4. It is considered at this stage a CFS.</li>
<li>A “VINNI SB Service 3rd part VNF” Service Specification which contains characteristics for support 3rd party VNFs to be included in the service. It is considered at this stage as an RFS but is subject to change in future</li>
<li>A “VINNI SB Service 3rd part NSD” Service Specification which contains characteristics for support 3rd party NSDs to be included in the service. It is considered at this stage as an RFS but is subject to change in future</li>
<li>A “VINNI SB Service Monitoring” Service Specification which contains characteristics for offering Monitoring capabilities on the requested Service. It is considered at this stage a CFS.</li>
<li>A “VINNI SB Service Testing” Service Specification which contains characteristics for offering Testing capabilities on the requested Service. It is considered at this stage a CFS.</li>
</ul>
<p><a href="../images/vinni_sb_model_diagram.png"><img alt="VINNI SB Template Model diagram" src="../images/vinni_sb_model_diagram.png" /></a></p>
<h2 id="manage-a-service-specification">Manage a Service Specification</h2>
<p>You can manage them though the Web UI</p>
<h2 id="assign-a-service-specification-to-service-categories-and-publish">Assign a Service Specification to Service Categories and Publish</h2>
<p>Just create categories and from the menu select the category and add services</p>
<h2 id="retireremove-a-service-specification">Retire/Remove a Service Specification</h2>
<p>Delete it from the category</p>
<h2 id="consume-and-expose-service-specifications-from-other-service-catalogues">Consume and expose Service Specifications from other Service Catalogues</h2>
<p>See more on <a href="../architecture/consumingServicesFromExternalPartners/">Consuming Services From External Partner Organizations</a></p></div>
</div>
</div>
<footer class="col-md-12">
<hr>
<p>Copyright © 2019-2023 Openslice Project</p>
<p>Documentation built with <a href="https://www.mkdocs.org/">MkDocs</a>.</p>
</footer>
<script src="../js/jquery-3.6.0.min.js"></script>
<script src="../js/bootstrap.min.js"></script>
<script>
var base_url = "..",
shortcuts = {"help": 191, "next": 78, "previous": 80, "search": 83};
</script>
<script src="../js/base.js"></script>
<script src="../js/version-select.js"></script>
<div class="modal" id="mkdocs_search_modal" tabindex="-1" role="dialog" aria-labelledby="searchModalLabel" aria-hidden="true">
<div class="modal-dialog modal-lg">
<div class="modal-content">
<div class="modal-header">
<h4 class="modal-title" id="searchModalLabel">Search</h4>
<button type="button" class="close" data-dismiss="modal"><span aria-hidden="true">×</span><span class="sr-only">Close</span></button>
</div>
<div class="modal-body">
<p>From here you can search these documents. Enter your search terms below.</p>
<form>
<div class="form-group">
<input type="search" class="form-control" placeholder="Search..." id="mkdocs-search-query" title="Type search term here">
</div>
</form>
<div id="mkdocs-search-results" data-no-results-text="No results found"></div>
</div>
<div class="modal-footer">
</div>
</div>
</div>
</div><div class="modal" id="mkdocs_keyboard_modal" tabindex="-1" role="dialog" aria-labelledby="keyboardModalLabel" aria-hidden="true">
<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<h4 class="modal-title" id="keyboardModalLabel">Keyboard Shortcuts</h4>
<button type="button" class="close" data-dismiss="modal"><span aria-hidden="true">×</span><span class="sr-only">Close</span></button>
</div>
<div class="modal-body">
<table class="table">
<thead>
<tr>
<th style="width: 20%;">Keys</th>
<th>Action</th>
</tr>
</thead>
<tbody>
<tr>
<td class="help shortcut"><kbd>?</kbd></td>
<td>Open this help</td>
</tr>
<tr>
<td class="next shortcut"><kbd>n</kbd></td>
<td>Next page</td>
</tr>
<tr>
<td class="prev shortcut"><kbd>p</kbd></td>
<td>Previous page</td>
</tr>
<tr>
<td class="search shortcut"><kbd>s</kbd></td>
<td>Search</td>
</tr>
</tbody>
</table>
</div>
<div class="modal-footer">
</div>
</div>
</div>
</div>
</body>
</html>