Version 1 (modified by 11 years ago) (diff) | ,
---|
GR-ADM-4: Emergency Stop Test
This page captures status for the test case GR-ADM-4. For additional information see the Acceptance Test Status - May 2013? page overall status, or the GRAM Acceptance Test Plan? for details about the planned evaluation.
Last Update: 2013/05/14"
Step | State | Notes | Tickets |
Step 1 | Fail | Emergency stop is not supported for the initial evaluation | |
Step 2 | Fail | ||
Step 3 | Fail | ||
Step 4 | Fail |
State Legend | Description |
Pass | Test completed and met all criteria |
Pass: most criteria | Test completed and met most criteria. Exceptions documented |
Fail | Test completed and failed to meet criteria. |
Complete | Test completed but will require re-execution due to expected changes |
Blocked | Blocked by ticketed issue(s). |
In Progress | Currently under test. |
Test Plan Steps
Evaluation note: Emergency stop is not supported for the initial evaluation.
Step 1. GMOC Emergency Stop procedure availability
GMOC's updated Emergency Stop procedure is approved and published on a public wiki.
Step 2. GRAM Shutdown procedure availability
GRAM's procedure for performing a shutdown operation on any type of sliver in an GRAM rack is published on a public wiki or on a protected wiki that all GRAM site administrators (including GPO) can access.
Step 3. Schedule Emergency Stop
An Emergency Stop test is scheduled at a convenient time for all participants and documented in GMOC ticket(s).
Step 4. Execute Emergency Stop
A test experiment is running that involves a slice with connections to at least one GRAM rack compute resource.