...
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..
| Warning |
|---|
This demo configuration does not attend to the following issues:
and should not be taken as a how to use ONAP in a production setting. |
...
Duration: ~60 min to bring up the 17 VMs and wait for all 5 docker containers on the last CDAP02 VM. 5 min to do all the GUI prep prior to robot init/preload scripts - 10 min total.
Figure 1. ONAP Platform Demo Configuration
...
- 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
View file name vLB_demo.mp4 height 250
- 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?
...
| View file | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|
This demonstration uses ONAP platform components on a Rackspace cloud as illustrated in Figure 1. You must have a Rackspace account.
| Warning |
|---|
This demo configuration does not attend to the following issues:
and should not be taken as a how to use ONAP in a production setting. |
| Info | ||
|---|---|---|
| ||
Images may still contain OpenECOMP |
Prerequisites
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.
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
View file name vLB_demo.mp4 height 250
- 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
| View file | ||||
|---|---|---|---|---|
|
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 |
|---|
Questions
User workflow
TODO: diagram separate flows for design and runtime users (designer - in progress while we rerun the demo 20170518)
License Model
as cs 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
./demo.sh init
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 (DemoModule)
./demo.sh appc DemoModuleChildren Display all true depth 1
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 |
|---|
Questions
User workflow
Duration: 5 min until robot init/preload - 10 min after that.
TODO: diagram separate flows for design and runtime users (designer - in progress while we rerun the demo 20170518)
...