1 .. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
3 .. Licensed under the Creative Commons License, Attribution 4.0 Intl.
4 (the "License"); you may not use this documentation except in compliance
5 with the License. You may obtain a copy of the License at
7 .. https://creativecommons.org/licenses/by/4.0/
9 .. Unless required by applicable law or agreed to in writing, software
10 distributed under the License is distributed on an "AS IS" BASIS,
11 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 See the License for the specific language governing permissions and
13 limitations under the License.
17 ------------------------
20 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
22 The following are the requirements related to PNF Plug and Play.
28 :introduced: casablanca
30 The PNF Vendor **MAY** provide software version(s) to be supported by PNF
31 for SDC Design Studio PNF Model. This is set in the PNF Model property
38 :introduced: casablanca
40 The following VES Events **MUST** be supported by the PNF: pnfRegistration
41 VES Event, HVol VES Event, and Fault VES Event. These are onboarded via
44 Note: these VES Events are emitted from the PNF to support PNF Plug and
45 Play, High Volume Measurements, and Fault events respectively.
51 :introduced: casablanca
53 The PNF **MUST** support & accept the provisioning of an ONAP contact IP
54 address (in IPv4 or IPv6 format).
56 Note: For example, it a possibility is that an external EMS would configure
57 & provision the ONAP contact IP address to the PNF (in either IPv4 or
58 IPv6 format). For the PNF Plug and Play Use Case, this IP address is the
59 service provider's "point of entry" to the DCAE VES Listener.
61 Note: different service provider's network architecture may also require
62 special setup to allow an external PNF to contact the ONAP installation.
63 For example, in the AT&T network, a maintenance tunnel is used to access
70 :introduced: casablanca
72 The PNF **MUST** have "ONAP Aware" software which is capable of performing
73 PNF PnP registration with ONAP. The "ONAP Aware" software is capable of
74 performing the PNF PnP Registration with ONAP MUST either be loaded
75 separately or integrated into the PNF software upon physical delivery
76 and installation of the PNF.
78 Note: It is up to the specific vendor to design the software management
85 :introduced: casablanca
87 The PNF **MUST** support the provisioning of security and authentication
88 parameters (HTTP username and password) in order to be able to authenticate
91 Note: In R3, a username and password are used with the DCAE VES Event
92 Listener which are used for HTTP Basic Authentication.
94 Note: The configuration management and provisioning software are specific
95 to a vendor architecture.
101 :introduced: casablanca
103 When the PNF sets up a HTTP or HTTPS connection, it **MUST** provide a
104 username and password to the DCAE VES Collector for HTTP Basic
107 Note: HTTP Basic Authentication has 4 steps: Request, Authenticate,
108 Authorization with Username/Password Credentials, and Authentication Status
109 as per RFC7617 and RFC 2617.
115 :introduced: casablanca
117 If the PNF set up a TLS connection and mutual (two-way) authentication is
118 being used, then the PNF **MUST** provide its own X.509v3 Certificate to
119 the DCAE VES Collector for authentication.
121 Note: This allows TLS authentication by DCAE VES Collector.
123 Note: The PNF got its X.509 certificate through Enrollment with an
124 operator certificate authority or a X.509 vendor certificate from the
127 Note: In R3 three authentication options are supported:
129 (1) HTTP with Username & Password and no TLS.
131 (2) HTTP with Username & Password & TLS with two-way certificate
134 (3) HTTP with Username & Password & TLS with server-side
135 certificate authentication.
141 :introduced: casablanca
143 The PNF **MUST** use a IP address to contact ONAP.
145 Note: it is expected that an ONAP operator can ascertain the ONAP IP
146 address or the security gateway to reach ONAP on the VID or ONAP portal
149 Note: The ONAP contact IP address has been previously configured and
150 provisioned prior to this step.
152 Note: The ONAP IP address could be provisioned or resolved through
159 :introduced: casablanca
161 The PNF **MUST** support a HTTPS connection to the DCAE VES Event
168 :introduced: casablanca
170 The PNF **MAY** support a HTTP connection to the DCAE VES Event Listener.
172 Note: HTTP is allowed but not recommended.
178 :introduced: casablanca
180 The PNF **MUST** support sending a pnfRegistration VES event.
186 :introduced: casablanca
188 The PNF **MUST** send the pnfRegistration VES event periodically.
194 :introduced: casablanca
196 The pnfRegistration VES event periodicity **MUST** be configurable.
198 Note: The PNF uses the service configuration request as a semaphore to
199 stop sending the pnfRegistration sent. See the requirement PNP-5360
206 :introduced: casablanca
208 If the PNF encounters an error authenticating, reaching the ONAP DCAE VES
209 Event listener or recieves an error response from sending the pnfRegistration
210 VES Event, it **MAY** log the error, and notify the operator.
212 Note: the design of how errors are logged, retrieved and reported
213 will be a vendor-specific architecture. Reporting faults and errors
214 is also a vendor specific design. It is expected that the PNF shall
215 have a means to log an error and notify a user when a fault condition
216 occurs in trying to contact ONAP, authenticate or send a pnfRegistration
223 :introduced: casablanca
225 The PNF **MUST** support the Ansible protocol for a Service Configuration
226 message exchange between the PNF and PNF Controller (in ONAP).
228 Note: this exchange may be either Ansible, Chef, or NetConf depending on
229 the PNF. Note: The PNF Controller may be VF-C, APP-C or SDN-C based on the
230 PNF and PNF domain. Note: for R3 (Casablanca) only Ansible is supported.
236 :introduced: casablanca
238 When the PNF receives a Service configuration from ONAP, the PNF **MUST**
239 cease sending the pnfRegistration VES Event.
245 :introduced: casablanca
247 The PNF **MAY** support the optional parameters for Service
248 Configuration Parameters.
250 Note: These are detailed in the Stage 5 PnP
252 Note: These parameters are optional, and not all PNFs will support any
253 or all of these parameters, it is up to the vendor and service provider
254 to ascertain which ones are supported up to an including all of the ones
255 that have been defined. Note: It is expected that there will be a growing
256 list of supported configuration parameters in future releases of ONAP.
262 :introduced: casablanca
264 (Error Case) - If an error is encountered by the PNF during a
265 Service Configuration exchange with ONAP, the PNF **MAY** log the
266 error and notify an operator.
272 :introduced: casablanca
274 (Error Case) - The PNF **MUST** support a configurable timer to stop the
275 periodicity sending of the pnfRegistration VES event. If this timer expires
276 during a Service Configuration exchange between the PNF and ONAP, it
277 MAY log a time-out error and notify an operator.
279 Note: It is expected that each vendor will enforce and define a PNF
280 service configuration timeout period. This is because the PNF cannot
281 wait indefinitely as there may also be a technician on-site trying to
282 complete installation & commissioning. The management of the VES event
283 exchange is also a requirement on the PNF to be developed by the PNF