Changes between Initial Version and Version 1 of GENIRacksHome/OpenGENIRacks/AcceptanceTestStatusMay2013/OG-ADM-7


Ignore:
Timestamp:
05/23/14 11:35:27 (10 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIRacksHome/OpenGENIRacks/AcceptanceTestStatusMay2013/OG-ADM-7

    v1 v1  
     1= GR-ADM-7: Documentation Review Test =
     2
     3
     4This page captures status for the test case GR-ADM-7. For additional information see the [wiki:GENIRacksHome/GRAMRacks/AcceptanceTestStatusMay2013 Acceptance Test Status - May 2013] page overall status, or the [wiki:GENIRacksHome/AcceptanceTests/GRAMAcceptanceTestsPlan GRAM Acceptance Test Plan] for details about the planned evaluation.
     5
     6
     7
     8''Last Update: 2013/05/17"
     9
     10= Test Status =
     11
     12This section captures the status for each step in the acceptance test plan.
     13
     14|| '''Documentation'''                                                        ||'''State'''                                      || ''' Tickets ''' || '''Notes''' ||
     15||1. GRAM Rack Installation Documentation                                     ||[[span(Partial, style=background-color: orange)]]||#74                 ||             ||
     16||2. GRAM Rack Part List Documentation                                        ||[[span(Fail, style=background-color: red)]]      ||#75                 ||             ||
     17||3. GRAM Software Components Identification Documentation                    ||[[span(Pass: most criteria, style=background-color: #98FB98)]]||#76                 ||             ||
     18||4. GRAM and OS Upgrade Plans                                                ||[[span(Fail, style=background-color: red)]]      ||#77                 ||             ||
     19||5. GRAM Software Components Functional Description and Access to Source code||[[span(Partial, style=background-color: orange)]]||#78             ||
     20||6. GRAM Rack Resources Usage and Policy Documentation                       ||[[span(Fail, style=background-color: red)]]      ||#79                 ||            ||
     21||7. GRAM Rack Resources Administration                                       ||[[span(Fail, style=background-color: red)]]      ||#80                 ||            ||
     22||8. GRAM Rack Administrative procedure for user accounts                     ||[[span(Fail, style=background-color: red)]]      ||#81                 ||            ||
     23||9. GRAM Rack Administrative procedure for rack operations                   ||[[span(Fail, style=background-color: red)]]      ||#82                 ||            ||
     24||10. GRAM Rack Administrative procedure for rack scheduled shutdown          ||[[span(Fail, style=background-color: red)]]      ||#83              ||            ||
     25||11. GRAM Rack Administrative procedure for Emergency Stop.                  ||[[span(Fail, style=background-color: red)]]      ||#84              ||            ||
     26||12. GRAM Rack Administrative procedure for health status                    ||[[span(Fail, style=background-color: red)]]      ||#85              ||            ||
     27||13. GRAM Rack Site Operations documentation                                 ||[[span(Fail, style=background-color: red)]]      ||#86              ||            ||
     28||14. Site Specific GRAM Deployment Data                                      ||[[span(Fail, style=background-color: red)]]      ||#87              ||            ||
     29
     30
     31[[BR]]
     32|| '''State Legend'''                                           || '''Description'''                                                    ||
     33||[[span(Pass, style=background-color: green )]]                ||Documentation review completed and met all criteria                                  ||
     34||[[span(Pass: most criteria, style=background-color: #98FB98)]]||Documentation review completed and met most criteria. Exceptions documented  ||
     35||[[span(Fail, style=background-color: red)]]                   ||Documentation review completed and failed to meet criteria .                          ||
     36||[[span(Complete, style=background-color: yellow)]]            ||Documentation review completed but will require re-execution due to expected changes  ||
     37||[[span(Partial, style=background-color: orange)]]             ||Minimal Documentation was found                                          ||
     38||[[span(In Progress, style=background-color: #63B8FF)]]        ||Currently under review                                                 ||
     39
     40[[BR]]
     41
     42= GRAM Documentation Tests =
     43
     44The GRAM Documentation Tests focus on documentation review, and apply the following criteria for each document:
     45 * The document has been provided in a public location. This criteria failed to be met, all documentation is internal for initial evaluation.
     46 * The document contains the required information.
     47 * The documented information appears to be accurate.
     48
     49Rack documentation available and reviewed to find required information includes:
     50 * [https://superior.bbn.com/trac/bbn-rack/wiki/AdministrationGuide GRAM Administration Guide]
     51 * [https://superior.bbn.com/trac/bbn-rack/wiki/InstallationGuideRevised  GRAM Installation Guide - Revised]
     52 * [https://superior.bbn.com/trac/bbn-rack/wiki/ArchitectureDescription GRAM Network and Software Architecture Description]
     53 * [https://superior.bbn.com/trac/bbn-rack/wiki/TestGuide GRAM Testing Guide]
     54 * [https://superior.bbn.com/trac/bbn-rack/wiki/UserGuide  GRAM Users Guide]
     55 * [https://superior.bbn.com/trac/bbn-rack/wiki/BOSRackDetails BBN GRAM Rack Details]
     56
     57
     58
     59== 1. GRAM Rack Installation Documentation ==   
     60
     61'''The goal of this evaluation:'''
     62
     63To find 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).
     64
     65
     66'''Evaluation Results:''' [[span(Partial, style=background-color: orange)]]
     67
     68Found:  The page [https://superior.bbn.com/trac/bbn-rack/wiki/BOSRackDetails BBN GRAM Rack Details] has:
     69 - mentions of Power Control Units, but no information was found about any power requirements, power plugs circuits, cooling requirements.
     70 - points the reader to the [http://groups.geni.net/geni/wiki/GENIRacksHome#GENIStarterRacks Starter Rack] information, where device type information is found. 
     71 - has address information for the rack.
     72
     73Did not find:
     74 - pre-installation document that lists specific minimum requirements for all site-provided services.
     75
     76 
     77== 2. GRAM Rack Part List Documentation ==     
     78
     79
     80'''The goal of this evaluation:'''
     81
     82To find a summary GRAM 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.
     83
     84
     85'''Evaluation Results:'''  [[span(Fail, style=background-color: red)]]
     86
     87Found:
     88 - [https://superior.bbn.com/trac/bbn-rack/wiki/BOSRackDetails BBN GRAM Rack Details] points to [http://groups.geni.net/geni/wiki/GENIRacksHome#GENIStarterRacks Starter Rack] which give a list of major rack components
     89
     90Did not find:
     91 - There is no full parts list.
     92 - No information on headroom,or PDU power budget was found.
     93 
     94
     95 
     96== 3. GRAM Software Components Identification Documentation  ==       
     97
     98'''The goal of this evaluation:'''
     99
     100Find a 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.
     101
     102'''Evaluation Results:''' [[span(Pass: most criteria, style=background-color: #98FB98)]]
     103
     104Found:
     105 - Clearly defined components in [https://superior.bbn.com/trac/bbn-rack/wiki/ArchitectureDescription GRAM Network and Software Architecture Description].
     106 - Information for system configurations used in GRAM rack in the  [https://superior.bbn.com/trac/bbn-rack/wiki/InstallationGuideRevised  GRAM Installation Guide - Revised].
     107 - Pointer to gram-dev@bbn.com for software help.
     108
     109Did not find:
     110 - No document detailing software versions for software components
     111 - No information about recent configuration and software changes
     112 
     113
     114== 4. GRAM and OS Upgrade Plans   ==                     
     115
     116'''The goal of this evaluation:'''
     117
     118Find documentation that explains how and when GRAM 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.
     119
     120'''Evaluation Results:''' [[span(Fail, style=background-color: red)]]
     121
     122Found software update information in:
     123 - [https://superior.bbn.com/trac/bbn-rack/wiki/InstallationGuideRevised  GRAM Installation Guide - Revised] includes instructions for installing !OpenStack and GRAM on the control and compute nodes.
     124
     125Did not find:
     126 - Update plans for software
     127 - Notification process for updates
     128 - Security updates plans
     129 
     130== 5. GRAM Software Components Functional Description and Access to Source code ==   
     131   
     132'''The goal of this evaluation:'''
     133
     134Find documentation that provides a description of the GRAM software running on a standard rack, and explanation of how to get access to the source code of each piece of standard GENI software.
     135
     136'''Evaluation Results:''' [[span(Partial, style=background-color: orange)]]
     137
     138Found:
     139 - Clearly defined components in [https://superior.bbn.com/trac/bbn-rack/wiki/ArchitectureDescription GRAM Network and Software Architecture Description].
     140 - [https://superior.bbn.com/trac/bbn-rack/wiki/SoftwareRepository Software Repository] page, but no instructions for getting account.
     141
     142Did not find:
     143
     144 - Instruction on how to get access to each piece of Software required.
     145 - Instruction on how to get git account.
     146
     147 
     148== 6. GRAM Rack Resources Usage and Policy Documentation ==   
     149 
     150'''The goal of this evaluation:''' [[span(Fail, style=background-color: red)]]
     151
     152Find documentation that provides a 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.
     153
     154'''Evaluation Results:'''
     155
     156Did not find any Resources Usage and Policy documents.
     157
     158   
     159== 7. GRAM Rack Resources Administration ==               
     160
     161'''The goal of this evaluation:'''
     162
     163Find documentation that provides a 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.
     164
     165'''Evaluation Results:'''  [[span(Fail, style=background-color: red)]]
     166
     167Found:
     168 - [https://superior.bbn.com/trac/bbn-rack/wiki/UserGuide  GRAM Users Guide] give minimal insight into node roles in GRAM
     169 - [https://superior.bbn.com/trac/bbn-rack/wiki/BOSRackDetails BBN GRAM Rack Details] which defines the actual node settings for the GRAM Rack.
     170
     171
     172Did not find:
     173 - documentation that would give an administrator a description of the expected state of all the GENI experimental resources in the rack.
     174 
     175
     176== 8. GRAM Rack Administrative procedure for user accounts ==         
     177
     178'''The goal of this evaluation:'''
     179
     180Find documentation that provides a procedure for creating new site administrator and operator accounts.
     181
     182'''Evaluation Results:''' [[span(Fail, style=background-color: red)]]
     183
     184No document exists that defines how rack administrative and operator accounts are created.
     185
     186== 9.  GRAM Rack Administrative procedure for rack operations ==   
     187
     188'''The goal of this evaluation:'''
     189
     190Find documentation that provides a procedure for changing IP addresses for all rack components.
     191
     192'''Evaluation Results:'''   [[span(Fail, style=background-color: red)]]
     193
     194No document exists that defines how to change IP addresses for all rack components
     195
     196== 10. GRAM Rack Administrative procedure for rack scheduled shutdown == 
     197
     198'''The goal of this evaluation:'''
     199
     200Find documentation that provides a procedure for cleanly shutting down an entire rack in case of a scheduled site outage.
     201
     202'''Evaluation Results:''' [[span(Fail, style=background-color: red)]]
     203
     204No document exists that defines how to shutdown the entire rack for scheduled shutdowns. 
     205
     206     
     207== 11. GRAM Rack Administrative procedure for Emergency Stop. ==     
     208 
     209'''The goal of this evaluation:'''
     210
     211Find documentation that provides a procedure for performing a shutdown operation on any type of sliver on a rack, in support of an Emergency St
     212op request.
     213
     214'''Evaluation Results:'''  [[span(Fail, style=background-color: red)]]
     215
     216No document exists that defines Emergency Stop
     217
     218== 12. GRAM Rack Administrative procedure for health status ==   
     219     
     220'''The goal of this evaluation:'''
     221
     222Find documentation that provides a 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).
     223
     224'''Evaluation Results:'''  [[span(Fail, style=background-color: red)]]
     225
     226No document exists that defines health check procedures.
     227 
     228== 13. GRAM Rack Site Operations documentation ==     
     229 
     230'''The goal of this evaluation:'''
     231
     232Find documentation that provides a Technical plan for handing off primary rack operations to site operators at all sites.
     233
     234'''Evaluation Results:''' [[span(Fail, style=background-color: red)]]
     235
     236No hand-off procedures are defined for GRAM
     237
     238== 14. Site Specific GRAM Deployment Data ==               
     239   
     240'''The goal of this evaluation:'''
     241
     242Find documentation that provides Per-site deployment details/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:
     243
     244   1.  Part numbers and quantities of PDUs, with NEMA input power connector types, and an inventory of which equipment connects to which PDU.
     245   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)
     246   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.
     247   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.)
     248
     249
     250'''Evaluation Results:''' [[span(Fail, style=background-color: red)]]
     251
     252No document exists that defined deployments details described above. 
     253