4 a. – Chef JSON Key Value Description
5 =================================================
7 The following provides the key value pairs that must be contained in the
8 JSON file supporting Chef action.
10 Table A1. Chef JSON File key value description
11 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
13 +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------+
14 | **Field Name** | **Description** | **Type** | **Comment** |
15 +===================+===================================================================================================================================================================================================================================================================================================+=============+=========================================================================================================================================+
16 | Environment | A JSON dictionary representing a Chef Environment object. If the VNF action requires loading or modifying Chef environment attributes associated with the VNF, all the relevant information must be provided in this JSON dictionary in a structure that conforms to a Chef Environment Object. | Optional | Depends on VNF action. |
17 +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------+
18 | Node | A JSON dictionary representing a Chef Node Object. | Mandatory | |
20 | | The Node JSON dictionary must include the run list to be triggered for the desired VNF action by the push job. It should also include any attributes that need to be configured on the Node Object as part of the VNF action. | | |
21 +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------+
22 | NodeList | Array of FQDNs that correspond to the endpoints (VMs) of a VNF registered with the Chef Server that need to trigger a chef-client run as part of the desired VNF action. | Mandatory | |
23 +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------+
24 | PushJobFlag | This field indicates whether the VNF action requires a push Job. Push job object will be created by ONAP if required. | Mandatory | If set to “True”, ONAP will request a push job. Ignored otherwise. |
25 +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------+
26 | CallbackCapable | This field indicates if the chef-client run invoked by push job corresponding to the VNF action is capable of posting results on a callback URL. | Optional | If Chef cookbook is callback capable, VNF owner is required to set it to “True”. Ignored otherwise. |
27 +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------+
28 | GetOutputFlag | Flag which indicates whether ONAP should retrieve output generated in a chef-client run from Node object attribute node[‘PushJobOutput’] for this VNF action (e.g., in Audit). | Mandatory | ONAP will retrieve output from NodeObject attributes [‘PushJobOutput’] for all nodes in NodeList if set to “True”. Ignored otherwise. |
29 +-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-----------------------------------------------------------------------------------------------------------------------------------------+
31 Chef Template example:
37 "description": "VNF Chef environment for HAR",
38 "json\_class": "Chef::Environment",
39 "chef\_type": "environment",
40 "default\_attributes": { },
41 "override\_attributes": {
44 “Database\_IP”:”10.10.1.5”
49 “name” : “signal.network.com “
51 "json\_class": "Chef::Node",
53 “IPAddress1”: “192.168.1.2”,
54 “IPAddress2”:”135.16.162.5”,
61 “chef\_environment” : “\_default”
62 "run\_list": [ "configure\_signal" ]
64 “NodeList”:[“node1.vnf\_a.onap.com”, “node2.vnf\_a.onap.com”],
66 “CallbackCapable”:True
67 “GetOutputFlag” : “False”
70 The example JSON file provided by the VNF provider for each VNF action will be
71 turned into a template by ONAP, that can be updated with instance
72 specific values at run-time.
74 Some points worth noting regarding the JSON fields:
76 a. The JSON file must be created for each action for each VNF.
78 b. If a VNF action involves multiple endpoints (VMs) of a VNF, ONAP will
79 replicate the “Node” JSON dictionary in the template and post it to
80 each FQDN (i.e., endpoint) in the NodeList after setting the “name”
81 field in the Node object to be the respective FQDN [1]_. Hence, it
82 is required that all end points (VMs) of a VNF involved in a VNF
83 action support the same set of Node Object attributes.
85 The following table describes the JSON dictionary to post in Callback.
87 Table A2. JSON Dictionary to Post in Callback
88 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
90 +-----------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------+
91 | **Key** | **Description** | **Type** | **Comment** |
92 +=================+===========================================================================================================================================================================================================+=============+=============================================================+
93 | RequestId | A unique string associated with the original request by ONAP. This key-value pair will be provided by ONAP in the environment of the push job request and must be returned as part of the POST message. | Mandatory | |
94 +-----------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------+
95 | StatusCode | An integer that must be set to | Mandatory | |
97 | | 200 if chef-client run on the node finished successfully | | |
99 | | 500 otherwise. | | |
100 +-----------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------+
101 | StatusMessage | A string which must be set to | Mandatory | |
103 | | ‘SUCCESS’ if StatusCode was 200 | | |
105 | | Appropriate error message otherwise. | | |
106 +-----------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------+
107 | Name | A string which corresponds to the name of the node where push job is run. It is required that the value be retrieved from the node object attributes (where it is always defined). | Mandatory | |
108 +-----------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------+
109 | PushJobOutput | Any output from the chef-client run that needs to be returned to ONAP. | Optional | Depends on VNF action. If empty, it must not be included. |
110 +-----------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------------------------------------------------------------+
113 b. – Ansible JSON Key Value Description
114 ===================================================
116 The following provides the key value pairs that must be contained in the
117 JSON file supporting Ansible action.
119 Table B1. Ansible JSON File key value description
120 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
122 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------------------------------------------------------------+
123 | **Field Name** | **Description** | **Type** | **Comment** |
124 +==================+============================================================================================================================================================================================================================================================================================+=============+=====================================================================+
125 | PlaybookName | VNF providor must list name of the playbook used to execute the VNF action. | Mandatory | |
126 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------------------------------------------------------------+
127 | Action | Name of VNF action. | Optional | |
128 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------------------------------------------------------------+
129 | EnvParameters | A JSON dictionary which should list key value pairs to be passed to the Ansible playbook. These values would correspond to instance specific parameters that a playbook may need to execute an action. | Optional | Depends on the VNF action. |
130 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------------------------------------------------------------+
131 | NodeList | A JSON array of FQDNs that the playbook must be executed on. | Optional | If not provided, playbook will be executed on the Ansible Server. |
132 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------------------------------------------------------------+
133 | FileParameters | A JSON dictionary where keys are filenames and values are contents of files. The Ansible Server will utilize this feature to generate files with keys as filenames and values as content. This attribute can be used to generate files that a playbook may require as part of execution. | Optional | Depends on the VNF action and playbook design. |
134 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------------------------------------------------------------+
135 | Timeout | Time (in seconds) that a playbook is expected to take to finish execution for the VNF. If playbook execution time exceeds this value, Ansible Server will terminate the playbook process. | Optional | |
136 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+---------------------------------------------------------------------+
138 Ansible JSON file example:
142 “Action”:”Configure”,
144 "PlaybookName": "Ansible\_configure.yml",
146 "NodeList": ["test1.vnf\_b.onap.com", “test2.vnf\_b.onap.com”],
150 "EnvParameters": {"Retry": 3, "Wait": 5, “ConfigFile”:”config.txt”},
152 “FileParameters”:{“config.txt”:”db\_ip=10.1.1.1, sip\_timer=10000”}
156 In the above example, the Ansible Server will:
158 a. Process the “FileParameters” dictionary and generate a file named
159 ‘config.txt’ with contents set to the value of the ‘config.txt’ key.
161 b. Execute the playbook named ‘Ansible\_configure.yml’ on nodes with
162 FQDNs test1.vnf\_b.onap.com and test2.vnf\_b.onap.com respectively
163 while providing the following key value pairs to the playbook:
164 Retry=3, Wait=5, ConfigFile=config.txt
166 c. If execution time of the playbook exceeds 60 secs (across all hosts),
167 it will be terminated.
169 c. – VNF License Information Guidelines
170 ===================================================
172 This Appendix describes the metadata to be supplied for VNF licenses.
174 1. General Information
176 Table C1 defines the required and optional fields for licenses.
178 Table C1. Required Fields for General Information
179 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
181 +---------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+-------------+
182 | **Field Name** | **Description** | **Data Type** | **Type** |
183 +=============================================+===========================================================================================================================================================================================================================================================================================================+===================+=============+
184 | VNF Provider Name | The name of the VNF provider. | String | Mandatory |
185 +---------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+-------------+
186 | VNF Provider Product | The name of the product to which this agreement applies. | String | Mandatory |
188 | | Note: a contract/agreement may apply to more than one VNF provider product. In that case, provide the metadata for each product separately. | | |
189 +---------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+-------------+
190 | VNF Provider Product Description | A general description of VNF provider software product. | String | Optional |
191 +---------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+-------------+
192 | Export Control Classification Number (ECCN) | ECCNs are 5-character alpha-numeric designations used on the Commerce Control List (CCL) to identify dual-use items for export control purposes. An ECCN categorizes items based on the nature of the product, i.e. type of commodity, software, or technology and its respective technical parameters. | String | Mandatory |
193 +---------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+-------------+
194 | Reporting Requirements | A list of any reporting requirements on the usage of the software product. | List of strings | Optional |
195 +---------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+-------------+
199 Entitlements describe software license use rights. The use rights may be
200 quantified by various metrics: # users, # software instances, # units.
201 The use rights may be limited by various criteria: location (physical or
202 logical), type of customer, type of device, time, etc.
204 One or more entitlements can be defined; each one consists of the
207 Table C2. Required Fields for Entitlements
208 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
210 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
211 | **Field Name** | **Description** | **Data Type** | **Type** |
212 +=========================================================+=======================================================================================================================================================================================+===================+===============+
213 | VNF Provider Part Number / Manufacture Reference Number | Identifier for the entitlement as described by the VNF provider in their price list / catalog / contract. | String | Mandatory |
214 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
215 | Description | Verbiage that describes the entitlement. | String | Optional |
216 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
217 | Entitlement Identifier | Each entitlement defined must be identified by a unique value (e.g., numbered 1, 2, 3….) | String | Mandatory |
218 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
219 | Minimum Order Requirement | The minimum number of entitlements that need to be purchased. For example, the entitlements must be purchased in a block of 100. If no minimum is required, the value will be zero. | Number | Mandatory |
220 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
221 | Unique Reporting Requirements | A list of any reporting requirements on the usage of the software product. (e.g.: quarterly usage reports are required) | List of Strings | Optional |
222 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
223 | License Type | Type of license applicable to the software product. (e.g.: fixed-term, perpetual, trial, subscription.) | String | Mandatory |
224 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
225 | License Duration | Valid values: | String | Conditional |
227 | | **year**, **quarter**, **month**, **day**. | | |
229 | | Not applicable when license type is Perpetual. | | |
230 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
231 | License Duration Quantification | Number of years, quarters, months, or days for which the license is valid. | Number | Conditional |
233 | | Not applicable when license type is Perpetual. | | |
234 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
235 | Limits | see section C.4 for possible values | List | Optional |
236 +---------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------+---------------+
240 This section defines information on any License Keys associated with the
241 Software Product. A license key is a data string (or a file) providing a
242 means to authorize the use of software. License key does not provide
243 entitlement information.
245 License Keys are not required. Optionally, one or more license keys can
246 be defined; each one consists of the following fields:
248 Table C3. Required Fields for License Keys
249 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
251 +--------------------------+---------------------------------------------------------------------------------------------------------------+-----------------+-------------+
252 | **Field Name** | **Description** | **Data Type** | **Type** |
253 +==========================+===============================================================================================================+=================+=============+
254 | Description | Verbiage that describes the license key | String | Mandatory |
255 +--------------------------+---------------------------------------------------------------------------------------------------------------+-----------------+-------------+
256 | License Key Identifier | Each license key defined must be identified by a unique value (e.g., numbered 1, 2, 3….) | String | Mandatory |
257 +--------------------------+---------------------------------------------------------------------------------------------------------------+-----------------+-------------+
258 | Key Function | Lifecycle stage (e.g., Instantiation or Activation) at which the license key is applied to the software. | String | Optional |
259 +--------------------------+---------------------------------------------------------------------------------------------------------------+-----------------+-------------+
260 | License Key Type | Valid values: | String | Mandatory |
262 | | **Universal, Unique** | | |
264 | | **Universal** - a single license key value that may be used with any number of instances of the software. | | |
266 | | **Unique**- a unique license key value is required for each instance of the software. | | |
267 +--------------------------+---------------------------------------------------------------------------------------------------------------+-----------------+-------------+
268 | Limits | see section C.4 for possible values | List | Optional |
269 +--------------------------+---------------------------------------------------------------------------------------------------------------+-----------------+-------------+
271 1. Entitlement and License Key Limits
273 Limitations on the use of software entitlements and license keys may be
274 based on factors such as: features enabled in the product, the allowed
275 capacity of the product, number of installations, etc... The limits may
276 generally be categorized as:
288 Multiple limits may be applicable for an entitlement or license key.
289 Each limit may further be described by limit behavior, duration,
290 quantification, aggregation, aggregation interval, start date, end date,
293 When the limit is associated with a quantity, the quantity is relative
294 to an instance of the entitlement or license key. For example:
296 - Each entitlement grants the right to 50 concurrent users. If 10
297 entitlements are purchased, the total number of concurrent users
298 permitted would be 500. In this example, the limit category is
299 **amount**, the limit type is **users**, and the limit
300 **quantification** is **50.**
302 Each license key may be installed on 3 devices. If 5 license keys are
303 acquired, the total number of devices allowed would be 15. In this
304 example, the limit category is **usages**, the limit type is
305 **device**, and the limit **quantification** is **3.**
309 Locations may be logical or physical location (e.g., site, country). For
312 - use is allowed in Canada
314 Table C4. Required Fields for Location
315 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
317 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
318 | **Field Name** | **Description** | **Data Type** | **Type** |
319 +========================+=====================================================================================================================+==================+=============+
320 | Limit Identifier | Each limit defined for an entitlement or license key must be identified by a unique value (e.g., numbered 1,2,3…) | String | Mandatory |
321 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
322 | Limit Description | Verbiage describing the limit. | String | Mandatory |
323 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
324 | Limit Behavior | Description of the actions taken when the limit boundaries are reached. | String | Mandatory |
325 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
326 | Limit Category | Valid value: **location** | String | Mandatory |
327 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
328 | Limit Type | Valid values: **city, county, state, country, region, MSA, BTA, CLLI** | String | Mandatory |
329 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
330 | Limit List | List of locations where the VNF provider Product can be used or needs to be restricted from use | List of String | Mandatory |
331 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
332 | Limit Set Type | Indicates if the list is an inclusion or exclusion. | String | Mandatory |
334 | | Valid Values: | | |
336 | | **Allowed** | | |
338 | | **Not allowed** | | |
339 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
340 | Limit Quantification | The quantity (amount) the limit expresses. | Number | Optional |
341 +------------------------+---------------------------------------------------------------------------------------------------------------------+------------------+-------------+
345 Limit on the length of time the software may be used. For example:
347 - license key valid for 1 year from activation
349 - entitlement valid from 15 May 2018 thru 30 June 2020
351 Table C5. Required Fields for Time
352 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
354 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
355 | **Field Name** | **Description** | **Data Type** | **Type** |
356 +========================+===============================================================================================================================+==================+===============+
357 | Limit Identifier | Each limit defined for an entitlement or license key must be identified by a unique value (e.g., numbered) | String | Mandatory |
358 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
359 | Limit Description | Verbiage describing the limit. | String | Mandatory |
360 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
361 | Limit Behavior | Description of the actions taken when the limit boundaries are reached. | String | Mandatory |
363 | | The limit behavior may also describe when a time limit takes effect. (e.g., key is valid for 1 year from date of purchase). | | |
364 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
365 | Limit Category | Valid value: **time** | String | Mandatory |
366 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
367 | Limit Type | Valid values: **duration, date** | String | Mandatory |
368 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
369 | Limit List | List of times for which the VNF Provider Product can be used or needs to be restricted from use | List of String | Mandatory |
370 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
371 | Duration Units | Required when limit type is duration. Valid values: **perpetual, year, quarter, month, day, minute, second, millisecond** | String | Conditional |
372 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
373 | Limit Quantification | The quantity (amount) the limit expresses. | Number | Optional |
374 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
375 | Start Date | Required when limit type is date. | Date | Optional |
376 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
377 | End Date | May be used when limit type is date. | Date | Optional |
378 +------------------------+-------------------------------------------------------------------------------------------------------------------------------+------------------+---------------+
382 Limits based on how the software is used. For example:
384 - use is limited to a specific sub-set of the features/capabilities the
387 - use is limited to a certain environment (e.g., test, development,
390 - use is limited by processor (vm, cpu, core)
392 - use is limited by software release
394 Table C6. Required Fields for Usage
395 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
397 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
398 | **Field Name** | **Description** | **Data Type** | **Type** |
399 +========================+==============================================================================================================+==================+=============+
400 | Limit Identifier | Each limit defined for an entitlement or license key must be identified by a unique value (e.g., numbered) | String | Mandatory |
401 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
402 | Limit Description | Verbiage describing the limit. | String | Mandatory |
403 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
404 | Limit Behavior | Description of the actions taken when the limit boundaries are reached. | String | Mandatory |
405 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
406 | Limit Category | Valid value: **usages** | String | Mandatory |
407 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
408 | Limit Type | Valid values: **feature, environment, processor, version** | String | Mandatory |
409 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
410 | Limit List | List of usage limits (e.g., test, development, vm, core, R1.2.1, R1.3.5…) | List of String | Mandatory |
411 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
412 | Limit Set Type | Indicates if the list is an inclusion or exclusion. | String | Mandatory |
414 | | Valid Values: | | |
416 | | **Allowed** | | |
418 | | **Not allowed** | | |
419 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
420 | Limit Quantification | The quantity (amount) the limit expresses. | Number | Optional |
421 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
425 Limit on the entity (product line, organization, customer) allowed to
426 make use of the software. For example:
428 - allowed to be used in support of wireless products
430 - allowed to be used only for government entities
432 Table C7. Required Fields for Entity
433 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
435 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
436 | **Field Name** | **Description** | **Data Type** | **Type** |
437 +========================+==============================================================================================================+==================+=============+
438 | Limit Identifier | Each limit defined for an entitlement or license key must be identified by a unique value (e.g., numbered) | String | Mandatory |
439 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
440 | Limit Description | Verbiage describing the limit. | String | Mandatory |
441 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
442 | Limit Behavior | Description of the actions taken when the limit boundaries are reached. | String | Mandatory |
443 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
444 | Limit Category | Valid value: **entity** | String | Mandatory |
445 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
446 | Limit Type | Valid values: **product line, organization, internal customer, external customer** | String | Mandatory |
447 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
448 | Limit List | List of entities for which the VNF Provider Product can be used or needs to be restricted from use | List of String | Mandatory |
449 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
450 | Limit Set Type | Indicates if the list is an inclusion or exclusion. | String | Mandatory |
452 | | Valid Values: | | |
454 | | **Allowed** | | |
456 | | **Not allowed** | | |
457 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
458 | Limit Quantification | The quantity (amount) the limit expresses. | Number | Optional |
459 +------------------------+--------------------------------------------------------------------------------------------------------------+------------------+-------------+
463 These limits describe terms relative to utilization of the functions of
464 the software (for example, number of named users permitted, throughput,
465 or capacity). Limits of this type may also be relative to utilization of
466 other resources (for example, a limit for firewall software is not based
467 on use of the firewall software, but on the number of network
470 The metadata describing this type of limit includes the unit of measure
471 (e.g., # users, # sessions, # MB, # TB, etc.), the quantity of units,
472 any aggregation function (e.g., peak or average users), and aggregation
473 interval (day, month, quarter, year, etc.).
475 Table C8. Required Fields for Amount
476 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
478 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
479 | **Field Name** | **Description** | **Data Type** | **Type** |
480 +========================+================================================================================================================================================================================================================================================================+=================+=============+
481 | Limit Identifier | Each limit defined for an entitlement or license key must be identified by a unique value (e.g., numbered) | String | Mandatory |
482 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
483 | Limit Description | Verbiage describing the limit. | String | Mandatory |
484 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
485 | Limit Behavior | Description of the actions taken when the limit boundaries are reached. | String | Mandatory |
486 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
487 | Limit Category | Valid value: **amount** | String | Mandatory |
488 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
489 | Limit Type | Valid values: **trunk, user, subscriber, session, token, transactions, seats, KB, MB, TB, GB** | String | Mandatory |
490 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
491 | Type of Utilization | Is the limit relative to utilization of the functions of the software or relative to utilization of other resources? | String | Mandatory |
493 | | Valid values: | | |
495 | | - **software functions** | | |
497 | | - **other resources** | | |
498 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
499 | Limit Quantification | The quantity (amount) the limit expresses. | Number | Optional |
500 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
501 | Aggregation Function | Valid values: **peak, average** | String | Optional |
502 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
503 | Aggregation Interval | Time period over which the aggregation is done (e.g., average sessions per quarter). Required when an Aggregation Function is specified. | String | Optional |
505 | | Valid values: **day, month, quarter, year, minute, second, millisecond** | | |
506 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
507 | Aggregation Scope | Is the limit quantity applicable to a single entitlement or license key (each separately)? Or may the limit quantity be combined with others of the same type (resulting in limit amount that is the sum of all the purchased entitlements or license keys)? | String | Optional |
509 | | Valid values: | | |
511 | | - **single** | | |
513 | | - **combined** | | |
514 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
515 | Type of User | Describes the types of users of the functionality offered by the software (e.g., authorized, named). This field is included when Limit Type is user. | String | Optional |
516 +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+
518 d. – Requirement List
519 ==================================
521 R-11200: The VNF MUST keep the scope of a Cinder volume module, when it exists, to be 1:1 with the VNF Base Module or Incremental Module.
523 R-01334: The VNF **MUST** conform to the NETCONF RFC 5717, “Partial Lock Remote Procedure Call”.
525 R-51910: The VNF **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.
527 R-29324: The VNF **SHOULD** implement the protocol operation: **copy-config(target, source) -** Copy the content of the configuration datastore source to the configuration datastore target.
529 R-72184: The VNF **MUST** have routable FQDNs for all the endpoints (VMs) of a VNF that contain chef-clients which are used to register with the Chef Server. As part of invoking VNF actions, ONAP will trigger push jobs against FQDNs of endpoints for a VNF, if required.
531 R-23740: The VNF **MUST** accommodate the security principle of “least privilege” during development, implementation and operation. The importance of “least privilege” cannot be overstated and must be observed in all aspects of VNF development and not limited to security. This is applicable to all sections of this document.
533 R-12709: The VNFC **SHOULD** be independently deployed, configured, upgraded, scaled, monitored, and administered by ONAP.
535 R-88031: The VNF **SHOULD** implement the protocol operation: **delete-config(target) -** Delete the named configuration datastore target.
537 R-42207: The VNF **MUST** design resiliency into a VNF such that the resiliency deployment model (e.g., active-active) can be chosen at run-time.
539 R-98617: The VNF provider **MUST** provide information regarding any dependency (e.g., affinity, anti-affinity) with other VNFs and resources.
541 R-62498: The VNF **MUST**, if not using the NCSP’s IDAM API, encrypt OA&M access (e.g., SSH, SFTP).
543 R-42366: The VNF **MUST** support secure connections and transports.
545 R-33955: The VNF **SHOULD** conform its YANG model to \*\*RFC 6991, “Common YANG Data Types”.
547 R-33488: The VNF **MUST** protect against all denial of service attacks, both volumetric and non-volumetric, or integrate with external denial of service protection tools.
549 R-57617: The VNF **MUST** include the field “success/failure” in the Security alarms (where applicable and technically feasible).
551 R-57271: The VNF **MUST** provide the capability of generating security audit logs by interacting with the operating system (OS) as appropriate.
553 R-44569: The VNF provider **MUST NOT** require additional infrastructure such as a VNF provider license server for VNF providor functions and metrics..
555 R-67918: The VNF **MUST** handle replication race conditions both locally and geo-located in the event of a data base instance failure to maintain service continuity.
557 R-35532: The VNF **SHOULD** release and clear all shared assets (memory, database operations, connections, locks, etc.) as soon as possible, especially before long running sync and asynchronous operations, so as to not prevent use of these assets by other entities.
559 R-37692: The VNFC **MUST** provide API versioning to allow for independent upgrades of VNFC.
561 R-50252: The VNF **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 VNF action (e.g., audit), a playbook is required to return any VNF information.
563 R-58977: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for Eavesdropping.
565 R-59391: The VNF provider **MUST**, where a VNF provider requires the assumption of permissions, such as root or administrator, first log in under their individual user login ID then switch to the other higher level account; or where the individual user login is infeasible, must login with an account with admin privileges in a way that uniquely identifies the individual performing the function.
567 R-93443: The VNF **MUST** define all data models in YANG [RFC6020], and the mapping to NETCONF shall follow the rules defined in this RFC.
569 R-72243: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for Phishing / SMishing.
571 R-33280: The VNF **MUST NOT** use any instance specific parameters in a playbook.
573 R-73468: The VNF **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.
575 R-46908: The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "password complexity" policy. When passwords are used, they shall be complex and shall at least meet the following password construction requirements: (1) be a minimum configurable number of characters in length, (2) include 3 of the 4 following types of characters: upper-case alphabetic, lower-case alphabetic, numeric, and special, (3) not be the same as the UserID with which they are associated or other common strings as specified by the environment, (4) not contain repeating or sequential characters or numbers, (5) not to use special characters that may have command functions, and (6) new passwords must not contain sequences of three or more characters from the previous password.
577 R-86261: The VNF **MUST NOT** allow VNF provider access to VNFs remotely.
579 R-75343: The VNF **MUST** provide the capability of testing the validity of a digital certificate by recognizing the identity represented by the certificate — the "distinguished name".
581 R-40813: The VNF **SHOULD** support the use of virtual trusted platform module, hypervisor security testing and standards scanning tools.
583 R-02454: The VNF **MUST** support the existence of multiple major/minor versions of the VNF software and/or sub-components and interfaces that support both forward and backward compatibility to be transparent to the Service Provider usage.
585 R-20353: The VNF **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.
587 R-01556: The VNF Package **MUST** include documentation describing the fault, performance, capacity events/alarms and other event records that are made available by the VNF. The document must include:
589 R-56815: The VNF Package **MUST** include documentation describing supported VNF scaling capabilities and capacity limits (e.g., number of users, bandwidth, throughput, concurrent calls).
591 R-56793: The VNF **MUST** test for adherence to the defined performance budgets at each layer, during each delivery cycle with delivered results, so that the performance budget is measured and the code is adjusted to meet performance budget.
593 R-54520: The VNF **MUST** log successful and unsuccessful login attempts.
595 R-10173: The VNF **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.
597 R-36280: The VNF provider **MUST** provide documentation describing VNF Functional Capabilities that are utilized to operationalize the VNF and compose complex services.
599 R-15671: The VNF **MUST NOT** provide public or unrestricted access to any data without the permission of the data owner. All data classification and access controls must be followed.
601 R-39342: The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "password changes (includes default passwords)" policy. Products will support password aging, syntax and other credential management practices on a configurable basis.
603 R-21558: The VNF **SHOULD** use intelligent routing by having knowledge of multiple downstream/upstream endpoints that are exposed to it, to ensure there is no dependency on external services (such as load balancers) to switch to alternate endpoints.
605 R-07545: The VNF **MUST** support all operations, administration and management (OAM) functions available from the supplier for VNFs using the supplied YANG code and associated NETCONF servers.
607 R-73541: The VNF **MIST** use access controls for VNFs and their supporting computing systems at all times to restrict access to authorized personnel only, e.g., least privilege. These controls could include the use of system configuration or access control software.
609 R-97102: The VNF Package **MUST** include VM requirements via a Heat template that provides the necessary data for:
611 R-44013: The VNF **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 VNF action requires the output of a chef-client run be made available (e.g., get running configuration).
613 R-40521: The VNF **MUST**, if not using the NCSP’s IDAM API, support use of common third party authentication and authorization tools such as TACACS+, RADIUS.
615 R-41829: The VNF **MUST** be able to specify the granularity of the lock via a restricted or full XPath expression.
617 R-19768: The VNF **SHOULD** support L3 VPNs that enable segregation of traffic by application (dropping packets not belonging to the VPN) (i.e., AVPN, IPSec VPN for Internet routes).
619 R-55478: The VNF **MUST** log logoffs.
621 R-14853: The VNF **MUST** respond to a "move traffic" [2]_ command against a specific VNFC, moving all existing session elsewhere with minimal disruption if a VNF provides a load balancing function across multiple instances of its VNFCs. Note: Individual VNF performance aspects (e.g., move duration or disruption scope) may require further constraints.
623 R-68165: The VNF **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.
625 R-31614: The VNF **MUST** log the field “event type” in the security audit logs.
627 R-87662: The VNF **SHOULD** implement the NETCONF Event Notifications [RFC5277].
629 R-26508: The VNF **MUST** support NETCONF server that can be mounted on OpenDaylight (client) and perform the following operations:
631 R-26567: The VNF Package **MUST** include a run list of roles/cookbooks/recipes, for each supported VNF action, that will perform the desired VNF action in its entirety as specified by ONAP (see Section 8.c, ONAP Controller APIs and Behavior, for list of VNF actions and requirements), when triggered by a chef-client run list in JSON file.
633 R-04158: The VNF **MUST** conform to the NETCONF RFC 4742, “Using the NETCONF Configuration Protocol over Secure Shell (SSH)”.
635 R-49109: The VNF **MUST** encrypt TCP/IP--HTTPS (e.g., TLS v1.2) transmission of data on internal and external networks.
637 R-15884: The VNF **MUST** include the field “date” in the Security alarms (where applicable and technically feasible).
639 R-15885: The VNF **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 VNF action, it should reflect this status on the Chef Server regardless of whether the Callback succeeded or not.
641 R-82223: The VNF **MUST** be decomposed if the functions have significantly different scaling characteristics (e.g., signaling versus media functions, control versus data plane functions).
643 R-37608: The VNF **MUST** provide a mechanism to restrict access based on the attributes of the VNF and the attributes of the subject.
645 R-02170: The VNF **MUST** use, whenever possible, standard implementations of security applications, protocols, and format, e.g., S/MIME, TLS, SSH, IPSec, X.509 digital certificates for cryptographic implementations. These implementations must be purchased from reputable vendors and must not be developed in-house.
647 R-11235: The VNF **MUST** implement the protocol operation: **kill-session(session)** - Force the termination of **session**.
649 R-87564: The VNF **SHOULD** conform its YANG model to RFC 7317, “A YANG Data Model for System Management”.
651 R-69649: The VNF **MUST** have all vulnerabilities patched as soon as possible. Patching shall be controlled via change control process with vulnerabilities disclosed along with mitigation recommendations.
653 R-75041: The VNF **MUST**, if not using the NCSP’s IDAM API, expire passwords at regular configurable intervals.
655 R-23035: The VNF **MUST** be designed to scale horizontally (more instances of a VNF or VNFC) and not vertically (moving the existing instances to larger VMs or increasing the resources within a VM) to achieve effective utilization of cloud resources.
657 R-97445: The VNF **MUST** log the field “date/time” in the security audit logs.
659 R-16777: The VNF provider **MUST** provide a JSON file for each supported action for the VNF. 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.
661 R-08134: The VNF **MUST** conform to the NETCONF RFC 6241, “NETCONF Configuration Protocol”.
663 R-01382: The VNF **MUST** allow the entire configuration of the VNF to be retrieved via NETCONF's <get-config> and <edit-config>, independently of whether it was configured via NETCONF or other mechanisms.
665 R-98929: The VNF **MAY** have a single endpoint.
667 R-48356: The VNF **MUST** fully exploit exception handling to the extent that resources (e.g., threads and memory) are released when no longer needed regardless of programming language.
669 R-90007: The VNF **MUST** implement the protocol operation: **close-session()**- Gracefully close the current session.
671 R-42140: The VNF **MUST** respond to data requests from ONAP as soon as those requests are received, as a synchronous response.
673 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.
675 R-05470: The VNF **MUST** host connectors for access to the database layer.
677 R-85633: The VNF **MUST** implement Data Storage Encryption (database/disk encryption) for Sensitive Personal Information (SPI) and other subscriber identifiable data. Note: subscriber’s SPI/data must be encrypted at rest, and other subscriber identifiable data should be encrypted at rest. Other data protection requirements exist and should be well understood by the developer.
679 R-36792: The VNF **MUST** automatically retry/resubmit failed requests made by the software to its downstream system to increase the success rate.
681 R-49036: The VNF **SHOULD** conform its YANG model to RFC 7277, “A YANG Data Model for IP Management”.
683 R-63217: The VNF **MUST**, if not using the NCSP’s IDAM API, support logging via ONAP for a historical view of “who did what and when”.
685 R-44125: The VNF 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.
687 R-22700: The VNF **MUST** conform its YANG model to RFC 6470, “NETCONF Base Notifications”.
689 R-74958: The VNF **MUST** activate security alarms automatically when the following event is detected: unsuccessful attempts to gain permissions or assume the identity of another user
691 R-44281: The VNF **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.
693 R-81777: The VNF **MUST** be configured with initial address(es) to use at deployment time. After that the address(es) may be changed through ONAP-defined policies delivered from ONAP to the VNF using PUTs to a RESTful API, in the same way that other controls over data reporting will be controlled by policy.
695 R-07879: The VNF Package **MUST** include all relevant playbooks to ONAP to be loaded on the Ansible Server.
697 R-57855: The VNF **MUST** support hitless staggered/rolling deployments between its redundant instances to allow "soak-time/burn in/slow roll" which can enable the support of low traffic loads to validate the deployment prior to supporting full traffic loads.
699 R-73285: The VNF **MUST** must encode the delivered data using JSON or Avro, addressed and delivered as described in the previous paragraphs.
701 R-85028: The VNF **MUST** authenticate system to system access and do not conceal a VNF provider user’s individual accountability for transactions.
703 R-28545: The VNF **MUST** conform its YANG model to RFC 6060, “YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)”
705 R-74712: The VNF **MUST** utilize FQDNs (and not IP address) for both Service Chaining and scaling.
707 R-29760: The VNFC **MUST** be installed on non-root file systems, unless software is specifically included with the operating system distribution of the guest image.
709 R-08315: The VNF **SHOULD** use redundant connection pooling to connect to any backend data source that can be switched between pools in an automated/scripted fashion to ensure high availability of the connection to the data source.
711 R-42874: The VNF **MUST** comply with Least Privilege (no more privilege than required to perform job functions) when persons or non-person entities access VNFs.
713 R-08312: The VNF **MAY** use other options which are expected to include
715 R-19082: The VNF **MUST NOT** run security testing tools and programs, e.g., password cracker, port scanners, hacking tools in production, without authorization of the VNF system owner.
717 R-39650: The VNF **SHOULD** provide the ability to test incremental growth of the VNF.
719 R-15325: The VNF **MUST** log the field “success/failure” in the security audit logs.
721 R-07617: The VNF **MUST** log creating, removing, or changing the inherent privilege level of users.
723 R-53015: The VNF **MUST** apply locking based on the sequence of NETCONF operations, with the first configuration operation locking out all others until completed.
725 R-83500: The VNF **MUST** provide the capability of allowing certificate renewal and revocation.
727 R-23772: The VNF **MUST** validate input at all layers implementing VNF APIs.
729 R-83227: The VNF **MUST** Provide the capability to encrypt data in transit on a physical or virtual network.
731 R-36843: The VNF **MUST** support the ability of the VNFC to be deployable in multi-zoned cloud sites to allow for site support in the event of cloud zone failure or upgrades.
733 R-10129: The VNF **SHOULD** conform its YANG model to RFC 7223, “A YANG Data Model for Interface Management”.
735 R-18733: The VNF **MUST** implement the protocol operation: **discard-changes()** - Revert the candidate configuration datastore to the running configuration.
737 R-21819: The VNF **MUST** support requests for information from law enforcement and government agencies.
739 R-92207: The VNF **SHOULD** implement a mechanism for automated and frequent "system configuration (automated provisioning / closed loop)" auditing.
741 R-63935: The VNF **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)
743 R-79224: The VNF **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.
745 R-12467: The VNF **MUST NOT** use the SHA, DSS, MD5, SHA-1 and Skipjack algorithms or other compromised encryption.
747 R-68589: The VNF **MUST**, if not using the NCSP’s IDAM API, support User-IDs and passwords to uniquely identify the user/application. VNF needs to have appropriate connectors to the Identity, Authentication and Authorization systems that enables access at OS, Database and Application levels as appropriate.
749 R-26115: The VNF **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.
751 R-49145: The VNF **MUST** implement **:confirmed-commit** If **:candidate** is supported.
753 R-04298: The VNF provider **MUST** provide their testing scripts to support testing.
755 R-92935: The VNF **SHOULD** minimize the propagation of state information across multiple data centers to avoid cross data center traffic.
757 R-47204: The VNF **MUST** protect the confidentiality and integrity of data at rest and in transit from unauthorized access and modification.
759 R-32695: The VNF **MUST** provide the ability to modify the number of retries, the time between retries and the behavior/action taken after the retries have been exhausted for exception handling to allow the NCSP to control that behavior.
761 R-58964: The VNF **MUST** provide the capability to restrict read and write access to data.
763 R-73364: The VNF **MUST** support at least two major versions of the VNF software and/or sub-components to co-exist within production environments at any time so that upgrades can be applied across multiple systems in a staggered manner.
765 R-33946: The VNF **MUST** conform to the NETCONF RFC 4741, “NETCONF Configuration Protocol”.
767 R-24269: The VNF **SHOULD** conform its YANG model to RFC 7407, “A YANG Data Model for SNMP Configuration”.
769 R-16039: The VNF **SHOULD** test for adherence to the defined resiliency rating recommendation at each layer, during each delivery cycle so that the resiliency rating is measured and feedback is provided where software resiliency requirements are not met.
771 R-46290: The VNF **MUST** respond to an ONAP request to deliver granular data on device or subsystem status or performance, referencing the YANG configuration model for the VNF by returning the requested data elements.
773 R-11240: The VNF **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.
775 R-83790: The VNF **MUST** implement the **:validate** capability
777 R-83873: The VNF **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 affected. This provides an 'all-or-nothing' edit mode for a single <edit-config> request.
779 R-25238: The VNF PACKAGE **MUST** validated YANG code using the open source pyang [3]_ program using the following commands:
781 R-58370: The VNF **MUST** coexist and operate normally with commercial anti-virus software which shall produce alarms every time when there is a security incident.
783 R-39604: The VNF **MUST** provide the capability of testing the validity of a digital certificate by checking the Certificate Revocation List (CRL) for the certificates of that type to ensure that the certificate has not been revoked.
785 R-06617: The VNF **MUST** support get-schema (ietf-netconf-monitoring) to pull YANG model over session.
787 R-13344: The VNF **MUST** log starting and stopping of security logging
789 R-02360: The VNFC **MUST** be designed as a standalone, executable process.
791 R-80070: The VNF **MUST** handle errors and exceptions so that they do not interrupt processing of incoming VNF requests to maintain service continuity.
793 R-02137: The VNF **MUST** implement all monitoring and logging as described in the Security Analytics section.
795 R-16496: The VNF **MUST** enable instantiating only the functionality that is needed for the decomposed VNF (e.g., if transcoding is not needed it should not be instantiated).
797 R-32217: The VNF **MUST** have routable FQDNs that are reachable via the Ansible Server for the endpoints (VMs) of a VNF on which playbooks will be executed. ONAP will initiate requests to the Ansible Server for invocation of playbooks against these end points [4]_.
799 R-47849: The VNF provider **MUST** support the metadata about licenses (and their applicable entitlements) as defined in this document for VNF software, and any license keys required to authorize use of the VNF software. This metadata will be used to facilitate onboarding the VNF 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.
801 R-85419: The VNF **SHOULD** use REST APIs exposed to Client Applications for the implementation of OAuth 2.0 Authorization Code Grant and Client Credentials Grant, as the standard interface for a VNF.
803 R-34660: The VNF **MUST** use the RESTCONF/NETCONF framework used by the ONAP configuration subsystem for synchronous communication.
805 R-88026: The VNF **MUST** include a NETCONF server enabling runtime configuration and lifecycle management capabilities.
807 R-48080: The VNF **SHOULD** support SCEP (Simple Certificate Enrollment Protocol).
809 R-43884: The VNF **MUST** integrate with external authentication and authorization services (e.g., IDAM).
811 R-70933: The VNF **MUST** provide the ability to migrate to newer versions of cryptographic algorithms and protocols with no impact.
813 R-48917: The VNF **MUST** monitor for and alert on (both sender and receiver) errant, running longer than expected and missing file transfers, so as to minimize the impact due to file transfer errors.
815 R-79107: The VNF **MUST**, if not using the NCSP’s IDAM API, enforce a configurable maximum number of Login attempts policy for the users. VNF provider must comply with "terminate idle sessions" policy. Interactive sessions must be terminated, or a secure, locking screensaver must be activated requiring authentication, after a configurable period of inactivity. The system-based inactivity timeout for the enterprise identity and access management system must also be configurable.
817 R-75850: The VNF **SHOULD** decouple persistent data from the VNFC and keep it in its own datastore that can be reached by all instances of the VNFC requiring the data.
819 R-46960: The VNF **MUST** utilize only the Guest OS versions that are supported by the NCSP’s Network Cloud. [5]_
821 R-21210: The VNF **MUST** implement the following input validation control: Validate that any input file has a correct and valid Multipurpose Internet Mail Extensions (MIME) type. Input files should be tested for spoofed MIME types.
823 R-23823: The VNF Package **MUST** include appropriate credentials so that ONAP can interact with the Chef Server.
825 R-24359: The VNF **MUST** provide the capability of testing the validity of a digital certificate by validating the date the certificate is being used is within the validity period for the certificate.
827 R-49224: The VNF **MUST** provide unique traceability of a transaction through its life cycle to ensure quick and efficient troubleshooting.
829 R-04982: The VNF **MUST NOT** include an authentication credential, e.g., password, in the security audit logs, even if encrypted.
831 R-74481: The VNF **MUST** NOT require the use of a dynamic routing protocol unless necessary to meet functional requirements.
833 R-98911: The VNF **MUST NOT** use any instance specific parameters for the VNF in roles/cookbooks/recipes invoked for a VNF action.
835 R-89571: The VNF **MUST** support and provide artifacts for configuration management using at least one of the following technologies:
837 R-87135: The VNF **MUST** comply with NIST standards and industry best practices for all implementations of cryptography.
839 R-04492: The VNF **MUST** generate security audit logs that must be sent to Security Analytics Tools for analysis.
841 R-02597: The VNF **MUST** implement the protocol operation: **lock(target)** - Lock the configuration datastore target.
843 R-13800: The VNF **MUST** conform to the NETCONF RFC 5277, “NETCONF Event Notification”.
845 R-64445: The VNF **MUST** support the ability of a requestor of the service to determine the version (and therefore capabilities) of the service so that Network Cloud Service Provider can understand the capabilities of the service.
847 R-64768: The VNF **MUST** limit the size of application data packets to no larger than 9000 bytes for SDN network-based tunneling when guest data packets are transported between tunnel endpoints that support guest logical networks.
849 R-75608: The VNF provider **MUST** provide playbooks to be loaded on the appropriate Ansible Server.
851 R-61354: The VNF **MUST** implement access control list for OA&M services (e.g., restricting access to certain ports or applications).
853 R-62468: The VNF **MUST** allow all configuration data shall to be edited through a NETCONF <edit-config> operation. Proprietary NETCONF RPCs that make configuration changes are not sufficient.
855 R-34552: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for OWASP Top 10.
857 R-29977: The VNF **MUST** provide the capability of testing the validity of a digital certificate by validating the CA signature on the certificate.
859 R-67709: The VNF **MUST** be designed, built and packaged to enable deployment across multiple fault zones (e.g., VNFCs deployed in different servers, racks, OpenStack regions, geographies) so that in the event of a planned/unplanned downtime of a fault zone, the overall operation/throughput of the VNF is maintained.
861 R-46567: The VNF Package **MUST** include configuration scripts for boot sequence and configuration.
863 R-55345: The VNF **SHOULD** use techniques such as “lazy loading” when initialization includes loading catalogues and/or lists which can grow over time, so that the VNF startup time does not grow at a rate proportional to that of the list.
865 R-88482: The VNF **SHOULD** use REST using HTTPS delivery of plain text JSON for moderate sized asynchronous data sets, and for high volume data sets when feasible.
867 R-56786: The VNF **MUST** implement “Closed Loop” automatic implementation (without human intervention) for Known Threats with detection rate in low false positives.
869 R-94525: The VNF **MUST** log connections to a network listener of the resource.
871 R-85428: The VNF **MUST** meet the same guidelines as Chef Server hosted by ONAP.
873 R-26371: The VNF **MUST** detect connectivity failure for inter VNFC instance and intra/inter VNF and re-establish connectivity automatically to maintain the VNF without manual intervention to provide service continuity.
875 R-35851: The VNF Package **MUST** include VNF topology that describes basic network and application connectivity internal and external to the VNF including Link type, KPIs, Bandwidth, latency, jitter, QoS (if applicable) for each interface.
877 R-29301: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for Password Attacks.
879 R-23957: The VNF **MUST** include the field “time” in the Security alarms (where applicable and technically feasible).
881 R-32636: The VNF **MUST** support API-based monitoring to take care of the scenarios where the control interfaces are not exposed, or are optimized and proprietary in nature.
883 R-39562: The VNF **MUST** disable unnecessary or vulnerable cgi-bin programs.
885 R-77334: The VNF **MUST** allow configurations and configuration parameters to be managed under version control to ensure consistent configuration deployment, traceability and rollback.
887 R-44723: The VNF **MUST** use symmetric keys of at least 112 bits in length.
889 R-86585: The VNFC **SHOULD** minimize the use of state within a VNFC to facilitate the movement of traffic from one instance to another.
891 R-18725: The VNF **MUST** handle the restart of a single VNFC instance without requiring all VNFC instances to be restarted.
893 R-53317: The VNF **MUST** conform its YANG model to RFC 6087, “Guidelines for Authors and Reviewers of YANG Data Model Documents”.
895 R-67114: The VNF **MUST** be installed with:
897 R-28168: The VNF **SHOULD** use an appropriately configured logging level that can be changed dynamically, so as to not cause performance degradation of the VNF due to excessive logging.
899 R-54930: The VNF **MUST** implement the following input validation control: Do not permit input that contains content or characters inappropriate to the input expected by the design. Inappropriate input, such as SQL insertions, may cause the system to execute undesirable and unauthorized transactions against the database or allow other inappropriate access to the internal network.
901 R-55830: The VNF **MUST** distribute all production code from NCSP internal sources only. No production code, libraries, OS images, etc. shall be distributed from publically accessible depots.
903 R-22367: The VNF **MUST** support detection of malformed packets due to software misconfiguration or software vulnerability.
905 R-93860: The VNF **MUST** provide the capability to integrate with an external encryption service.
907 R-09467: The VNF **MUST** utilize only NCSP standard compute flavors. [5]_
909 R-62170: The VNF **MUST** over-ride any default values for configurable parameters that can be set by ONAP in the roles, cookbooks and recipes.
911 R-41994: The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "No Self-Signed Certificates" policy. Self-signed certificates must be used for encryption only, using specified and approved encryption protocols such as LS 1.1 or higher or equivalent security protocols such as IPSec, AES.
913 R-nnnnn: The VNF MUST have a corresponding environment file for a Cinder Volume Module.
915 R-84160: The VNF **MUST** have security logging for VNFs and their OSs be active from initialization. Audit logging includes automatic routines to maintain activity records and cleanup programs to ensure the integrity of the audit/logging systems.
917 R-99656: The VNF **MUST** NOT terminate stable sessions if a VNFC instance fails.
919 R-80898: The VNF **MUST** support heartbeat via a <get> with null filter.
921 R-20974: The VNF **MUST** deploy the base module first, prior to the incremental modules.
923 R-69610: The VNF **MUST** provide the capability of using certificates issued from a Certificate Authority not provided by the VNF provider.
925 R-27310: The VNF Package **MUST** include all relevant Chef artifacts (roles/cookbooks/recipes) required to execute VNF actions requested by ONAP for loading on appropriate Chef Server.
927 R-98191: The VNF **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.
929 R-31412: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for XSS / CSRF.
931 R-58775: The VNF provider **MUST** provide software components that can be packaged with/near the VNF, if needed, to simulate any functions or systems that connect to the VNF system under test. This component is necessary only if the existing testing environment does not have the necessary simulators.
933 R-45496: The VNF **MUST** host connectors for access to the OS (Operating System) layer.
935 R-13151: The VNF **SHOULD** disable the paging of the data requiring encryption, if possible, where the encryption of non-transient data is required on a device for which the operating system performs paging to virtual memory. If not possible to disable the paging of the data requiring encryption, the virtual memory should be encrypted.
937 R-49308: The VNF **SHOULD** test for adherence to the defined resiliency rating recommendation at each layer, during each delivery cycle with delivered results, so that the resiliency rating is measured and the code is adjusted to meet software resiliency requirements.
939 R-74763: The VNF provider **MUST** provide an artifact per VNF that contains all of the VNF Event Records supported. The artifact should include reference to the specific release of the VNF 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>`__)
941 R-77786: The VNF Package **MUST** include all relevant cookbooks to be loaded on the ONAP Chef Server.
943 R-54373: The VNF **MUST** have Python >= 2.7 on the endpoint VM(s) of a VNF on which an Ansible playbook will be executed.
945 R-60106: The VNF **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 VNF supported schemas.
947 R-35305: The VNF **MUST** meet the same guidelines as the Ansible Server hosted by ONAP.
949 R-95864: The VNF **MUST** use commercial tools that comply with X.509 standards and produce x.509 compliant keys for public/private key generation.
951 R-23475: The VNF **SHOULD** utilize only NCSP provided Guest OS images. [5]_
953 R-64503: The VNF **MUST** provide minimum privileges for initial and default settings for new user accounts.
955 R-42681: The VNF **MUST** use the NCSP’s IDAM API or comply with the requirements if not using the NCSP’s IDAM API, for identification, authentication and access control of OA&M and other system level functions.
957 R-19219: The VNF **MUST** provide audit logs that include user ID, dates, times for log-on and log-off, and terminal location at minimum.
959 R-73067: The VNF **MUST** use industry standard cryptographic algorithms and standard modes of operations when implementing cryptography.
961 R-25878: The VNF **MUST** use certificates issued from publicly recognized Certificate Authorities (CA) for the authentication process where PKI-based authentication is used.
963 R-70266: The VNF **MUST** respond to an ONAP request to deliver the current data for any of the record types defined in Section 8.d “Data Model for Event Records” by returning the requested record, populated with the current field values. (Currently the defined record types include the common header record, technology independent records such as Fault, Heartbeat, State Change, Syslog, and technology specific records such as Mobile Flow, Signaling and Voice Quality records. Additional record types will be added in the future as they are standardized and become available.)
965 R-70496: The VNF **MUST** implement the protocol operation: **commit(confirmed, confirm-timeout)** - Commit candidate configuration datastore to the running configuration.
967 R-19624: The VNF **MUST** encode and serialize content delivered to ONAP using JSON (option 1). High-volume data is to be encoded and serialized using Avro, where Avro data format are described using JSON (option 2) [6]_.
969 R-25094: The VNF **MUST** perform data capture for security functions.
971 R-44032: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for Man in the Middle (MITM).
973 R-47068: The VNF **MAY** expose a single endpoint that is responsible for all functionality.
975 R-49396: The VNF **MUST** support each VNF action by invocation of **one** playbook [7]_. The playbook will be responsible for executing all necessary tasks (as well as calling other playbooks) to complete the request.
977 R-63953: The VNF **MUST** have the echo command return a zero value otherwise the validation has failed
979 R-56904: The VNF **MUST** interoperate with the ONAP (SDN) Controller so that it can dynamically modify the firewall rules, ACL rules, QoS rules, virtual routing and forwarding rules.
981 R-37929: The VNF **MUST** accept all necessary instance specific data from the environment or node object attributes for the VNF in roles/cookbooks/recipes invoked for a VNF action.
983 R-84366: The VNF Package **MUST** include documentation describing VNF Functional APIs that are utilized to build network and application services. This document describes the externally exposed functional inputs and outputs for the VNF, including interface format and protocols supported.
985 R-58421: The VNF **SHOULD** be decomposed into granular re-usable VNFCs.
987 R-27711: The VNF provider **MUST** provide an XML file that contains a list of VNF error codes, descriptions of the error, and possible causes/corrective action.
989 R-78282: The VNF **MUST** conform to the NETCONF RFC 6242, “Using the Network Configuration Protocol over Secure Shell”.
991 R-99766: The VNF **MUST** allow configurations and configuration parameters to be managed under version control to ensure the ability to rollback to a known valid configuration.
993 R-89010: The VNF **MUST** survive any single points of software failure internal to the VNF (e.g., in memory structures, JMS message queues).
995 R-77667: The VNF **MUST** test for adherence to the defined performance budget at each layer, during each delivery cycle so that the performance budget is measured and feedback is provided where the performance budget is not met.
997 R-21652: The VNF **MUST** implement the following input validation control: Check the size (length) of all input. Do not permit an amount of input so great that it would cause the VNF to fail. Where the input may be a file, the VNF API must enforce a size limit.
999 R-54190: The VNF **MUST** release locks to prevent permanent lock-outs when/if a session applying the lock is terminated (e.g., SSH session is terminated).
1001 R-12271: The VNF **SHOULD** conform its YANG model to RFC 7223, “IANA Interface Type YANG Module”.
1003 R-25547: The VNF **MUST** log the field “protocol” in the security audit logs.
1005 R-22286: The VNF **MUST** support Integration functionality via API/Syslog/SNMP to other functional modules in the network (e.g., PCRF, PCEF) that enable dynamic security control by blocking the malicious traffic or malicious end users
1007 R-16560: The VNF **MUST** conduct a resiliency impact assessment for all inter/intra-connectivity points in the VNF to provide an overall resiliency rating for the VNF to be incorporated into the software design and development of the VNF.
1009 R-99112: The VNF **MUST** provide the capability to restrict access to data to specific users.
1011 R-02997: The VNF **MUST** preserve their persistent data. Running VMs will not be backed up in the Network Cloud infrastructure.
1013 R-19367: The VNF **MUST** monitor API invocation patterns to detect anomalous access patterns that may represent fraudulent access or other types of attacks, or integrate with tools that implement anomaly and abuse detection.
1015 R-33981: The VNF **SHOULD** interoperate with various access control mechanisms for the Network Cloud execution environment (e.g., Hypervisors, containers).
1017 R-26881: The VNF provider **MUST** provide the binaries and images needed to instantiate the VNF (VNF and VNFC images).
1019 R-69565: The VNF Package **MUST** include documentation describing VNF Management APIs. The document must include information and tools for:
1021 R-92571: The VNF **MUST** provide operational instrumentation such as logging, so as to facilitate quick resolution of issues with the VNF to provide service continuity.
1023 R-77737: The VNF **MUST**
1025 R-29488: The VNF **MUST** implement the protocol operation: **get-config(source, filter)** - Retrieve a (filtered subset of a) configuration from the configuration datastore source.
1027 R-03070: The VNF **MUST**, by ONAP Policy, provide the ONAP addresses as data destinations for each VNF, and may be changed by Policy while the VNF is in operation. We expect the VNF 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.
1029 R-89800: The VNF **MUST NOT** require Hypervisor-level customization from the cloud provider.
1031 R-12110: The VNF **MUST NOT** use keys generated or derived from predictable functions or values, e.g., values considered predictable include user identity information, time of day, stored/transmitted data.
1033 R-03954: The VNF **MUST** survive any single points of failure within the Network Cloud (e.g., virtual NIC, VM, disk failure).
1035 R-98391: The VNF **MUST**, if not using the NCSP’s IDAM API, support Role-Based Access Control to permit/limit the user/application to performing specific activities.
1037 R-29967: The VNF **MUST** conform its YANG model to RFC 6022, “YANG module for NETCONF monitoring”.
1039 R-80335: The VNF **MUST** make visible a Warning Notices: A formal statement of resource intent, i.e., a warning notice, upon initial access to a VNF provider user who accesses private internal networks or Company computer resources, e.g., upon initial logon to an internal web site, system or application which requires authentication.
1041 R-48596: The VNF Package **MUST** include documentation describing the characteristics for the VNF reliability and high availability.
1043 R-49956: The VNF **MUST** pass all access to applications (Bearer, signaling and OA&M) through various security tools and platforms from ACLs, stateful firewalls and application layer gateways depending on manner of deployment. The application is expected to function (and in some cases, interwork) with these security tools.
1045 R-02616: The VNF **MUST** permit locking at the finest granularity if a VNF 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).
1047 R-15659: The VNF **MUST** restrict changing the criticality level of a system security alarm to administrator(s).
1049 R-96634: The VNF provider **MUST** describe scaling capabilities to manage scaling characteristics of the VNF.
1051 R-32641: The VNF **MUST** provide the capability to encrypt data on non-volatile memory.
1053 R-48470: The VNF **MUST** support Real-time detection and notification of security events.
1055 R-91681: The VNF **MUST** meet the ONAP Ansible Server API Interface requirements.
1057 R-41825: The VNF **MUST** activate security alarms automatically when the following event is detected: configurable number of consecutive unsuccessful login attempts
1059 R-52870: The VNF **MUST** provide a method of metrics gathering and analysis to evaluate the resiliency of the software from both a granular as well as a holistic standpoint. This includes, but is not limited to thread utilization, errors, timeouts, and retries.
1061 R-89474: The VNF **MUST** log the field “Login ID” in the security audit logs.
1063 R-13390: The VNF provider **MUST** provide cookbooks to be loaded on the appropriate Chef Server.
1065 R-24825: The VNF **MUST** provide Context awareness data (device, location, time, etc.) and be able to integrate with threat detection system.
1067 R-23882: The VNF **SHOULD** be scanned using both network scanning and application scanning security tools on all code, including underlying OS and related configuration. Scan reports shall be provided. Remediation roadmaps shall be made available for any findings.
1069 R-22946: The VNF **SHOULD** conform its YANG model to RFC 6536, “NETCONF Access Control Model”.
1071 R-89753: The VNF **MUST NOT** install or use systems, tools or utilities capable of capturing or logging data that was not created by them or sent specifically to them in production, without authorization of the VNF system owner.
1073 R-88899: The VNF **MUST** support simultaneous <commit> operations within the context of this locking requirements framework.
1075 R-96554: The VNF **MUST** implement the protocol operation: **unlock(target)** - Unlock the configuration datastore target.
1077 R-27995: The VNF **SHOULD** include control loop mechanisms to notify the consumer of the VNF of their exceeding SLA thresholds so the consumer is able to control its load against the VNF.
1079 R-31809: The VNF **MUST** support the HealthCheck RPC. The HealthCheck RPC, executes a VNF providor-defined VNF Healthcheck over the scope of the entire VNF (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 VNF is unable to run the HealthCheck, return a standard http error code and message.
1081 R-25401: The VNF **MUST** use asymmetric keys of at least 2048 bits in length.
1083 R-31961: The VNF **MUST** support integrated DPI/monitoring functionality as part of VNFs (e.g., PGW, MME).
1085 R-47597: The VNF **MUST** carry data in motion only over secure connections.
1087 R-43253: The VNF **MUST** use playbooks designed to allow Ansible Server to infer failure or success based on the “PLAY_RECAP” capability.
1089 R-23135: The VNF **MUST**, if not using the NCSP’s IDAM API, authenticate system to system communications were one system accesses the resources of another system, and must never conceal individual accountability.
1091 R-99730: The VNF **MUST** include the field “Login ID” in the Security alarms (where applicable and technically feasible).
1093 R-88199: The VNF **MUST** utilize virtualized, scalable open source database software that can meet the performance/latency requirements of the service for all datastores.
1095 R-08598: The VNF **MUST** log successful and unsuccessful changes to a privilege level.
1097 R-87352: The VNF **SHOULD** utilize Cloud health checks, when available from the Network Cloud, from inside the application through APIs to check the network connectivity, dropped packets rate, injection, and auto failover to alternate sites if needed.
1099 R-56920: The VNF **MUST** protect all security audit logs (including API, OS and application-generated logs), security audit software, data, and associated documentation from modification, or unauthorized viewing, by standard OS access control mechanisms, by sending to a remote system, or by encryption.
1101 R-35291: The VNF **MUST** support the ability to failover a VNFC automatically to other geographically redundant sites if not deployed active-active to increase the overall resiliency of the VNF.
1103 R-43332: The VNF **MUST** activate security alarms automatically when the following event is detected: successful modification of critical system or application files
1105 R-81147: The VNF **MUST** have greater restrictions for access and execution, such as up to 3 factors of authentication and restricted authorization, for commands affecting network services, such as commands relating to VNFs, must.
1107 R-60656: The VNF **MUST** support sub tree filtering.
1109 R-51883: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for Replay.
1111 R-66070: The VNF Package **MUST** include VNF Identification Data to uniquely identify the resource for a given VNF provider. The identification data must include: an identifier for the VNF, the name of the VNF as was given by the VNF provider, VNF description, VNF provider, and version.
1113 R-19804: The VNF **MUST** validate the CA signature on the certificate, ensure that the date is within the validity period of the certificate, check the Certificate Revocation List (CRL), and recognize the identity represented by the certificate where PKI-based authentication is used.
1115 R-06327: The VNF **MUST** respond to a "drain VNFC" [2]_ command against a specific VNFC, preventing new session from reaching the targeted VNFC, with no disruption to active sessions on the impacted VNFC, if a VNF provides a load balancing function across multiple instances of its VNFCs. This is used to support scenarios such as proactive maintenance with no user impact,
1117 R-85653: The VNF **MUST** provide metrics (e.g., number of sessions, number of subscribers, number of seats, etc.) to ONAP for tracking every license.
1119 R-63330: The VNF **MUST** detect when the security audit log storage medium is approaching capacity (configurable) and issue an alarm via SMS or equivalent as to allow time for proper actions to be taken to pre-empt loss of audit data.
1121 R-22645: The VNF **SHOULD** use commercial algorithms only when there are no applicable governmental standards for specific cryptographic functions, e.g., public key cryptography, message digests.
1123 R-22888: The VNF provider **MUST** provide documentation for the VNF Policy Description to manage the VNF runtime lifecycle. The document must include a description of how the policies (conditions and actions) are implemented in the VNF.
1125 R-78066: The VNF **MUST** support requests for information from law enforcement and government agencies.
1127 R-35144: The VNF **MUST**, if not using the NCSP’s IDAM API, comply with the NCSP’s credential management policy.
1129 R-85959: The VNF **SHOULD** automatically enable/disable added/removed sub-components or component so there is no manual intervention required.
1131 R-28756: The VNF **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.
1133 R-41252: The VNF **MUST** support the capability of online storage of security audit logs.
1135 R-77707: The VNF provider **MUST** include a Manifest File that contains a list of all the components in the VNF package.
1137 R-20860: The VNF **MUST** be agnostic to the underlying infrastructure (such as hardware, host OS, Hypervisor), any requirements should be provided as specification to be fulfilled by any hardware.
1139 R-01478: The VNF Package **MUST** include documentation describing all parameters that are available to monitor the VNF after instantiation (includes all counters, OIDs, PM data, KPIs, etc.) that must be collected for reporting purposes. The documentation must include a list of:
1141 R-22059: The VNF **MUST NOT** execute long running tasks (e.g., IO, database, network operations, service calls) in a critical section of code, so as to minimize blocking of other operations and increase concurrent throughput.
1143 R-30650: The VNF **MUST** utilize cloud provided infrastructure and VNFs (e.g., virtualized Local Load Balancer) as part of the VNF so that the cloud can manage and provide a consistent service resiliency and methods across all VNF's.
1145 R-30654: The VNF 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 VNF (e.g., configure).
1147 R-29705: The VNF **MUST** restrict changing the criticality level of a system security alarm to administrator(s).
1149 R-71787: The VNF **MUST** comply with Segregation of Duties (access to a single layer and no developer may access production without special oversight) when persons or non-person entities access VNFs.
1151 R-86758: The VNF **SHOULD** provide an automated test suite to validate every new version of the software on the target environment(s). The tests should be of sufficient granularity to independently test various representative VNF use cases throughout its lifecycle. Operations might choose to invoke these tests either on a scheduled basis or on demand to support various operations functions including test, turn-up and troubleshooting.
1153 R-06885: The VNF **SHOULD** support the ability to scale down a VNFC pool without jeopardizing active sessions. Ideally, an active session should not be tied to any particular VNFC instance.
1155 R-06924: The VNF **MUST** deliver asynchronous data as data becomes available, or according to the configured frequency.
1157 R-65134: The VNF **SHOULD** maintain state in a geographically redundant datastore that may, in fact, be its own VNFC.
1159 R-13627: The VNF **MUST** monitor API invocation patterns to detect anomalous access patterns that may represent fraudulent access or other types of attacks, or integrate with tools that implement anomaly and abuse detection.
1161 R-86455: The VNF **SHOULD** support hosting connectors for OS Level and Application Access.
1163 R-68990: The VNF **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.
1165 R-78010: The VNF **MUST** use the NCSP’s IDAM API for Identification, authentication and access control of customer or VNF application users.
1167 R-46986: The VNF **SHOULD** have source code scanned using scanning tools (e.g., Fortify) and provide reports.
1169 R-97293: The VNF provider **MUST NOT** require audits of Service Provider’s business.
1171 R-16065: The VNF provider **MUST** provide configurable parameters (if unable to conform to YANG model) including VNF attributes/parameters and valid values, dynamic attributes and cross parameter dependencies (e.g., customer provisioning data).
1173 R-34484: The VNF **SHOULD** create a single component VNF for VNFCs that can be used by other VNFs.
1175 R-30278: The VNF provider **MUST** provide a Resource/Device YANG model as a foundation for creating the YANG model for configuration. This will include VNF attributes/parameters and valid values/attributes configurable by policy.
1177 R-35401: The VNF **MUST** 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.
1179 R-68200: The VNF **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.
1181 R-41159: The VNF **MUST** deliver any and all functionality from any VNFC in the pool. The VNFC pool member should be transparent to the client. Upstream and downstream clients should only recognize the function being performed, not the member performing it.
1183 R-18864: The VNF **MUST** NOT use technologies that bypass virtualization layers (such as SR-IOV) unless approved by the NCSP (e.g., if necessary to meet functional or performance requirements).
1185 R-37028: The VNF **MUST** be composed of one “base” module.
1187 R-40827: The VNF provider **MUST** enumerate all of the open source licenses their VNF(s) incorporate.
1189 R-95950: The VNF **MUST** provide a NETCONF interface fully defined by supplied YANG models for the embedded NETCONF server.
1191 R-10716: The VNF **MUST** support parallel and simultaneous configuration of separate objects within itself.
1193 R-71842: The VNF **MUST** include the field “service or program used for access” in the Security alarms (where applicable and technically feasible).
1195 R-54430: The VNF **MUST** use the NCSP’s supported library and compute flavor that supports DPDK to optimize network efficiency if using DPDK. [5]_
1197 R-03465: The VNF **MUST** release locks to prevent permanent lock-outs when the corresponding <partial-unlock> operation succeeds.
1199 R-65755: The VNF **SHOULD** support callback URLs to return information to ONAP upon completion of the chef-client run for any chef-client run associated with a VNF action.
1201 R-11499: The VNF **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.
1203 R-95105: The VNF **MUST** host connectors for access to the application layer.
1205 R-77157: The VNF **MUST** conform to approved request, workflow authorization, and authorization provisioning requirements when creating privileged users.
1207 R-63473: The VNF **MUST** automatically advertise newly scaled components so there is no manual intervention required.
1209 R-13613: The VNF **MUST** provide clear measurements for licensing purposes to allow automated scale up/down by the management system.
1211 R-66793: The VNF **MUST** guarantee the VNF 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 VNF without locking either configuration method out).
1213 R-19790: The VNF **MUST NOT** include authentication credentials in security audit logs, even if encrypted.
1215 R-97529: The VNF **SHOULD** implement the protocol operation: **get-schema(identifier, version, format) -** Retrieve the YANG schema.
1217 R-84473: The VNF **MUST** enable DPDK in the guest OS for VNF’s requiring high packets/sec performance. High packet throughput is defined as greater than 500K packets/sec.
1219 R-54816: The VNF **MUST** support the storage of security audit logs for agreed period of time for forensic analysis.
1221 R-34957: The VNF **MUST** provide a method of metrics gathering for each layer's performance to identify/document variances in the allocations so they can be addressed.
1223 R-43958: The VNF Package **MUST** include documentation describing the tests that were conducted by the VNF provider and the test results.
1225 R-61648: The VNF **MUST** support event logging, formats, and delivery tools to provide the required degree of event data to ONAP
1227 R-18525: The VNF provider **MUST** provide a JSON file for each supported action for the VNF. 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.
1229 R-99174: The VNF **MUST** comply with Individual Accountability (each person must be assigned a unique ID) when persons or non-person entities access VNFs.
1231 R-99771: The VNF **MUST** provide all code/configuration files in a “Locked down” or hardened state or with documented recommendations for such hardening. All unnecessary services will be disabled. VNF provider default credentials, community strings and other such artifacts will be removed or disclosed so that they can be modified or removed during provisioning.
1233 R-58358: The VNF **MUST** implement the **:with-defaults** capability [RFC6243].
1235 R-78116: The VNF **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 VNF action.
1237 R-84879: The VNF **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 VNF. In this case, the network will promptly resolve connectivity problems caused by a collector or network failure transparently to the VNF.
1239 R-06413: The VNF **MUST** log the field “service or program used for access” in the security audit logs.
1241 R-51442: The VNF **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 VNF (e.g., configure).
1243 R-98989: The VNF **SHOULD** utilize resource pooling (threads, connections, etc.) within the VNF application so that resources are not being created and destroyed resulting in resource management overhead.
1245 R-58998: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for Malware (Key Logger).
1247 R-52499: The VNF **MUST** meet their own resiliency goals and not rely on the Network Cloud.
1249 R-43327: The VNF **SHOULD** use “Modeling JSON text with YANG”, https://trac.tools.ietf.org/id/draft-lhotka-netmod-yang-json-00.html, If YANG models need to be translated to and from JSON. YANG configuration and content can be represented via JSON, consistent with Avro, as described in “Encoding and Serialization” section.
1251 R-52060: The VNF **MUST** provide the capability to configure encryption algorithms or devices so that they comply with the laws of the jurisdiction in which there are plans to use data encryption.
1253 R-10353: The VNF **MUST** conform its YANG model to RFC 6244, “An Architecture for Network Management Using NETCONF and YANG”.
1255 R-26586: The VNF **SHOULD** support the ability to work with aliases (e.g., gateways, proxies) to protect and encapsulate resources.
1257 R-14025: The VNF **MUST** provide or support the Identity and Access Management (IDAM) based threat detection data for Session Hijacking.
1259 R-86835: The VNF **MUST** set the default settings for user access to sensitive commands and data to deny authorization.
1261 R-73583: The VNF **MUST** allow changes of configuration parameters to be consumed by the VNF without requiring the VNF or its sub-components to be bounced so that the VNF availability is not effected.
1263 R-73223: The VNF **MUST** support proactive monitoring to detect and report the attacks on resources so that the VNFs and associated VMs can be isolated, such as detection techniques for resource exhaustion, namely OS resource attacks, CPU attacks, consumption of kernel memory, local storage attacks.
1265 R-06668: The VNF **MUST** handle the start or restart of VNFC instances in any order with each VNFC instance establishing or re-establishing required connections or relationships with other VNFC instances and/or VNFs required to perform the VNF function/role without requiring VNFC instance(s) to be started/restarted in a particular order.
1267 R-41215: The VNF **MAY** have zero to many “incremental” modules.
1269 R-85991: The VNF provider **MUST** provide a universal license key per VNF to be used as needed by services (i.e., not tied to a VM instance) as the recommended solution. The VNF provider may provide pools of Unique VNF License Keys, where there is a unique key for each VNF instance as an alternate solution. Licensing issues should be resolved without interrupting in-service VNFs.
1271 R-52085: The VNF **MUST**, if not using the NCSP’s IDAM API, provide the ability to support Multi-Factor Authentication (e.g., 1st factor = Software token on device (RSA SecureID); 2nd factor = User Name+Password, etc.) for the users.
1273 R-29495: The VNF **MUST** support locking if a common object is being manipulated by two simultaneous NETCONF configuration operations on the same VNF 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).
1275 R-31751: The VNF **MUST** subject VNF provider VNF access to privilege reconciliation tools to prevent access creep and ensure correct enforcement of access policies.
1277 R-48698: The VNF **MUST** utilize information from key value pairs that will be provided by the Ansible Server as extra-vars during invocation to execute the desired VNF action. If the playbook requires files, they must also be supplied using the methodology detailed in the Ansible Server API.
1279 R-44290: The VNF **MUST** control access to ONAP and to VNFs, and creation of connections, through secure credentials, log-on and exchange mechanisms.
1281 R-40293: The VNF **MUST** make available (or load on VNF Ansible Server) playbooks that conform to the ONAP requirement.
1283 R-30932: The VNF **MUST** provide security audit logs including records of successful and rejected system access data and other resource access attempts.
1285 R-12538: The VNF **SHOULD** support load balancing and discovery mechanisms in resource pools containing VNFC instances.
1287 R-59610: The VNF **MUST** implement the data model discovery and download as defined in [RFC6022].
1289 R-49945: The VNF **MUST** authorize VNF provider access through a client application API by the client application owner and the resource owner of the VNF before provisioning authorization through Role Based Access Control (RBAC), Attribute Based Access Control (ABAC), or other policy based mechanism.
1291 R-20912: The VNF **MUST** support alternative monitoring capabilities when VNFs do not expose data or control traffic or use proprietary and optimized protocols for inter VNF communication.
1294 e. - Ansible Playbook Examples
1295 ==============================
1297 The following sections contain examples of Ansible playbook contents
1298 which follow the guidelines.
1300 Guidelines for Playbooks to properly integrate with APPC
1301 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1303 NOTE: To support concurrent requests to multiple VNF instances of same
1304 or different type, VNF hosts and other files with VNF specific default
1305 values are kept or created in separate directories.
1307 Example of an Ansible command (after pwd) to run playbook again
1308 vfdb9904v VNF instance:
1310 .. code-block:: none
1313 /storage/vfdb/V16.1/ansible/configure
1314 $ ansible-playbook -i ../inventory/vfdb9904v/hosts site.yml --extra-vars "vnf_instance=vfdb9904v"
1316 Example of corresponding APPC API Call from ONAP – Ansible Server
1319 An example POST for requesting execution of configure Playbook:
1321 .. code-block:: none
1323 {"Id": "10", "PlaybookName":
1324 "/storage/vfdb/latest/ansible/configure/site.yml", "NodeList":
1325 ["vfdb9904v"], "Timeout": 60, "EnvParameters": {"Retry": 3, "Wait": 5},
1326 "LocalParameters": {"vfdb9904v": {"T_true": 10, "T_false": 5,
1331 - An ID number is assigned to each request. This ID number is used to
1332 track request down to completion and provide status to APPC when
1335 - Playbook Name provided in the request (full path in this case)
1337 - Playbook path (in this example provided as part of playbook name as
1338 full path) or, later in a separate variable, playbook root directory
1339 needs to be part of APPC template.
1341 Ansible Playbooks will use the VNF instance name (passed using
1342 --extra-vars "vnf\_instance=vfdb9904v") to identify other default values
1343 to run the playbook(s) against the target VNF instance. Same example as
1346 .. code-block:: none
1348 $ ansible-playbook -i ../inventory/vfdb9904v/hosts site.yml --extra-vars "vnf_instance=vfdb9904v"
1350 SSH key info (name/path), used to authenticate with the VNF VMs, is one
1351 of the attributes stored in the Ansible Server inventory hosts file for
1352 the VNF instance and later will be passed down by APPC, in the inventory
1353 hosts file, to the Ansible Server as part of the request. Here hosts
1354 file to run ansible-playbook listed in this example above (IP addresses
1357 .. code-block:: none
1359 $ more ../inventory/vfdb9904v/hosts
1361 localhost ansible_connection=local
1364 1xx.2yy.zzz.109 ansible_ssh_private_key_file=/storage/.ssh/Kilo-SSH-Key.pem
1365 1xx.2yy.zzz.110 ansible_ssh_private_key_file=/storage/.ssh/Kilo-SSH-Key.pem
1368 1xx.2yy.zzz.105 ansible_ssh_private_key_file=/storage/.ssh/Kilo-SSH-Key.pem
1369 1xx.2yy.zzz.106 ansible_ssh_private_key_file=/storage/.ssh/Kilo-SSH-Key.pem
1371 NOTE: APPC requests to run Playbooks/Cookbooks are specific to a VNF,
1372 but could be more limited to one VM or one type of VM by the request
1373 parameters. Actions that may impact a site (LCP), a service, or an
1374 entire platform must be orchestrated by MSO in order to execute requests
1375 via APPC which then invoke VNF level playbooks. Playbooks that impact
1376 more than a single VNF are not the current focus of these guidelines.
1378 And here the scrubbed default arguments for this VNF instance:
1380 .. code-block:: none
1382 vnf_instance=vfdb9904v
1384 $ more ../vars/vfdb9904v/default_args.yml
1385 vnf_provider_network_network: d69fea03-xxx-yyy-zzz-nnnnnnnnnnnn
1386 vnf_provider_network_subnet: a07f6a3d-xxxx-yyy-zzz-ssssssssssss
1387 vm_config_oam_vnfc_name: vfdb9904vm001oam001
1388 vm_config_oam_hostname: vfdb9904vm001
1389 vm_config_oam_provider_ip_address: 1xx.2yy.zzz.109
1392 IMPORTANT: The APPC and default file attribute name for
1393 vm\_config\_oam\_vnfc\_name, as an example, is derived from vm\_config
1394 array structure (list) in the CSAR package ENV file, with dots replaced
1397 .. code-block:: none
1401 oam: {vnfc_name: {{ vm_config_oam_vnfc_name }}, hostname: {{
1402 vm_config_oam_hostname }}, provider_ip_address: {{
1403 vm_config_oam_provider_ip_address }
1409 Parameters like VNF names, VNFC names, OA&M IP addresses, after
1410 February, 2018 ONAP release, will be extracted from A&AI by APPC and
1411 then passed down to Ansible Server, as part of APPC request through REST
1412 API. In the meantime, these VNF instance specific required values, will
1413 be stored on VNF instance directory, default arguments file and will be
1414 used as defaults. For parameterized playbooks attribute-value pairs
1415 passed down by APPC to Ansible Server always take precedence over
1416 template or VNF instance specific defaults stored in defaults file(s).
1418 .. code-block:: none
1421 /storage/vfdb/latest/ansible
1423 $ more vars/vfdb9904v/default_args.yml
1425 vm_config_oam1_vnfc_name: vfdb9904vm001oam001
1426 vm_config_oam1_hostname: vfdb9904vm001
1427 vm_config_oam1_provider_ip_address: 1xx.2yy.zzz.109
1429 vm_config_oam2_vnfc_name: vfdb9904vm002oam001
1430 vm_config_oam2_hostname: vfdb9904vm002
1431 vm_config_oam2_provider_ip_address: 1xx.2yy.zzz.110
1433 vm_config_rdb1_vnfc_name: vfdb9904vm003rdb001
1434 vm_config_rdb1_hostname: vfdb9904vm003
1435 vm_config_rdb1_provider_ip_address: 1xx.2yy.zzz.105
1437 vm_config_rdb2_vnfc_name: vfdb9904vm004rdb001
1438 vm_config_rdb2_hostname: vfdb9904vm004
1439 vm_config_rdb2_provider_ip_address: 1xx.2yy.zzz.106
1441 vm_config_rdb3_vnfc_name: vfdb9904vm005rdb001
1442 vm_config_rdb3_hostname: vfdb9904vm005
1443 vm_config_rdb3_provider_ip_address: 1xx.2yy.zzz.xxx
1445 vm_config_rdb4_vnfc_name: vfdb9904vm006rdb001
1446 vm_config_rdb4_hostname: vfdb9904vm006
1447 vm_config_rdb4_provider_ip_address: 1xx.2yy.zzz.yyy
1449 One of the first tasks on the Ansible Playbooks is to combine the VNF
1450 type generic template, derived from ENV files in CSAR or other files,
1451 with these default values stored on the Ansible Server, together with
1452 the overriding parameters passed down from APPC, to create the VNF
1453 instance specific set of attribute-value pairs to be used for the run in
1454 YAML format. Here is an excerpt from such a file that should look
1455 somewhat similar to ENV files:
1457 .. code-block:: none
1459 $ more tmp/vfdb9904v/all.yml
1461 deployment_prefix: vfdb9904v
1463 oam1: { vnfc_name: vfdb9904vm001oam001, hostname: vfdb9904vm001, provider_ip_address: 1xx.2yy.zzz.109, private_ip_address: 192.168.10.107 }
1464 oam2: { vnfc_name: vfdb9904vm002oam001, hostname: vfdb9904vm002, provider_ip_address: 1xx.2yy.zzz.110, private_ip_address: 192.168.10.108 }
1465 rdb1: { vnfc_name: vfdb9904vm003rdb001, hostname: vfdb9904vm003, provider_ip_address: 1xx.2yy.zzz.105, private_ip_address: 192.168.10.109 }
1466 rdb2: { vnfc_name: vfdb9904vm004rdb001, hostname: vfdb9904vm004, provider_ip_address: 1xx.2yy.zzz.106, private_ip_address: 192.168.10.110 }
1467 rdb3: { vnfc_name: vfdb9904vm005rdb001, hostname: vfdb9904vm005, provider_ip_address: 1xx.2yy.zzz.xxx, private_ip_address: 192.168.10.111 }
1468 rdb4: { vnfc_name: vfdb9904vm006rdb001, hostname: vfdb9904vm006, provider_ip_address: 1xx.2yy.zzz.yyy, private_ip_address: 192.168.10.112 }
1472 template_version: '2014-10-16'
1473 stack_name: vfdb9904v
1474 key_name: ONAPkilo-keypair
1476 stackName: vfdb9904v
1480 # logins list contain 'login name', 'login group', 'login password'
1482 .. code-block:: none
1485 - { name: 'm99999', group: 'm99999', password: 'abcdefgha' }
1486 - { name: 'gsuser', group: 'gsuser', password: ' abcdefgha' }
1487 - { name: 'peruser', group: 'peruser', password: ' abcdefgha' }
1488 - { name: 'dbuser', group: 'dbuser', password: ' abcdefgha' }
1490 NOTE: Arguments passed by APPC to Ansible Server to run a playbook take
1491 precedence over any defaults stored in Ansible Server.
1493 Ansible Playbooks – Notes On Artifacts Required to Run Playbooks
1494 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1496 Inventory hosts file: should be VNF instance specific.
1498 Default variables: should be VNF instance specific/
1500 NOTE: Some playbooks may rely on inventory directory contents to target
1501 the collection of VNFs in the Services Platform supported through
1504 Playbooks and paths to referenced files: Playbooks shall not use
1505 absolute paths for file include entries (variables or playbooks) or
1506 other types of references.
1508 For this to work properly when running playbooks, the directory where
1509 the playbook resides shall be the current directory.
1511 Playbook includes use paths relative to the main playbook directory when
1514 Root directory named ansible - Any files provided with playbooks,
1515 included or referenced by playbooks, shall reside under the ansible
1516 playbooks (root) directory, containing all playbook subdirectories, or
1517 below that ansible root directory, in other subdirectories to support
1518 on-boarding and portability of VNF collection of playbooks and related
1521 Designing for a shared environment, concurrently running playbooks,
1522 targeting multiple VNF instances – inventory hosts file:
1524 To avoid inventory hosts file overwrites or collisions between multiple
1525 concurrently running VNF instance requests, chosen approach is for each
1526 VNF instance hosts file, to be stored under the Ansible Server Playbooks
1527 root directory, under the inventory subdirectory, and under a directory
1528 for each VNF instance, named after the VNF instance, as follows:
1530 ansible/inventory/<VNF\_instance\_name>/hosts
1532 Example of inventory hosts file path, relative to ansible playbooks root
1533 directory (playbooks\_dir): ansible/inventory/vnfx0001v/hosts
1535 Designing for a shared environment, concurrently running playbooks,
1536 targeting multiple VNF instances – default argument variables for
1537 specific VNF instances:
1539 Files containing attribute name value pairs (variable name and default
1540 values), referenced/included by playbooks – Files containing VNF
1541 instance specific default values – in a later APPC release, some or all
1542 the default attribute value pairs contained in the defaults file, may be
1543 passed down by APPC, to the Ansible Server, overriding these defaults:
1545 Following the same approach for inventory hosts files, files
1546 referenced/included by playbooks containing default values,
1547 default\_args.yml, shall be stored under a directory with VNF instance
1552 ansible/vars/<VNF\_instance\_name>/default\_args.yml
1554 Files containing attribute name value pairs (variable name and default
1555 values), referenced/included by playbooks – created dynamically by
1558 Following the same approach for inventory hosts files, to avoid
1559 overwrites or collisions of multiple concurrently running VNF instance
1560 requests, files created dynamically by playbooks, based on VNF generic
1561 templates, combined with default values and arguments passed down by
1562 APPC (as part of the request), shall be stored under a directory with
1563 VNF instance name on the path.
1567 tmp/<VNF\_instance\_name>/all.yml
1569 Files containing site specific (Openstack location non-instance
1570 specific) attribute name value pairs, like NTP server and DNS server’s
1571 IP addresses and other parameters, referenced/included by playbooks, not
1572 VNF specific – Could/should be stored under vars directory, in a
1573 subdirectory named after the string used to identify the site (nyc1,
1578 ansible/vars/<Site>/default\_args.yml
1580 ansible/vars/nyc1/default\_args.yml
1582 ansible/vars/lax2/default\_args.yml
1584 \ **Ansible Server Design - Directory Structure**
1586 To help understanding the contents of this section, here are few basic
1589 **VNF type a.k.a VNF Function Code** - Based on current Services
1590 Platform naming convention, each Virtual Network Function is assigned a
1591 4 character string (example vfdb), they are the first 4 characters on
1592 the VNF instance name, which is 9 characters long. VNF instance name in
1593 some cases corresponds to the stack name for the VNF when VNF instance
1594 is built based on a single module, single stack. Example of VNF instance
1595 name: vfdb9904v. All VNF performing this function, running the same
1596 software, coming from the same VNF provider will start with the same 4
1597 characters, in this example, vfdb.
1599 VNF type, determined through these 4 characters, is also known as VNF
1600 Function Code and is assigned by inventory team. All Services Platform
1601 VNF Function Codes can be found in inventory database and/or A&AI as
1602 well as Services Platform Network Design Documents.
1604 NOTE: Current Services Platform naming convention is undergoing changes
1605 to include geographical location to the VNF names.
1607 Version – As in VNF software version is the release of the software
1608 running on the VNF for which the playbooks were developed. VNF
1609 configuration steps may change from release to release and this
1610 <Version> in the path will allow the Ansible Server to host playbooks
1611 associated with each software release. And run the playbooks that match
1612 the software release running on each VNF instance. APPC initially will
1613 not support playbook versioning only latest playbook is supported.
1615 Playbook Function - Is a name associated with a life cycle management
1616 task(s) performed by the playbook(s) stored in this directory. It should
1617 clearly identify the type of action(s) performed by the main playbook
1618 and possibly other playbooks stored in this same directory. Ideally,
1619 playbook function would match APPC corresponding function that executes
1620 the main playbook in this directory. Following Ansible Naming standards
1621 main playbook is usually named site.yml. There can be other playbooks on
1622 the same directory that use a subset of the roles used by the main
1623 playbook site.yml. Examples of Playbook Function directory names:
1625 - configure – Contains post-instantiation (bulk) configuration
1628 - healthcheck – Contains VNF health check playbook(s), roles,…
1630 - stop – Contains VNF application stop playbook(s), roles,…
1632 - start – Contains VNF application start playbook(s), roles,…
1634 Directory structure to allow hosting multiple version sets of playbooks,
1635 for the same VNF type, to be hosted in the runtime environment on the
1636 Ansible Servers. Generic directory structure:
1638 Ansible Playbooks – Function directory and main playbook:
1640 .. code-block:: none
1642 /storage/<VNF type>/<Version>/ansible/<Playbook Function>/site.yml
1644 Example – Post-instantiation (bulk) configuration –APPC Function -
1647 .. code-block:: none
1649 /storage/<VNF type>/<Version>/ansible/configure/site.yml
1651 Example – Health-check –APPC Function - HealthCheck:
1653 .. code-block:: none
1655 /storage/<VNF type>/<Version>/ansible/healthcheck/site.yml
1657 OR (Function directory name does not need to match APPC function name)
1659 .. code-block:: none
1661 /storage/<VNF type>/<Version>/ansible/check/site.yml
1663 Ansible Directories for other artifacts – VNF inventory hosts file -
1666 .. code-block:: none
1668 /storage/<VNF type>/<Version>/ansible/inventory/<VNF instance name>/hosts
1670 Ansible Directories for other artifacts – VNF inventory hosts file –
1673 .. code-block:: none
1675 /storage/<VNF type>/<Version>/ansible/vars/<VNF instance name>/default\_args.yml
1677 NOTE: This requirement is expected to be deprecated in part in the
1678 future, for automated actions, once APPC can pass down all VNF specific
1679 arguments for each action. Requirement remains while manual actions are
1680 to be supported. Other automated inventory management mechanisms may be
1681 considered in the future, Ansible supports many automated inventory
1682 management mechanisms/tools/solutions.
1684 Ansible Directories for other artifacts – VNF (special) groups –
1687 .. code-block:: none
1689 /storage/<VNF type>/<Version>/ansible/groups/<VNF instance name>/common\_groups.yml
1691 NOTE: Default groups will be created based on VNFC type, 3 characters,
1692 on VNFC name. Example: “oam”, “rdb”, “dbs”, “man”, “iox”, “app”,…
1694 Ansible Directories for other artifacts – VNF (special) other files –
1695 Optional – Example – License file:
1697 .. code-block:: none
1699 /storage/<VNF type>/<Version>/ansible/<Other directory(s)>
1701 CAUTION: On referenced files used/required by playbooks.
1703 - To avoid missing files, during on-boarding or uploading of Ansible
1704 Playbooks and related artifacts, all permanent files (not generated
1705 by playbooks as part of execution), required to run any playbook,
1706 shall reside under the ansible root directory or below on other
1709 - Any references to files, on includes or other playbook entries, shall
1712 - This is the ansible (root directory) directory referenced on this
1715 .. code-block:: none
1717 /storage/<VNF type>/<Version>/ansible/
1719 There will be a soft link to the latest set of Ansible Playbooks for
1720 each VNF type and this is the default set of playbooks that are executed
1721 unless a different release is specified in APPC request.
1723 VNF type directories use A&AI inventory VNF function code. Ansible
1724 Playbooks will be stored on a Cinder Volume mounted on the Ansible
1725 Servers as /storage. Example:
1727 /storage/vfdb/latest/ansible – This soft link point to the latest set of
1728 playbooks (or the only set)
1730 /storage/vfdb/V16.1/ansible – Root directory for database VNF Ansible
1731 Playbooks for release 16.1
1733 CAUTION: To support this directory structure as the repository to store
1734 Ansible Playbooks run by APPC, APPC API in the Ansible Server side needs
1735 to be configured to run playbooks from directory, not MySQL database.
1737 Ansible Server HTTP will be configured to support APPC REST API requests
1738 to run playbooks as needed, against specific VNF instances, or specific
1739 VM(s) as specified in the request.
1741 ONAP APPC REST API to Ansible Server is documented separately and can be
1742 found under ONAP (onap.org).
1744 \ **Ansible Server – On-boarding Ansible Playbooks **
1746 Once playbooks are developed following the guidelines listed in prior
1747 section(s), playbooks need to be on-boarded onto Ansible Server(s). In
1748 the future, they’ll be on-boarded and distributed through ONAP, at least
1749 that is the proposed plan, but for now they need to be uploaded
1752 These are the basic steps to on-board playbooks manually onto the
1755 1. Upload CSAR, zip, or tar file containing VNF playbooks and related
1758 2. Create full directory (using –p option below) to store Ansible
1759 Playbooks and other artifacts under /storage file system.
1761 a. Includes VNF type using VNF function code 4 characters under
1764 b. Includes VNF “Version” directory as part of the path to store
1765 playbooks for this VNF version.
1767 c. Include generic ansible root directory. Creating full directory
1770 .. code-block:: none
1772 $ mkdir –p /storage/vfdb/V16.1/ansible**/**
1774 3. Make this directory (VNF ansible root directory) current directory
1777 .. code-block:: none
1779 cd /storage/vfdb/V16.1/ansible/
1781 4. Extract Ansible Playbooks and other Ansible artifacts associated with
1782 the playbooks onto the ansible directory. Command depends on the type
1783 of file uploaded, examples would be:
1785 .. code-block:: none
1791 5. Create directory for VNF (VMs) inventory hosts file with all VMs and
1792 OA&M IP addresses for all VNF instances with known OA&M IP addresses
1793 for respective VMs, example:
1795 .. code-block:: none
1797 $ mkdir –p inventory/vfdb9904v
1799 $ touch inventory/vfdb9904v/hosts
1801 $ cat inventory/vfdb9904v/hosts
1804 localhost ansible\_connection=local
1807 1xx.2yy.zzz.109 ansible\_ssh\_private\_key\_file=/storage/.ssh/Kilo-SSH-Key.pem
1808 1xx.2yy.zzz.110 ansible\_ssh\_private\_key\_file=/storage/.ssh/Kilo-SSH-Key.pem
1811 1xx.2yy.zzz.105 ansible\_ssh\_private\_key\_file=/storage/.ssh/Kilo-SSH-Key.pem
1812 1xx.2yy.zzz.106 ansible\_ssh\_private\_key\_file=/storage/.ssh/Kilo-SSH-Key.pem
1814 6. Create directory to hold default arguments for each VNF instance,
1817 .. code-block:: none
1819 $ mkdir –p vars/vfdb9904v
1820 $ touch vars/vfdb9904v/default\_args.yml
1821 $ cat vars/vfdb9904v/default\_args.yml
1822 vm\_config\_oam1\_vnfc\_name: vfdb9904vm001oam001
1823 vm\_config\_oam1\_hostname: vfdb9904vm001
1824 vm\_config\_oam1\_provider\_ip\_address: 1xx.2yy.zzz.109
1826 vm\_config\_oam2\_vnfc\_name: vfdb9904vm002oam001
1827 vm\_config\_oam2\_hostname: vfdb9904vm002
1828 vm\_config\_oam2\_provider\_ip\_address: 1xx.2yy.zzz.110
1830 vm\_config\_rdb1\_vnfc\_name: vfdb9904vm003rdb001
1831 vm\_config\_rdb1\_hostname: vfdb9904vm003
1832 vm\_config\_rdb1\_provider\_ip\_address: 1xx.2yy.zzz.105
1834 vm\_config\_rdb2\_vnfc\_name: vfdb9904vm004rdb001
1835 vm\_config\_rdb2\_hostname: vfdb9904vm004
1836 vm\_config\_rdb2\_provider\_ip\_address: 1xx.2yy.zzz.106
1838 vm\_config\_rdb3\_vnfc\_name: vfdb9904vm005rdb001
1839 vm\_config\_rdb3\_hostname: vfdb9904vm005
1840 vm\_config\_rdb3\_provider\_ip\_address: 1xx.2yy.zzz.xxx
1842 vm\_config\_rdb4\_vnfc\_name: vfdb9904vm006rdb001
1843 vm\_config\_rdb4\_hostname: vfdb9904vm006
1844 vm\_config\_rdb4\_provider\_ip\_address: 1xx.2yy.zzz.yyy
1846 NOTE: Please note names in this file shall use underscore “\_” not dots
1849 7. Perform some basic playbook validation running with “--check” option,
1850 running dummy playbooks or other.
1852 8. Upload any SSH keys referenced on hosts file to appropriate
1855 NOTE: HOT templates used by Heat to instantiate VNF configured by these
1856 playbooks shall include the same SSH key to be installed as part of
1859 Other non-VNF provider specific playbook tasks need to be incorporated on
1860 overall post-instantiation configuration playbooks or company Playbooks
1861 need to be uploaded and executed after VNF provided or internally
1862 developed playbooks for the VNF.
1866 The “name” field is a mandatory field in a valid Chef Node Object
1870 Not currently supported in ONAP release 1
1873 https://github.com/mbj4668/pyang
1876 Upstream elements must provide the appropriate FQDN in the request to
1877 ONAP for the desired action.
1880 Refer to NCSP’s Network Cloud specification
1883 This option is not currently supported in ONAP and it is currently
1884 under consideration.
1887 Multiple ONAP actions may map to one playbook.
Code Review / vnfrqts / requirements.git / blob