You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 85 Next »

This demonstration uses ONAP platform components on a Rackspace cloud as illustrated in Figure 1.  You must have a Rackspace account, stack creation can occur on either the IAD or DFW DCs..

This demo configuration should not be taken as a how to use ONAP in a production setting - it currently does not attend to the following issues: Password management, API securing, Disaster recovery, High availability

ONAP Deployment Types

ReleaseArtifactReferencesDescription
1.0.0

Rackspace ONAP Heat Template

openecomp_rackspace.env

openecomp_rackspace.yaml

https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/OpenECOMP;h=a35931e0732cf321898568ce6ecfd7c353133c1e;hb=refs/heads/release-1.0.0

Videos (on public AWS S3 folder at $0.20/download-set - we have a 1.5G limit here - see how this goes)

1 - 2.2G 23min 16:33-16:57 (bootstrap rackspace ONAP VMs - before 5 DCAE boot up)
https://s3.amazonaws.com/onap/20170718_rackspace_iad_bootstrap_1.mov

2 - 1.2G 10min 17:00-17:10 (Observe 5 DCAE VMs come up - wait for ONAP to be stable) - only for timing - does not show much!
https://s3.amazonaws.com/onap/20170718_rackspace_iad_bootstrap_2_dcae.mov

3 - 1.6G 32min 17:11-17:43 (Run vFirewall demo including closed-loop DMaaP TCA/Measurement stats)
https://s3.amazonaws.com/onap/20170718_rackspace_iad_vFirewall_closed_loop_demo_3.mov

replace variables in the env template

supports default public IPs for DCAE

1.1.0


Vanilla Openstack Heat Templatehttps://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/OpenECOMP;h=440dbbee20f631e18208368f41e967ef4cc64c30;hb=HEADSupports floating IPs for DCAE

ONAP VF Templates

ReleaseArtifactReferencesDescription
1.0.0

vFirewall VF Heat Template

 vFW_100_20170608.zip 

Example zip on reference page

or build your own zip with a manifest.json
https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/vFW/1.0.0/base_vfw.env

https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/vFW/1.0.0/base_vfw.env

containing the repo

https://nexus.onap.org/content/sites/raw/org.openecomp.demo/vnfs/vfw/1.0.0-SNAPSHOT

vFirewall heat template zips
1.0.0

vFirewall SSH key

/testsuite/robot/assets/keys/robot_ssh_private_key.pvtssh key for the demo instances (fwl, sink, traffic generator)
1.0.0vLB/vDNS Heat Template

Build your own zip with a manifest.json (see here for instructions on how to generate manifest.json)

Use base_vlb.env, base_vlb.yaml, dnsscaling.env, dnsscaling.yaml from: https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/vLB/1.0.0-SNAPSHOT/

Note: DO NOT use packet_gen_vlb.env and packet_gen_vlb.yaml for version 1.0.0 as packet_gen is not part of the VNF in this version. Please see the README.md for demo VNFs for instructions on how to use a separate packet generator VM to generate DNS queries https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=README.md;h=88f723eaec6c908e373c2a544ec6f28d823774c3;hb=refs/heads/master

vLoadBalancer and vDNS heat template zips


Known Issues

UCA-17 - Getting issue details... STATUS  

https://lists.onap.org/pipermail/onap-discuss/2017-June/001936.html

UCA-19 - Getting issue details... STATUS

APPC-76 - Getting issue details... STATUS

Prerequisites

I keep forgetting about this page - Release Notes 1.0.0 draft also read the demo project readme

Duration: ~60-90 min to bring up the 17 VMs and wait for all 5 docker containers on the last CDAP02 VM - The 5 DCAE VMs starting with coll00 - will take 5-30 min to start depending on pull/build times.  5 min to do all the GUI prep prior to robot init/preload scripts - 10 min total.

Figure 1. ONAP Platform Demo Configuration


The demonstration configuration includes two Services: a Domain Name Service with load balancing, and a firewall with a traffic adjuster as illustrated below.

vFirewall Closed Loop

ONAP Demo Services

  • vFirewall - Spin up a vFirewall and virtual traffic generators.
                      Based on the load of the vFirewall, traffic volume is adjusted as to not overload the vFirewall with low priority traffic.



    Figure 2. ONAP vFirewall Demo

     vLB_demo.mp4

  • vLB - TODO: describe the Load Balancer demo
  • vDNS - Spin up an authoritative vDNS on Rackspace, connected to a network facing the public Internet.
                 The number of vDNS is dynamically adjusted based on load and policy?

Figure 3. ONAP vLoadBalancer/vDNS Demo


   vFW_demo.mp4

See also Tutorials

Additional detail on the configuration of platform components may be found in the Release notes.  Preparing virtual functions is covered in the design process and instructions for running the demo platform and services are provided by the following tutorial pages.

Rackspace/Openstack tenant

yaml + env files

Rackspace/Openstack demo

vFW yaml + env files

replace configuration options in the env file

onap_private_net_id: PUT THE ONAP PRIVATE NETWORK NAME HERE
onap_private_subnet_id: PUT THE ONAP PRIVATE NETWORK NAME HERE

Quickstart Instructions

(The following are a short form of the full demo instructions)

User workflow

Duration: 5 min until robot init/preload - 10 min after that.

Tutorial: Verifying and Observing a deployed Service Instance#vFirewallFlow

License Model

as cs on SDC onboard | new license model | 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 LA (Lversion 1, LA, then FG) save | upload zip | checkin | submit

Onboard home | drop vendor software prod repo | select, import vsp | create | icon | submit for testing

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 | submit for testing 

as jm | start testing | accept 

as gv | approve 

as op | distribute

VSP

ssh to vm1-robot, cd /opt

./demo.sh init (takes around 90 sec) - verify customer is on AA&I by doing a https://aai:8443/aai/v8/business/customers (auth AAI:AAI)

as demo | vid | service models | deploy (service - the one you created - not demoVFW or demoVLB - these 2 are leftover pre-population artifacts of the init script and will be removed) | create service instance "DemoInstance" | add VNF "DemoVNF" | passed | (view add volume and VF-Module dropdowns) 

./demo.sh preload DemoVNF DemoModule

as demo | Create VF Module (DemoModule)

./demo.sh appc DemoModule



References

Use base_vlb.env, base_vlb.yaml, dnsscaling.env, dnsscaling.yaml from

Images

Images may still contain OpenECOMP

Use Case: Use Case: vFW/vDNS (Approved)



  • No labels