summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJason Kölker <jason@koelker.net>2011-06-16 11:27:01 -0500
committerJason Kölker <jason@koelker.net>2011-06-16 11:27:01 -0500
commit2a90b44ddd797b7e493bbfbe4de80115c96a9ab4 (patch)
tree523e2302060e7209c5e3077db3d1941b9ca61b1e
parent4ef6b76ff882271ea611c0bba9542760a485c4fb (diff)
initial commit of multinic doc
-rw-r--r--doc/source/devref/multinic.rst26
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/source/devref/multinic.rst b/doc/source/devref/multinic.rst
new file mode 100644
index 000000000..2a0101078
--- /dev/null
+++ b/doc/source/devref/multinic.rst
@@ -0,0 +1,26 @@
+MultiNic
+========
+
+What is it
+----------
+
+Multinic allows an instance to have more than one vif connected to it. Each vif is represenative of a separate network with its own IP block.
+
+<Diagram of virtual machine with 2 vifs & hypervisor with 2 bridges>
+
+Managers
+--------
+
+Each of the 3 network managers are designed to run indipendantly of the compute manager. They expose a common API for the compute manager to call to determine and configure the network(s) for an instance. Direct calls to either the network api or especially the DB should be avoided by the virt layers.
+
+Flat Examples
+-------------
+
+
+
+
+FlatDHCP Examples
+-----------------
+
+VLAN Examples
+-------------