History

Feature List and Draft Planning for OMF 5.3.X and 5.4¶

The items below are presented in the order of priority in terms of implementation.

1. New Features required for GEC9 Demonstrations (Deadline: October 25 - GEC9 date: November 2-4)¶

A - Extend the support for mobile disconnected experiments:
- OML Proxy needs to support multiple disconnect/reconnect events (Jolyon)
- OMF needs to support global synchronisation of RC on particular events -- note: Ivan said this would be optional for the demos, thus has a lower priority
- Issues: #393

B - AM support for WiMAX: (Ivan)
- this will be developed by Ivan at WINLAB, but requires technical advices from NICTA

C - OMF Support for resources that do not have a CMC (Christoph, Jolyon, Thierry)
- Issue 1: a laptop has no CMC, but the EC makes a CMC call to turn on all resources at the beginning of experiment
- Issue 2: the EC request the list of all available resources at the beginning of the experiments, which results in a CMC/Inventory call
- Proposed solution: we discussed a design during our OMF meeting (Wednesday, September 1) and assigned associated tasks, the details are on this other wiki page.
- Issues: #386 #387 #388 #389

D - Instrumentation of AM services with OML: (Jolyon and Ivan)
- AM services (e.g. frisbee, cmc,...) should use OML to collect and store usage information and other relevant stats
- AM services should have access to OML collected stats as inputs for their decisions algorithms (e.g. WiMAX AM Service would use measurements in making resource allocation decisions)
- Issues: #392

E - OML streams should be able to go to multiple arbitrary consumers (Jolyon)
- for example: from one producer, stream X would go to consumer 1 and 2, while stream Y would go to consumer 3
- Note: this feature is already available in current OML 2.3.9/2.4 - The task here would be to write at least a simple example/tutorial to show how to use it.
- Issues: #393

F - Proper GPS Support in OMF/OML: (Christoph)
- use GPSD to make GPS information available to both local EC/RC (via OML) for local GPS-triggered events and remote OML server for overall experimental measurements.
- Issues: #391

G - OEDL Support for measurement-triggered Events: (Thierry)
- allow users to describe events which will be triggered by operations on measurement values
- Issues: #390

H - EC Support for improved visualisation, i.e. display of graphs on the EC webpage (Max)
- Issues: #438

I - Low Priority: AM support for OpenFlow switches and the interface of ION L2-connectivity setup
- needs access and documentation to both to be able to develop this

A - Flexible new device handing mechanism:
- Required feature:
  - allow experimenter to easily add/define new devices
  - allow experimenter to use custom drivers for the device (arbitrary list/combination)
  - allow experimenter to define custom mapping between OEDL interface names and OS interface names

B - Support for Generic Virtualisation scheme:
- Resource Manager should accept commands to create slivers with different types, e.g. exclusive-use (no virtual machine), openvz, kvm

C - Integration of new Graph generation code to OMF
- Max has another graph engine and graph types, which should be included and tested with EC

D - Support for Slice Creation and Resource Association to Slice:
- we need OMF interface to create slice: for us this is just creating the pubsub groups for the slice
- we need OMF interface to associate resources to a slice, this job could be done by the resource manager?

F - Implementation of Phase 2 of PlanetLab Integration, as described on the OMF/SFA integration document

G - Extension of current Authentication/Authorisation Scheme
- fully implement the certificate & assertion-based authentication/authorisation scheme

H - OEDL commands to access Inventory information
- We need a mechanism to allow experimenters to get resource-specific inventory information (and use them) in their experiment scripts
- Use of a "ping" message to the pubsub group of the resource, which would be replied to by a "pong+info" message?

A - Remaining issues with AM refactoring with PubSub XMPP support:
- EC should not have

C - Create/extend existing testing suites for OMF component:
- extend the set of existing operational tests (i.e. simple self-checking experiments)
- create whenever required unit tests for OMF components such as AM classes
- develop a larger framework to automatically test OMF build deployment (e.g. using virtual machines)

D - Move EC's built-in experiment repositories to a web portal
- we should move the application and prototype definitions in repository/test/{app,proto,exp} to our web portal

D - Move EC deferred sending queues from the Node & NodeSet classes down to the communicator class