support stitch points

[ahelsing]

Ensure stitcher supports stitch points - stitching to arbitrary endpoints supported by aggregates

EG seems to define an external_ref in the ad to hold the interface, and that interface_ref will be on a link showing what is connected to that point.

IG seems to define a fake node holding that interface, and you can request a link / lan to connect to that interface.

Imported from trac ticket #581, created by ahelsing on 03-28-2014 at 10:47, last modified: 01-30-2015 at 13:39

[ahelsing]

To do

• confirm this understanding
• maybe try to make these consistent?
• are the interfaces in the stitching extension, with available VLAN tags defined?
• What has to happen for stitcher to support this?

Trac comment by ahelsing on 03-28-2014 at 10:48

[ahelsing]

Emailed Marshall @ GRAM support, and Ilya to clarify how it works in EG

Trac comment by ahelsing on 03-31-2014 at 15:23

[ahelsing]

Brecht does interesting things here in Fed4Fire. He says:

- indeed we have also ports at our protogeni which are just loose ports
at the switch where other things can be connected. So these are defined
in protogeni and you use the node as follows:
(you see the component_id)

This is a complete port defined as a node ! (untagged)

    <node client_id="sw741"
component_id="urn:publicid:IDN+wall1.ilabt.iminds.be+node+switch2-7-41"
component_manager_id="urn:publicid:IDN+wall1.ilabt.iminds.be+authority+cm"
exclusive="true">
        <sliver_type name="raw-pc">
          <disk_image
name="urn:publicid:IDN+emulab.net+image+emulab-ops:GENERICDEV"/>
      </sliver_type>
        <jFed:location x="433.0" y="188.0"/>
        <jFed:nodeDescription>physical-node</jFed:nodeDescription>
        <interface client_id="sw741:if0">
            <ip address="10.0.0.2" netmask="255.255.255.0" type="ipv4"/>
        </interface>
    </node>

- but what we actually do, is stitch to fake testbeds (meaning they have
no AM yet) with vlans all on a single port for several testbeds, and for
this you need to trigger stitching ports (which make tagged traffic on
defined ports). So in our case we have 5 testbeds behind a single
gigabit port. (so you can have multiple slices at the same moment on
different vlans)

Trac comment by ahelsing on 06-30-2014 at 11:13