Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagejs
{
    "cloud_region_id": "krd",
    "rb_profile_id-name": "12345678-8888-4578-3344-987654398731",
    "csar_id": "94e414f6-9ca4-11e8-bb6a-52540067263b""p1",
	"rb-name":"test-rbdef",
	"rb-version":"v1",
    "labels": {
	}
}

NOTE: Make sure that the namespace is already created before instantiation.
See

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-462
for more details.

...

This command returns the following JSON:

Code Block
languagejs
{
  "vnf_id": "3c13ZKMTSaxv",
  "cloud_region_id":"krdrb-name": "mongo",
  "rb-version": "v1",
  "profile-name": "profile1",
  "cloud-region": "kud",
  "namespace": "testnamespace1testns",
  "vnf_components": {
resources": [
    {
      "GVK": {
        "Group": "",
        "Version": "v1",
        "Kind": "Service"
      },
      "Name": "mongo"
    },
    {
      "GVK": {
        "Group": "",
        "Version": "v1",
        "Kind": "Service"
      },
      "Name": "mongo-read"
    },
    {
      "GVK": {
        "Group": "apps",
        "Version": "v1beta1",
        "Kind": "StatefulSet"
      },
      "deploymentName":[ "krd-testnamespace1-3c13-test-rbprofile-vault-consul-dev"],profile1-mongo"
    "service":["krd-testnamespace1-3c13-aaf-sms-db"]}
  }]
}

Delete Instantiated Kubernetes resources

The vnf_The id  field from the returned JSON can be used to DELETE the resources created in the previous step

...

Code Block
languagebash
titleCommand to Instantiate a Profile
curl -X DELETE http://localhost:8081/v1/vnf_instances/krd/testnamespace1/3c13instance/ZKMTSaxv


Configuration API's

Day 2 Configurations for applications are applied using K8S kinds (typically CRDs) implemented by application specific operators.  For a given application, type of configuration is similar (but not the values), therefore configuration templates are created by applications.  These templates are for each application and are expected to be created even before Day 2 configuration is applied. Once the templates are created, configuration can be applied by choosing the right template. Day 2 configuration is applied by users as and when new configuration is required. As a user, he/she should select the template and supply values to apply new configuration. 

...