wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-3

Version 1 (modified by Josh Smift, 7 years ago) (diff)

--

Detailed test plan for IG-ADM-3: Full Rack Reboot Test

This page is GPO's working page for performing IG-ADM-3. It is public for informational purposes, but it is not an official status report. See GENIRacksHome/InstageniRacks/AcceptanceTestStatus for the current status of InstaGENI acceptance tests.

Page format

  • The status chart summarizes the state of this test
  • The high-level description from test plan contains text copied exactly from the public test plan and acceptance criteria pages.
  • The steps contain things i will actually do/verify:
    • Steps may be composed of related substeps where i find this useful for clarity
    • Each step is either a preparatory step (identified by "(prep)") or a verification step (the default):
      • Preparatory steps are just things we have to do. They're not tests of the rack, but are prerequisites for subsequent verification steps
      • Verification steps are steps in which we will actually look at rack output and make sure it is as expected. They contain a Using: block, which lists the steps to run the verification, and an Expect: block which lists what outcome is expected for the test to pass.

Status of test

See GENIRacksHome/InstageniRacks/AcceptanceTestStatus for the meanings of test states.

Step State Date completed Open Tickets Closed Tickets/Comments
1A Color(#63B8FF,In Progress)?
1B Color(#63B8FF,In Progress)?
2A Color(#63B8FF,In Progress)?
2B Color(#63B8FF,In Progress)?


High-level description from test plan

In this test, a full rack reboot is performed as a drill of a procedure which a site administrator may need to perform for site maintenance.

Procedure

  1. Review relevant rack documentation about shutdown options and make a plan for the order in which to shutdown each component.
  2. Cleanly shutdown and/or hard-power-off all devices in the rack, and verify that everything in the rack is powered down.
  3. Power on all devices, bring all logical components back online, and use monitoring and comprehensive health tests to verify that the rack is healthy again.

Criteria to verify as part of this test

  • IV.01. All experimental hosts are configured to boot (rather than stay off pending manual intervention) when they are cleanly shut down and then remotely power-cycled. (C.3.c)
  • V.10. Site administrators can authenticate remotely and power on, power off, or power-cycle, all physical rack devices, including experimental hosts, servers, and network devices. (C.3.c)
  • V.11. Site administrators can authenticate remotely and virtually power on, power off, or power-cycle all virtual rack resources, including server and experimental VMs. (C.3.c)
  • VI.16. A procedure is documented for cleanly shutting down the entire rack in case of a scheduled site outage. (C.3.c)
  • VII.16. A public document explains how to perform comprehensive health checks for a rack (or, if those health checks are being run automatically, how to view the current/recent results). (F.8)

Step 1: Shut down the rack

Step 1A: Test functionality before shutting down the rack

Overview of Step 1A

Check the state of the rack before shutting down:

Make a note of anything that wasn't ok before shutting down, since it may not be ok after starting up, and if it isn't, that won't indicate a problem with the test.

Results of testing Step 1A on 2013-03-08

FIXME: Update the date to the date on which we actually do the test.

FIXME: Fill this in when we actually do the test.

Step 1B: Shut down all rack components

Overview of Step 1B

Shut everything down:

  • Browse to https://boss.instageni.gpolab.bbn.com/showpool.php, and use the table a the top of the page to identify which nodes are in the shared pool, and which are exclusive nodes.
  • Log in to boss, and from there:
    • Shut down the testbed:
      sudo testbed-control shutdown
      
    • Shut down the nodes:
      for node in pc{1..5} ; do sudo ssh $node shutdown -H now ; done
      
  • Log out of boss.
  • Log in to control, and from there:
    • Shut down all of the VMs that run there:
      sudo xm shutdown -a -w
      
    • Shut down control itself:
      sudo init 0 && exit
      

Visually verify that everything in the rack is powered off, and physically power off anything that isn't already.

Results of testing Step 1B on 2013-03-08

FIXME: Update the date to the date on which we actually do the test.

FIXME: Fill this in when we actually do the test.

Step 2: Start up the rack on

Step 2A: Start up all rack components

Overview of Step 2A

Turn everything on:

  • Power on the switches
  • Power on the control node
  • Wait for the contol node and its VMs to come up
  • Power on the experimenter nodes

Verify that everything in the rack is powered on.

Results of testing Step 2A on 2013-03-08

FIXME: Update the date to the date on which we actually do the test.

FIXME: Fill this in when we actually do the test.

Step 2B: Test functionality after starting up the rack

Overview of Step 2B

Check the state of the rack after starting up:

Make a note of anything that isn't ok now and *was* ok before shutting down.

Results of testing Step 2B on 2013-03-08

FIXME: Update the date to the date on which we actually do the test.

FIXME: Fill this in when we actually do the test.