blob: 9b715dd48952ccbaf6ad9eee911d9d1b96efaf42 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
.. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
.. Licensed under the Creative Commons License, Attribution 4.0 Intl.
(the "License"); you may not use this documentation except in compliance
with the License. You may obtain a copy of the License at
.. https://creativecommons.org/licenses/by/4.0/
.. Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Purpose
=======
- The purpose of these requirements is to accelerate adoption of VNF or PNF
best practices which will increase innovation, minimize customization needed
to onboard VNFs or PNFs as well as reduce implementation complexity, time and
cost for all impacted stakeholders.
- The consolidated requirements provide common VNF or PNF requirements across
the industry in order to drive interoperability, simplify management, and
reduce cost to build, deploy and manage VNFs or PNFs.
- These requirements serve multiple purposes:
- Primarily it provides a detailed list of requirements for VNF or PNF
providers to meet to be compatible with ONAP; VNF or PNF providers will
use the VNF or PNF requirements to build VNFs/PNFs that are compatible
with ONAP.
- It can also serve as a list of requirements that service providers can
use in RFPs for selecting VNFs/PNFs.
- It will also be used as a basis for testing and certification of
VNFs or PNFs for compliance with ONAP; ONAP projects such as the VNF
Validation Project will uses these VNFs or PNFs requirements to build
test cases to validate VNFs or PNFs for compliance with ONAP.
|
