Versions Compared

Old Version 44

changes.mady.by.user Georg Kunz

Saved on

compared with

New Version 45

changes.mady.by.user Parker Berberian

Saved on

Key

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

...

  • Test tools
    • Functest + Xtesting
    • VSPerf: Although originally named to emphasize data plane benchmarking and performance testing of vSwitch and NFV Infrastructure, VSPerf has expanded its scope to multiple types of networking technologies (Kernel Bypass and Cloud-Native) and allow deployment in multiple scenarios (such as containers). VSperf can utilize several different Traffic Generators and Receivers for testing, including several popular Hardware and Software-based systems. The VSPerf tool has many modes of operation, including the "traffic-generator-only" mode, where any virtual network manager sets up the path to be tested, and VSPerf automates the traffic generation and results replrting. VSperf is compliant with ETSI NFV TST009 and IETF RFC 2544.
    • NFVBench
    • Yardstick
  • Lab as a service
    • Lab as a Service (LaaS) is a “bare-metal cloud” hosting resource for the LFN community. We host compute and network resources that are installed and configured on demand for the developers through an online web portal. The highly configurable nature of LaaS means that users can reserve a Pharos compliant or CNTT compliant POD. Resources are booked are scheduled in blocks of time, ensuring individual projects and users do now monopolize resources.  By providing a lab environment to developers, we enable more testing, faster development, and better collaboration between LFN projects.
  • CI/CD for continuous deployment and testing of NFVI stacks
  • OPNFV Lab Infrastructure

    • OPNFV leverages globally distributed community labs provided by member organisations. These labs are used by both developers of OPNFV projects as well as the extensive CI/CD machinery to continuously deploy and test OPNFV reference stacks. In order to ensure a consistent environment across different labs, OPNFV community labs follow a lab specification (Pharos spec) defining a high-level hardware configuration and network topology. In the context of CNTT reference implementations, the existing Pharos specification might be updated (Can somebody confirm this is work in progress?)

  • Feature projects working towards closing feature gaps in upstream open source communities providing the components for building full NFVI stacks
  • Deployment tools
    • Airship
    • Fuel / MCP

...