-Routing basic elements: hosts and links
-***************************************
-
-A platform is composed of a set of resources, namely hosts, links and disks.
-On these resources you may run activities that will require some capacity and
-will make the time advance.
-
-Given a look at this example of some hosts and links being declared
-
-.. code-block:: xml
-
- <zone id="AS5-4" routing="Full">
- <host id="host0" speed="1Gf"/>
- <host id="host1" speed="2Gf"/>
- <link id="link0" bandwidth="125MBps" latency="100us"/>
- </zone>
-
-It describes a simple FullZone with 2 hosts inside connected through
-a link. Note that the ``link0`` just represents a resource with a
-certain bandwidth capacity and latency. It's only when you add
-a route between ``host0`` and ``host1`` that this link will be used by
-SimGrid in the communications.
-
-.. code-block:: xml
-
- <zone id="AS5-4" routing="Full">
- ...
- <route src="host0" dst="host1"><link_ctn id="link0"/></route>
- </zone>
-
-Note that no verification is performed concerning the links you use in a route.
-This is quite flexible and enables interesting features. However, it also allows you
-to do some strange topologies, such as having a single link used by a pair
-of hosts from different zone:
-
-.. code-block:: xml
-
- <zone id="Nonsense" routing="Full">
- <host id="host3" speed="1Gf"/>
- <host id="host4" speed="2Gf"/>
- <route src="host3" dst="host4"><link_ctn id="link0"/></route>
- </zone>
-
-Probably you do not want to do this, but it's your responsibility to write
-your platform file properly. SimGrid will not try to be smarter than you!
-
-Describing routes: intra vs inter
-*********************************
-
-Intra zone
-==========
-
-TLDR: use :ref:`pf_tag_route`
-
-The communications inside a given zone is defined by ``routing=`` parameter
-in the :ref:`pf_tag_zone`. For example, in a *Full* zone, the user must declare
-a :ref:`pf_tag_route` for each pair of hosts inside the zone. Other zones, such as *Floyd*
-or *Dijkstra* will calculate the shortest path, while *DragonFly* and *Fat-Tree* uses
-specialized routing algorithms to improve performance.
-
-When adding a route inside a zone, keep in mind that you need 3 main parameters:
- - src: Host (or router) source
- - dst: Host (or router) destination
- - links: list of resources (links in this case) used in the communication
-
-Inter zone
-==========
-
-TLDR: use :ref:`pf_tag_zoneroute`
-
-When describing complex topologies, such as the one depicted in the beginning
-of this page, you will need to connected not only hosts but zones too. The rationale
-behind a route between zone is exactly the same as for hosts. The only difference is
-the 2 new gateway parameters in the syntax of :ref:`pf_tag_zoneroute`.
-
-A zone is not a physical resource, just a collection of resources. Consequently, you
-need to describe the gateway, i.e. the physical resource inside the zone used for the route.
-It gives you 4 parameters to describe a zoneRoute:
- - src: The object of source zone
- - dst: The object of destination zone
- - gw_src: Gateway inside src zone. A Host (or router) belonging to src zone.
- - gw_dst: Gateway inside dst zone. A Host (or router) belonging to src zone.
- - links: Links that connect gw_src to gw_dst.
-
-.. note:: You must be careful to call zoneRoute with the correct parameters: zones for src and dst, and hosts/routers for gw_src and gw_dst
-
-.. warning:: SimGrid does not have the concept of default gateway/router. Each zoneRoute must describe the appropriate gateways which may be different for each route.
-
-Calculating the routes
-**********************