Changes between Version 3 and Version 4 of GENIRacksProjects/AcceptanceTestsCriteria


Ignore:
Timestamp:
04/11/12 17:02:48 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIRacksProjects/AcceptanceTestsCriteria

    v3 v4  
    162162 * I.06. An experimenter can create and access a sliver containing a VM and a bare-metal node, each with a dataplane interface on the same VLAN. (C.1.c)
    163163 * I.07. If an experimenter creates a sliver containing a VM and a bare-metal node, each with a dataplane interface on the same VLAN, the nodes can communicate on that VLAN. (C.1.c) 
    164  * I.19. An experimenter can request an unbound exclusive VLAN from a local aggregate manager in the rack, and dataplane traffic can be sent on that VLAN and seen on the campus's primary dataplane switch. (C.2.e)
    165164 * I.20. An experimenter can allocate and run a slice in which a compute resource in the rack sends traffic via an unbound exclusive rack VLAN, traversing a dynamically-created topology in a core L2 network, to another rack's dataplane. (C.2.e)
    166165 * I.22. An experimenter can create and access an experiment which configures a bare-metal compute resource to have at least two logical dataplane interfaces with distinct MAC addresses. (G.2)
    … …  
    756755
    757756This section provides a list of Acceptance Criteria that are not verified as part of the System Acceptance Test effort.  The following Acceptance Criteria are "not part of" "or mapped to" not in any test case at this time:
    758 
     757 - I.19. An experimenter can request an unbound exclusive VLAN from a local aggregate manager in the rack, and dataplane traffic can be sent on that VLAN and seen on the campus's primary dataplane switch. (C.2.e)
    759758 - II.02. An experimenter can create a sliver including an unbound exclusive VLAN whose traffic is OpenFlow-controlled by a controller that they run. (C.2.f)
    760759 - II.06. An experimenter can run a controller (for any type of OpenFlow sliver) on a compute resource which they're requesting at the same time as the OpenFlow sliver, by specifying in the request which compute resource they want to use. (The AM can define how unbound this can be, e.g. "one of the VMs", or "the VM with this client_id", or whatever.) (C.2.f)