VNFRQTS - Needs update 2/3

[vnfrqts/requirements.git] / docs / data / needs.json

diff --git a/docs/data/needs.json b/docs/data/needs.json
index de5f038..c5493e4 100644 (file)
--- a/docs/data/needs.json
+++ b/docs/data/needs.json
@@ -1,5 +1,5 @@
 {
-    "created": "2018-11-27T18:42:30.067398",
+    "created": "2018-12-03T10:32:05.973553",
     "current_version": "dublin",
     "project": "",
     "versions": {
@@ -45910,7 +45910,7 @@
             "needs_amount": 789
         },
         "dublin": {
-            "created": "2018-11-27T18:42:30.067379",
+            "created": "2018-12-03T10:32:05.973520",
             "needs": {
                 "R-00011": {
                     "description": "A VNF's Heat Orchestration Template's parameter defined\nin a nested YAML file\n**MUST NOT** have a parameter constraint defined.",
@@ -46338,8 +46338,8 @@
                     "validation_mode": ""
                 },
                 "R-01427": {
-                    "description": "The PNF **MUST** support the provisioning of security and authentication\nparameters (HTTP username and password) in order to be able to authenticate\nwith DCAE (in ONAP).\n\nNote: In R3, a username and password are used with the DCAE VES Event\nListener which are used for HTTP Basic Authentication.\n\nNote: The configuration management and provisioning software are specific\nto a vendor architecture.",
-                    "docname": "Chapter7/PNF-Plug-and-Play",
+                    "description": "The xNF **MUST** support the provisioning of security and authentication\nparameters (HTTP username and password) in order to be able to authenticate\nwith DCAE (in ONAP).\n\nNote: In R3, a username and password are used with the DCAE VES Event\nListener which are used for HTTP Basic Authentication.\n\nNote: The configuration management and provisioning software are specific\nto a vendor architecture.",
+                    "docname": "Chapter7/Monitoring-And-Management",
                     "full_title": "",
                     "hide_links": "",
                     "id": "R-01427",
@@ -46351,21 +46351,22 @@
                     "links": [],
                     "notes": "",
                     "parts": {},
-                    "section_name": "PNF Plug and Play",
+                    "section_name": "Security",
                     "sections": [
-                        "PNF Plug and Play",
-                        "PNF Plug and Play"
+                        "Security",
+                        "Monitoring & Management Requirements",
+                        "Monitoring & Management"
                     ],
                     "status": null,
                     "tags": [],
-                    "target": "PNF",
+                    "target": "XNF",
                     "test": "",
                     "test_case": "",
                     "test_file": "",
                     "title": "",
                     "title_from_content": "",
                     "type_name": "Requirement",
-                    "updated": "",
+                    "updated": "dublin",
                     "validated_by": "",
                     "validation_mode": ""
                 },
@@ -52154,7 +52155,7 @@
                     "validation_mode": ""
                 },
                 "R-256347": {
-                    "description": "The PNF **MUST** support the Ansible protocol for a Service Configuration\nmessage exchange between the PNF and PNF Controller (in ONAP).\n\nNote: this exchange may be either Ansible, Chef, or NetConf depending on\nthe PNF. Note: The PNF Controller may be VF-C, APP-C or SDN-C based on the\nPNF and PNF domain. Note: for R3 (Casablanca) only Ansible is supported.",
+                    "description": "The PNF **MUST** support one of the protocols for a Service Configuration\nmessage exchange between the PNF and PNF Controller (in ONAP):\na) Netconf/YANG, b) Chef, or c) Ansible.\n\nNote: The PNF Controller may be VF-C, APP-C or SDN-C based on the\nPNF and PNF domain.",
                     "docname": "Chapter7/PNF-Plug-and-Play",
                     "full_title": "",
                     "hide_links": "",
@@ -68455,8 +68456,8 @@
                     "validation_mode": ""
                 },
                 "R-894004": {
-                    "description": "When the PNF sets up a HTTP or HTTPS connection, it **MUST** provide a\nusername and password to the DCAE VES Collector for HTTP Basic\nAuthentication.\n\nNote: HTTP Basic Authentication has 4 steps: Request, Authenticate,\nAuthorization with Username/Password Credentials, and Authentication Status\nas per RFC7617 and RFC 2617.",
-                    "docname": "Chapter7/PNF-Plug-and-Play",
+                    "description": "When the xNF sets up a HTTP or HTTPS connection to the collector, it **MUST**\nprovide a username and password to the DCAE VES Collector for HTTP Basic\nAuthentication.\n\nNote: HTTP Basic Authentication has 4 steps: Request, Authenticate,\nAuthorization with Username/Password Credentials, and Authentication Status\nas per RFC7617 and RFC 2617.",
+                    "docname": "Chapter7/Monitoring-And-Management",
                     "full_title": "",
                     "hide_links": "",
                     "id": "R-894004",
@@ -68468,21 +68469,22 @@
                     "links": [],
                     "notes": "",
                     "parts": {},
-                    "section_name": "PNF Plug and Play",
+                    "section_name": "Security",
                     "sections": [
-                        "PNF Plug and Play",
-                        "PNF Plug and Play"
+                        "Security",
+                        "Monitoring & Management Requirements",
+                        "Monitoring & Management"
                     ],
                     "status": null,
                     "tags": [],
-                    "target": "PNF",
+                    "target": "XNF",
                     "test": "",
                     "test_case": "",
                     "test_file": "",
                     "title": "",
                     "title_from_content": "",
                     "type_name": "Requirement",
-                    "updated": "",
+                    "updated": "dublin",
                     "validated_by": "",
                     "validation_mode": ""
                 },