<?xml version='1.0'?>
-<!DOCTYPE platform SYSTEM "http://simgrid.gforge.inria.fr/simgrid/simgrid.dtd">
+<!DOCTYPE platform SYSTEM "https://simgrid.org/simgrid.dtd">
<platform version="4.1">
- <zone id="world" routing="Full">
- <!-- this platform models 3 clusters, interconnected over the Internet
- --
- -- This example intends to be somewhat exhaustive, your platform should probably be simpler.
- --
- -- In particular, the clusters are modeled in very different ways,
- -- but you should pick the way you prefer, and stick to it.
- -->
+ <!-- _________
+ | |
+ | router |
+ ____________|__________|_____________ backbone link
+ | | | | | |
+ l0| l1| l2| l97| l96 | | l99
+ | | | ........ | | |
+ | |
+ node-0.simgrid.org node-99.simgrid.org
+
+ The route from node-0 to node-2 is: l0.UP ; backbone ; l2.DOWN
- <!-- Here comes the first cluster, the simplest one.
-
- Every nodes are connected through a private link to a router
- (ie a machine that cannot host computations).
-
- node-0.1core.org --[l0]--
- \
- node-1.1core.org --[l1]-- router -- (outer world)
- ... /
- node-7.1core.org --[l9]--
-
-
- So the route from node-0 to node-1 is {l0.UP, l1.DOWN}
- -->
- <cluster id="simple" prefix="node-" radical="0-7" suffix=".1core.org" speed="1Gf" bw="125MBps" lat="50us" />
-
-
- <!-- This second cluster has a backbone link, connecting all private links:
-
- node-0.2cores.org --[l0]-------+
- |
- node-1.2cores.org --[l1]--[backbone]-- router -- (outer world)
- ... |
- node-7.2cores.org --[l7]-------+
-
-
- The route from node-0 to node-1 is: l0.UP ; backbone ; l1.DOWN
-
The route from node-0 to the outer world begins with: l0.UP ; backbone
- -->
- <cluster id="backboned" prefix="node-" radical="0-7" suffix=".2cores.org"
- speed="1Gf" core="2"
- bw="125MBps" lat="50us"
+ -->
+ <cluster id="cluster0" prefix="node-" radical="0-99" suffix=".simgrid.org"
+ speed="1Gf" bw="125MBps" lat="50us"
bb_bw="2.25GBps" bb_lat="500us"/>
-
-
- <!-- This cluster has a backbone link, but no links are splitduplex.
- -- It means that up and down communications compete as if they
- -- were using exactly the same resource. If you send and receive
- -- at the same time, then each get half of the bandwidth.
- --
- -- Also, the hosts have 4 cores.
- -->
- <cluster id="halfduplex" prefix="node-" radical="0-7" suffix=".4cores.org" speed="1Gf" core="4"
- bw="125MBps" lat="50us" sharing_policy="SHARED"
- bb_bw="2.25GBps" bb_lat="500us" bb_sharing_policy="SHARED" />
-
-
- <!-- And now, we create the routes between the clusters, ie inter-zone routes -->
-
- <!-- We have only one outer link, representing the internet
- -- Its sharing is FATPIPE, meaning that communications have no impact on each others.
- -- Any given comm can use the full provided bandwidth.
- --
- -- This models the big links constituting the backbone of the internet,
- -- that users cannot saturate.
- -- Users' bandwidth is mostly limited by their outgoing connexion,
- -- not by the network backbone. -->
-
- <link id="backbone" bandwidth="1.25GBps" latency="500us" sharing_policy="FATPIPE"/>
-
- <zoneRoute src="simple" dst="backboned"
- gw_src="node-simple_router.1core.org"
- gw_dst="node-backboned_router.2cores.org">
- <link_ctn id="backbone" />
- </zoneRoute>
-
- <zoneRoute src="simple" dst="halfduplex"
- gw_src="node-simple_router.1core.org"
- gw_dst="node-halfduplex_router.4cores.org">
- <link_ctn id="backbone" />
- </zoneRoute>
-
- <zoneRoute src="backboned" dst="halfduplex"
- gw_src="node-backboned_router.2cores.org"
- gw_dst="node-halfduplex_router.4cores.org">
- <link_ctn id="backbone" />
- </zoneRoute>
-</zone>
</platform>
