*WIP*: draft of a blueprint for configuring a PNF

This is a still-in-development draft of a blueprint, intended to be
used to configure PNFs. It has been put in review as requested, to make
easier for the community to make comments on it.

The design considers that a blueprint will be created for each possible
PNF.

In some files, there are questions about the structure or content. The-
se questions are surrounded by HTML comment tags <!-- -->, even if the
file itself is not HTML - the intent is just to clearly highlight the
questions. All of them are preceded by the string "QUESTION", to facil-
itate search.

Change-Id: Ib3ed2afb80693429dc23b7ac73c5cbe49b3f5c9a
Issue-ID: CCSDK-1107
Signed-off-by: Rodrigo Ottero <rodrigo.ottero@est.tech>

5 files changed, 88 insertions, 0 deletions

diff --git a/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/config-assign-pnf-mapping.json b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/config-assign-pnf-mapping.json
new file mode 100644
index 000000000..85533abc5
--- /dev/null
+++ b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/config-assign-pnf-mapping.json
@@ -0,0 +1,16 @@
+<!-- QUESTION:
+     when using dictionary-source as capability, what else needs to be defined?
+     because odl_host will come from the application.properties entry -->
+[
+  {
+    "name": "odl_host",
+    "input-param": true,
+    "property": {
+      "type": "string"
+    },
+    "dictionary-name": "odl_host",
+    "dictionary-source": "capability",
+    "dependencies": [
+    ]
+  }
+]
diff --git a/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/config-assign-restconf-configlet-template.vtl b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/config-assign-restconf-configlet-template.vtl
new file mode 100644
index 000000000..e3d7a6716
--- /dev/null
+++ b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/config-assign-restconf-configlet-template.vtl
@@ -0,0 +1,19 @@
+<yang-patch xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-patch">
+<patch-id>example-patch</patch-id>
+<comment>Example patch</comment>
+<edit>
+  <edit-id>edit1</edit-id>
+  <operation>create</operation>
+  <target>/car-entry</target>
+  <value>
+    <car-entry xmlns="urn:opendaylight:params:xml:ns:yang:controller:config:sal-clustering-it:car">
+      <id>0</id>
+    </car-entry>
+  </value>
+</edit>
+<edit>
+  <edit-id>edit2</edit-id>
+  <operation>delete</operation>
+  <target>/car-entry/0</target>
+</edit>
+</yang-patch>
diff --git a/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-pnf-mapping.json b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-pnf-mapping.json
new file mode 100644
index 000000000..123680c0c
--- /dev/null
+++ b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-pnf-mapping.json
@@ -0,0 +1,38 @@
+<!-- QUESTION:
+     when using dictionary-source as capability, what else needs to be defined?
+     because these variables will be obtained based on the pnf_id -->
+[
+  {
+    "name": "pnf_id",
+    "input-param": true,
+    "property": {
+      "type": "string"
+    },
+    "dictionary-name": "pnf_id",
+    "dictionary-source": "capability",
+    "dependencies": [
+    ]
+  },
+  {
+    "name": "pnf_ip",
+    "input-param": true,
+    "property": {
+      "type": "string"
+    },
+    "dictionary-name": "pnf_ip",
+    "dictionary-source": "capability",
+    "dependencies": [
+    ]
+  },
+  {
+    "name": "pnf_ip_port",
+    "input-param": true,
+    "property": {
+      "type": "string"
+    },
+    "dictionary-name": "pnf_ip_port",
+    "dictionary-source": "capability",
+    "dependencies": [
+    ]
+  }
+]
diff --git a/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-restconf-mount-template.vtl b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-restconf-mount-template.vtl
new file mode 100644
index 000000000..17f7a3679
--- /dev/null
+++ b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-restconf-mount-template.vtl
@@ -0,0 +1,14 @@
+<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
+    <node-id>$pnf_id</node-id>
+    <key-based xmlns="urn:opendaylight:netconf-node-topology">
+        <key-id xmlns="urn:opendaylight:netconf-node-topology">ODL-private-key</key-id>
+        <username xmlns="urn:opendaylight:netconf-node-topology">netconf</username>
+     </key-based>
+    <host xmlns="urn:opendaylight:netconf-node-topology">$pnf_ip</host>
+    <port xmlns="urn:opendaylight:netconf-node-topology">$pnf_ip_port</port>
+    <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
+ 	<protocol xmlns="urn:opendaylight:netconf-node-topology">
+        <name xmlns="urn:opendaylight:netconf-node-topology">TLS</name>
+    </protocol>
+    <max-connection-attempts xmlns="urn:opendaylight:netconf-node-topology">2</max-connection-attempts>
+</node>
diff --git a/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-restconf-unmount-template.vtl b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-restconf-unmount-template.vtl
new file mode 100644
index 000000000..a0990367e
--- /dev/null
+++ b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Templates/configure-restconf-unmount-template.vtl
@@ -0,0 +1 @@
+TBD