For the use case 'vFirewall Closed Loop and vDNS' which version of the ONAP release is stable to use ?

 
1
0
-1

We are trying to setup the sample use of vFirewall Closed Loop and vDNS. Can somebody please suggest the stable version and share the config yaml ?

    CommentAdd your comment...

    1 answer

    1.  
      2
      1
      0

      Well, yes, good question. I use a mainly 1.0 docker based instance with 1.1 DCAE-Controller and only one AAI VM. I also saved a few container when they where working, so it is not only a matter of the correct HEAT template, but also the docker images pulled at the time of VM initialization and/or restart.

      I have tried a second ONAP instance on a very different cloud environment with 1.1 docker and 1.0 docker. In one case demo.sh init already throws some errors , in the other case, AAI access by VID "hangs" so I didn't investigate further.

      I fear, and I hope to proven wrong, there is no stable version available. But this might change by day.

      I use https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/ONAP/onap_openstack_float.env;h=bbc70199de388c4ec514586a799a2ab0c07f7a8c;hb=HEAD changing docker versions between 1.0 and 1.1


      1. subray bhat

        Thanks Josef. Appreciate it.

        How about SDNC ? Have you used 1.0 SDNC itself ? (Asking because 1.0 SDNC is not coming up for us) 

        If you can share the SDNC config that you are using, that will help a lot. 


        Regards,

        Subray 

      2. Roger Maitland

        The Integration team has a page with the current status of the master branch: ONAP master branch Stabilization  This is a good resource to see if the issue(s) you are facing are common to the current ONAP master branch or something unique to your environment.

        Have you tried an ONAP Operations Manager Project based startup of ONAP?  You might find it easier and faster than the VM deployment option.


        Cheers,

        Roger

      3. Daniel Rose

        unfortunately as the master branch stabilization page shows 1.1 is not ready for demo use. Similarly some show stopping bugs that effect common scenarios are not being fixed in 1.0 and their fixes have been deferred to 1.1 so Josef's answer is correct.

      4. Michael O'Brien

        current vFirewall state:  20170913: in 1.1

        sdc service distribution has aai errors - JIRA pending

        demo.sh init - will then fail as customer and region are not set - these can be manually PUT to aai

        service deployment will fail because of above

        I have not heard of anyone that has passed the middle step of vf creation in VID 

        Today I was able to view the partially distributed service in VID (only)

        I would stick with 1.0 for now - however almost all the teams (at least 10) are focused on making the 1.1 demo work - as we all need 1.1-only code and also are working in OOM which contains more of the newer containers.

        Also note that the 1.0 and 1.1 DCAE code/containers are the same - they both are 1.0 - just labelled differently (DCAEGEN2 will be very different for R1)

      5. subray bhat

        Thank you all for the reply.

        https://www.youtube.com/watch?v=GM6hLDr-zuw

        I was in the impression that there must be some tagged stable version on which these two use cases (vFW & vDNS) are in working condition as shown in the above video starting from 18th min.

        Surprised to know no one in the community is successfully running these two demo use cases (If my understanding from all the above comments is correct).



      CommentAdd your comment...