Yes, there is a manual option for uploading the blueprint to SDC.

Please note you should upload the artifact to the VF in the service, set the artifactType to be DCAE_INVENTORY_BLUEPRINT, the file name should have a suffix of “event_proc_bp.yaml”

In more details:
In SDC:
1. open a service for editing -> go to Composition tab -> choose the VF in the canvas you wish to attach your artifact to (verify that the right tab is showing the info of the VF) -> in the right menu, select “deployment artifact”


2. click on “Add Artifact”, select the artifact type, fill necessary fields and upload the artifact (pay attention your artifact has the suffix “event_proc_bp.yaml” – it was requested by DCAE inventory)

3. After adding the artifact, you should check-in the service (you can do it from the UI of course)
4. Distribution flow requires several steps: submit for testing, testing and certifying by the user with tester role, approving for distribution by a user with governor role and distribution by a user with Ops role.




  • No labels

1 Comment

  1. Vamshi Krishna Namilikonda

    Hi Michael Lando, Razvan Taranu I attempted to design service which distributes CLAMP controlloop. However I'm falling short of  blueprint yaml you've uploaded here. Can you suggest how this blueprint yaml looks, any sample file you refer. I browsed following yaml file as blueprint controloop, is that correct ?  Please correct me if I'm wrong somewhere, Appreciate your help. Thank you

    controlLoop:
      version: 2.0.0
      controlLoopName: ControlLoop-vdns_dev-48f0c2c3-a172-4192-9ae3-052274181b6e
      trigger_policy: unique-policy-id-1-scale-up
      timeout: 3600
     
    policies:
      - id: unique-policy-id-1-scale-up
        name: policy-vdns_dev
        description:
        actor: SO
        recipe: VF Module Create
        target:
          type: VNF
        retry: 0
        timeout: 1200
        success: final_success
        failure: final_failure
        failure_timeout: final_failure_timeout
        failure_retries: final_failure_retries
        failure_exception: final_failure_exception
        failure_guard: final_failure_guard


    I see the distribution failure for CLAMP, which says the following error.


    2018-10-10T11:09:01,335Z||pool-4-thread-10|||||INFO|||Receive a callback notification in SDC, nb of resources: 1

    2018-10-10T11:09:06,335Z||pool-4-thread-10|||||INFO|||Notification received for service UUID:3c4ee84d-94d2-40fd-ae4b-890ffa5ff4b1

    2018-10-10T11:09:06,336Z||pool-4-thread-10|||||INFO|||Trying to download the artifact : /sdc/v1/catalog/services/Clamptest1/1.0/artifacts/service-Clamptest1-csar.csar UUID: 8c8e3e24-8141-4bca-9429-4abcb04a4f76

    2018-10-10T11:09:06,810Z||pool-4-thread-10|||||INFO|||Successfully downloaded the artifact /sdc/v1/catalog/services/Clamptest1/1.0/artifacts/service-Clamptest1-csar.csar UUID 8c8e3e24-8141-4bca-9429-4abcb04a4f76Size of payload 78193

    2018-10-10T11:09:06,810Z||pool-4-thread-10|||||INFO|||Writing CSAR file to: /tmp/sdc-controllers/sdc-controller/service-Clamptest1-csar.csar UUID 8c8e3e24-8141-4bca-9429-4abcb04a4f76)

    2018-10-10T11:09:08,157Z||pool-4-thread-10|||||INFO|||Found a blueprint entry in the CSAR controlloop.yaml for resource instance Name 00e0654a-ed83-466b-a08c 0

    2018-10-10T11:09:08,157Z||pool-4-thread-10|||||INFO|||1 blueprint(s) will be converted to closed loop

    2018-10-10T11:09:08,159Z||pool-4-thread-10|||||ERROR|||Unexpected exception caught during the notification processing

    java.lang.NullPointerException: null

            at org.onap.clamp.clds.sdc.controller.installer.CsarInstallerImpl.searchForPolicyScopePrefix(CsarInstallerImpl.java:195)

            at org.onap.clamp.clds.sdc.controller.installer.CsarInstallerImpl.buildModelName(CsarInstallerImpl.java:114)

            at org.onap.clamp.clds.sdc.controller.installer.CsarInstallerImpl.isCsarAlreadyDeployed(CsarInstallerImpl.java:105)

            at org.onap.clamp.clds.sdc.controller.installer.CsarInstallerImpl$$FastClassBySpringCGLIB$$c70b96f8.invoke(<generated>)

            at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)

            at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669)

            at org.onap.clamp.clds.sdc.controller.installer.CsarInstallerImpl$$EnhancerBySpringCGLIB$$e182f961.isCsarAlreadyDeployed(<generated>)

            at org.onap.clamp.clds.sdc.controller.SdcSingleController.treatNotification(SdcSingleController.java:239)

            at org.onap.clamp.clds.sdc.controller.SdcSingleController$SdcNotificationCallBack.activateCallback(SdcSingleController.java:90)

            at org.onap.sdc.impl.NotificationConsumer.run(NotificationConsumer.java:71)

            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

            at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

            at java.lang.Thread.run(Thread.java:748)

    2018-10-10T11:09:08,159Z||pool-4-thread-10|||||INFO|||Sending DEPLOY(DEPLOY_ERROR) notification to SDC for