Changes between Version 16 and Version 17 of TopdlLibrary

Timestamp:

Oct 8, 2012 11:40:43 AM (12 years ago)

Author:

faber

Comment:

--

TopdlLibrary

@@ -35 +35 @@
   * [TopdlLibrary#CPUClass CPU] (0 or more)
     * [TopdlLibrary#AttributeClass Attribute] (0 or more)
-  * [TopdlLibrary#OperatingSystemClass !OperatingSystem] (0 or more)
+  * [TopdlLibrary#OperatingSystemClass OperatingSystem] (0 or more)
     * [TopdlLibrary#AttributeClass Attribute] (0 or more)
   * [TopdlLibrary#SoftwareClass Software] (0 or more)
@@ -46 +46 @@
     * [TopdlLibrary#AttributeClass Attribute] (0 or more)
   * [TopdlLibrary#ServiceClass Service] (0 or more)
-    * [TopdlLibrary#ServiceParamClass !ServiceParam] (0 or more)
+    * [TopdlLibrary#ServiceParamClass ServiceParam] (0 or more)
 
 Most classes can have attributes attached to them that contain extention attributes that different applications make use of.  The presence or absence of an optional nested object does not mean the presence or absence of the thing it describes, but that the description is unbound.  As [TopDl#Representation we have seen] a Computer without a nested CPU object does not describe a computer without a CPU, but a computer with no constraints on the CPU.
@@ -479 +479 @@
 This example constructs the topdl describing a simple start topology with 11 nodes, one center and 10 satellites.
 
-[[Image(ten_smaller.png)]]
-
-A python program to create that looks like this:
+[[Image(ten_small.png)]]
+
+A python program to print the topdl describing that topology looks like this:
 
 {{{
@@ -519 +519 @@
 }}}
 
-The program builds the topology by creating a [TopdlLibrary#ComputerClass computer object] that is the center of the star, then creates other computers that are connected to the center.  The connection is accomplished by creating a [TopdlLibrary#SubstrateClass Substrate object] that represents the connection and adding [TopdlLibrary#InterfaceClass Interface objects] to the center computer and the satellite that bind them to the substrate.
-
-
+The [attachment:ten.py program] builds the topology by creating a [TopdlLibrary#ComputerClass Computer object] that is the center of the star, then creates other computers that are connected to the center.  The connection is accomplished by creating a [TopdlLibrary#SubstrateClass Substrate object] that represents the connection and adding [TopdlLibrary#InterfaceClass Interface objects] to the center computer and the satellite that bind them to the substrate.
+
+For comparison, [attachment:ten.tcl here] is the equivalent ns2 description:
+
+{{{
+source tb_compat.tcl
+set ns [new Simulator]
+
+# Create the center node (named by its variable name)
+set center [$ns node]
+
+# Connect 10 satellites
+for { set i 0} { $i < 10 } { incr i} {
+    # Create node n-1 (tcl n($i) becomes n-$i in the experiment)
+    set n($i) [$ns node]
+    # Connect center to $n($i)
+    ns duplex-link $center $n($i) 100Mb 0ms DropTail
+}
+
+# Creation boilerplate
+$ns rtptoto Static
+$ns run
+}}}
+
+== A More Complex Topology ==
+
+The next few examples will build on one another to show a more complex change to a topology.  We will take a topology, find the degrees of nodes, assign operating systems to them based on that degree, and output DETER-ready ns2.
+
+To try this we need a more complex topology.  The program below creates a topology with {{{nrouters}}} completely connected routers, each of which has {{{nleaves}}} leaves, except for one central router that has none.