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 Environments
ONAP Installation Strategy for Release A | OOM Deployment Status
| Release | Artifacts | References | State | Description |
|---|---|---|---|---|
| 1.0.0 | Rackspace ONAP Heat Template | stable branch | replace variables in the env template supports default public IPs for DCAE | |
| 1.0.0 | OOM Kubernetes | ONAP on Kubernetes#RunningONAPPortalUIOperations | running except DCAE | |
| 1.1.0/R1 master | Rackspace ONAP Heat Template | supports default public IPs for DCAE 20170812 build looks stable - running vFW to verify | pending (dcae vms coming up) | replace variables in the env template |
1.1.0 | Vanilla Openstack Heat Template | use https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;hb=master
| Supports floating IPs for DCAE |
ONAP VF Templates
| Release | Artifact | References | Description |
|---|---|---|---|
| 1.0.0 | vFirewall VF Heat Template |
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.pvt | ssh key for the demo instances (fwl, sink, traffic generator) |
| 1.0.0 | vLB/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 |
| 1.1.0 | vFW, vLB |
ONAP Deployment Videos
| ONAP Version | Undercloud | Description | Video |
|---|---|---|---|
| 1.0.0 | Rackspace | 1 - 2.2G 23min 16:33-16:57 (bootstrap rackspace ONAP VMs - before 5 DCAE boot up) | |
| Rackspace | 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! DCAE 1.0.0 takes up to 26 min to get the dcae-controller docker container up and another 7 min to start orchestration of the cdap cluster check progress by watching the dcae-controller "docker ps" - the collector instance is first to come up, pstg may take up to 24 min after container start and 48 min after VM start, cdap02 is last
| ||
| Rackspace | 3 - 1.6G 32min 17:11-17:43 (Run vFirewall demo including closed-loop DMaaP TCA/Measurement stats) (there is a swap of the vLB during onboarding that only affects the service icon - both vLB and vFW are layer 4) | ||
| 1.0.0 | OOM Kubernetes on Rancher on Openstack | https://wiki.onap.org/download/attachments/13598723/zoom_0.mp4?version=1&modificationDate=1502986268000&api=v2 | |
| 1.0.0 | OOM Kubernetes on Rancher on EC2 | ONAP on AWS | |
| 1.1.0 | 20170812 looks promising |
Known Issues
ONAP master branch Stabilization
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
vFW_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
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 |
|---|
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
| Optional |
|---|
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 | proceed to validation | 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) OR POST to http://{{mso_ip}}:8080/ecomp/mso/infra/serviceInstances/v2/<id>/vnfs/<id>/vfModules - see UCA-20 OSS JAX-RS 2 Client
./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)