Changes between Version 12 and Version 13 of Omni

Timestamp:

09/15/10 08:59:20 (14 years ago)

Author:

Aaron Helsinger

Comment:

--

Omni

@@ -225 +225 @@
 === OpenFlow ===
 
+OpenFlow native RSpecs are different formats for advertisements and reservations. The Omni omnispec is an intermediate format - Omni will convert between the two formats for you, allowing you to edit the omnispec directly. 
+
+The native advertisement RSpecs describe a network in terms of switches and links. To reserve flowspace you you will need to define a slice (needs a name and controller URL), a project (named), a user for logging in to FlowVisor, and then one or more flowspace entries (flowvisor rules). The flowspace needs the switches it applies to, and then the ports, dl, vlnan, nw, etc specs for what it should match. Everything in your reservation RSpec will go to the slice / controller you have specified.
+
+Note that in these RSpecs, all integers can be specified as hex or decimal. * or missing means wildcard.
+
 A native OpenFlow advertisement RSpec looks like this:
 {{{
@@ -280 +286 @@
 }}}
 
-This gets converted by Omni (when you call listresources) into an omnispec that looks like this:
+This advertisement RSpec gets converted by Omni (when you call listresources) into an omnispec. The omnispec can be edited directly, and Omni will convert that into the appropriate reservation RSpec. The OpenFlow omnispec looks like this:
 
 {{{
@@ -413 +419 @@
 }}}
 
-To allocate, simply set "allocate" to true for each switch that you want to allocate, and fill in the flowspace options for the flowspace on that switch.  Next, fill in 'sliceinfo' section with your name, password, etc and pass the omnispec in for the omni createsliver call.
+To allocate, simply set "allocate" to true for each switch that you want to allocate, and fill in the flowspace options for the flowspace on that switch (nw/dl/tp/vlan specifying the matching rules you want for your flowspace entry).  Next, fill in 'sliceinfo' section with your name, password, controller URL, etc and pass the omnispec in for the omni createsliver call.
+
+
+The native OpenFlow reservation RSpec looks like this:
+{{{
+    <resv_rspec>
+        <user
+            firstname="John"
+            lastname="Doe"
+            email="john.doe@geni.net"
+            password="slice_pass"
+        />
+        <project
+            name="Stanford Networking Group"
+            description="Internet performance research to ..."
+        />
+        <slice
+            name="Crazy Load Balancer"
+            description="Does this and that..."
+            controller_url="tcp:controller.stanford.edu:6633"
+        />
+        <flowspace>
+            <switches>
+                <switch urn="urn:publicid:IDN+openflow:stanford+switch:0">
+                <switch urn="urn:publicid:IDN+openflow:stanford+switch:2">
+            </switches>
+            <port from="1" to="4" />
+            <dl_src from="22:33:44:55:66:77" to="22:33:44:55:66:77" />
+            <dl_dst from="*" to="*" />
+            <dl_type from="0x800" to="0x800" />
+            <vlan_id from="15" to="20" />
+            <nw_src from="192.168.3.0" to="192.168.3.255" />
+            <nw_dst from="192.168.3.0" to="192.168.3.255" />
+            <nw_proto from="17" to="17" />
+            <tp_src from="100" to="100" />
+            <tp_dst from="100" to="*" />
+        </flowspace>
+        <flowspace>
+            <switches>
+                <switch urn="urn:publicid:IDN+openflow:stanford+switch:1">
+            </switches>
+            <tp_src from="100" to="100" />
+            <tp_dst from="100" to="*" />
+        </flowspace>
+    </resv_rspec>
+}}}