Changes between Version 3 and Version 4 of NewImpl


Ignore:
Timestamp:
Aug 20, 2013 3:13:25 PM (7 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewImpl

    v3 v4  
    4848  * support development of the DBI
    4949  * allow simultaneously creating a new minimal access web interface that will become the default interface
    50  2. Migrate user and permissions function into the new interface - 2 weeks
     50 2. Migrate user and permissions function into the new interface
    5151  * At this point parallel policy development tool development can begin
    52  3. Build the in-testbed processes that use the containers API for configuration - 1 month
     52 3. Build the in-testbed processes that use the containers API for configuration
    5353  * A transition plan for existing images is also required here
    54  4. Complete integration of testbed API and containers API - 2 weeks
     54 4. Complete integration of testbed API and containers API
    5555  * At this point a transitional web DB will be in place
    5656 5. Allow dual testbed use through either interface - new users on new interface
    5757 6. After about 1 month, shut down old interfaces.
     58
     59
     60== Short Term Schedule and Milestones ==
     61
     62 * Access Control integrated with API calls
     63   * '''Milestone 23 Aug''' demonstrate access controlled calls to API
     64     * Subset of regression tests demonstrate access control in place
     65 * Front end access to Experiments
     66   * '''Milestone 28 Aug''' Wiki documnetation of Emulab integration plan for meshing new interface to Emulab (matching DETER & Emulab users, reconciling Emulab Projects and DETER circles)
     67   * '''Milestone 30 Aug''' Wiki documentation of Specification of internal representation of experiment topology this is a spec of what we store and how for experiment topologies and how they become emulab/containers topologies.  For actions, data gathering, and constraints placeholder files will be used.  These will be expanded.
     68   * '''Milestone 6 Sept''' Working Experiment API calls that access saved but realistic experiment topologies and placeholder files on other axes.  Initial subset of regression tests.
     69
     70 * Experiment Back-end
     71   * '''Milestone 11 Sept''' demonstrate connection of DETER users to Emulab users.  API creation of user on E-in-E results in correct creation of Emulab users and projects as outlined in the 28 Aug milestone.
     72   * '''Milestone 18 Sept''' can create physical node-only experiment from interface on e-in-e.
     73   * '''Milestone 27 Sept''' can create containerized experiment on e-in-e with virtual machines.