Crossing a New Milestone in NFV: Open Source Verification of Commercial Products



  • By Chris Donley, Sr Director, Open Source Ecosystems, Huawei; Chair, OPNFV Certification & Compliance Committee

    As we kick off 2018, the OPNFV Compliance & Certification committee—the members driven body within OPNFV that defines recommendations to the Board for policies and oversight for compliance and certification—is pleased to announce the launch of the OPNFV Verified Program (OVP). The program is designed to simplify adoption of NFV in commercial products by establishing an industry threshold based on OPNFV releases. The fact we are using an open source platform as referent to measure compliance of commercial products—not necessarily based on its source code—is a new and innovative step for the industry.

    The OPNFV Verified Program facilitates both vendor self-testing and third-party lab testing using the Dovetail test suite. In our initial version, we will be testing NFV infrastructure components: NFVI and VIM. In the future, we may expand the program to cover VNFs and other components, as well. In December, just ahead of the launch, we conducted a “beta program” with several vendors: Huawei, Nokia, Wind River, and ZTE. These companies provided valuable feedback while we refined and finalized the program. They also represent the first cohort to received the privilege of using the OPNFV Verified mark and logo. Congratulations to these companies and we welcome additional members of the open NFV ecosystem to join us!

    OPNFV Verified Program is designed to help operators establish entry criteria for their trials and RFPs. We have worked closely with end user advisor operators to establish a framework and an initial bar to support their requirements. The program will also reduce operator testing load by identifying a set of common tests and executing them just once under the auspices of the OPNFV Verified Program, rather than many times in many labs. As OPNFV and the industry at large continue to mature, we will steadily raise the bar in future versions as to what becomes verified. We expect two OPNFV Verified versions per year, denoted with the month and the year to make it easy to identify the compliance level of submitted products.

    Under the auspices of The Linux Foundation, we are well positioned to expand the program to support other projects in the future. Prior to the official launch, we initiated discussions with related projects on leveraging the program to support the wider open source community. OPNFV’s C&C, the group responsible for chartering the OPNFV Verified Program, is also exploring additional operator use cases that can be incorporated into the compliance test suite.

    I am excited about the launch of the OPNFV Verified Program and I hope you will join us in 2018! To operators, I invite you to share your use cases and functional requirements, and please consider incorporating OPNFV Verified into your RFP process or lab trials. To vendors, I hope you’ll download the Dovetail tool and test your commercial offerings. If you’re looking for assistance, several third-party labs are eager to help. Learn more about the OPNFV Verified Program and get started today!

    Please direct any questions you may have to verified@opnfv.org.

    This article originally appeared at OPNFV.

    The post Crossing a New Milestone in NFV: Open Source Verification of Commercial Products appeared first on The Linux Foundation.

    https://www.linuxfoundation.org/blog/crossing-new-milestone-nfv-open-source-verification-commercial-products/





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
screen
re-attach a detached session tmux attach OR
tmux attach-session
screen-r
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]
});