Pre-requisite

Setup the OOM Infrastructure: OOM Infrastructure setup

Deploy OOM

Video describing all the steps

We will basically follow this guide: http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/OOM%20User%20Guide/oom_user_guide.html?highlight=oom

1. Clone OOM release-1.1.0 branch

   git clone -b release-1.1.0 ssh://adetalhouet@gerrit.onap.org:29418/oom

2. Prepare configuration

   1. Edit the onap-parameters.yaml under

      oom/kubernetes/config

   2. To have endpoints registering to MSB, add your kubectl config token in kube2msb config, under kubeMasterAuthToken located at

      oom/kubernetes/kube2msb/values.yaml

3. Create the config

   cd oom/kubernetes/config
   ./createConfig.sh -n onap

4. Deploy ONAP

   cd oom/kubernetes/oneclick
   ./createAll.bash -n onap

5. Now, time for a break. This will take arround 30/40 minutes.
   

Running vFW demo

1. Login into the VNC. Password is password

   <kubernetes-vm-ip>:30211

2. Open the browser and navigate to the ONAP Portal

   Login using the Designer user. cs0008/demo123456!

   http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm

3. Open SDC application, click on the OnBoard tab.
   1. click Create new VLM (Licence Model)
      1. Use onap as Vendor Name, and enter a description
      2. clicksave
      3. click Licence Key Group and Add Licence Key Group, then fill in the required fields
      4. click Entitlements Pools and Add Entitlement Pool, then fill in the required fields
      5. click Feature Groups and Add Feature Group, then fill in the required fields. Also, under the Entitlement Pools tab, drag the created entitlement pool to the left. Same for the License Key Groups
      6. click Licence Aggreements and Add Licence Agreement, then fill in the required fields. Under the tab Features Groups, drag the feature group created previously.
      7. then check-in and submit
      8. go back to OnBoard page
   2. click Create a new VSP
      1. First we create the vFW sinc; give it a name, i.e. vFW_SINC. Select the Vendor (onap) and the Category (Firewall) and give it a description.
      2. Click on the warning, and add a licence model
      3. Get the zip package: vfw-sinc.zip
      4. Click on overview, and import the zip
      5. Click Proceed to validation then check-in then submit
   3. Create the vFW_PG VSP
      1. Get the zip package: vfw_pg.zip

License Model

as cs on SDC onboard | new license model (lkg/ep/fg/ep - all not required) | license key groups (network wide / Universal) | Entitlement pools (network wide / absolute 100 / CPU / 000001 / Other tbd / Month) | Feature Groups (123456) | Available Entitlement Pools (push right) | License Agreements | Add license agreement (unlimited) - push right / save / check-in / submit | Onboard breadcrumb 

VF

Onboard | new Vendor (not Virtual) Software Product (FWL App L4+) - | select network package not manual checkbox | select LA (Lversion 1, LA, then FG) - ignore warning - save | upload SP vFWSink attachments zip (same one from R0 above) | proceed to validation | checkin | submitproceed to validation | checkin | submit | 2nd VSP - same above expept vFWPG.zip | proceed validation, checkin submit | 

Onboard home | drop vendor software prod repo on "top right" | select, import vsp | create | icon | submit for testing - do twice for each vFWSNK, vFWPG

Distributing

as jm | start testing | accept 

as cs | sdc home | see firewall | add service | cat=l4, 123456 create | icon | composition, expand left app L4 - drag TBD(need new zip? - 2 services)| submit for testing 

as jm | start testing | accept 

as gv | approve 

as op | distribute | monitor