| 18 | |
| 19 | The experiment topology is an given in an extended version of DETER's ns2 syntax, or in [http://fedd.deterlab.net/wiki/TopDl topdl], a topology description language. Currently experimenters pick containers directly using those languages. |
| 20 | |
| 21 | == Kinds of Containers == |
| 22 | |
| 23 | A container is a virtualization technology, like a virtual machine implementation. We use the term ''container'' to mean any one of the various virtualization technologies from an openvz container to a physical machine to a simulation. The container system gives us a way to create interconnections of containers (in our sense) holding different experiment elements. A containerized topology might include a physical machine, a [http://wiki.qemu.org/Main_Page qemu] virtual machine and a [http://openvz.org openvz container] that can all commuinicate transparently. |
| 24 | |
| 25 | The container system framework supports multiple kinds of containers, but at this point researchers can request these: |
| 26 | |
| 27 | || __Container Type__ || __Fidelity__ || __Scalability__ || |
| 28 | || Physical Machine || Complete fidelity || 1 per physical machine || |
| 29 | || [http://wiki.qemu.org/Main_Page Qemu virtual Machine] || Virtual hardware || 10's of containers per physical machine || |
| 30 | || [http://openvz.org Openvz container ] || Partitioned resources in one Linux kernel || 100's of contatiners per physical machine || |
| 31 | || [http://wiki.virtualsquare.org/wiki/index.php/Introduction#View_OS ViewOS process ] || Process with isolated network stack || 1000's of containers per physical machine || |
| 32 | |
| 33 | == Further Information == |
| 34 | |
| 35 | * [UsersGuide Users Guide & Tutorial] |
| 36 | * [ReferenceGuide Reference] |