VirtualSOP (VSOP)

Description

Release notes

Show release notes
Version 2.0.2 - Early deployment
  • Bugfix: Better error message are now printed when the file system does not support quotas. (M12531)
  • Dependency:
    • VSOP Support module >= 2.0.0
    • vSOP host data partition must be XFS formatted for disk quota support
    • Optional: SMP version 5.2.0. Required for ETL.

Version 2.0.1 - Early deployment
  • Bugfix: Only last VLAN defined was taken into account
  • Dependency:
    • VSOP Support module >= 2.0.0
    • vSOP host data partition must be XFS formatted for disk quota support
    • Optional: SMP version 5.2.0. Required for ETL.

Version 2.0.0 - Early deployment
  • Feature: Support for multiple guests with same VLAN ID on same host. (M8403)
  • Dependency:
    • VSOP Support module >= 2.0.0
    • vSOP host data partition must be XFS formatted for disk quota support
    • Optional: SMP version 5.2.0. Required for ETL.

Version 1.2.0 - General deployment
  • Bugfix: VSOP installation behaves properly when ETL is used (M7769)
  • Improvement: Clarified guest/host eth0/1 configuration
  • Limitation: On the same physical host, each vlan id can only be used by one vSOP at a time (M8403)
  • Feature: Support hard disk limit with quota on XFS (M8265)
  • Improvement: Allow mounting SSHFS on VSOPs (M9203)
  • Feature: Added support for Fax Server in VSOP. (M9769)
  • Limitation: cannot install more than 1 vSOP resource with the same VLAN ID (M8404)
  • Dependency:
    • VSOP Support module >= 1.6.0
    • vSOP host data partition must be XFS formatted for disk quota support
    • Optional: SMP version 5.2.0. Required for ETL.

Version 1.1.2 - General deployment
  • Improvement: VSOP installation behaves properly when Lua is used (M7769)
  • Limitation: Could not install more than 1 vSOP resource with the same VLAN ID (M8404)
  • Dependency:
    • VSOP Support module >= 1.3.0

Version 1.1.1 - Early deployment
  • Improvement: Backport Allow mounting SSHFS on VSOPs (MS-142)
  • Dependency:
    • VSOP Support module >= 1.3.0

Version 1.1.0 - Early deployment
  • Feature: Add support for baseline 3 vSOP's (M7534)
  • Feature: Support for a private network with NAT
  • Limitation: cannot install more than 1 vSOP resource with the same VLAN ID (M8404)
  • Dependency:
    • VSOP Support module >= 1.3.0

Version 1.0.7 - Early deployment
  • Feature: Added support for Fax Server in VSOP. (M9769)
  • Limitation: cannot install more than 1 vSOP resource with the same VLAN ID (M8404)
  • Dependency:
    • VSOP Support module 1.0

Version 1.0.6 - General deployment
  • Feature: Support vSOP on baseline 3 (M7314)
  • Limitation: cannot install more than 1 vSOP resource with the same VLAN ID (M8404)
  • Dependency:
    • VSOP Support module 1.0

Version 1.0.5 - General deployment
  • Feature: Allow mounting of cgroup directory inside the container itself (M0005974)
  • Limitation: cannot install more than 1 vSOP resource with the same VLAN ID (M8404)
  • Dependency:
    • VSOP Support module 1.0

Version 1.0.4 - General deployment
  • Feature: allow vsop eth0 to be attached to host eth1 and vice versa
  • Bugfix: make all combinations work eth0/eth1 bridge/vlan/private
  • Limitation: cannot install more than 1 vSOP resource with the same VLAN ID (M8404)
  • Dependency:
    • VSOP Support module 1.0

Version 1.0.3 - Deprecated
  • Feature: allow vsop eth0 to be attached to host eth1 and vice versa (M0)
  • Bugfix: make all combinations work eth0/eth1 bridge/vlan/private (M0)
  • Deprecated: Resource was rejected by or has not been validated by our quality assurance department. (M5733)
  • Dependency:
    • VSOP Support module 1.0

Version 1.0.2 - Deprecated
  • Improvement: Drop capabilities of container to prevent it from harming the host or other containers (M0)
  • Deprecated: Resource was rejected by or has not been validated by our quality assurance department. (M5733)
  • Dependency:
    • VSOP Support module 1.0

Version 1.0.1 - Deprecated
  • Improvement: Better error handling (M0)
  • Deprecated: Resource was rejected by or has not been validated by our quality assurance department. (M5733)
  • Dependency:
    • VSOP Support module 1.0

Version 1.0 - Deprecated
  • Deprecated: Resource was rejected by or has not been validated by our quality assurance department. (M5733)
  • Dependency:
    • VSOP Support module 1.0

Resource configuration interface

GUI unavailable.

Resource configuration parameters

ALERT! To apply the changes done in the VSOP resource you need to stop and start the VSOP ALERT!,
  • Guest eth0. This parameters indicates to the guest, how its eth0 interface should be connected to the host.
  • Guest eth0 VLAN ID. Indicate here the VLAN Id, if you chose VLAN on host eth0 or VLAN on host eth1 on the dropdown above.
  • Guest eth1. This parameters indicates to the guest, how its eth1 interface should be connected to the host.
  • Guest eth1 VLAN ID. Indicate here the VLAN Id, if you chose VLAN on host eth0 or VLAN on host eth1 on the dropdown above.
  • CPU share (optional, default=1024) By default, CPU shares are fairly distributes between vSOPs (a specific vSOP can take all CPU but if 2 vSOPs want to take the whole CPU, the CPU is evenly shared between the 2 vSOPS regardless of their load). It is possible however to give more CPU to a specific vSOP by, for example, doubling the CPU shares for this vSOP
  • Physical Memory Limit (RAM) (optional) Expressed in bytes or suffix with M, G for megabytes, gigabytes, E.g. 256M. You can leave blank for no limit.
  • Virtual Memory Limit (RAM+swap) (optional) Expressed in bytes or suffix with M, G for megabytes, gigabytes, E.g. 256M. You can leave blank for no limit.

ALERT! Note that:
  • VLAN: Your vSOP will be able to communicate with other devices on that vlan.
  • Bridge: Your vSOP will be able to communicate with all the devices connected to the bridge, this means all the devices accessible from the host interface, as well as all the VSOPs on the host.
  • Bridge for VMware: This option still requires the VMware port interface to be configured in promiscuous mode. note: On specific vmware install, the flags "Forged Transmits" and "MAC address changes" could be necessary.
  • Private Bridge: Your vSOP will be able to communicate with all the devices accessible from the host interface, but it will not be able to communicate with the host interface and other vSOPs on that host.
  • Private network with NAT: Your vSOP will be isolated in a private network on the vSOP host. Outgoing communication is still possible, but any requests to the outside will be natted and the source address will be the address of the vSOP host. To avoid network overlap with existing customer subnets, the subnet is always 192.0.2.240/28 where the default gateway and DNS server is at 192.0.2.254.
  • VLAN IDs: On the same physical host, each vlan id can only be used by one vSOP at a time. More than one vSOP using the same vlan id will not work.
  • Multiple physical interfaces on the same LAN is generally not supported.

Administration guide

The administration guide and the installation procedure for vSOPs can be found here.
Copyright © Escaux SA