Changes between Initial Version and Version 1 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-7


Ignore:
Timestamp:
08/13/12 15:40:42 (9 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-7

    v1 v1  
     1[[PageOutline]]
     2
     3= EG-ADM-7: Documentation Review Test =
     4
     5
     6This page captures status for the test case EG-ADM-7, which verifies the availability of Documentation for the ExoGENI rack. For overall status see the [wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus ExoGENI Acceptance Test Status] page.
     7
     8= Test Status =
     9This section captures the status for each step in the acceptance test plan.
     10
     11|| '''Step''' || '''State'''              || ''' Ticket ''' || '''Comments''' ||
     12
     13
     14[[BR]]
     15|| '''State Legend'''                     || '''Description'''                                                    ||
     16|| [[Color(green,Pass)]]                  || Test completed and met all criteria                                  ||
     17|| [[Color(#98FB98,Pass: most criteria)]] || Test completed and met most criteria. Exceptions documented          ||
     18|| [[Color(red,Fail)]]                    || Test completed and failed to meet criteria.                          ||
     19|| [[Color(yellow,Complete)]]             || Test completed but will require re-execution due to expected changes ||
     20|| [[Color(orange,Blocked)]]              || Blocked by ticketed issue(s).                                        ||
     21|| [[Color(#63B8FF,In Progress)]]         || Currently under test.                                                ||
     22[[BR]]
     23
     24
     25= Test Plan Steps =
     26
     27Documentation review criteria applied to each required document includes:
     28
     29 * The document has been provided in a public location
     30 * The document contains the required information.
     31 * The documented information appears to be accurate.
     32
     33
     34Documents to be reviewed include:
     35
     36
     37 1. ExoGENI Rack Installation Documentation
     38
     39 * Pre-installation document that lists specific minimum requirements for all site-provided services for potential rack sites (e.g. space, number and type of power plugs, number and type of power circuits, cooling load, public addresses, NLR or Internet2 layer2 connections, etc.).  This document should also list all standard expected rack interfaces (e.g. 10GBE links to at least one research network).
     40
     41 2. ExoGENI Rack Part List Documentation
     42
     43 * Summary GENI Rack parts list, including vendor part numbers for "standard" equipment intended for all sites (e.g. a VM server) and per-site equipment options (e.g. transceivers, PDUs etc.), if any.  This document should also indicate approximately how much headroom, if any, remains in the standard rack PDUs' power budget to support other equipment that sites may add to the rack.
     44
     45
     46 3. ExoGENI Software Components Identification Documentation
     47
     48 * Procedure for identifying the software versions and system file configurations running on a rack, and how to get information about recent changes to the rack software and configuration.
     49
     50 4.ExoGENI and OS Upgrade Plans
     51
     52 * Explanation of how and when software and OS updates can be performed on a rack, including plans for notification and update if important security vulnerabilities in rack software are discovered.
     53
     54 5. ExoGENI Software Components Functional Description and Access to Source code.
     55
     56 * Description of the GENI software running on a standard rack, and explanation of how to get access to the source code of each piece of standard GENI software.
     57
     58 6. ExoGENI Rack Resources Usage and Policy Documentation
     59
     60 * Description of all the GENI experimental resources within the rack, and what policy options exist for each, including: how to configure rack nodes as bare metal vs. VM server, what options exist for configuring automated approval of compute and network resource requests and how to set them, how to configure rack aggregates to trust additional GENI slice authorities, and whether it is possible to trust local users within the rack.
     61
     62 7. ExoGENI Rack Resources Administration
     63
     64 * Description of the expected state of all the GENI experimental resources in the rack, including how to determine the state of an experimental resource and what state is expected for an unallocated bare metal node.
     65
     66 8. ExoGENI Rack Administrative procedure for user accounts
     67
     68 * Procedure for creating new site administrator and operator accounts.
     69
     70 9.  ExoGENI Rack Administrative procedure for rack operations
     71 * Procedure for changing IP addresses for all rack components.
     72
     73 10. ExoGENI Rack Administrative procedure for rack scheduled shutdown
     74 * Procedure for cleanly shutting down an entire rack in case of a scheduled site outage.
     75
     76 10. ExoGENI Rack Administrative procedure for Emergency Stop.
     77 * Procedure for performing a shutdown operation on any type of sliver on a rack, in support of an Emergency Stop request.
     78
     79 11. ExoGENI Rack Administrative procedure for health status
     80 * Procedure for performing comprehensive health checks for a rack (or, if those health checks are being run automatically, how to view the current/recent results).
     81
     82 12. ExoGENI Rack Site Operations documentation
     83
     84 * Technical plan for handing off primary rack operations to site operators at all sites.
     85
     86 13. Site Specific ExoGENI Deployment Details Data should include:
     87
     88 * Per-site documentation.  This documentation should be prepared before sites are installed and kept updated after installation to reflect any changes or upgrades after delivery.  Text, network diagrams, wiring diagrams and labeled photos are all acceptable for site documents.  Per-site documentation should include the following items for each site:
     89   1.  Part numbers and quantities of PDUs, with NEMA input power connector types, and an inventory of which equipment connects to which PDU.
     90   2.  Physical network interfaces for each control and data plane port that connects to the site's existing network(s), including type, part numbers, maximum speed etc. (eg. 10-GB-SR fiber)
     91   3.  Public IP addresses allocated to the rack, including: number of distinct IP ranges and size of each range, hostname to IP mappings which should be placed in site DNS, whether the last-hop routers for public IP ranges subnets sit within the rack or elsewhere on the site, and what firewall configuration is desired for the control network.
     92   4.  Data plane network connectivity and procedures for each rack, including core backbone connectivity and documentation, switch configuration options to set for compatibility with the L2 core, and the site and rack procedures for connecting non-rack-controlled VLANs and resources to the rack data plane.  A network diagram is highly recommended (See existing !OpenFlow meso-scale network diagrams on the GENI wiki for examples.)