GENI-NSF / geni-tools

Omni, stitcher, GCF sample aggregate manager, and other GENI tools.
Other
11 stars 15 forks source link

Handle different capacity units at ExoGENI #678

Closed ahelsing closed 9 years ago

ahelsing commented 9 years ago

At ExoGENI, capacity is in bps. Everywhere else it is in kbps.

Somehow handle this in stitcher.

Imported from trac ticket #678, created by ahelsing on 08-04-2014 at 15:48, last modified: 10-18-2014 at 11:35

ahelsing commented 9 years ago

Perhaps stitcher can edit the capacity attributes on the right pieces of the request rspec before submitting to EG based AMs.

Trac comment by ahelsing on 08-04-2014 at 15:52

ahelsing commented 9 years ago

Luisa says:

Having different properties seems to work.  Using the following capacities:

  <link client_id="link-eggpo-ig">
    <component_manager
name="urn:publicid:IDN+exogeni.net:bbnvmsite+authority+am"/>
    <interface_ref client_id="eg-gpo:if0"/>
    <property source_id="eg-gpo:if0" dest_id="ig-rut:if0"
capacity="100000000"/>
    <component_manager
name="urn:publicid:IDN+instageni.rutgers.edu+authority+cm"/>
    <interface_ref client_id="ig-rut:if0"/>
    <property source_id="ig-rut:if0" dest_id="eg-gpo:if0"
capacity="100000"/>
  </link>

I am able to get 100 Mbps between EG GPO and Rutgers IG. 

Trac comment by ahelsing on 08-04-2014 at 16:21

ahelsing commented 9 years ago

Ilya confirms they are only looking at link properties to date.

Trac comment by ahelsing on 08-05-2014 at 11:27

ahelsing commented 9 years ago

Ilya says his RSpec converter could change the units. So we'd have nothing to do except update documentation.

Trac comment by ahelsing on 08-05-2014 at 13:31

ahelsing commented 9 years ago

On 8/5 I asked Ilya:

f you can do the conversion in any place you care about the listed capacity, then we can treat it as in kbps.

While you're there if it is easy, you might put in support for units on capacity. Handle one of these: G, g, Gbps, gbps, M, M, Mbps, mbps, K, k, Kbps, kbps, B, b, bps

Or return an error if the parser can't handle the listed units.

Pinged him just now to ask for a status update.

Trac comment by ahelsing on 09-05-2014 at 08:56

ahelsing commented 9 years ago

Ilya says it is still on his list to do this, but doesn't want to touch this right now during the upgrade to Orca 5.

Trac comment by ahelsing on 09-08-2014 at 16:07

ahelsing commented 9 years ago

Ilya today seems to have an update to the converter to handle this. It handles units. If there is a conflict between the main body and the extension, it uses the main body.

Test this and then clean up the documentation.

Trac comment by ahelsing on 10-17-2014 at 16:27

ahelsing commented 9 years ago

Ilya deployed the change.

Trac comment by ahelsing on 10-18-2014 at 10:34