1
0
-1

Hi,

I have been trying to implement closed loop with vDNS/vLB setup. I am using release-1.0.0 ONAP setup except with DCAE in 1.1 on top of Vanilla Openstack. As I am working behind the proxy, setting up DCAE -1.1 is not straight forward and not simple as DCAE is controller launches other VMs. So I have to get userdata in each VM and add necessary proxy details to it. Though it is still in progress, I make sure DCAE collector is up and running. I can see the VES streams from collector API. I am following the closedloop flow for DNS described in https://wiki.onap.org/pages/viewpage.action?pageId=3246170#UseCase:vFW/vDNS(Approved)-1.4CloseLoopvDNS . As per the flow diagram (1.4 Close Loop vDNS), after receiving the telemetry details:

1) The DCAE has to send threshold crossing notice to policy. Eventually policy has to send two requests. One is to AAI to update the vLB details with dnsscaling data. And the second one is to SO to instantiate the DNS scaling. My query here is how MSO is aware of dnsscaling details like what heat template to use ? How to onboard dnsscaling template in SDC,? I am also trying to see what are APIs the policy is using to trigger AAI and MSO, but if you already have the API details, can you please share them, it would be really helpful.


As I have issue with MSO and DMaaP, I have manually inserted template details into DB. So if you can share the details of how it looks after onboarding dnsscaling template, that would be helpful.

2) I have checked the VES streams, I couldn't see the vf_module or VNF details, so in that case how DCAE can trigger the policy with the exact policy rule? 3) As I mostly interested to see closedloop, so can I safely ignore CDAP cluster VM, if not , may I know the role of CDAP and PGaaS VM in this scenario. Probably I am missing something here.


As I mentioned before, if we can make DCAE instantiation simple(especially considering all types of environments like proxy) that would make setting up of DCAE a lot easier 

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      The DNS scaling Heat template is on-boarded via SDC at service creation time. In addition to the base_* template, also the dnsscaling.yaml template is uploaded. For each template, SDC creates an object called vf_module, which appears as metadata in the Heat template and env file. If you look at the Heat template, you see vf_module_id in the VM metadata section. The corresponding value in the env file is actually a placeholder (we set that value to make OpenStack happy when we instantiate VNFs outside ONAP for unit testing), and it is overridden by ONAP during VNF onboarding or distribution (can’t remember this detail).

       

      When Policy receives notification from the DCAE threshold-crossing microservice, it gets the vf_module_id from AAI and then sends it to MSO, such that MSO knows what to do.

        CommentAdd your comment...