Data provider release

Change-Id: Ia041a07152e8dabd87de05992d3670cbdc1ddaae
Issue-ID: INT-2010
Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl>

13 files changed, 235 insertions, 0 deletions

diff --git a/samples/BASIC_VM_enriched.zip b/samples/BASIC_VM_enriched.zip
new file mode 100644
index 0000000..28c14bb
--- /dev/null
+++ b/samples/BASIC_VM_enriched.zip
diff --git a/samples/README.md b/samples/README.md
new file mode 100644
index 0000000..bf62051
--- /dev/null
+++ b/samples/README.md
@@ -0,0 +1,29 @@
+# Data provider infra file samples
+
+## vendor.yaml
+
+Creates vendor
+
+## vsp.yaml
+
+Creates vendor and two vsps. Shows YAML anchor usage example.
+
+## xnfs.yaml
+
+Creates PNFs and VNFs
+
+## service.yaml
+
+Creates and distribute SDC service
+
+## complex.yaml
+
+Creates Complex
+
+## cloud-region.yaml
+
+Creates cloud region and register it in multicloud (all data \[like tenants] from OpenStack are going to be created by ONAP)
+
+## customer.yaml
+
+Creates customer with subscribed service
diff --git a/samples/aai_business.yaml b/samples/aai_business.yaml
new file mode 100644
index 0000000..65a70bd
--- /dev/null
+++ b/samples/aai_business.yaml
@@ -0,0 +1,17 @@
+# A&AI business sample
+# Creates one owning entity, project, platform and line of business
+#
+odpSchemaVersion: 1.0
+resources:
+  owning_entities:
+    - owning-entity:
+        name: oran_owner
+  projects:
+    - project:
+        name: oran_town
+  platforms:
+    - platform:
+        name: oran_platform
+  lines-of-business:
+    - line-of-business:
+        name: oran_lob
diff --git a/samples/aai_service.yaml b/samples/aai_service.yaml
new file mode 100644
index 0000000..1200d38
--- /dev/null
+++ b/samples/aai_service.yaml
@@ -0,0 +1,9 @@
+# A&AI service sample
+# Creates one A&AI service model resource
+#
+odpSchemaVersion: 1.0
+resources:
+  aai-services:
+    - aai-service:
+        service-id: test_aai_service
+        service-description: test_aai_service
diff --git a/samples/cloud-region.yaml b/samples/cloud-region.yaml
new file mode 100644
index 0000000..86c7273
--- /dev/null
+++ b/samples/cloud-region.yaml
@@ -0,0 +1,27 @@
+# Cloud region sample
+# Cloud region resource is one of the biggest to describe (if you want to configure it with OpenStack)
+# Please fill the data based on your OpenStack instance RC v3 file (ask OpenStack admin).
+#
+odpSchemaVersion: 1.0
+resources:
+  cloud-regions:
+    - cloud-region:
+        cloud-owner: sample-cloud-owner
+        cloud-region-id: RegionOne
+        orchestration-disabled: false
+        in-maint: false
+        complex:
+          physical-location-id: sample-complex # Make sure it exists!
+        register-to-multicloud: true
+        availability-zones:
+          - cloud-owner: sample-cloud-owner
+            availability-zone-name: sample-availbility-zone
+            hypervisor-type: nova
+        esr-system-infos: # Take these information from openstack config file
+          - esr-system-info-id: 5433b0ac-594d-41f7-911d-dfe413e1cb2c # Has to be unique
+            user-name: username
+            password: password
+            system-type: VIM
+            service-url: http://127.0.0.1:5000/v3
+            cloud-domain: Default
+            default-tenant: default-tenant
diff --git a/samples/complex.yaml b/samples/complex.yaml
new file mode 100644
index 0000000..8b989c7
--- /dev/null
+++ b/samples/complex.yaml
@@ -0,0 +1,8 @@
+# Complex sample
+# Creates one complex with `sample-complex` physical location id
+#
+odpSchemaVersion: 1.0
+resources:
+  complexes:
+    - complex:
+        physical-location-id: sample-complex
diff --git a/samples/customer.yaml b/samples/customer.yaml
new file mode 100644
index 0000000..e8fdbec
--- /dev/null
+++ b/samples/customer.yaml
@@ -0,0 +1,14 @@
+# Customer sample
+# Creates a customer with one service subscribed - sample-service. It's not required to create customer
+# with service subscription, but it's useful if you want to use that customer later for service
+# instantiation.
+# Service type has to be the name of the SDC service!
+odpSchemaVersion: 1.0
+resources:
+  customers:
+    - customer:
+        global-customer-id: sample-customer
+        subscriber-name: sample-customer
+        subscriber-type: Customer
+        service-subscriptions:
+          - service-type: sample-service # Make sure it exists!
diff --git a/samples/msb_k8s.yaml b/samples/msb_k8s.yaml
new file mode 100644
index 0000000..a6efaf3
--- /dev/null
+++ b/samples/msb_k8s.yaml
@@ -0,0 +1,11 @@
+odpSchemaVersion: 1.0
+resources:
+  msb-k8s-definitions:
+    - name: test
+      version: test
+      artifact: definition.tar.gz
+      profiles:
+        - name: test
+          namespace: test
+          k8s-version: "1.19"
+          artifact: profile.tar.gz
diff --git a/samples/service.yaml b/samples/service.yaml
new file mode 100644
index 0000000..36c92d7
--- /dev/null
+++ b/samples/service.yaml
@@ -0,0 +1,52 @@
+# Service sample
+# Using that file you will create SDC Services both with custom properties and not.
+# * sample-service-with-vf is a simple service with VF resource
+# * sample-service-with-vf-and-properties is a service with VF resource and
+#   it's properties - it's ready to create service instance using Macro flow
+# * sample-service-with-pnf is a simple service with PNF resource
+# * sample-service-with-pnf-and-properties is a service with PNF resource and
+#   it's properties - it's ready to create service instance using Macro flow
+# * sample-service-with-vl is a simple service with VL resource
+# Make sure that resources you want to use are already created. If not - use `xnfs.yaml`
+# sample file and create needed xNFs.
+#
+odpSchemaVersion: 1.0
+resources:
+  services:
+    - service:
+        name: sample-service-with-vf
+        resources:
+          - name: sample-vnf # Make sure it exists!
+            type: VF
+    - service:
+        name: sample-service-with-vf-and-properties
+        resources:
+          - name: sample-vnf # Make sure it exists!
+            type: VF
+            properties:
+              controller_actor: "CDS"
+              skip_post_instantiation_configuration: False
+              sdnc_artifact_name: "vnf"
+              sdnc_model_version: "1.0.0"
+              sdnc_model_name: "ubuntu20"
+    - service:
+        name: sample-service-with-pnf
+        resources:
+          - name: sample-pnf # Make sure it exists!
+            type: PNF
+    - service:
+        name: sample-service-with-pnf-and-properties
+        resources:
+          - name: sample-pnf # Make sure it exists!
+            type: PNF
+            properties:
+              controller_actor: "CDS"
+              skip_post_instantiation_configuration: False
+              sdnc_artifact_name: "vnf"
+              sdnc_model_version: "1.0.0"
+              sdnc_model_name: "ubuntu20"
+    - service:
+        name: sample-service-with-vl
+        resources:
+          - name: sample-vl # Make sure it exists!
+            type: VL
diff --git a/samples/ubuntu.zip b/samples/ubuntu.zip
new file mode 100644
index 0000000..2dc60aa
--- /dev/null
+++ b/samples/ubuntu.zip
diff --git a/samples/vendor.yaml b/samples/vendor.yaml
new file mode 100644
index 0000000..abffca8
--- /dev/null
+++ b/samples/vendor.yaml
@@ -0,0 +1,8 @@
+# Vendor sample
+# Using that file you will create one SDC Vendor resource with "sample-vendor" name
+#
+odpSchemaVersion: 1.0
+resources:
+  vendors:
+    - vendor:
+        name: sample-vendor
diff --git a/samples/vsp.yaml b/samples/vsp.yaml
new file mode 100644
index 0000000..6336f44
--- /dev/null
+++ b/samples/vsp.yaml
@@ -0,0 +1,25 @@
+# VSP sample
+# Using that file you will create:
+#  - one SDC Vendor resource with "sample-vendor" name
+#  - two SDC VSPs:
+#      * one with "sample-vsp-anchor" name, where we use YAML's anchor to share vendor name between two resource,
+#      * onw with "sample-vsp-no-anchor" name where we just simply copy&paste the name of the vendor we want to use.
+#    It will also use "ubuntu.zip" package as an VSP artifact.
+#    Remember: package value is a path, it has to point to the file from the `onap-data-provider` runner perspective.
+#    I recommend to use absulute path to be sure there will be no errors.
+#
+odpSchemaVersion: 1.0
+resources:
+  vendors:
+    - vendor:
+        name: &vendor sample-vendor
+
+  vsps:
+    - vsp:
+        name: sample-vsp-anchor
+        vendor: *vendor
+        package: ubuntu.zip
+    - vsp:
+        name: sample-vsp-no-anchor
+        vendor: sample-vendor
+        package: ubuntu.zip
diff --git a/samples/xnfs.yaml b/samples/xnfs.yaml
new file mode 100644
index 0000000..35f3024
--- /dev/null
+++ b/samples/xnfs.yaml
@@ -0,0 +1,35 @@
+# VNFs and PNFs sample.
+# In that sample we don't create any additional resources - just xNFs. Make
+# sure that VSP you want to use already exists or use sample from `vsp.yaml`
+# file and create it.
+# It will also use "BASIC_VM_enriched.zip" package as an xNF artifact.
+# Remember: package value is a path, it has to point to the file from the `onap-data-provider` runner perspective.
+# I recommend to use absulute path to be sure there will be no errors.
+
+odpSchemaVersion: 1.0
+resources:
+  vnfs:
+    - vnf:
+        name: sample-vnf-without-artifact
+        vsp: sample-vsp # Make sure it exists!
+    - vnf:
+        name: sample-vnf-with-artifact
+        vsp: sample-vsp # Make sure it exists!
+        deployment_artifact:
+          artifact_type: CONTROLLER_BLUEPRINT_ARCHIVE
+          artifact_name: BASIC_VM_enriched.zip
+          artifact_label: vfwcds
+          artifact_file_name: BASIC_VM_enriched.zip
+
+  pnfs:
+    - pnf:
+        name: sample-pnf-without-artifact
+        vsp: sample-vsp # Make sure it exists!
+    - pnf:
+        name: sample-pnf-with-artifact
+        vsp: sample-vsp # Make sure it exists!
+        deployment_artifact:
+          artifact_type: CONTROLLER_BLUEPRINT_ARCHIVE
+          artifact_name: BASIC_VM_enriched.zip
+          artifact_label: vfwcds
+          artifact_file_name: BASIC_VM_enriched.zip