Changes between Version 5 and Version 6 of ReferenceGuide

Timestamp:

Oct 18, 2012 11:27:17 AM (12 years ago)

Author:

Ted Faber

Comment:

--

ReferenceGuide

@@ -110 +110 @@
 == Container Notes ==
 
-Different container types have some quirks.  This section lists limitations of each container.
+Different container types have some quirks.  This section lists limitations of each container, as well as issues in interconnecting them.
 
-=== Openvz ===
+=== Qemu ===
 
-Openvz containers use a custom OS image to support their virtualization.  They cannot share physical resources with other containers.  A physical node holding openvz containers holds only openvz containers.  They are interconnected with one another through bridges and kernel virtual networking rather than through VDE switches (as qemu and process containers are)).  As a result, openvz containers provide network delays using per-container endpoint traffic shaping.  This means that they cannot correctly interconnect with traffic sphped qemu nodes.
+Qemu nodes are limited to 7 experimental interfaces.  They currently run only Ubuntu 12.04 32 bit operating systems.
+
+=== ViewOS Processes ===
+
+These have no way to log in or work as conventional machines.  Process tree rooted in the startcommand is created, so a service will run with its own view of the network.  It does not have an address on the control net.
+
+Because of a bug in their internal routing, multi-homed processes do not respond correctly 
 
 === Interconnections: VDE switches and local networking ===
@@ -144 +150 @@
 Similarly embedded physical nodes use only endnode traffic shaping, as routing outgoing traffic through a virtual switch infrastructure that just connects to its physical interfaces is at best confusing.
 
-Unfortunately, endnode traffic shaping and VDE shaping are incompatible.
+Unfortunately, endnode traffic shaping and VDE shaping are incompatible.  Because end node shaping does not impose delays on arriving traffic, it cannot delay traffic from a VDE delayed node correctly.
 
 This is primarily of academic interest, unless a researcher wants to impose traffic shaping between containers using incompatible traffic shaping.  There needs to be an unshaped link between the two kinds of traffic shaping.