A Match Made in Heaven: ETSI NFV Plugtests + OPNFV Plugfest

  • Join the ETSI and OPNFV communities in Sophia-Antipolis, France, May 29 – June 8 for co-located ETSI NFV Plugtests and OPNFV Plugfest

    By Pierre Lynch, Chair, ETSI NFV ISG, TST Working Group & Lead Technologist at Ixia Solutions Group, Keysight Technologies

    The ETSI Plugtests have always had open source community support, with Open Baton, OpenStack, ETSI OSM and OPNFV as supporting organizations since the beginning. But this is the first time that both the OPNFV Plugfest and the ETSI NFV Plugtests will be held in the same location, at the same time.

    Since OPNFV is an integration project incorporating multiple components from various other open source communities into an NFV reference platform, its focus has been on testing from the beginning. Obvious examples of this are the testing projects that are being used by the industry, like Yardstick, Functest, NFVBench and Bottlenecks. Testing is at the core of OPNFV. ETSI, with its Center for Testing and Interoperability (CTI), who run the Plugtests, along with the ETSI NFV TST working group, responsible for testing, experimentation and open source collaboration, also make sure that testing is at the center of attention at ETSI NFV.

    With this in mind, the ETSI NFV community is very happy to have testers and developers from both communities assemble under one roof and work together. This is, in my view, such a natural progression of the already excellent relationship between the testing communities of both organizations.

    There are multiple ETSI NFV – OPNFV collaboration activities that will happen during the event, which takes place at the ETSI headquarters, May 29 – June 8 in Sophia Antipolis, France:

    • The OPNFV Dovetail tool (implementing the OPNFV Verified Program test cases) will have its own track during the Plugtest allowing NFVI+VIM platform vendors and participants to run the OPNFV compliance test suite on the platforms
    • The OPNFV SFC feature support will be available to allow MANOs and VNFs who support SFC to test against it
    • Multiple OPNFV test frameworks will try to test the platforms (NFVI+VIM) that are participating in the Plugtests
    • Contributors for the TST009 work item at ETSI NFV (Testing Specification of Networking Benchmarks and Measurement Methods for NFVI) will be directly attempting the search algorithms from the document using test frameworks from OPNFV. This is an excellent example of standards and open source working hand in hand in order to test concepts immediately by implementing them in order to obtain feedback into the specifications.
    • Contributors to the TST010 work item (API Conformance Testing Specification) and OPNFV leaders will discuss how the OPNFV platform can be leveraged to help automate the test suite envisaged by TST010.

    There are also multiple OPNFV project meetings that will occur during the Plugfest:

    • The edge cloud project team will give an overview on specific operator requirements as well as brainstorm on how to meet those requirements
    • The OPNFV Verified Program tool Dovetail will be giving an update on current status and way forward
    • Long Duration Test (LDT) will give an update and brainstorm on how to better use monitoring for the tests
    • The Yardstick/NSB team will get together to explore NFVI testing, as well as plan for the Gambia release
    • A deep dive on how TRex is being used for data plane testing within various OPNFV test frameworks, including NFVBench integration with those other frameworks

    And of course, there is an entire set of interoperability test sessions scheduled between all the Plugtests participants, bringing in their NFVI+VIM, VNFs and MANO stacks. As in previous Plugtests, several OPNFV scenarios will be actively involved in those sessions in the role of NFV platform (NFVI+VIM). There will be 47 organizations participating in the 3rd NFV Plugtests, that will start one week ahead of the co-located Plugtests with OPNFV. As with the second ETSI Plugtests, the testing will get more ambitious, bringing in advanced functionality, more EPA test cases, more sophisticated auto-scaling, including scale to level, as well as FM and PM advances. In addition, the experimental API track, started during the last Plugtests in January, will be expanded to include additional APIs. This track allows participants to try out their new API implementations based on ETSI NFV-SOL specifications, and will provide input to the NFV-TST010 specification on NFV Conformance

    This will be a busy and productive week for both communities, as these events usually are. However, having both communities together will also lead to more learning and collaboration opportunities unlike no other individual event. We are all looking forward to it.

    There is still time to register! Click these links for details on the ETSI NFV Plugtests and OPNFV Plugfest.

    The post A Match Made in Heaven: ETSI NFV Plugtests + OPNFV Plugfest appeared first on The Linux Foundation.


Log in to reply

Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
re-attach a detached session tmux attach OR
tmux attach-session
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • Use the same script for updating/ upgrading

    Make sure to change the versions to the latest releases:

    #!/bin/bash set -e bpcver=4.2.1 bpcxsver=0.57 rsyncbpcver=

    Scroll through the script, know what you are doing.

    Uncomment the upgrade section(s) and comment out the install section(s)

    read more
  • Again running smartctl after all is said and done:

    smartctl --all /dev/sda

    ddrescue-smartctl-after-rescue.png ddrescue-smartctl-2.png

    Yet an old drive in itself, I run the wheels off of them, and monitor regularly as anyone should.

    read more