OPNFV Verification Program to Simplify Commercial NFV Adoption



  • Open source NFV project establishes industry threshold for NFV testing, deployment

    San Francisco — February 6, 2018 — The OPNFV Project, an open source project within The Linux Foundation that facilitates the development and evolution of Network Functions Virtualization (NFV) components across various open source ecosystems through integration, deployment, and testing, today announced the availability of the OPNFV Verified Program (OVP). Designed to simplify adoption in commercial NFV products, OVP establishes an industry threshold based on OPNFV capabilities and test cases. A new landing page explains the program benefits in more detail, and users can get started at the new OPNFV Verified portal.

    OPNFV members, including network operators, worked closely to establish a framework and reached consensus for an initial set of capabilities that help operators establish entry criteria for their POCs and RFPs. OVP facilitates both vendor self-testing and third-party lab testing. The initial version will test and verify NFV infrastructure components and features, including NFVI, VIM, underlying cloud infrastructure, basic packet forwarding, IPv6, and VPN. The program will evolve over time as more capabilities and test cases are added, with continuing test suite releases and possibly expanding to include VNFs and other components in the future.

    “We are breaking new ground by leveraging open source platforms to measure compliance of commercial products,” said Heather Kirksey, VP, Community and Ecosystem Development, The Linux Foundation. “This is a huge step for the industry, and speaks to the power of open, community-driven solutions to help the ecosystem in real-world deployments. I am incredibly proud of the collaborative work that has gone into establishing this set of common NFV platform requirements to aid the industry on the path towards robust NFV deployments.”

    Based on early participation during the beta program, several vendors provided valuable feedback that helped refine and finalize the program, and those organizations now represent the first cohort to receive the privilege of using the OPNFV Verified mark and logo: Huawei, Nokia, Wind River, and ZTE.

    Operators are encouraged to participate in the program by sharing use cases and functional requirements as well as incorporating OVP into RFP processes and trials. Vendors may download the Dovetail framework for compliance testing of commercial offerings.

    More information about OVP is available at https://www.opnfv.org/verified.

    Quotes from OVP Verified Organizations

    Huawei
    “The OPNFV Verified Program (OVP) is a great example of open source communities leading the way to help lower complexity in multi-vendor NFV solutions,” said Wenjing Chu, senior director, head of Open Source and Research, Huawei. “OVP reduces risks for carriers in NFV adoption by decreasing the integration and verification cost and enhancing interoperability. Huawei is a leader and strong supporter of this community initiative, and we are excited that FusionSphere is one of the first products certified under OVP. Huawei is committed to NFV and carrier transformation towards more agile and intelligent networks. As part of that commitment, we will continue to strongly support OPNFV to help evolve OVP and foster a vibrant and open NFV ecosystem.”

    Nokia
    “Nokia is very excited to support openness in networking by joining the first companies in the OPNFV Verified program,” said Antti Romppanen, head of Cloud Foundation Product Management, Nokia. “Being able to verify the compatibility of the OPNFV software with our AirFrame data center solution, which is based on open hardware specifications from the Open Compute Project, demonstrates the power of open source across the NFV infrastructure. Going forward, we expect to raise the bar in OPNFV to extend the verification to higher layers and to make the open platform even more competitive.”

    Wind River
    _“_As a founding member of OPNFV, Wind River has been participating closely in the innovative work of the technical community to accelerate open source NFV across the industry,” said Charlie Ashton, senior director of business development, Software-defined Infrastructure, Wind River. “We are extremely proud to be in the first group of companies to complete the OPNFV Verified program with our Titanium Cloud solution, enabling us to better meet the needs of our service provider customers while achieving the highest levels of compatibility. We look forward to continuing this work and to contributing further to this important open source initiative.”

    ZTE
    “As an active member of the community, ZTE is a strong contributor to open source SDN and NFV communities,” said Mr. Julien (Jun) Zhang, chief NFV architect, ZTE. “The OPNFV Verified Program (OVP) is a big milestone for NFV, as it sets parameters for industry interoperability, cooperation and transformation. This will enable better development of network convergence and accelerate the maturity of the cloud industry. ZTE is proud that ZTE TECS Openstack is among the first initiatives to become OPNFV Verified and we look forward to contributing further towards OVP development.”

    OPNFV, as well as other LF Networking projects, will be onsite at ONS North America, March 26-29 in Los Angeles. The event will include an expanded set of six tracks bringing networking and orchestration innovations together with a focus on the convergence of business (CIO/CTO/Architects) and technical (DevOps) communities.

    About The Linux Foundation
    The Linux Foundation is the organization of choice for the world’s top developers and companies to build ecosystems that accelerate open technology development and industry adoption. Together with the worldwide open source community, it is solving the hardest technology problems by creating the largest shared technology investment in history. Founded in 2000, The Linux Foundation today provides tools, training and events to scale any open source project, which together deliver an economic impact not achievable by any one company. More information can be found at www.linuxfoundation.org.

    The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our trademark usage page: https://www.linuxfoundation.org/trademark-usage. Linux is a registered trademark of Linus Torvalds.

    The post OPNFV Verification Program to Simplify Commercial NFV Adoption appeared first on The Linux Foundation.

    https://www.linuxfoundation.org/networking-orchestration/opnfv-verification-program-simplify-commercial-nfv-adoption/


 



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]
  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:

    lsblk

    Output:

    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s

    Fin!

    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more
});