Version 13 (modified by Aaron Helsinger, 9 years ago) (diff)


GEC22 Developer Roundtable

This is an informal session for GENI developers to discuss details of software integration, and software issues that affect multiple control frameworks or tools. Note that this session is separate from the parallel experimenter and operations drop-in session.


Thursday, 9.00am - 10.30am & 11.00am - 12.30pm

Session Leaders

Tom Mitchell
Aaron Helsinger

Agenda / Details

This software development session provides an opportunity for GENI developers to collaborate informally. Topics are TBD based on topics raised by the GENI developers in attendance. The agenda is currently in discussion on the dev at mailing list. Candidate topics are detailed below.

Cross Slice Stitching

We had an interesting conversation about this topic at GEC21. To run a service in a slice, like Choice Net or other FIA architecture, or VTS, requires connecting multiple slices. Today, that requires using shared VLANs. Is there a better way?

  • Does a slice provision a special 'port'?
  • Does a slice that wants to accept connections do something at reservation time? After the resources are provisioned?
  • How are clients authorized to connect?
  • Note that some kinds of cross slice connections are possible now, but somewhat difficult.

Cross Testbed Federation

The Open MultiNet discussions covering GENI/FIRE collaboration, translating RSpecs and NDL based ontologies, and related topics could be a substantive conversation. Check out

  • On what level should testbeds federate?

Resource Queries

The AM API allows tools to ask for everything that an aggregate has (optionally filtered to what is currently available). But it provides no standard way to ask for only what the tool wants; the tool must parse the full response to find what it wants. This capability would better support tools trying to help with topology embedding.

  • Could we support an option (e.g. geni_query) in some query language (SPARQL?), allowing aggregates to support richer resource queries?
  • Should this be a separate and optional service, or part of the AM API?
  • How would an aggregate advertise the ontology or internal namespace it uses, to allow formulating reasonable queries?

Note that this is a small piece of a potential other topic: allowing RDF format RSpecs. But that larger topic has gotten some push-back.

Update Regression Tests

Sometimes after software or system updates, existing pieces of basic functionality are broken. Are there basic regression tests that we can do as part of developing any updates and during upgrades to ensure that experimenters don't have to do our regression testing? Are there automated test frameworks we can use to do these tests?

  • test all AM API functions
  • test basic disk images
  • test standard RSpecs
  • ?

Listresources without authorization

Currently the AM API ListResources call requires both a valid certificate (authentication) and a user credential (authorization). To the extend to which Advertisements are not user specific, the credential is arguably not required. If we made the credential optional, then tools (with a valid and trusted GENI certificate) could pre-fetch Advertisements for use by multiple users.

Dynamically add bandwidth

For initial experiments, a small topology is appropriate for stitched links. But later experimenters may want to use a larger capacity link. Could we support an AM APIv3 PerformOperationalAction command to increase the capacity of stitched links? Do the networks support changing capacity without reprovisioning the links?

Session Summary