Changes between Version 14 and Version 15 of wish-list

Show
Ignore:
Timestamp:
07/21/11 17:00:06 (8 years ago)
Author:
ibaldin (IP: 152.54.6.148)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • wish-list

    v14 v15  
    1010    * Scheduling of a group allocation around the bottleneck resource (advance reservations) 
    1111 * Make !ResourceSet event-driven (per Aydan) 
     12    * Introduce queues in !ResourceSets; modifications to !ResourceSets should be done using a queue to avoid locking. 
    1213    * Will clean up a lot of code. 
    1314 * Fix renewable problems  #211 
     
    120121== NDL Integration == 
    121122 
    122  * Describe site delegations in NDL (ILIA)  
    123   * What I'm proposing is that in addition to an RDF file describing substrate there are one or more rdf files describing delegations, not dissimilar to the current request in rdf, where there is a topology description and then a Reservation object that lists members (URLs, unique names) of nodes and links that belong to the request. We can have a similar Delegation object class that is described inside a separate file referencing individuals from the substrate description. You can have several files describing several reservations (to e.g. different brokers). Since in RDF every delegation is a unique object with a unique name/URL, all that needs to be put in the export stanza of the config.xml file in this case is the URL of the delegation (and a reference to the rdf file describing it; note that there is not a one-to-one correspondence between files and delegations: they can all be in separate files or in one file). The config processor would need to rip the substrate RDF and the delegation RDFs which reference the objects in the substrate RDF, convert the delegations into unit counts and form traditional ORCA delegations that are used internally. This has the advantage of not impacting internal logic, but bringing order to the use of RDF as a resource description mechanism in ORCA without manually replicating delegation information in config.xml as is done today.  
     123   * Describe site delegations in NDL (ILIA)  
     124    * What I'm proposing is that in addition to an RDF file describing substrate there are one or more rdf files describing delegations, not dissimilar to the current request in rdf, where there is a topology description and then a Reservation object that lists members (URLs, unique names) of nodes and links that belong to the request. We can have a similar Delegation object class that is described inside a separate file referencing individuals from the substrate description. You can have several files describing several reservations (to e.g. different brokers). Since in RDF every delegation is a unique object with a unique name/URL, all that needs to be put in the export stanza of the config.xml file in this case is the URL of the delegation (and a reference to the rdf file describing it; note that there is not a one-to-one correspondence between files and delegations: they can all be in separate files or in one file). The config processor would need to rip the substrate RDF and the delegation RDFs which reference the objects in the substrate RDF, convert the delegations into unit counts and form traditional ORCA delegations that are used internally. This has the advantage of not impacting internal logic, but bringing order to the use of RDF as a resource description mechanism in ORCA without manually replicating delegation information in config.xml as is done today.  
     125   * Review the code for static members and general structure 
     126   * Support Q-in-Q. 
     127   * Multipoint BEN and Sherpa 
     128   * Represent IP address assignment for multiple VMs per site in the RDF request. Need to parse IP range in the controller and pass to the VMControl policy. 
     129   * Improve Port to Port provisioning to allow the request to specify the specific ports name.  
     130   * Investigate persistent triple store from BBN http://parliament.semwebcentral.org/ 
     131   * Get port payload information out of the substrate RDF for the DTN switches 
     132   * For BEN, in the case of multiple connections between different pair of devices, a connection may consist of portions of cross-layer segments and existing Ethernet virtual connection segments, need to review and run more tests to make sure the release actions in different orders are correct. 
     133   * ~~Can we have controller (ID controller) query NDL's on demand instead of only in the beginning.~~ 
     134   * ~~Should improve the performance of the label assignment policy and label range update utility in the model.~~  
     135   * ~~May need to get rid of the domain name entry in the config.xml, and get it from the NDL when delegating resource pools.~~ 
     136   * ~~May need to get rid of the build.property in the handler to get the device information (name/address) out of the NDL file.~~ 
     137 
     138 * Can we use cytoscape to visualize our RDFs in a useful way (example: in the registry add an option to show a visualization of the delegated resources)?