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

  • Join the ETSI and OPNFV communities in Sophia-Antipolis, France, May 29 :undefined:–:undefined: 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.

    SinceOPNFV 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 :undefined:–:undefined: OPNFV collaboration activities that will happen during the event, which takes place at the ETSI headquarters, May 29 :undefined:–:undefined: 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 theETSI NFV Plugtests andOPNFV Plugfest.

    The postA Match Made in Heaven: ETSI NFV Plugtests + OPNFV Plugfest appeared first onThe Linux Foundation.



  • 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:



    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


    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