Re: [help] Documentation of topology tag in FOAM rspec advertisement.

[Niky Riga]

Hi Adithya,

I am forwarding your email to geni-users[1] that has the right set of
people to help with that.

Cheers,
Niky

[1] If you are not a member please sigh up here:
http://groups.google.com/group/geni-users

Adithya Raju Yavanamanda wrote:
> Hi,
>
> I have been working with the FOAM rspec tag, I noticed that some of
> advertisements have topology tag which isn't part of the standard FOAM
> rspec. Its parent tag is port and name space
> http://geni.bssoftworks.com/rspec/ext/topo/1.
>
>
> I looked around the geni.net <http://geni.net/> and groups.geni pages
> and I couldn't find any information about the tag.
>
> Are there any resources or people you could point me to for some more
> information?
>
> --
> Thanks & Regards,
> Adithya Raju.

[Nicholas Bastin]

Adithya Raju Yavanamanda wrote:

I have been working with the FOAM rspec tag, I noticed that some of
advertisements have topology tag which isn't part of the standard FOAM
rspec. Its parent tag is port and name space
http://geni.bssoftworks.com/rspec/ext/topo/1.


I looked around the geni.net <http://geni.net/> and groups.geni pages
and I couldn't find any information about the tag.

Are there any resources or people you could point me to for some more
information?

The topology extension is intended to help you understand where ports are connected in OpenFlow topologies in the GENI mesoscale.  The tags should be relatively self explanatory, and can describe connections internal to an aggregate as well as (more usefully) connections to other aggregates.  For example, Internet2 has a relatively complete set of topology information, of the form:

    <openflow:port name="GBE0/1" num="1">

      <topology:geni-of desc="GPO" remote-component-id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:12:e2:b8:a5:d0" remote-port-name="GBE0/13"/>

    </openflow:port>

The "desc" attribute is free-form text - meant to be human readable and hint to a human where this port connects.  The "remote-component-id" attribute is the component_id of the remote datapath that is at the end of this link - it is intended to be used by tools (or humans) to make it easier to write rspecs that build topologies across the federation.  The "remote-port-name" is the name of the port on that datapath, also necessary for making a request rspec.

There are other variants of the tag (connections to PG nodes, unknown devices, etc.), but the most useful ones are typically the topology:geni-of variety.

--

Nick