1 .. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
3 .. Licensed under the Creative Commons License, Attribution 4.0 Intl.
4 (the "License"); you may not use this documentation except in compliance
5 with the License. You may obtain a copy of the License at
7 .. https://creativecommons.org/licenses/by/4.0/
9 .. Unless required by applicable law or agreed to in writing, software
10 distributed under the License is distributed on an "AS IS" BASIS,
11 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 See the License for the specific language governing permissions and
13 limitations under the License.
16 VNF On-boarding and package management
17 --------------------------------------
22 The ONAP Design Time Framework provides the ability to design NFV
23 resources including VNFs, Services, and products. The VNF provider must
24 provide VNF packages that include a rich set of recipes, management and
25 functional interfaces, policies, configuration parameters, and
26 infrastructure requirements that can be utilized by the ONAP Design
27 module to onboard and catalog these resources. Initially this
28 information may be provided in documents, but in the near future a
29 method will be developed to automate as much of the transfer of data as
30 possible to satisfy its long term requirements.
32 The current VNF Package Requirement is based on a subset of the
33 Requirements contained in the ETSI Document: ETSI GS NFV-MAN 001 v1.1.1
34 and GS NFV IFA011 V0.3.0 (2015-10) - Network Functions Virtualization
35 (NFV), Management and Orchestration, VNF Packaging Specification.
38 ^^^^^^^^^^^^^^^^^^^^^^
46 The xNF provider **MUST** include a Manifest File that
47 contains a list of all the components in the xNF package.
54 The xNF Package **MUST** include xNF Identification Data to
55 uniquely identify the resource for a given xNF provider. The identification
56 data must include: an identifier for the xNF, the name of the xNF as was
57 given by the xNF provider, xNF description, xNF provider, and version.
64 The xNF Package **MUST** include documentation describing xNF
65 Management APIs, which must include information and tools for ONAP to
66 deploy and configure (initially and ongoing) the xNF application(s)
67 (e.g., NETCONF APIs) which includes a description of configurable
68 parameters for the xNF and whether the parameters can be configured
69 after xNF instantiation.
76 The xNF Package **MUST** include documentation describing xNF
77 Management APIs, which must include information and tools for
78 ONAP to monitor the health of the xNF (conditions that require
79 healing and/or scaling responses).
86 The xNF Package **MUST** include documentation which includes
87 a description of parameters that can be monitored for the xNF
88 and event records (status, fault, flow, session, call, control
89 plane, etc.) generated by the xNF after instantiation.
96 The xNF Package **MUST** include documentation which includes a
97 description of runtime lifecycle events and related actions (e.g.,
98 control responses, tests) which can be performed for the xNF.
105 The xNF Package **MUST** include documentation describing
106 xNF Functional APIs that are utilized to build network and
107 application services. This document describes the externally exposed
108 functional inputs and outputs for the xNF, including interface
109 format and protocols supported.
116 The xNF provider **MUST** provide documentation describing
117 xNF Functional Capabilities that are utilized to operationalize the
118 xNF and compose complex services.
125 The xNF provider **MUST** provide information regarding any
126 dependency (e.g., affinity, anti-affinity) with other xNFs and resources.
132 :introduced: casablanca
133 :validation_mode: static
135 The xNF package MUST provide :doc:`VES Event Registration <../../../../vnfsdk/model.git/docs/files/VESEventRegistration_3_0>`
136 for all VES events provided by that xNF.
142 :introduced: casablanca
144 The VNF documentation **MUST** contain a list of the files within the VNF
145 package that are static during the VNF's runtime.
148 Resource Configuration
149 ^^^^^^^^^^^^^^^^^^^^^^^
157 The xNF **MUST** support and provide artifacts for configuration
158 management using at least one of the following technologies;
159 a) Netconf/YANG, b) Chef, or c) Ansible.
161 Note: The requirements for Netconf/YANG, Chef, and Ansible protocols
162 are provided separately and must be supported only if the corresponding
163 protocol option is provided by the xNF providor.
166 Configuration Management via NETCONF/YANG
167 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
174 The xNF provider **MUST** provide a Resource/Device YANG model
175 as a foundation for creating the YANG model for configuration. This will
176 include xNF attributes/parameters and valid values/attributes configurable
179 Configuration Management via Chef
180 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
188 The xNF provider **MUST** provide cookbooks to be loaded
189 on the appropriate Chef Server.
196 The xNF provider **MUST** provide a JSON file for each
197 supported action for the xNF. The JSON file must contain key value
198 pairs with all relevant values populated with sample data that illustrates
199 its usage. The fields and their description are defined in Tables A1
200 and A2 in the Appendix.
202 Note: Chef support in ONAP is not currently available and planned for 4Q 2017.
205 Configuration Management via Ansible
206 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
214 The xNF provider **MUST** provide playbooks to be loaded
215 on the appropriate Ansible Server.
222 The xNF provider **MUST** provide a JSON file for each
223 supported action for the xNF. The JSON file must contain key value
224 pairs with all relevant values populated with sample data that illustrates
225 its usage. The fields and their description are defined in Table B1
233 The xNF Package **MUST** include configuration scripts
234 for boot sequence and configuration.
241 The xNF provider **MUST** provide configurable parameters
242 (if unable to conform to YANG model) including xNF attributes/parameters
243 and valid values, dynamic attributes and cross parameter dependencies
244 (e.g., customer provisioning data).
246 Resource Control Loop
247 ^^^^^^^^^^^^^^^^^^^^^^^
255 The xNF provider **MUST** provide documentation for the xNF
256 Policy Description to manage the xNF runtime lifecycle. The document
257 must include a description of how the policies (conditions and actions)
258 are implemented in the xNF.
265 The xNF Package **MUST** include documentation describing the
266 fault, performance, capacity events/alarms and other event records
267 that are made available by the xNF.
274 The xNF Package **MUST** include documentation which must include
275 a unique identification string for the specific xNF, a description of
276 the problem that caused the error, and steps or procedures to perform
277 Root Cause Analysis and resolve the issue.
284 The xNF Package **MUST** include documentation which must include
285 all events, severity level (e.g., informational, warning, error) and
286 descriptions including causes/fixes if applicable for the event.
293 The xNF Package **MUST** include documentation which must include
294 all events (fault, measurement for xNF Scaling, Syslogs, State Change
295 and Mobile Flow), that need to be collected at each VM, VNFC (defined in `VNF Guidelines <https://onap.readthedocs.io/en/latest/submodules/vnfrqts/guidelines.git/docs/vnf_guidelines/vnf_guidelines.html>`__ ) and for the overall xNF.
303 The xNF Package **MUST** include documentation describing all
304 parameters that are available to monitor the xNF after instantiation
305 (includes all counters, OIDs, PM data, KPIs, etc.) that must be
306 collected for reporting purposes.
313 The xNF Package **MUST** include documentation about monitoring
314 parameters/counters exposed for virtual resource management and xNF
315 application management.
322 The xNF Package **MUST** include documentation about KPIs and
323 metrics that need to be collected at each VM for capacity planning
324 and performance management purposes.
331 The xNF Package **MUST** include documentation about the monitoring
332 parameters that must include latencies, success rates, retry rates, load
333 and quality (e.g., DPM) for the key transactions/functions supported by
334 the xNF and those that must be exercised by the xNF in order to perform
342 The xNF Package **MUST** include documentation for each KPI, provide
343 lower and upper limits.
350 The xNF Package **MUST** include documentation to, when relevant,
351 provide a threshold crossing alert point for each KPI and describe the
352 significance of the threshold crossing.
359 The xNF Package **MUST** include documentation for each KPI,
360 identify the suggested actions that need to be performed when a
361 threshold crossing alert event is recorded.
368 The xNF Package **MUST** include documentation that describes
369 any requirements for the monitoring component of tools for Network
370 Cloud automation and management to provide these records to components
378 The xNF Package **MUST** include documentation to when applicable,
379 provide calculators needed to convert raw data into appropriate reporting
387 The xNF Package **MUST** include documentation describing
388 supported xNF scaling capabilities and capacity limits (e.g., number
389 of users, bandwidth, throughput, concurrent calls).
396 The xNF Package **MUST** include documentation describing
397 the characteristics for the xNF reliability and high availability.
404 The xNF provider **MUST** provide an artifact per xNF that contains
405 all of the xNF Event Records supported. The artifact should include
406 reference to the specific release of the xNF Event Stream Common Event
407 Data Model document it is based on. (e.g.,
408 `VES Event Listener <https://onap.readthedocs.io/en/latest/submodules/vnfsdk/model.git/docs/files/VESEventListener.html>`__)
410 Compute, Network, and Storage Requirements
411 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
419 The xNF Package **MUST** include xNF topology that describes
420 basic network and application connectivity internal and external to the
421 xNF including Link type, KPIs, Bandwidth, latency, jitter, QoS (if
422 applicable) for each interface.
429 The VNF Package **MUST** include VM requirements via a Heat
430 template that provides the necessary data for VM specifications
431 for all VNF components - for hypervisor, CPU, memory, storage.
438 The VNF Package **MUST** include VM requirements via a Heat
439 template that provides the necessary data for network connections,
440 interface connections, internal and external to VNF.
447 The VNF Package **MUST** include VM requirements via a Heat
448 template that provides the necessary data for high availability
456 The VNF Package **MUST** include VM requirements via a Heat
457 template that provides the necessary data for scaling/growth VM
460 Note: Must comply with the *Heat requirements in 5.b*.
467 The VNF provider **MUST** provide the binaries and images
468 needed to instantiate the VNF (VNF and VNFC images).
475 The xNF provider **MUST** describe scaling capabilities
476 to manage scaling characteristics of the xNF.
488 The xNF Package **MUST** include documentation describing
489 the tests that were conducted by the xNF provider and the test results.
496 The xNF provider **MUST** provide their testing scripts to
504 The xNF provider **MUST** provide software components that
505 can be packaged with/near the xNF, if needed, to simulate any functions
506 or systems that connect to the xNF system under test. This component is
507 necessary only if the existing testing environment does not have the
508 necessary simulators.
510 Licensing Requirements
511 ^^^^^^^^^^^^^^^^^^^^^^^
519 The xNF **MUST** provide metrics (e.g., number of sessions,
520 number of subscribers, number of seats, etc.) to ONAP for tracking
528 The xNF provider **MUST** agree to the process that can
529 be met by Service Provider reporting infrastructure. The Contract
530 shall define the reporting process and the available reporting tools.
537 The xNF provider **MUST** enumerate all of the open
538 source licenses their xNF(s) incorporate.
545 The xNF provider **MUST NOT** require audits
546 of Service Provider's business.
553 The xNF provider **MUST NOT** require additional
554 infrastructure such as a xNF provider license server for xNF provider
555 functions and metrics.
562 The VNF **MUST** provide clear measurements for licensing
563 purposes to allow automated scale up/down by the management system.
570 The VNF provider **MUST** provide the ability to scale
571 up a VNF provider supplied product during growth and scale down a
572 VNF provider supplied product during decline without "real-time"
573 restrictions based upon VNF provider permissions.
580 The xNF provider **MUST** provide a universal license key
581 per xNF to be used as needed by services (i.e., not tied to a VM
582 instance) as the recommended solution. The xNF provider may provide
583 pools of Unique xNF License Keys, where there is a unique key for
584 each xNF instance as an alternate solution. Licensing issues should
585 be resolved without interrupting in-service xNFs.
592 The xNF provider **MUST** support the metadata about
593 licenses (and their applicable entitlements) as defined in this
594 document for xNF software, and any license keys required to authorize
595 use of the xNF software. This metadata will be used to facilitate
596 onboarding the xNF into the ONAP environment and automating processes
597 for putting the licenses into use and managing the full lifecycle of
598 the licenses. The details of this license model are described in
599 Tables C1 to C8 in the Appendix.
601 Note: License metadata support in ONAP is not currently available
602 and planned for 1Q 2018.