This demonstration uses ONAP platform components on a Rackspace cloud as illustrated in Figure 1. You must have a Rackspace account.
This demo configuration does not attend to the following issues:
- Password management
- API securing
- Disaster recovery
- High availability
and should not be taken as a how to use ONAP in a production setting.
Images
Images may still contain OpenECOMP
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
- 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?
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.
Prerequisites
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)