Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


FeatureDescription and related demo prep tasksStatusWorking on it
Lab infra for the demoGet a single server (for virtual install) or multi-node (preferred) allocated from Pharos thru June (JIRA: INFRA-114)In progressBryan Sullivan
Bare metal, VM host, and app analytics

Using collectd, collect system analytics and adapt to VES JSON schema for delivery to the Collector.


  • Resolve the current merge conflict
  • Update the VES schema to AT&T 5.0 (Gerrit 34733)
  • Update the VES plugin to the current schema
  • Update the VES C agent to the current schema
In progressMaryam Tahhan, Bryan Sullivan

Using the VES Collector code, run the Collector in a VM, providing a UI for visualization of the analytics.


  • Integrate the current collector code into an InfluxDB frontend, creating a schema for VES data to be stored in InfluxDB, running the collector listener and saving event data in the database as received
  • Integrate a Grafana dashboard with the InfluxDB database, and develop queries to present the following statistics
    • Packet volume in/out each VM
    • HTTP request rate at the web servers
    • VM and host resource utilization e.g. CPU, memory, disk I/O
In progressGokul Singaraju
VNF deployment

Deployment of the demo blueprint.


  1. Create based upon the Barcelona demo install script (
  2. Create copy blueprint folder blueprints / tosca-vnfd-hello-ves to vhello_onap
  3. As needed, update the VES blueprint to align with the current Models test
  4. Copy the blueprint VDU3 config (from blueprint.yaml) into VDU4 and update the current VDU4 (Monitor) to VDU5 in the blueprint and scripts.
  5. Update the iptables setup for VDU4 to act as a firewall only (forward all incoming requests to the private address of VDU3). Later we will update VDU4 to use the new vFW code.
  6. Update test scripts to route client request thru the vFW VM.
  7. Update the deployment scripts to add collectd agent deployment in VDU4.
  8. Using the existing, deploy and test operation of the new demo blueprint in this form, to ensure that the basic topology and script updates work.
  9. Update VDU3 to use the ONAP vLB.
  10. Update VDU4 to use the ONAP vFW.
  11. Using the existing, deploy and test operation of the demo blueprint.
  12. Add deployment of the new collector, InfluxDB, and Grafana functions in VDU5.
  13. Using the new VDU5 collector etc, deploy and test operation of the completed demo blueprint.
In progress

Bryan Sullivan

Aimee Ukasick

Overall demo script

Scenarios to be demonstrated:

  • deployment and idle web server, vLB, and vFW stats in the dashboard
  • startup of traffic, showing updated stats in the dashboard
  • suspend/resume of one web server, showing updated stats in the dashboard
  • ...
In progressBryan Sullivan