Changes between Version 15 and Version 16 of wish-list

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

--

Legend:

Unmodified
Added
Removed
Modified
  • wish-list

    v15 v16  
    2626 
    2727  * remoting the management interface 
     28  * Add 'exportAll' to the AM config file 
     29  * Add instantiating a controller from config file vs. GUI 
    2830 
    2931== Features to test, verify, cleanup, document ==  
     
    9092 * small/medium/large (independent of broker policy) 
    9193 * in-progress additions to handler catalog: EBS, sunfish storage, xcat, I2/ION 
     94 * Support Q-in-Q. 
     95 * EC2/Euca 
     96   * Allow passing instance size as a parameter from controllers (and NDL) 
     97 * Sherpa needs support for dealing with a pool of predefined VLANs 
     98 * Network drivers 
     99   * Improve 6509 driver performance by caching login sessions 
     100   * 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. 
     101   * Add returning basic configuration errors, e.g., existing vlan or vlan mapping. 
     102   * Add vlan translation to ex3200 
     103{{{ 
     104ckh# set vlans ORCA-test-Hadoop interface ge-0/0/0.0 mapping 10 ? 
     105Possible completions: 
     106+ apply-groups         Groups from which to inherit configuration data 
     107+ apply-groups-except  Don't inherit configuration data from these groups 
     108 push                 Push additional tag on packet 
     109 swap                 Translate VLAN tag for the packet 
     110[edit] 
     111}}} 
    92112 
    93113== Extensions to staged core workflow == 
     
    124144    * 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.  
    125145   * Review the code for static members and general structure 
    126    * Support Q-in-Q. 
    127146   * Multipoint BEN and Sherpa 
    128147   * 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.