Page Comparison

...

1. Add VES to your VNF
   1. Create a debian package of the VES client for DANOS using the VESreporting_vFW5.0_DANOS sub-directory from the demo repository
   2. The DANOS build process uses debian packages so this step is creating a VES reporting Debian client that can use the DANOS API's to retrieve statistics
   3. libevel.so must be built and bundled into the package since its not available on the ONAP artifact repositories as a debian package.
2. Create a Openstack Image
   1. Create Download or Create  a DANOS ISO image that includes the VES client
   2. RECOMMENDED: Download a DANOS ISO image that includes the VES client from here fill in url
      1. this iso image was built with dependency constraints that make sure only the correct versions of upstream debian libraries are pulled in.
      2. DANOS 2005 release will fix this problem.
   3. ALTERNATIVE:  Create an Image. 
      1. This is following the existing DANOS procedures for building an  ISO from binaries and the procedures for creating an Openstack image
      2. NOTE: there is a build issue that debian libraries newer than those referenced in the build package may mistakenly be pulled in by the debian build so we recommend using the pre-built ISO image referenced above.
      3. Follow instructions in BUILD_DANOS.md in the demo repository which has slight changes from the DANOS tutorials.
      4. https://danosproject.atlassian.net/wiki/spaces/DAN/pages/491554/Creating+a+DANOS+ISO+using+binary+packages
      5. https://danosproject.atlassian.net/wiki/spaces/DAN/pages/79560705/Creating+a+DANOS+Virtual+Router+VNF+in+Openstack
   4. DANOS supports SNMP already but we want to use the vRouter as a replacement for the existing vFW which is VES based.
   5. DANOS could be used for both VES and SNMP based testing with the addition of this simplified VES client.
3. Create the heat template
   1. Create the heat template for DANOS under a new service vFWCLDN
   2. vFWCLDN is a short hand that makes naming of the VNFs fit within the string lengths in Openstack and ONAP.
   3. The full VNF will be the same packet generator and traffic sink as the standard vFWCL but use DANOS vRouter instead of the ONAP vFW
   4. The DANOS vRouter heat template is minimal.
4. Create the preload_data
   1. This will be the same data items as vFWCL but will demonstrate one of the steps to use for onboarding any VNF to ONAP's automated testing
5. Create the service mapping data
   1. This will add the pointers to the heat templates that are primarily just a name change from vFWCL to vFWCLDN so that the testing tools can map the service to the locations of the various artifacts
6. Add the QCOW2 the  image for your VNF to your glance repository
   1. Add the QCOW2 the  image for the DANOS with VES vRouter to your Openstack glance repository
7. Create the flavor for your VNF
   1. Create the flavor for the DANOS vRouter - 4 vcpu, 4 Gig ram, 8 GB disk with hw_options for cpu_model: passthrough
      
      1. cpu passthrough is the simplest way to ensure that SSSE3 is exposed as a capability in the virtualized hardware.
      2. hw:cpu_model = passthrough

...