3 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
4 .. http://creativecommons.org/licenses/by/4.0
5 .. Copyright 2017 AT&T Intellectual Property. All rights reserved.
8 **7. ONAP Management Requirements**
9 =====================================
11 The ONAP platform is the part of the larger Network Function Virtualization/Software Defined Network (NFV/SDN) ecosystem that is responsible for the efficient control, operation and management of Virtual Network Function (VNF) capabilities and functions. It specifies standardized abstractions and interfaces that enable efficient interoperation of the NVF/SDN ecosystem components. It enables product/service independent capabilities for design, creation and runtime lifecycle management (includes all aspects of installation, change management, assurance, and retirement) of resources in NFV/SDN environment (see ECOMP white paper ). These capabilities are provided using two major architectural frameworks: (1) a Design Time Framework to design, define and program the platform (uniform onboarding), and (2) a Runtime Execution Framework to execute the logic programmed in the design environment (uniform delivery and runtime lifecycle management). The platform delivers an integrated information model based on the VNF package to express the characteristics and behavior of these resources in the Design Time Framework. The information model is utilized by Runtime Execution Framework to manage the runtime lifecycle of the VNFs. The management processes are orchestrated across various modules of ONAP to instantiate, configure, scale, monitor, and reconfigure the VNFs using a set of standard APIs provided by the VNF developers.
13 Although the guidelines and requirements specified in this document were originally driven by the need to standardize and automate the management of the virtualized environments (with VNFs) operated by Service Providers, we believe that most of the requirements are equally applicable to the operation of the physical network functions (PNFs), those network functions provided by traditional physical network elements (e.g. whitebox switches) or customized peripherals (e.g. a video rendering engine for augmented reality). The primary area of difference will be in how the network function is orchestrated into place – VNFs can be much more dynamically created & placed by ONAP to support varying geographic, availability and scalability needs, whereas the PNFs have to be deployed a priori in specific locations based on planning and engineering – their availability and scalability will be determined by the capabilities offered by the PNFs.
15 **PNF** is a vendor-provided Network Function(s) implemented using a bundled set of hardware and software while VNFs utilize cloud resources to provide Network Functions through virtualized software modules. PNF can be supplied by a vendor as a Black BOX (provides no knowledge of its internal characteristics, logic, and software design/architecture) or as a White Box (provides detailed knowledge and access of its internal components and logic) or as a Grey Box (provides limited knowledge and access to its internal components).
17 * Requirements that equally apply to both VNFs and PNFs are defined as "The xNF MUST/SHOULD/..."
18 * Requirements that only apply to VNFs are defined as "The VNF MUST/SHOULD/..."
19 * Requirements that only apply to PNFs are defined as "The PNF MUST/SHOULD/..."
25 This section, Service Design, has been left intentionally blank. It is out-of-scope for the VNF Requirements project for the Amsterdam release and no numbered requirements are expected. Content may be added in future updates of this document.
27 b. VNF On-boarding and package management
28 ==========================================
32 The ONAP Design Time Framework provides the ability to design NFV
33 resources including VNFs, Services, and products. The VNF provider must
34 provide VNF packages that include a rich set of recipes, management and
35 functional interfaces, policies, configuration parameters, and
36 infrastructure requirements that can be utilized by the ONAP Design
37 module to onboard and catalog these resources. Initially this
38 information may be provided in documents, but in the near future a
39 method will be developed to automate as much of the transfer of data as
40 possible to satisfy its long term requirements.
42 The current VNF Package Requirement is based on a subset of the
43 Requirements contained in the ETSI Document: ETSI GS NFV-MAN 001 v1.1.1
44 and GS NFV IFA011 V0.3.0 (2015-10) - Network Functions Virtualization
45 (NFV), Management and Orchestration, VNF Packaging Specification.
47 **Resource Description**
49 * R-77707 The VNF provider **MUST** include a Manifest File that contains a list of all the components in the VNF package.
50 * R-66070 The xNF Package **MUST** include xNF Identification Data to uniquely identify the resource for a given xNF provider. The identification data must include: an identifier for the xNF, the name of the xNF as was given by the xNF provider, xNF description, xNF provider, and version.
51 * R-69565 The xNF Package **MUST** include documentation describing xNF Management APIs. The document must include information and tools for:
53 - ONAP to deploy and configure (initially and ongoing) the xNF application(s) (e.g., NETCONF APIs). Includes description of configurable parameters for the xNF and whether the parameters can be configured after xNF instantiation.
54 - ONAP to monitor the health of the xNF (conditions that require healing and/or scaling responses). Includes a description of:
56 - Parameters that can be monitored for the xNF and event records (status, fault, flow, session, call, control plane, etc.) generated by the xNF after instantiation.
57 - Runtime lifecycle events and related actions (e.g., control responses, tests) which can be performed for the xNF.
59 * R-84366 The xNF Package **MUST** include documentation describing xNF Functional APIs that are utilized to build network and application services. This document describes the externally exposed functional inputs and outputs for the xNF, including interface format and protocols supported.
60 * R-36280 The xNF provider **MUST** provide documentation describing xNF Functional Capabilities that are utilized to operationalize the xNF and compose complex services.
61 * R-98617 The xNF provider **MUST** provide information regarding any dependency (e.g., affinity, anti-affinity) with other xNFs and resources.
63 **Resource Configuration**
65 * R-89571 The xNF **MUST** support and provide artifacts for configuration management using at least one of the following technologies:
71 Note: The requirements for Netconf/YANG, Chef, and Ansible protocols are provided separately and must be supported only if the corresponding protocol option is provided by the xNF providor.
73 **Configuration Management via Netconf/YANG**
75 * R-30278 The xNF provider **MUST** provide a Resource/Device YANG model as a foundation for creating the YANG model for configuration. This will include xNF attributes/parameters and valid values/attributes configurable by policy.
77 **Configuration Management via Chef**
79 * R-13390 The xNF provider **MUST** provide cookbooks to be loaded on the appropriate Chef Server.
80 * R-18525 The xNF provider **MUST** provide a JSON file for each supported action for the xNF. The JSON file must contain key value pairs with all relevant values populated with sample data that illustrates its usage. The fields and their description are defined in Appendix A.
82 Note: Chef support in ONAP is not currently available and planned for 4Q 2017.
84 **Configuration Management via Ansible**
86 * R-75608 The xNF provider **MUST** provide playbooks to be loaded on the appropriate Ansible Server.
87 * R-16777 The xNF provider **MUST** provide a JSON file for each supported action for the xNF. The JSON file must contain key value pairs with all relevant values populated with sample data that illustrates its usage. The fields and their description are defined in Appendix B.
89 * R-46567 The xNF Package **MUST** include configuration scripts for boot sequence and configuration.
90 * R-16065 The xNF provider **MUST** provide configurable parameters (if unable to conform to YANG model) including xNF attributes/parameters and valid values, dynamic attributes and cross parameter dependencies (e.g., customer provisioning data).
92 **Resource Control Loop**
94 * R-22888 The xNF provider **MUST** provide documentation for the xNF Policy Description to manage the xNF runtime lifecycle. The document must include a description of how the policies (conditions and actions) are implemented in the xNF.
95 * R-01556 The xNF Package **MUST** include documentation describing the fault, performance, capacity events/alarms and other event records that are made available by the xNF. The document must include:
97 - A unique identification string for the specific xNF, a description of the problem that caused the error, and steps or procedures to perform Root Cause Analysis and resolve the issue.
98 - All events, severity level (e.g., informational, warning, error) and descriptions including causes/fixes if applicable for the event.
99 - All events (fault, measurement for xNF Scaling, Syslogs, State Change and Mobile Flow), that need to be collected at each VM, VNFC (defined in `VNF Guidelines <http://onap.readthedocs.io/en/latest/submodules/vnfrqts/guidelines.git/docs/vnf_guidelines/vnf_guidelines.html#a-glossary>`__ ) and for the overall xNF.
101 * R-27711 The xNF provider **MUST** provide an XML file that contains a list of xNF error codes, descriptions of the error, and possible causes/corrective action.
102 * R-01478 The xNF Package **MUST** include documentation describing all parameters that are available to monitor the xNF after instantiation (includes all counters, OIDs, PM data, KPIs, etc.) that must be collected for reporting purposes. The documentation must include a list of:
104 - Monitoring parameters/counters exposed for virtual resource management and xNF application management.
105 - KPIs and metrics that need to be collected at each VM for capacity planning and performance management purposes.
106 - The monitoring parameters must include latencies, success rates, retry rates, load and quality (e.g., DPM) for the key transactions/functions supported by the xNF and those that must be exercised by the xNF in order to perform its function.
107 - For each KPI, provide lower and upper limits.
108 - When relevant, provide a threshold crossing alert point for each KPI and describe the significance of the threshold crossing.
109 - For each KPI, identify the suggested actions that need to be performed when a threshold crossing alert event is recorded.
110 - Describe any requirements for the monitoring component of tools for Network Cloud automation and management to provide these records to components of the xNF.
111 - When applicable, provide calculators needed to convert raw data into appropriate reporting artifacts.
113 * R-56815 The xNF Package **MUST** include documentation describing supported xNF scaling capabilities and capacity limits (e.g., number of users, bandwidth, throughput, concurrent calls).
114 * R-48596 The xNF Package **MUST** include documentation describing the characteristics for the xNF reliability and high availability.
115 * R-74763 The xNF provider **MUST** provide an artifact per xNF that contains all of the xNF Event Records supported. The artifact should include reference to the specific release of the xNF Event Stream Common Event Data Model document it is based on. (e.g., `VES Event Listener <https://github.com/att/evel-test-collector/tree/master/docs/att_interface_definition>`__)
117 **Compute, Network, and Storage Requirements**
119 * R-35851 The xNF Package **MUST** include xNF topology that describes basic network and application connectivity internal and external to the xNF including Link type, KPIs, Bandwidth, latency, jitter, QoS (if applicable) for each interface.
120 * R-97102 The VNF Package **MUST** include VM requirements via a Heat template that provides the necessary data for:
122 - VM specifications for all VNF components - for hypervisor, CPU, memory, storage.
123 - Network connections, interface connections, internal and external to VNF.
124 - High availability redundancy model.
125 - Scaling/growth VM specifications.
127 Note: Must comply with the *Heat requirements in 5.b*.
129 * R-26881 The xNF provider **MUST** provide the binaries and images needed to instantiate the xNF (xNF and VNFC images).
130 * R-96634 The VNF provider **MUST** describe scaling capabilities to manage scaling characteristics of the VNF.
135 * R-43958 The xNF Package **MUST** include documentation describing the tests that were conducted by the xNF providor and the test results.
136 * R-04298 The xNF provider **MUST** provide their testing scripts to support testing.
137 * R-58775 The xNF provider **MUST** provide software components that can be packaged with/near the xNF, if needed, to simulate any functions or systems that connect to the xNF system under test. This component is necessary only if the existing testing environment does not have the necessary simulators.
139 **Licensing Requirements**
141 * R-85653 The xNF **MUST** provide metrics (e.g., number of sessions, number of subscribers, number of seats, etc.) to ONAP for tracking every license.
142 * R-44125 The xNF provider **MUST** agree to the process that can be met by Service Provider reporting infrastructure. The Contract shall define the reporting process and the available reporting tools.
143 * R-40827 The xNF provider **MUST** enumerate all of the open source licenses their xNF(s) incorporate.
144 * R-97293 The xNF provider **MUST NOT** require audits of Service Provider’s business.
145 * R-44569 The xNF provider **MUST NOT** require additional infrastructure such as a xNF provider license server for xNF provider functions and metrics.
146 * R-13613 The VNF **MUST** provide clear measurements for licensing purposes to allow automated scale up/down by the management system.
147 * R-27511 The VNF provider **MUST** provide the ability to scale up a VNF provider supplied product during growth and scale down a VNF provider supplied product during decline without “real-time” restrictions based upon VNF provider permissions.
148 * R-85991 The xNF provider **MUST** provide a universal license key per xNF to be used as needed by services (i.e., not tied to a VM instance) as the recommended solution. The xNF provider may provide pools of Unique xNF License Keys, where there is a unique key for each xNF instance as an alternate solution. Licensing issues should be resolved without interrupting in-service xNFs.
149 * R-47849 The xNF provider **MUST** support the metadata about licenses (and their applicable entitlements) as defined in this document for xNF software, and any license keys required to authorize use of the xNF software. This metadata will be used to facilitate onboarding the xNF into the ONAP environment and automating processes for putting the licenses into use and managing the full lifecycle of the licenses. The details of this license model are described in Appendix C. Note: License metadata support in ONAP is not currently available and planned for 1Q 2018.
151 c. Configuration Management
152 ===========================
154 ONAP interacts directly with VNFs through its Network and Application
155 Adapters to perform configuration activities within NFV environment.
156 These activities include service and resource
157 configuration/reconfiguration, automated scaling of resources, service
158 and resource removal to support runtime lifecycle management of VNFs and
159 services. The Adapters employ a model driven approach along with
160 standardized APIs provided by the VNF developers to configure resources
161 and manage their runtime lifecycle.
163 Additional details can be found in the `ONAP Application Controller (APPC) API Guide <http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20API%20Guide/APPC%20API%20Guide.html>`_, `ONAP VF-C project <http://onap.readthedocs.io/en/latest/submodules/vfc/nfvo/lcm.git/docs/index.html>`_ and the `ONAP SDNC project <http://onap.readthedocs.io/en/latest/submodules/sdnc/northbound.git/docs/index.html>`_.
165 NETCONF Standards and Capabilities
166 ----------------------------------
168 ONAP Controllers and their Adapters utilize device YANG model and
169 NETCONF APIs to make the required changes in the VNF state and
170 configuration. The VNF providers must provide the Device YANG model and
171 NETCONF server supporting NETCONF APIs to comply with target ONAP and
174 **VNF Configuration via NETCONF Requirements**
176 **Configuration Management**
178 * R-88026 The xNF **MUST** include a NETCONF server enabling runtime configuration and lifecycle management capabilities.
179 * R-95950 The xNF **MUST** provide a NETCONF interface fully defined by supplied YANG models for the embedded NETCONF server.
181 **NETCONF Server Requirements**
183 * R-73468 The xNF **MUST** allow the NETCONF server connection parameters to be configurable during virtual machine instantiation through Heat templates where SSH keys, usernames, passwords, SSH service and SSH port numbers are Heat template parameters.
184 * R-90007 The xNF **MUST** implement the protocol operation: **close-session()**- Gracefully close the current session.
185 * R-70496 The xNF **MUST** implement the protocol operation: **commit(confirmed, confirm-timeout)** - Commit candidate configuration datastore to the running configuration.
186 * R-18733 The xNF **MUST** implement the protocol operation: **discard-changes()** - Revert the candidate configuration datastore to the running configuration.
187 * R-44281 The xNF **MUST** implement the protocol operation: **edit-config(target, default-operation, test-option, error-option, config)** - Edit the target configuration datastore by merging, replacing, creating, or deleting new config elements.
188 * R-60106 The xNF **MUST** implement the protocol operation: **get(filter)** - Retrieve (a filtered subset of) the running configuration and device state information. This should include the list of xNF supported schemas.
189 * R-29488 The xNF **MUST** implement the protocol operation: **get-config(source, filter)** - Retrieve a (filtered subset of a) configuration from the configuration datastore source.
190 * R-11235 The xNF **MUST** implement the protocol operation: **kill-session(session)** - Force the termination of **session**.
191 * R-02597 The xNF **MUST** implement the protocol operation: **lock(target)** - Lock the configuration datastore target.
192 * R-96554 The xNF **MUST** implement the protocol operation: **unlock(target)** - Unlock the configuration datastore target.
193 * R-29324 The xNF **SHOULD** implement the protocol operation: **copy-config(target, source) -** Copy the content of the configuration datastore source to the configuration datastore target.
194 * R-88031 The xNF **SHOULD** implement the protocol operation: **delete-config(target) -** Delete the named configuration datastore target.
195 * R-97529 The xNF **SHOULD** implement the protocol operation: **get-schema(identifier, version, format) -** Retrieve the YANG schema.
196 * R-62468 The xNF **MUST** allow all configuration data to be edited through a NETCONF <edit-config> operation. Proprietary NETCONF RPCs that make configuration changes are not sufficient.
197 * R-01382 The xNF **MUST** allow the entire configuration of the xNF to be retrieved via NETCONF's <get-config> and <edit-config>, independently of whether it was configured via NETCONF or other mechanisms.
198 * R-28756 The xNF **MUST** support **:partial-lock** and **:partial-unlock** capabilities, defined in RFC 5717. This allows multiple independent clients to each write to a different part of the <running> configuration at the same time.
199 * R-83873 The xNF **MUST** support **:rollback-on-error** value for the <error-option> parameter to the <edit-config> operation. If any error occurs during the requested edit operation, then the target database (usually the running configuration) will be left unaffected. This provides an 'all-or-nothing' edit mode for a single <edit-config> request.
200 * R-68990 The xNF **MUST** support the **:startup** capability. It will allow the running configuration to be copied to this special database. It can also be locked and unlocked.
201 * R-68200 The xNF **MUST** support the **:url** value to specify protocol operation source and target parameters. The capability URI for this feature will indicate which schemes (e.g., file, https, sftp) that the server supports within a particular URL value. The 'file' scheme allows for editable local configuration databases. The other schemes allow for remote storage of configuration databases.
202 * R-20353 The xNF **MUST** implement at least one of the capabilities **:candidate** or **:writable-running**. If both **:candidate** and **:writable-running** are provided then two locks should be supported.
203 * R-11499 The xNF **MUST** fully support the XPath 1.0 specification for filtered retrieval of configuration and other database contents. The 'type' attribute within the <filter> parameter for <get> and <get-config> operations may be set to 'xpath'. The 'select' attribute (which contains the XPath expression) will also be supported by the server. A server may support partial XPath retrieval filtering, but it cannot advertise the **:xpath** capability unless the entire XPath 1.0 specification is supported.
204 * R-83790 The xNF **MUST** implement the **:validate** capability
205 * R-49145 The xNF **MUST** implement **:confirmed-commit** If **:candidate** is supported.
206 * R-58358 The xNF **MUST** implement the **:with-defaults** capability [RFC6243].
207 * R-59610 The xNF **MUST** implement the data model discovery and download as defined in [RFC6022].
208 * R-87662 The xNF **SHOULD** implement the NETCONF Event Notifications [RFC5277].
209 * R-93443 The xNF **MUST** define all data models in YANG [RFC6020], and the mapping to NETCONF shall follow the rules defined in this RFC.
210 * R-26115 The xNF **MUST** follow the data model upgrade rules defined in [RFC6020] section 10. All deviations from section 10 rules shall be handled by a built-in automatic upgrade mechanism.
211 * R-10716 The xNF **MUST** support parallel and simultaneous configuration of separate objects within itself.
212 * R-29495 The xNF **MUST** support locking if a common object is being manipulated by two simultaneous NETCONF configuration operations on the same xNF within the context of the same writable running data store (e.g., if an interface parameter is being configured then it should be locked out for configuration by a simultaneous configuration operation on that same interface parameter).
213 * R-53015 The xNF **MUST** apply locking based on the sequence of NETCONF operations, with the first configuration operation locking out all others until completed.
214 * R-02616 The xNF **MUST** permit locking at the finest granularity if a xNF needs to lock an object for configuration to avoid blocking simultaneous configuration operations on unrelated objects (e.g., BGP configuration should not be locked out if an interface is being configured or entire Interface configuration should not be locked out if a non-overlapping parameter on the interface is being configured).
215 * R-41829 The xNF **MUST** be able to specify the granularity of the lock via a restricted or full XPath expression.
216 * R-66793 The xNF **MUST** guarantee the xNF configuration integrity for all simultaneous configuration operations (e.g., if a change is attempted to the BUM filter rate from multiple interfaces on the same EVC, then they need to be sequenced in the xNF without locking either configuration method out).
217 * R-54190 The xNF **MUST** release locks to prevent permanent lock-outs when/if a session applying the lock is terminated (e.g., SSH session is terminated).
218 * R-03465 The xNF **MUST** release locks to prevent permanent lock-outs when the corresponding <partial-unlock> operation succeeds.
219 * R-63935 The xNF **MUST** release locks to prevent permanent lock-outs when a user configured timer has expired forcing the NETCONF SSH Session termination (i.e., product must expose a configuration knob for a user setting of a lock expiration timer)
220 * R-10173 The xNF **MUST** allow another NETCONF session to be able to initiate the release of the lock by killing the session owning the lock, using the <kill-session> operation to guard against hung NETCONF sessions.
221 * R-88899 The xNF **MUST** support simultaneous <commit> operations within the context of this locking requirements framework.
222 * R-07545 The xNF **MUST** support all operations, administration and management (OAM) functions available from the supplier for xNFs using the supplied YANG code and associated NETCONF servers.
223 * R-60656 The xNF **MUST** support sub tree filtering.
224 * R-80898 The xNF **MUST** support heartbeat via a <get> with null filter.
225 * R-06617 The xNF **MUST** support get-schema (ietf-netconf-monitoring) to pull YANG model over session.
226 * R-25238 The xNF PACKAGE **MUST** validated YANG code using the open source pyang [1]_ program using the following commands:
228 .. code-block:: python
230 $ pyang --verbose --strict <YANG-file-name(s)>
233 * R-63953 The xNF **MUST** have the echo command return a zero value otherwise the validation has failed
234 * R-26508 The xNF **MUST** support NETCONF server that can be mounted on OpenDaylight (client) and perform the following operations:
236 - Modify, update, change, rollback configurations using each configuration data element.
237 - Query each state (non-configuration) data element.
238 - Execute each YANG RPC.
239 - Receive data through each notification statement.
243 The following requirements provides the Yang models that suppliers must
244 conform, and those where applicable, that suppliers need to use.
246 * R-28545 The xNF **MUST** conform its YANG model to RFC 6060, “YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)”
247 * R-29967 The xNF **MUST** conform its YANG model to RFC 6022, “YANG module for NETCONF monitoring”.
248 * R-22700 The xNF **MUST** conform its YANG model to RFC 6470, “NETCONF Base Notifications”.
249 * R-10353 The xNF **MUST** conform its YANG model to RFC 6244, “An Architecture for Network Management Using NETCONF and YANG”.
250 * R-53317 The xNF **MUST** conform its YANG model to RFC 6087, “Guidelines for Authors and Reviewers of YANG Data Model Documents”.
251 * R-33955 The xNF **SHOULD** conform its YANG model to RFC 6991, “Common YANG Data Types”.
252 * R-22946 The xNF **SHOULD** conform its YANG model to RFC 6536, “NETCONF Access Control Model”.
253 * R-10129 The xNF **SHOULD** conform its YANG model to RFC 7223, “A YANG Data Model for Interface Management”.
254 * R-12271 The xNF **SHOULD** conform its YANG model to RFC 7223, “IANA Interface Type YANG Module”.
255 * R-49036 The xNF **SHOULD** conform its YANG model to RFC 7277, “A YANG Data Model for IP Management”.
256 * R-87564 The xNF **SHOULD** conform its YANG model to RFC 7317, “A YANG Data Model for System Management”.
257 * R-24269 The xNF **SHOULD** conform its YANG model to RFC 7407, “A YANG Data Model for SNMP Configuration”.
259 The NETCONF server interface shall fully conform to the following
262 * R-33946 The xNF **MUST** conform to the NETCONF RFC 4741, “NETCONF Configuration Protocol”.
263 * R-04158 The xNF **MUST** conform to the NETCONF RFC 4742, “Using the NETCONF Configuration Protocol over Secure Shell (SSH)”.
264 * R-13800 The xNF **MUST** conform to the NETCONF RFC 5277, “NETCONF Event Notification”.
265 * R-01334 The xNF **MUST** conform to the NETCONF RFC 5717, “Partial Lock Remote Procedure Call”.
266 * R-08134 The xNF **MUST** conform to the NETCONF RFC 6241, “NETCONF Configuration Protocol”.
267 * R-78282 The xNF **MUST** conform to the NETCONF RFC 6242, “Using the Network Configuration Protocol over Secure Shell”.
272 Healthcheck is a command for which no NETCONF support exists. Therefore, this must be supported using a RESTful interface (defined in this section) or
273 with a Chef cookbook/Ansible playbook (defined in sections `Chef Standards and Capabilities`_ and `Ansible Standards and Capabilities`_).
275 HealthCheck Definition: The VNF level HealthCheck is a check over the entire scope of the VNF.
276 The VNF must be 100% healthy, ready to take requests and provide services, with all VNF required
277 capabilities ready to provide services and with all active and standby resources fully ready with
278 no open MINOR, MAJOR or CRITICAL alarms. NOTE: A switch may need to be turned on, but the VNF
279 should be ready to take service requests or be already processing service requests successfully.
281 The VNF must provide a REST formatted GET RPCs to support Healthcheck queries via the GET method
284 The port number, url, and other authentication information is provided
289 * R-31809 The xNF **MUST** support the HealthCheck RPC. The HealthCheck RPC executes a xNF Provider-defined xNF Healthcheck over the scope of the entire xNF (e.g., if there are multiple VNFCs, then run a health check, as appropriate, for all VNFCs). It returns a 200 OK if the test completes. A JSON object is returned indicating state (healthy, unhealthy), scope identifier, time-stamp and one or more blocks containing info and fault information. If the xNF is unable to run the HealthCheck, return a standard http error code and message.
297 "identifier": "scope represented",
299 "time": "01-01-1000:0000"
304 "identifier": "scope represented",
305 "state": "unhealthy",
307 "info": "System threshold exceeded details",
314 "time": "01-01-1000:0000"
318 Chef Standards and Capabilities
319 -------------------------------
321 ONAP will support configuration of VNFs via Chef subject to the
322 requirements and guidelines defined in this section.
324 The Chef configuration management mechanism follows a client-server
325 model. It requires the presence of a Chef-Client on the VNF that will be
326 directly managed by a Chef Server. The Chef-client will register with
327 the appropriate Chef Server and are managed via ‘cookbooks’ and
328 configuration attributes loaded on the Chef Server which contain all
329 necessary information to execute the appropriate actions on the VNF via
332 ONAP will utilize the open source Chef Server, invoke the documented
333 Chef REST APIs to manage the VNF and requires the use of open source
334 Chef-Client and Push Jobs Client on the VNF
335 (https://downloads.chef.io/).
337 **VNF Configuration via Chef Requirements**
339 **Chef Client Requirements**
341 * R-79224 The xNF **MUST** have the chef-client be preloaded with validator keys and configuration to register with the designated Chef Server as part of the installation process.
342 * R-72184 The xNF **MUST** have routable FQDNs for all the endpoints (VMs) of a xNF that contain chef-clients which are used to register with the Chef Server. As part of invoking xNF actions, ONAP will trigger push jobs against FQDNs of endpoints for a xNF, if required.
343 * R-47068 The xNF **MAY** expose a single endpoint that is responsible for all functionality.
344 * R-67114 The xNF **MUST** be installed with:
346 - Chef-Client >= 12.0
347 - Chef push jobs client >= 2.0
349 **Chef Roles/Requirements**
351 * R-27310 The xNF Package **MUST** include all relevant Chef artifacts (roles/cookbooks/recipes) required to execute xNF actions requested by ONAP for loading on appropriate Chef Server.
352 * R-26567 The xNF Package **MUST** include a run list of roles/cookbooks/recipes, for each supported xNF action, that will perform the desired xNF action in its entirety as specified by ONAP (see Section 7.c, ONAP Controller APIs and Behavior, for list of xNF actions and requirements), when triggered by a chef-client run list in JSON file.
353 * R-98911 The xNF **MUST NOT** use any instance specific parameters for the xNF in roles/cookbooks/recipes invoked for a xNF action.
354 * R-37929 The xNF **MUST** accept all necessary instance specific data from the environment or node object attributes for the xNF in roles/cookbooks/recipes invoked for a xNF action.
355 * R-62170 The xNF **MUST** over-ride any default values for configurable parameters that can be set by ONAP in the roles, cookbooks and recipes.
356 * R-78116 The xNF **MUST** update status on the Chef Server appropriately (e.g., via a fail or raise an exception) if the chef-client run encounters any critical errors/failures when executing a xNF action.
357 * R-44013 The xNF **MUST** populate an attribute, defined as node[‘PushJobOutput’] with the desired output on all nodes in the push job that execute chef-client run if the xNF action requires the output of a chef-client run be made available (e.g., get running configuration).
358 * R-30654 The xNF Package **MUST** have appropriate cookbooks that are designed to automatically ‘rollback’ to the original state in case of any errors for actions that change state of the xNF (e.g., configure).
359 * R-65755 The xNF **SHOULD** support callback URLs to return information to ONAP upon completion of the chef-client run for any chef-client run associated with a xNF action.
361 - As part of the push job, ONAP will provide two parameters in the environment of the push job JSON object:
362 - ‘RequestId’ a unique Id to be used to identify the request,
363 - ‘CallbackUrl’, the URL to post response back.
365 - If the CallbackUrl field is empty or missing in the push job, then the chef-client run need not post the results back via callback.
367 * R-15885 The xNF **MUST** Upon completion of the chef-client run, POST back on the callback URL, a JSON object as described in Table A2 if the chef-client run list includes a cookbook/recipe that is callback capable. Failure to POST on the Callback Url should not be considered a critical error. That is, if the chef-client successfully completes the xNF action, it should reflect this status on the Chef Server regardless of whether the Callback succeeded or not.
372 This section outlines the workflow that ONAP invokes when it receives an
373 action request against a Chef managed VNF.
375 1. When ONAP receives a request for an action for a Chef Managed VNF, it
376 retrieves the corresponding template (based on **action** and
377 **VNF)** from its database and sets necessary values in the
378 “Environment”, “Node” and “NodeList” keys (if present) from either
379 the payload of the received action or internal data.
381 2. If “Environment” key is present in the updated template, it posts the
382 corresponding JSON dictionary to the appropriate Environment object
383 REST endpoint on the Chef Server thus updating the Environment
384 attributes on the Chef Server.
386 3. Next, it creates a Node Object from the “Node” JSON dictionary for
387 all elements listed in the NodeList (using the FQDN to construct the
388 endpoint) by replicating it [2]_. As part of this process, it will
389 set the name field in each Node Object to the corresponding FQDN.
390 These node objects are then posted on the Chef Server to
391 corresponding Node Object REST endpoints to update the corresponding
394 4. If PushJobFlag is set to “True” in the template, ONAP requests a push
395 job against all the nodes in the NodeList to trigger
396 chef-client\ **.** It will not invoke any other command via the push
397 job. ONAP will include a callback URL in the push job request and a
398 unique Request Id. An example push job posted by ONAP is listed
404 "command": "chef-client",
406 "nodes”: [“node1.vnf\_a.onap.com”, “node2.vnf\_a.onap.com”],
408 “RequestId”:”8279-abcd-aksdj-19231”,
409 “CallbackUrl”:”<callback>”
413 5. If CallbackCapable field in the template is not present or set to
414 “False” ONAP will poll the Chef Server to check completion status of
417 6. If “GetOutputFlag” is set to “True” in the template and
418 CallbackCapable is not set to “True”, ONAP will retrieve any output
419 from each node where the push job has finished by accessing the Node
420 Object attribute node[‘PushJobOutput’].
422 Ansible Standards and Capabilities
423 ----------------------------------
425 ONAP will support configuration of VNFs via Ansible subject to the
426 requirements and guidelines defined in this section.
428 Ansible allows agentless management of VNFs/VMs/VNFCs via execution of ‘playbooks’
429 over ssh. The ‘playbooks’ are a structured set of tasks which contain all the necessary
430 data and execution capabilities to take the necessary action on one or more target VMs
431 (and/or VNFCs) of the VNF. ONAP will utilize the framework of an Ansible Server that
432 will host and run playbooks to manage VNFs that support Ansible.
434 **VNF Configuration via Ansible Requirements**
436 **Ansible Client Requirements**
438 * R-32217 The xNF **MUST** have routable FQDNs that are reachable via the Ansible Server for the endpoints (VMs) of a xNF on which playbooks will be executed. ONAP will initiate requests to the Ansible Server for invocation of playbooks against these end points [3]_.
439 * R-54373 The xNF **MUST** have Python >= 2.7 on the endpoint VM(s) of a xNF on which an Ansible playbook will be executed.
440 * R-35401 The xNF **MUST** support SSH and allow SSH access to the Ansible server for the endpoint VM(s) and comply with the Network Cloud Service Provider guidelines for authentication and access.
441 * R-82018 The VNF **SHOULD** load the SSH key onto VNF VM(s) as part of instantiation. This will allow the Ansible Server to authenticate to perform post-instantiation configuration without manual intervention and without requiring specific VNF login IDs and passwords.
443 CAUTION: For VNFs configured using Ansible, to eliminate the need for manual steps, post-instantiation and pre-configuration, to upload of SSH keys, SSH keys loaded during (heat) instantiation shall be preserved and not removed by (heat) embedded scripts.
445 * R-92866 The VNF **MUST** include as part of post-instantiation configuration done by Ansible Playbooks the removal/update of SSH keys loaded through instantiation to support Ansible. This may include download and install of new SSH keys.
446 * R-91745 The VNF **MUST** update the Ansible Server and other entities storing and using the SSH key for authentication when the SSH key used by Ansible is regenerated/updated.
448 **Ansible Playbook Requirements**
450 An Ansible playbook is a collection of tasks that is executed on the Ansible server (local host) and/or the target VM (s) in order to complete the desired action.
452 * R-40293 The xNF **MUST** make available playbooks that conform to the ONAP requirement.
453 * R-49396 The xNF **MUST** support each xNF action by invocation of **one** playbook [4]_. The playbook will be responsible for executing all necessary tasks (as well as calling other playbooks) to complete the request.
454 * R-33280 The xNF **MUST NOT** use any instance specific parameters in a playbook.
455 * R-48698 The xNF **MUST** utilize information from key value pairs that will be provided by the Ansible Server as extra-vars during invocation to execute the desired xNF action. If the playbook requires files, they must also be supplied using the methodology detailed in the Ansible Server API.
457 The Ansible Server will determine if a playbook invoked to execute a xNF action finished successfully or not using the “PLAY_RECAP” summary in Ansible log. The playbook will be considered to successfully finish only if the “PLAY RECAP” section at the end of playbook execution output has no unreachable hosts and no failed tasks. Otherwise, the playbook will be considered to have failed.
459 * R-43253 The xNF **MUST** use playbooks designed to allow Ansible Server to infer failure or success based on the “PLAY_RECAP” capability.
460 * R-50252 The xNF **MUST** write to a specific set of text files that will be retrieved and made available by the Ansible Server if, as part of a xNF action (e.g., audit), a playbook is required to return any xNF information. The text files must be written in the same directory as the one from which the playbook is being executed. A text file must be created for each host the playbook run targets/affects, with the name ‘<hostname>_results.txt’ into which any desired output from each respective VM/xNF must be written.
461 * R-51442 The xNF **SHOULD** use playbooks that are designed to automatically ‘rollback’ to the original state in case of any errors for actions that change state of the xNF (e.g., configure).
463 NOTE: In case rollback at the playbook level is not supported or possible, the xNF provider shall provide alternative locking mechanism (e.g., for a small xNF the rollback mechanism may rely on workflow to terminate and re-instantiate VNF VMs and then re-run playbook(s)). Backing up updated files also recommended to support rollback when soft rollback is feasible.
465 * R-58301 The VNF **SHOULD NOT** use playbooks that make requests to Cloud resources e.g. Openstack (nova, neutron, glance, heat, etc.); therefore, there is no use for Cloud specific variables like Openstack UUIDs in Ansible Playbooks.
467 Rationale: Flows that require interactions with Cloud services e.g. Openstack shall rely on workflows run by an Orchestrator or other capability (such as a control loop or Operations GUI) outside Ansible Server which can be executed by a Controller such as APPC. There are policies, as part of Control Loop models, that send remediation action requests to APPC; these are triggered as a response to an event or correlated events published to Event Bus.
469 * R-02651 The VNF **SHOULD** use the Ansible backup feature to save a copy of configuration files before implementing changes to support operations such as backing out of software upgrades, configuration changes or other work as this will help backing out of configuration changes when needed.
470 * R-43353 The VNF **MUST** return control from Ansible Playbooks only after tasks are fully complete, signaling that the playbook completed all tasks. When starting services, return control only after all services are up. This is critical for workflows where the next steps are dependent on prior tasks being fully completed.
474 StopApplication Playbook – StopApplication Playbook shall return control and a completion status only after VNF application is fully stopped, all processes/services stopped.
475 StartApplication Playbook – StartApplication Playbook shall return control and a completion status only after all VNF application services are fully up, all processes/services started and ready to provide services. NOTE: Start Playbook should not be declared complete/done after starting one or several processes that start the other processes.
477 HealthCheck Playbook:
479 SUCCESS – HealthCheck success shall be returned (return code 0) by a Playbook or Cookbook only when VNF is 100% healthy, ready to take requests and provide services, with all VNF required capabilities ready to provide services and with all active and standby resources fully ready with no open MINOR, MAJOR or CRITICAL alarms.
481 NOTE: In some cases, a switch may need to be turned on, but a VNF reported as healthy, should be ready to take service requests or be already processing service requests successfully.
483 A successful execution of a health-check playbook shall also create one file per VNF VM, named using IP address or VM name followed by “_results.txt (<hostname>_results.txt) to indicate health-check was executed and completed successfully, example: 1xx.2yy.zzz.105_results.txt, with the following contents:
489 $ cat 1xx.2yy.zzz.105_results.txt
493 FAILURE – A health check playbook shall return a non-zero return code in case VNF is not 100% healthy because one or more VNF application processes are stopped or not ready to take service requests or because critical or non-critical resources are not ready or because there are open MINOR, MAJOR or CRITICAL traps/alarms or because there are issues with the VNF that need attention even if they do not impact services provided by the VNF.
495 A failed health-check playbook shall also create one file per VNF VM, named using Playbook Name plus IP address or VM name, followed by “_results.txt to indicate health-check was executed and found issues in the health of the VNF. This is to differentiate from failure to run health-check playbook or tasks to verify the health of the VNF, example: 1xx.2yy.zzz.105_results.txt, with the following contents:
501 $ cat 1xx.2yy.zzz.105_results.txt
505 See `VNF REST APIs`_ for additional details on HealthCheck.
507 ONAP Controller / Ansible API Usage
508 -----------------------------------
510 This section outlines the workflow that ONAP Controller invokes when it receives an action request against an Ansible managed VNF.
512 #. When ONAP Controller receives a request for an action for an AnsibleManaged VNF, it retrieves the corresponding template (based on **action** and **VNF**) from its database and sets necessary values (such as an Id, NodeList, and EnvParameters) from either information in the request or data obtained from other sources. This is referred to as the payload that is sent as a JSON object to the Ansible server.
513 #. The ONAP Controller sends a request to the Ansible server to execute the action.
514 #. The ONAP Controller polls the Ansible Server for result (success or failure). The ONAP Controllers has a timeout value which is contained in the template. If the result is not available when the timeout is reached, the ONAP Controller stops polling and returns a timeout error to the requester. The Ansible Server continues to process the request.
517 ONAP Controller APIs and Behavior
518 ---------------------------------
520 ONAP Controllers such as APPC expose a northbound API to clients which offer a set of commands. The following commands are expected to be supported
521 on all VNF’s if applicable, either directly (via the Netconf interface) or indirectly (via a Chef or Ansible server). There are additional commands
522 offered to northbound clients that are not listed here, as these commands either act internally on the Controller itself or depend upon network cloud
523 components for implementation (thus, these actions do not put any special requirement on the VNF provider).
525 The following table summarizes how the VNF must act in response to
528 Table 8. ONAP Controller APIs and NETCONF Commands
530 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
531 | **Action** | **Description** | **NETCONF Commands** |
532 +=====================+==================================================================================================================================================================================================================================================================================+===============================================================================================================================================================================================================================+
533 | Action | Queries ONAP Controller for the current state of a previously submitted runtime LCM (Lifecycle Management) action. | There is currently no way to check the request status in NETCONF so action status is managed internally by the ONAP controller. |
536 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
537 | Audit, Sync | Compare active (uploaded) configuration against the current configuration in the ONAP controller. Audit returns failure if different. Sync considers the active (uploaded) configuration as the current configuration. | The <get-config> operation is used to retrieve the running configuration from the VNF. |
538 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
539 | Lock, | Returns true when the given VNF has been locked. | There is currently no way to query lock state in NETCONF so VNF locking and unlocking is managed internally by the ONAP controller. |
544 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
545 | Configure, | Configure applies a post-instantiation configuration the target VNF or VNFC. ConfigModify updates only a subset of the total configuration parameters of a VNF. | The <edit-config> operation loads all or part of a specified configuration data set to the specified target database. If there is no <candidate/> database, then the target is the <running/> database. A <commit> follows. |
548 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
549 | Health | Executes a VNF health check and returns the result. A health check is VNF-specific. | This command has no existing NETCONF RPC action. It must be supported either by REST (see `VNF REST APIs`_) or using Ansible or Chef. |
552 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
553 | StartApplication, | ONAP requests application to be started or stopped on the VNF. These actions do not need to be supported if (1) the application starts automatically after Configure or if the VM’s are started and (2) the application gracefully shuts down if the VM’s are stopped. | These commands have no specific NETCONF RPC action. |
555 | StopApplication | | If applicable, these commands must be supported using Ansible or Chef (see Table 9 below). |
556 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
557 | ConfigBackup, | ONAP requests the VNF configuration parameters to be backed up or restored (replacing existing configuration parameters on the VNF). | These commands have no specific NETCONF RPC action. |
559 | ConfigRestore | | They can be supported using Ansible or Chef (see Table 9 below). |
560 +---------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
562 Table 9 lists the required Chef and Ansible support for commands from
565 Table 9. ONAP Controller APIs and Chef/Ansible Support
567 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
568 | **Action** | **Chef** | **Ansible** |
569 +=====================+==================================================================================================================================================================================================================================================================================================+=============================================================================================================================================================================================================================================================================================+
570 | Action | Not needed. ActionStatus is managed internally by the ONAP controller. | Not needed. ActionStatus is managed internally by the ONAP controller. |
573 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
574 | Audit, Sync | VNF provider must provide any necessary roles, cookbooks, recipes to retrieve the running configuration from a VNF and place it in the respective Node Objects ‘PushJobOutput’ attribute of all nodes in NodeList when triggered by a chef-client run. | VNF provider must provide an Ansible playbook to retrieve the running configuration from a VNF and place the output on the Ansible server in a manner aligned with playbook requirements listed in this document. |
576 | | The JSON file for this VNF action is required to set “PushJobFlag” to “True” and “GetOutputFlag” to “True”. The “Node” JSON dictionary must have the run list populated with the necessary sequence of roles, cookbooks, recipes. | The PlaybookName must be provided in the JSON file. |
578 | | The Environment and Node values should contain all appropriate configuration attributes. | NodeList must list FQDNs of an example VNF on which to execute playbook. |
580 | | NodeList must list sample FQDNs that are required to conduct a chef-client run for this VNF Action. | |
581 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
582 | Lock, | Not needed. VNF locking and unlocking is managed internally by the ONAP controller. | Not needed. VNF locking and unlocking is managed internally by the ONAP controller. |
587 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
588 | Configure, | VNF provider must provide any necessary roles, cookbooks, recipes to apply configuration attributes to the VNF when triggered by a chef-client run. All configurable attributes must be obtained from the Environment and Node objects on the Chef Server. | VNF provider must provide an Ansible playbook that can configure the VNF with parameters supplied by the Ansible Server. |
590 | ConfigModify | The JSON file for this VNF action should include all configurable attributes in the Environment and/or Node JSON dictionary. | The PlaybookName must be provided in the JSON file. |
592 | | The “PushJobFlag” must be set to “True”. | The “EnvParameters” and/or “FileParameters” field values should be provided and contain all configurable parameters for the VNF. |
594 | | The “Node” JSON dictionary must have the run list populated with necessary sequence of roles, cookbooks, recipes. This action is not expected to return an output. | NodeList must list FQDNs of an example VNF on which to execute playbook. |
596 | | “GetOutputFlag” must be set to “False”. | |
598 | | NodeList must list sample FQDNs that are required to conduct a chef-client run for this VNF Action. | |
599 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
600 | Health | The VNF level HealthCheck run a check over the entire scope of the VNF (for more details, see `VNF REST APIs`_). It can be supported either via a REST interface or with Chef roles, cookbooks, and recipes. | The VNF level HealthCheck run a check over the entire scope of the VNF (for more details, see `VNF REST APIs`_). It can be supported either via a REST interface or with an Ansible playbook. |
603 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
604 | StartApplication, | VNF provider must provide roles, cookbooks, recipes to start an application on the VNF when triggered by a chef-client run. If application does not start, the run must fail or raise an exception. If application is already started, or starts successfully, the run must finish successfully. | VNF provider must provide an Ansible playbook to start the application on the VNF. If application does not start, the playbook must indicate failure. If application is already started, or starts successfully, the playbook must finish successfully. |
606 | StopApplication | For StopApplication, the application must be stopped gracefully (no loss of traffic). | For StopApplication, the application must be stopped gracefully (no loss of traffic). |
607 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
608 | ConfigBackup, | VNF provider must provide roles, cookbooks, recipes to backup or restore the configuration parameters on the VNF when triggered by an ECOMP request. | VNF provider must provide an Ansible playbook to backup or restore the configuration parameters on the VNF when triggered by an ECOMP request. |
610 | | When the ConfigBackup command is executed, the current VNF configuration parameters are copied over to the Ansible or Chef server (if there is an existing set of backed up parameters, they are overwritten). When the ConfigRestore command is executed, the VNF configuration parameters | When the ConfigBackup command is executed, the current VNF configuration parameters are copied over to the Ansible or Chef server (if there is an existing set of backed up parameters, they are overwritten). When the ConfigRestore command is executed, the VNF configuration parameters |
611 | ConfigRestore | which are backed up on the Ansible or Chef server are applied to the VNF (replacing existing parameters). It can be assumed that the VNF is not in service when a ConfigRestore command is executed. | which are backed up on the Ansible or Chef server are applied to the VNF (replacing existing parameters). It can be assumed that the VNF is not in service when a ConfigRestore command is executed. |
613 | | If either command fails, the run must fail or raise an exception. | If either command fails, the run must fail or raise an exception. |
614 +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
616 For information purposes, the following ONAP controller functions are
617 planned in the future:
619 Table 10. Planned ONAP Controller Functions
621 +------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
622 | Action | Description |
623 +==================+=================================================================================================================================================================================+
624 | UpgradeSoftware | Upgrades the target VNF to a new software version. |
625 +------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
626 | QuiesceTraffic, | Quiesces traffic (stops traffic gracefully) and resume traffic on the VNF. These commands do not stop the application processes (which is done using StopApplication). |
628 +------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
631 d. Monitoring & Management
632 ===========================
634 This section addresses data collection and event processing functionality that is directly
635 dependent on the interfaces provided by the VNFs’ APIs. These can be in the form of asynchronous
636 interfaces for event, fault notifications, and autonomous data streams. They can also be
637 synchronous interfaces for on-demand requests to retrieve various performance, usage,
638 and other event information.
640 The target direction for VNF interfaces is to employ APIs that are implemented
641 utilizing standardized messaging and modeling protocols over standardized transports.
642 Migrating to a virtualized environment presents a tremendous opportunity to eliminate
643 the need for proprietary interfaces for VNF provider equipment while removing the traditional
644 boundaries between Network Management Systems and Element Management Systems. Additionally,
645 VNFs provide the ability to instrument the networking applications by creating event
646 records to test and monitor end-to-end data flow through the network, similar to what
647 physical or virtual probes provide without the need to insert probes at various points
648 in the network. The VNF providers must be able to provide the aforementioned set of required
649 data directly to the ONAP collection layer using standardized interfaces.
651 Data Model for Event Records
652 ----------------------------
654 This section describes the data model for the collection of telemetry data from VNFs
655 by Service Providers (SPs) to manage VNF health and runtime lifecycle. This data
656 model is referred to as the VNF Event Streaming (VES) specifications. While this
657 document is focused on specifying some of the records from the ONAP perspective,
658 there may be other external bodies using the same framework to specify additional
659 records. For example, OPNFV has a VES project that is looking to specify records
660 for OpenStack’s internal telemetry to manage Application (VNFs), physical and
661 virtual infrastructure (compute, storage, network devices), and virtual infrastructure
662 managers (cloud controllers, SDN controllers). Note that any configurable parameters
663 for these data records (e.g., frequency, granularity, policy-based configuration)
664 will be managed using the “Configuration” framework described in the prior sections
667 The Data Model consists of:
669 - Common Header Record: This data structure precedes each of the
670 Technology Independent and Technology Specific records sections of
673 - Technology Independent Records: This version of the document specifies
674 the model for Fault, Heartbeat, State Change, Syslog, Threshold Crossing
675 Alerts, and VNF Scaling* (short for measurementForVfScalingFields – actual
676 name used in JSON specification) records. In the future, these may be
677 extended to support other types of technology independent records. Each
678 of these records allows additional fields (name/ value pairs) for extensibility.
679 The VNF provider can use these VNF Provider-specific additional fields to provide
680 additional information that may be relevant to the managing systems.
682 - Technology Specific Records: This version of the document specifies the model
683 for Mobile Flow records, Signaling and Voice Quality records. In the future,
684 these may be extended to support other types of records (e.g. Network Fabric,
685 Security records, etc.). Each of these records allows additional fields
686 (name/value pairs) for extensibility. The VNF providers can use these VNF-specific
687 additional fields to provide additional information that may be relevant to the
688 managing systems. A placeholder for additional technology specific areas of
689 interest to be defined in the future documents has been depicted.
693 Figure 1. Data Model for Event Records
695 Event Records - Data Structure Description
696 ------------------------------------------
698 The data structure for event records consists of:
700 - a Common Event Header block;
702 - zero or more technology independent domain blocks; and
704 - e.g., Fault domain, State Change domain, Syslog domain, etc.
706 - zero or more technology specific domain blocks.
708 - e.g., Mobile Flow domain, Signaling domain, Voice Quality domain,
712 ~~~~~~~~~~~~~~~~~~~~~
714 The common header that precedes any of the domain-specific records contains
715 information identifying the type of record to follow, information about
716 the sender and other identifying characteristics related to timestamp,
717 sequence number, etc.
719 Technology Independent Records – Fault Fields
720 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
722 The Fault Record, describing a condition in the Fault domain, contains
723 information about the fault such as the entity under fault, the
724 severity, resulting status, etc.
726 Technology Independent Records – Heartbeat Fields
727 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
729 The Heartbeat Record provides an optional structure for communicating
730 information about heartbeat or watchdog signaling events. It can
731 contain information about service intervals, status information etc.
732 as required by the heartbeat implementation.
734 Note: Heartbeat records would only have the Common Event Header block.
735 An optional heartbeat domain is available if required by the heartbeat
738 Technology Independent Records – State Change Fields
739 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
741 The State Change Record provides a structure for communicating information
742 about data flow through the VNF. It can contain information about state
743 change related to physical device that is reported by VNF. As an example,
744 when cards or port name of the entity that has changed state.
746 Technology Independent Records – Syslog Fields
747 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
749 The Syslog Record provides a structure for communicating any type of
750 information that may be logged by the VNF. It can contain information
751 about system internal events, status, errors, etc.
753 Technology Independent Records – Threshold Crossing Alert Fields
754 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
756 The Threshold Crossing Alert (TCA) Record provides a structure for
757 communicating information about threshold crossing alerts. It can
758 contain alert definitions and types, actions, events, timestamps
759 and physical or logical details.
761 Technology Independent Records - VNF Scaling Fields
762 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
764 The VNF Scaling\* (short for measurementForVfScalingFields –
765 actual name used in JSON specification) Record contains information
766 about VNF and VNF resource structure and its condition to help in
767 the management of the resources for purposes of elastic scaling.
769 Technology Independent Records – otherFields
770 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
772 The otherFields Record defines fields for events belonging to the
773 otherFields domain of the Technology Independent domain enumeration.
774 This record provides a mechanism to convey a complex set of fields
775 (possibly nested or opaque) and is purely intended to address
776 miscellaneous needs such as addressing time-to-market considerations
777 or other proof-of-concept evaluations. Hence, use of this record
778 type is discouraged and should be minimized.
780 Technology Specific Records – Mobile Flow Fields
781 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
783 The Mobile Flow Record provides a structure for communicating
784 information about data flow through the VNF. It can contain
785 information about connectivity and data flows between serving
786 elements for mobile service, such as between LTE reference points, etc.
788 Technology Specific Records – Signaling Fields
789 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
791 The Signaling Record provides a structure for communicating information
792 about signaling messages, parameters and signaling state. It can
793 contain information about data flows for signaling and controlling
794 multimedia communication sessions such as voice and video calls.
796 Technology Specific Records – Voice Quality Fields
797 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
798 The Voice Quality Record provides a structure for communicating information
799 about voice quality statistics including media connection information,
800 such as transmitted octet and packet counts, packet loss, packet delay
801 variation, round-trip delay, QoS parameters and codec selection.
803 Technology Specific Records – Future Domains
804 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
806 The futureDomains Record is a placeholder for additional technology
807 specific areas of interest that will be defined and described
808 in the future documents.
810 Data Structure Specification of the Event Record
811 ------------------------------------------------
813 For additional information on the event record formats of the data
814 structures mentioned above, please refer to `VES Event
815 Listener <https://github.com/att/evel-test-collector/tree/master/docs/att_interface_definition>`__.
817 Transports and Protocols Supporting Resource Interfaces
818 -------------------------------------------------------
820 Delivery of data from VNFs to ONAP must use the common transport mechanisms and protocols
821 for all VNFs as defined in this document. Transport mechanisms and protocols have been
822 selected to enable both high volume and moderate volume datasets, as well as asynchronous
823 and synchronous communications over secure connections. The specified encoding provides
824 self-documenting content, so data fields can be changed as needs evolve, while minimizing
825 changes to data delivery.
827 The term ‘Event Record’ is used throughout this document to represent various forms of
828 telemetry or instrumentation made available by the VNF including, faults, status events,
829 various other types of VNF measurements and logs. Headers received by themselves must be
830 used as heartbeat indicators. Common structures and delivery protocols for other types of
831 data will be given in future versions of this document as we get more insight into data
832 volumes and required processing.
834 In the following sections, we provide options for encoding, serialization and data
835 delivery. Agreements between Service Providers and VNF providers shall determine which
836 encoding, serialization and delivery method to use for particular data sets. The selected
837 methods must be agreed to prior to the on-boarding of the VNF into ONAP design studio.
839 VNF Telemetry using VES/JSON Model
840 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
842 The preferred model for data delivery from a VNF to ONAP DCAE is the JSON driven model as depicted in Figure 2.
846 Figure 2. VES/JSON Driven Model
848 VNF providers will provide a YAML artifact to the Service Provider that describes:
850 * standard VES/JSON model information elements (key/values) that the VNF provides
851 * any additional non-standard (custom) VES/JSON model information elements (key/values) that the VNF provides
853 Using the semantics and syntax supported by YAML, VNF providers will indicate specific conditions that may
854 arise, and recommend actions that should be taken at specific thresholds, or if specific conditions
855 repeat within a specified time interval.
857 Based on the VNF provider's recommendations, the Service Provider may create additional YAML artifacts
858 (using ONAP design Studio), which finalizes Service Provider engineering rules for the processing of
859 the VNF events. The Service Provider may alter the threshold levels recommended by the VNF providor,
860 and may modify and more clearly specify actions that should be taken when specified conditions arise.
861 The Service Provider-created version of the YAML artifact will be distributed to ONAP applications
862 by the Design framework.
864 VNF Telemetry using YANG Model
865 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
867 In addition to the JSON driven model described above, a YANG driven model can also be
868 supported, as depicted in Figure 3.
872 Figure 3. YANG Driven Model
874 VNF providers will provide to the Service Provider the following YANG model artifacts:
876 * common IETF YANG modules that support the VNF
877 * native (VNF provider-supplied) YANG modules that support the VNF
878 * open (OpenConfig) YANG modules and the following configuration-related information, including:
880 * telemetry configuration and operational state data; such as:
883 * subscription bindings
886 * transport mechanisms
889 * a YAML artifact that provides all necessary mapping relationships between YANG model data types to VES/JSON information elements
890 * YANG helper or decoder functions that automate the conversion between YANG model data types to VES/JSON information elements
891 * OPTIONAL: YANG Telemetry modules in JSON format per RFC 7951
893 Using the semantics and syntax supported by YANG, VNF providers will indicate specific conditions that may
894 arise, and recommend actions that should be taken at specific thresholds, or if specific conditions
895 repeat within a specified time interval.
897 Based on the VNF provider's recommendations, the Service Provider may create additional YAML artifacts
898 (using ONAP design Studio), which finalizes Service Provider engineering rules for the processing
899 of the VNF events. The Service Provider may alter the threshold levels recommended by the
900 VNF provider, and may modify and more clearly specify actions that should be taken when specified
901 conditions arise. The Service Provided-created version of the YAML will be distributed to ONAP
902 applications by the Design framework.
904 Note: While supporting the YANG model described above, we are still leveraging the VES JSON
905 based model in DCAE. The purpose of the diagram above is to illustrate the concept only and
906 not to imply a specific implementation.
908 VNF Telemetry using Google Protocol Buffers
909 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
911 In addition to the data delivery models described above, support for delivery of VNF telemetry
912 using Google Protocol Buffers (GPB) can also be supported, as depicted in Figure 4.
914 VNF providers will provide to the Service Provider the additional following artifacts to
915 support the delivery of VNF telemetry to DCAE via the open-source gRPC mechanism using
916 Google's Protocol Buffers:
918 * the YANG model artifacts described in support of the "VNF Telemetry using YANG Model"
919 * valid definition file(s) for all GPB / KV-GPB encoded messages
920 * valid definition file(s) for all gRPC services
921 * gRPC method parameters and return types specified as Protocol Buffers messages
925 Figure 4. Protocol Buffers Driven Model
927 Note: if Google Protocol Buffers are employed for delivery of VNF telemetry, Key-Value
928 Google Protocol Buffers (KV-GPB) is the preferred serialization method. Details of
929 specifications and versioning corresponding to a release can be found
930 at: `VES Event Listener <https://github.com/att/evel-test-collector/tree/master/docs/att_interface_definition>`__.
932 Note: While supporting the VNF telemetry delivery approach described above, we are
933 still leveraging the VES JSON based model in DCAE. The purpose of the diagram above
934 is to illustrate the concept only and not to imply a specific implementation.
936 Monitoring & Management Requirements
937 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
939 **VNF telemetry via standardized interface**
941 * R-51910 The xNF **MUST** provide all telemetry (e.g., fault event records, syslog records, performance records etc.) to ONAP using the model, format and mechanisms described in this section.
943 **Encoding and Serialization**
945 Content delivered from VNFs to ONAP is to be encoded and serialized using JSON:
949 * R-19624 The xNF **MUST** encode and serialize content delivered to ONAP using JSON (RFC 7159) plain text format. High-volume data
950 is to be encoded and serialized using `Avro <http://avro.apache.org/>`_, where the Avro [5]_ data format are described using JSON.
952 - JSON plain text format is preferred for moderate volume data sets (option 1), as JSON has the advantage of having well-understood simple processing and being human-readable without additional decoding. Examples of moderate volume data sets include the fault alarms and performance alerts, heartbeat messages, measurements used for xNF scaling and syslogs.
953 - Binary format using Avro is preferred for high volume data sets (option 2) such as mobility flow measurements and other high-volume streaming events (such as mobility signaling events or SIP signaling) or bulk data, as this will significantly reduce the volume of data to be transmitted. As of the date of this document, all events are reported using plain text JSON and REST.
954 - Avro content is self-documented, using a JSON schema. The JSON schema is delivered along with the data content (http://avro.apache.org/docs/current/ ). This means the presence and position of data fields can be recognized automatically, as well as the data format, definition and other attributes. Avro content can be serialized as JSON tagged text or as binary. In binary format, the JSON schema is included as a separate data block, so the content is not tagged, further compressing the volume. For streaming data, Avro will read the schema when the stream is established and apply the schema to the received content.
956 In addition to the preferred method (JSON), content can be delivered from xNFs to ONAP can be encoded and serialized using Google Protocol Buffers (GPB).
960 Telemetry data delivered using Google Protocol Buffers v3 (proto3) can be serialized in one of the following methods:
962 * Key-value Google Protocol Buffers (KV-GPB) is also known as self-describing GPB:
964 * keys are strings that correspond to the path of the system resources for the VNF being monitored.
965 * values correspond to integers or strings that identify the operational state of the VNF resource, such a statistics counters and the state of a VNF resource.
967 * VNF providers must supply valid KV-GPB definition file(s) to allow for the decoding of all KV-GPB encoded telemetry messages.
969 * Native Google Protocol Buffers (GPB) is also known as compact GPB:
971 * keys are represented as integers pointing to the system resources for the VNF being monitored.
972 * values correspond to integers or strings that identify the operational state of the VNF resource, such a statistics counters and the state of a VNF resource.
974 * Google Protocol Buffers (GPB) requires metadata in the form of .proto files. VNF providers must supply the necessary GPB .proto files such that GPB telemetry messages can be encoded and decoded.
976 * In the future, we may consider support for other types of encoding & serialization methods based on industry demand
979 **Reporting Frequency**
981 * R-98191 The xNF **MUST** vary the frequency that asynchronous data is delivered based on the content and how data may be aggregated or grouped together. For example, alarms and alerts are expected to be delivered as soon as they appear. In contrast, other content, such as performance measurements, KPIs or reported network signaling may have various ways of packaging and delivering content. Some content should be streamed immediately; or content may be monitored over a time interval, then packaged as collection of records and delivered as block; or data may be collected until a package of a certain size has been collected; or content may be summarized statistically over a time interval, or computed as a KPI, with the summary or KPI being delivered.
983 - We expect the reporting frequency to be configurable depending on the virtual network function’s needs for management. For example, Service Provider may choose to vary the frequency of collection between normal and trouble-shooting scenarios.
984 - Decisions about the frequency of data reporting will affect the size of delivered data sets, recommended delivery method, and how the data will be interpreted by ONAP. These considerations should not affect deserialization and decoding of the data, which will be guided by the accompanying JSON schema or GPB definition files.
986 **Addressing and Delivery Protocol**
988 ONAP destinations can be addressed by URLs for RESTful data PUT. Future data sets may also be addressed by host name and port number for TCP streaming, or by host name and landing zone directory for SFTP transfer of bulk files.
990 * R-88482 The xNF **SHOULD** use REST using HTTPS delivery of plain text JSON for moderate sized asynchronous data sets, and for high volume data sets when feasible.
991 * R-84879 The xNF **MUST** have the capability of maintaining a primary and backup DNS name (URL) for connecting to ONAP collectors, with the ability to switch between addresses based on conditions defined by policy such as time-outs, and buffering to store messages until they can be delivered. At its discretion, the service provider may choose to populate only one collector address for a xNF. In this case, the network will promptly resolve connectivity problems caused by a collector or network failure transparently to the xNF.
992 * R-81777 The VNF **MUST** be configured with initial address(es) to use at deployment time. Subsequently, address(es) may be changed through ONAP-defined policies delivered from ONAP to the VNF using PUTs to a RESTful API, in the same manner that other controls over data reporting will be controlled by policy.
993 * R-08312 The xNF **MAY** use other options which are expected to include
995 - REST delivery of binary encoded data sets.
996 - TCP for high volume streaming asynchronous data sets and for other high volume data sets. TCP delivery can be used for either JSON or binary encoded data sets.
997 - SFTP for asynchronous bulk files, such as bulk files that contain large volumes of data collected over a long time interval or data collected across many xNFs. This is not preferred. Preferred is to reorganize the data into more frequent or more focused data sets, and deliver these by REST or TCP as appropriate.
998 - REST for synchronous data, using RESTCONF (e.g., for xNF state polling).
1000 * R-03070 The xNF **MUST**, by ONAP Policy, provide the ONAP addresses as data destinations for each xNF, and may be changed by Policy while the xNF is in operation. We expect the xNF to be capable of redirecting traffic to changed destinations with no loss of data, for example from one REST URL to another, or from one TCP host and port to another.
1002 **Asynchronous and Synchronous Data Delivery**
1004 * R-06924 The xNF **MUST** deliver asynchronous data as data becomes available, or according to the configured frequency.
1005 * R-73285 The xNF **MUST** must encode, address and deliver the data as described in the previous paragraphs.
1006 * R-42140 The xNF **MUST** respond to data requests from ONAP as soon as those requests are received, as a synchronous response.
1007 * R-34660 The xNF **MUST** use the RESTCONF/NETCONF framework used by the ONAP configuration subsystem for synchronous communication.
1008 * R-86585 The VNF **MUST** use the YANG configuration models and RESTCONF [RFC8040] (https://tools.ietf.org/html/rfc8040).
1009 * R-11240 The xNF **MUST** respond with content encoded in JSON, as described in the RESTCONF specification. This way the encoding of a synchronous communication will be consistent with Avro.
1010 * R-70266 The xNF **MUST** respond to an ONAP request to deliver the current data for any of the record types defined in `Event Records - Data Structure Description`_ by returning the requested record, populated with the current field values. (Currently the defined record types include fault fields, mobile flow fields, measurements for xNF scaling fields, and syslog fields. Other record types will be added in the future as they become standardized and are made available.)
1011 * R-46290 The xNF **MUST** respond to an ONAP request to deliver granular data on device or subsystem status or performance, referencing the YANG configuration model for the xNF by returning the requested data elements.
1012 * R-43327 The xNF **SHOULD** use `Modeling JSON text with YANG <https://tools.ietf.org/html/rfc7951>`_, If YANG models need to be translated to and from JSON{RFC7951]. YANG configuration and content can be represented via JSON, consistent with Avro, as described in “Encoding and Serialization” section.
1016 * R-42366 The xNF **MUST** support secure connections and transports such as Transport Layer Security (TLS) protocol [`RFC5246 <https://tools.ietf.org/html/rfc5246>`_] and should adhere to the best current practices outlined in `RFC7525 <https://tools.ietf.org/html/rfc7525>`_.
1017 * R-44290 The xNF **MUST** control access to ONAP and to xNFs, and creation of connections, through secure credentials, log-on and exchange mechanisms.
1018 * R-47597 The xNF **MUST** carry data in motion only over secure connections.
1019 * R-68165 The xNF **MUST** encrypt any content containing Sensitive Personal Information (SPI) or certain proprietary data, in addition to applying the regular procedures for securing access and delivery.
1023 https://github.com/mbj4668/pyang
1026 Recall that the Node Object **is required** to be identical across
1027 all VMs of a VNF invoked as part of the action except for the “name”.
1030 Upstream elements must provide the appropriate FQDN in the request to
1031 ONAP for the desired action.
1034 Multiple ONAP actions may map to one playbook.
1037 This option is not currently supported in ONAP and it is currently
1038 under consideration.
1041 https://wiki.opnfv.org/display/PROJ/VNF+Event+Stream
1043 .. |image0| image:: Data_Model_For_Event_Records.png
1048 .. |image1| image:: VES_JSON_Driven_Model.png
1052 .. |image2| image:: YANG_Driven_Model.png
1056 .. |image3| image:: Protocol_Buffers_Driven_Model.png
Code Review / vnfrqts / requirements.git / blob