Changes between Version 19 and Version 20 of wish-list

Show
Ignore:
Timestamp:
08/19/14 17:36:20 (5 years ago)
Author:
ibaldin (IP: 152.54.9.232)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • wish-list

    v19 v20  
    77 * Two-pass stitching and dynamic stitching, modify support 
    88  * Pieces of the slice described by separate pieces of NDL. Pieces of aggregates coming and going to/from the slice. 
    9   * modify() entry point 
     9  * ~~modify() entry point~~ 
    1010   * sliver restart as example of modify 
    11    * workflow-driven slice evolution 
     11   * ~~workflow-driven slice evolution~~ 
    1212 * Group Allocation (atomic allocations of resources) 
    1313    * Scheduling of a group allocation around the bottleneck resource (advance reservations) 
     
    1919 * Administration and robustness 
    2020  * reset inventory delegations at the broker: forget old delegations, or try to renew them 
    21   * AM full restart or hard reset: clean the substrate, and reissue delegations.  Rejects old tickets and leases? 
    22   * AM full restart: how to rebuild delegations? 
    23   * slice reclamation on AM and broker: time out an empty slice 
     21  * ~~AM full restart or hard reset: clean the substrate, and reissue delegations.  Rejects old tickets and leases?~~ 
     22  * ~~AM full restart: how to rebuild delegations?~~ 
     23  * ~~slice reclamation on AM and broker: time out an empty slice~~ 
    2424  * SM query/discovery of reservations in the slice; poll/request lease status 
    2525  * AM query interfaces: slices per user, leases per slice, identify by IP or vlan 
    26   * GMOC monitoring feed: faithful AMs publish an asynchronous stream "feed" of sliver create/renewal notifications to ST. 
     26  * ~~GMOC monitoring feed: faithful AMs publish an asynchronous stream "feed" of sliver create/renewal notifications to ST.~~ 
    2727 
    2828== Administration == 
    2929 
    30   * remoting the management interface 
     30  * ~~remoting the management interface~~ 
    3131  * Add 'exportAll' to the AM config file 
    32   * Add instantiating a controller from config file vs. GUI 
     32  * ~~Add instantiating a controller from config file vs. GUI~~ 
    3333 
    3434== Features to test, verify, cleanup, document ==  
    35  * extension packages 
     35 * ~~extension packages~~ 
    3636   * AM side: handlers for new resource types 
    3737   * SM side: controller/handler/view 
    38  * SM controller classes and interfaces 
     38 * ~~SM controller classes and interfaces~~ 
    3939 * SM-side handler and stitching, e.g., for elastic Condor 
    4040 * pushbutton Euca site deploys with NDL cookbook, including IP connectivity, canned xCAT images, etc. 
    41  * Error reporting/logging from NDL processors 
    42  * error reporting/logging from handlers 
    43  * error reporting distinguishes authorization failure vs. resource limit vs. internal error vs. user error 
     41 * ~~Error reporting/logging from NDL processors~~ 
     42 * ~~error reporting/logging from handlers~~ 
     43 * ~~error reporting distinguishes authorization failure vs. resource limit vs. internal error vs. user error~~ 
    4444 * ~~Ticket validation, including signature failure~~ and oversubscription, and rejection path 
    4545 * Ticket rejection and cleanup at SM and broker 
     
    5252 * AM probe detects resource failure, updates containing lease 
    5353 * interdomain path computation across multiple brokers 
    54  * openflow handler 
     54 * ~~openflow handler~~ 
    5555 
    5656== Advance reservations == 
     
    6767 
    6868== Broker resource policies: wish list == 
    69  * generic web view for admin approval of slices and reservations 
    70  * broker resource menu with fixed prices and budgets 
     69 * ~~generic web view for admin approval of slices and reservations~~ 
     70 * ~~broker resource menu with fixed prices and budgets~~ 
    7171 * attribute-based shares or quotas, with policy plugin view to manipulate them 
    7272 * congestion pricing 
    7373 * stackable broker policies 
    74  * euca instance size selection (small/medium/large properties/handlers) 
     74 * ~~euca instance size selection (small/medium/large properties/handlers)~~ 
    7575 * map global type attributes specified by SM into candidate pool IDs (site selection) 
    7676 * VM placement (site selection) based on data location  
     
    8484 * per-site policies: ACLs by idp.attribute (test case: RENCI cluster) 
    8585 * signed security attributes on images transported by Image Proxy 
    86  * GMOC back door: attribute-based authorization for slice shutdown  
     86 * ~~GMOC back door: attribute-based authorization for slice shutdown ~~ 
    8787 * SA module and/or actor 
    8888 
    8989== Handler infrastructure == 
    90  * Config handler invocation: threadpool, synchronization, and new scripting support 
     90 * ~~Config handler invocation: threadpool, synchronization, and new scripting support~~ 
    9191 * dynamic interposition/withdrawal of perfsonar  
    9292 * handler-driven sliver stitching: storage volume create/attach  
    9393 * small/medium/large (independent of broker policy) 
    9494 * in-progress additions to handler catalog: EBS, sunfish storage, xcat, I2/ION 
    95  * Support Q-in-Q. 
    96  * EC2/Euca 
    97    * Allow passing instance size as a parameter from controllers (and NDL) 
    98  * Sherpa needs support for dealing with a pool of predefined VLANs 
     95 * ~~Support Q-in-Q.~~ 
     96 * ~~EC2/Euca~~ 
     97   * ~~Allow passing instance size as a parameter from controllers (and NDL)~~ 
     98 * ~~Sherpa needs support for dealing with a pool of predefined VLANs~~ 
    9999 * Network drivers 
    100100   * Improve 6509 driver performance by caching login sessions 
    101101   * Consider separating adding a QoS profile to vlan from vlan creation. This may be needed to deal with vlan delays and in general give more flexibility. 
    102    * Add returning basic configuration errors, e.g., existing vlan or vlan mapping. 
     102   * ~~Add returning basic configuration errors, e.g., existing vlan or vlan mapping.~~ 
    103103   * Add vlan translation to ex3200 
    104104{{{ 
     
    118118 
    119119== Pushbutton slices/demos == 
    120  * Hadoop 
    121  * elastic Condor w/local DAGman 
     120 * ~~Hadoop~~ 
     121 * ~~elastic Condor w/local DAGman~~ 
    122122 * triangle and/or star, intradomain and interdomain cases 
    123123 * Harold's three-tier cloudscale 
     
    144144   * Describe site delegations in NDL (ILIA)  
    145145    * 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.  
    146    * Review the code for static members and general structure 
    147    * Multipoint BEN and Sherpa 
     146   * ~~Review the code for static members and general structure~~ 
     147   * ~~Multipoint BEN and Sherpa~~ 
    148148   * 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. 
    149149   * Improve Port to Port provisioning to allow the request to specify the specific ports name.  
    150    * Investigate persistent triple store from BBN http://parliament.semwebcentral.org/ 
     150   * ~~Investigate persistent triple store from BBN http://parliament.semwebcentral.org/~~ 
    151151   * Get port payload information out of the substrate RDF for the DTN switches 
    152152   * 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.