Changes between Version 5 and Version 6 of GENIRacksProjects/AcceptanceTestsCriteria

Timestamp:

04/11/12 17:25:06 (12 years ago)

Author:

tupty@bbn.com

Comment:

Added notes for which ACs are not verified in ExoGENI but are verified in InstaGENI

GENIRacksProjects/AcceptanceTestsCriteria

@@ -859 +859 @@
 
 This 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:
- - 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)
+ - 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) [Verified in InstaGENI test plan, not in ExoGENI test plan] 
  - 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)
  - 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)
@@ -867 +867 @@
  - I.14. An experimenter can create and access a sliver containing a compute resource in the rack with dataplane interfaces connected to multiple bound VLANs. (C.2.b)
  - I.16. An experimenter can create and access a sliver containing multiple compute resources in the rack with dataplane interfaces on each connected to multiple bound VLANs. (C.2.b)  
- - I.25. An experimenter can request a publically routable IP address or public TCP/UDP port mapping for the control interface of any compute resource in their sliver (subject to availability of IPs at the site), and can access their resource at that IP address and/or port from the commodity internet, and send traffic outbound from their resource to the internet. (F.1) 
+ - I.25. An experimenter can request a publically routable IP address or public TCP/UDP port mapping for the control interface of any compute resource in their sliver (subject to availability of IPs at the site), and can access their resource at that IP address and/or port from the commodity internet, and send traffic outbound from their resource to the internet. (F.1) [Verified in InstaGENI test plan, not in ExoGENI test plan] 
  - I.26. An experimenter can request a sliver which creates a layer 2 path, between two dataplane interfaces on the rack switch which connect to non-rack resources (e.g. a bound or unbound VLAN between the core and a campus compute resource), without requesting any rack compute resources. (use case 4) 
  - I.27. If the rack's control network cannot reach the control network at the rack vendor's home site but is working otherwise, an experimenter can create and access an experimental sliver containing a compute resource and a VLAN (assuming the experimenter's slice authority is reachable). (E)