Difference between revisions of "Vnx-latest-features"

From VNX
Jump to: navigation, search
Line 5: Line 5:
 
<li>'''30/8/2017 - Added support for VyOS network operating system'''. Now VNX supports the creation of virtual scenarios including VyOS based virtual machines (either KVN or LXC).</li>
 
<li>'''30/8/2017 - Added support for VyOS network operating system'''. Now VNX supports the creation of virtual scenarios including VyOS based virtual machines (either KVN or LXC).</li>
  
[[https://vyos.io/en/ VyOS]] is an open source network operating system that is based on Debian GNU/Linux and that joins multiple applications such as Quagga, ISC DHCPD, OpenVPN, StrongS/WAN and others under a single management interface. It can be installed on physical hardware or on virtual machines and it is a community fork of [https://en.wikipedia.org/wiki/Vyatta Vyatta].
+
[https://vyos.io/en/ VyOS] is an open source network operating system that is based on Debian GNU/Linux and that joins multiple applications such as Quagga, ISC DHCPD, OpenVPN, StrongS/WAN and others under a single management interface. It can be installed on physical hardware or on virtual machines and it is a community fork of [https://en.wikipedia.org/wiki/Vyatta Vyatta].
  
 
To test the LXC based VyOS images you can use the "tutorial_lxc_vyos.xml" tutorial scenario:
 
To test the LXC based VyOS images you can use the "tutorial_lxc_vyos.xml" tutorial scenario:
Line 21: Line 21:
 
  vnx -f tutorial_vyos.xml -v -t
 
  vnx -f tutorial_vyos.xml -v -t
  
Access the VyOS routers with vnx/xxxx or vyos/vyos users/passwds. See the [[https://wiki.vyos.net/wiki/User_Guide VyOS User Guide]] for more details about VyOS configuration.  
+
Access the VyOS routers with vnx/xxxx or vyos/vyos users/passwds. See the [https://wiki.vyos.net/wiki/User_Guide VyOS User Guide] for more details about VyOS configuration.  
  
 
<li>'''22/10/2016 - New attribute 'stp' added to <net> tags'''. Now VNX allows to individually control the activation of Spanning Tree (STP) protocol on virtual_bridge and openvswitch networks. For example:</li>
 
<li>'''22/10/2016 - New attribute 'stp' added to <net> tags'''. Now VNX allows to individually control the activation of Spanning Tree (STP) protocol on virtual_bridge and openvswitch networks. For example:</li>

Revision as of 13:03, 30 August 2017

VNX latest features implemented

  • 30/8/2017 - Added support for VyOS network operating system. Now VNX supports the creation of virtual scenarios including VyOS based virtual machines (either KVN or LXC).
  • VyOS is an open source network operating system that is based on Debian GNU/Linux and that joins multiple applications such as Quagga, ISC DHCPD, OpenVPN, StrongS/WAN and others under a single management interface. It can be installed on physical hardware or on virtual machines and it is a community fork of Vyatta.

    To test the LXC based VyOS images you can use the "tutorial_lxc_vyos.xml" tutorial scenario:

    vnx_update   # Latest version of VNX needed
    cd /usr/share/vnx/filesystems 
    vnx_download_rootfs -r vnx_rootfs_lxc_vyos64-1.1.7-v025.tgz
    cd ../examples
    vnx -f tutorial_lxc_vyos.xml -v -t
    

    To test the KVM based VyOS images you can use the "tutorial_vyos.xml" tutorial scenario:

    vnx_update   # Latest version of VNX needed
    cd /usr/share/vnx/filesystems 
    vnx_download_rootfs -r vnx_rootfs_kvm_vyos64-1.1.7-v025.qcow2
    cd ../examples
    vnx -f tutorial_vyos.xml -v -t
    

    Access the VyOS routers with vnx/xxxx or vyos/vyos users/passwds. See the VyOS User Guide for more details about VyOS configuration.

  • 22/10/2016 - New attribute 'stp' added to <net> tags. Now VNX allows to individually control the activation of Spanning Tree (STP) protocol on virtual_bridge and openvswitch networks. For example:
  • <net name="Net1" mode="openvswitch" stp="on"/>
    

    will activate STP on Open vSwitch of Net1.

    Additionally, STP can be activated globally using the <netconfig> tag. For example:

    ...
    <vm_defaults/>
    <netconfig stp="off"/>
    ...
    

    will activate STP on all virtual_bridge or openvswitch networks.

  • 16/5/2016 - Support for virtio drivers in KVM implemented. A new option has been added to /etc/vnx.conf to activate the use of virtio drivers in KVM to improve performance. To use this new feature:
    • Update VNX with vnx_update command
    • Update the autoconfiguration daemon of your root filesystems with:
    • vnx --modify-rootfs your-rootfs.qcow2 --update-aced
      
    • Activate the use of virtio drivers in /etc/vnx.conf
    • [libvirt]
      ...
      virtio = yes
      

      Note that in the case of FreeBSD images, you additionally need to edit the /etc/fstab to change the name of the devices /dev/ada0pX by /dev/vtbd0pX. For that reason, new rootfs images with a name extension "novirtio" have been added to be used with no virtio drivers.

  • 7/5/2016 - New option added to 'vnx_download_rootfs' command. Now vnx_download_rootfs includes -p pattern option to specify a string to filter the list of root filesystems. For example, to see only the lxc images just type:
  • vnx_download_rootfs -p lxc
    
  • 2/5/2016 - OpenBSD support: VNX now supports OpenBSD virtual machines thanks to Francisco Javier Ruiz contribution. Update your VNX version with vnx_update, download the OpenBSD root filesystems using vnx_download_rootfs and test it with the simple_openbsd.xml (32 bits) and simple_openbsd64.xml (64 bits).
  • 21/3/2016 - Host command execution modified: by default <exec> commands defined for the <host> where always executed, even if a virtual machine list was specified with -M option. Now, if -M option is selected, host commands are only executed if 'host' is included in the list. For example:
  • vnx -f scenario.xml -x cmd1 -M vm1,vm2,host
    

    will execute al, the <exec> tags defined in vm1, vm2 and the host.

  • 21/3/2016 - Multiline commands in <exec> tags, by using the standard convention of ending the first lines with an '\':
    <exec seq="createfiles" type="verbatim">
      touch \
        /tmp/file1 \
        /tmp/file2 
    </exec>