2 "description": "This is Netconf Transaction Configuration Component API",
\r
6 "type": "tosca.capabilities.Node"
\r
10 "netconf-connection": {
\r
11 "capability": "netconf",
\r
12 "node": "vnf-netconf-device",
\r
13 "relationship": "tosca.relationships.ConnectsTo"
\r
17 "org-openecomp-sdnc-netconf-adaptor-service-NetconfExecutorNode": {
\r
22 "description": "Request Id used to store the generated configuration, in the database along with the template-name",
\r
26 "service-template-name": {
\r
27 "description": "Service Template Name",
\r
31 "service-template-version": {
\r
32 "description": "Service Template Version",
\r
37 "description": "Action Name to get from Database, Either (message & mask-info ) or ( resource-id & resource-type & action-name & template-name ) should be present. Message will be given higest priority",
\r
42 "description": "Resource Type to get from Database, Either (message & mask-info ) or( resource-id & resource-type & action-name & template-name ) should be present. Message will be given higest priority",
\r
47 "description": "Resource Id to get from Database, Either (message & mask-info ) or ( resource-id & resource-type & action-name & template-name ) should be present. Message will be given higest priority",
\r
52 "description": "Reservation Id used to send to NPM",
\r
56 "execution-script": {
\r
57 "description": "Python Script to Execute for this Component action, It should refer any one of Prython Artifact Definition for this Node Template.",
\r
64 "description": "Execution Response Data in JSON format.",
\r
69 "description": "Status of the Component Execution ( success or failure )",
\r
78 "derived_from": "tosca.nodes.Component"
\r