Page tree
Skip to end of metadata
Go to start of metadata

Please use this page to highlight particular accomplishments that your project made during the Iruya release.  These will be used to help promote the release.

Project NameDescription of AccomplishmentWhy is this significant?Contact for follow-up questions
  • Creation of a synthetic workload container.
  • Sunset of OpenStack API usage.
  • The storperf_workloadagent container may be used under any containerized environment to provide a synthetic workload for StorPerf to drive when characterizing containerized storage performance.
  • StorPerf will deprecate the use of OpenStack APIs in the future in order to reduce the dependency on OpenStack and make it more portable to other technologies.
Mark Beierl

  • switch to Ceph in our Functest SUTs
  • add Neutron features in our SUTs to improve the test case verification
  • test all capabilities possible (e.g. vnc_console)
  • verify automatically the CNTT-related containers into additional to the classical ones
  • offer new testcases: tempest_horizon, tempest_keystone, tempest_cinder, refstack_platform, refstack_object, octavia, xrally_kubernetes
  • support CNTT RC (API testing, API and dataplane benchmarking, VNF onboarding and testing)
  • verify ONAP WindRiver OpenLab via Functest CI in a VM ("Inception model")
  • allow minimal l2-only testing via Rally
  • increase NFVI testing coverage in Functest
  • publish new Functest CNTT-specific containers already mandatory in CNTT RC
  • verify both Orange and WindRiver ONAP Openlabs
Cedric Ollivier

  • support multiple deployment models: fully centralized (LFN), distributed or mixed of them
  • fully support NAT or ssh tunneling model
  • support GitlabCI
  • fully manage artifacts publication via S3 (e.g.
  • dump all log compaign easily via S3 (see Kubernetes Conformance)
  • partially integrate a generic dashboard based on Cachet
  • add behave driver
  • enhance Xtesting for the Network Automation Journey (GitlabCI support, Dashboards, new deployment models, etc.)
  • offer the rules to smoothly integrate all test cases needed for CNTT
  • implement the CNTT Compliance/Certification cookbook
  • Containerization: VSPERF now includes multiple containers - Deploy, Test and Results Containers - in its distribution
  • New versions of Upstream Software.
  • Configuration Wizard
  • With containers, now VSPERF can integrate with 'larger/generic' test frameworks such as XTesting/Dovetail.
  • Users can use these containers to use VSPERF in either an Interactive more or Auto mode.
  • The containers also help user to deploy and run tests from any where, as long as there is connectivity to DUT-node and Traffic-Generator Node.
  • The newer version of the upstream software - DPDK, OVS, VPP and Qemu - makes VSPERF more relevant and useful.
  • The configuration helps those new to VSPERF to easily understand, configure and run tests.
  • Bump upstream components: Openstack Stein, ODL Neon, Ubuntu Bionic, Python3, DPDK 18.11 etc.
  • Minor bug fixing
  • Performance tuning of cluster nodes
  • Get latest functionality, security updates and bug fixes from upstream projects
  • Fix integration issues of various components (e.g. Openstack Dashboard)
  • Improved IDF/PDF configuration for the current CI PODs
  • Support latest Fenix for Telco infrastructure rolling maintenance and upgrade
  • Use Python3, all testing to Fuel
  • Keep driving Telco needed rolling maintenance and upgrade. Have it ready with ETSI FEAT03 support, standard implementation and CNTT later on.

NFVbench is a full stack dataplane benchmarking tool currently widely deployed in production around the world. The OPNFV Iruya release matches the NFVBench 4.0.0 version (NFVbench is released independently) and adds the following features:

  • Adds support for L3 router insertion in the packet path
  • Native support for VxLAN benchmarking with per chain latency stats
  • Adds support for High Dynamic Range histograms for latency stats
  • Full migration to python3
  • L3 router insertion allows to benchmark the overhead of an L3 router in the NFV packet path (e.g. OpenStack Neutron Router)
  • VxLAN is an important NFV network overlay use case for large scale deployments that cannot use the simpler VLAN encapsulation
  • Dataplane benchmarks typically use low accuracy latency reporting (min/max/avg and coarse grain histogram buckets). HDR histograms provide high accuracy across the range (1usec to 10sec) with lossless histograms.
Alec Hothan
  • No labels


  1. At the OPNFV TSC meeting today (Jan 28), there was a desire expressed to:

    • Review the Release Announcement (before publication)
    • Add some material in the Release Announcement, under the heading OPNFV 2.0 (below are my suggestions):
      • revisiting Mission and Roadmap/Goals, both near and longer term
      • embracing efficiencies in many areas and new leadership roles
      • conducting project reviews for wider visibility and value recognition
      • developing clear communication channels with CNTT
  2. Would it better to drive the significant points regarding the external ententies or users? (the first example seems more a changelog)

    1. I agree. Is this table supposed to be a release notes that only contains the changes done for the Iruya release?

      If the purpose of this table is to "help promote the release", it will clearly lack a lot of information on what each project does (ie a release notes does not provide a good viewpoint for what the project does and does not provide any indication of all the features already baked in in each project before this release)

      1. The "Description of Accomplishments" column header tells me that this table will list the New Features and Changes. There needs to be a short description of each project and its capabilities.

        Plus, the message needs to Answer WHAT is OPNFV, what are its NEW capabilities (above), and WHERE OPNFV is going NEXT.


  3. The intent of this table is to support marketing of the Iruya release.  It is not intended to be general release notes.  Don't feel obliged to add to this table if your project simply did essential updates and bug fixes.  What we're really looking for are accomplishments that would catch the eye of a stakeholder who isn't involved in the day-to-day operation of OPNFV.  So, something like, "we updated from v1.7 to v2.0 of component zeta", might be important for the project, it's too far in the weeds for an outside observer.  Things like "introduction of Cloud Native support", or "developed a test framework for CNTT", etc. are what we're after.