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


Ignore:
Timestamp:
08/13/12 16:06:17 (9 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v1 v2  
    3535
    3636
    37  1. ExoGENI Rack Installation Documentation
     37== 1. ExoGENI Rack Installation Documentation ==
    3838
    3939 * 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).
    4040
    41  2. ExoGENI Rack Part List Documentation
    4241
    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.
     42== 2. ExoGENI Rack Part List Documentation ==
     43
     44'''The goal of this evaluation:'''
     45
     46To find a summary ExoGENI 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.
    4447
    4548
    46  3. ExoGENI Software Components Identification Documentation
     49'''Evaluation Results:'''
    4750
    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.
     51There is not one document, but a series of parts lists pages were found at the  http://www.exogeni.net site:
     52
     53     * [https://wiki.exogeni.net/doku.php?id=public:hardware:network:start&s[]=part ExoGENI Network]
     54     * [https://wiki.exogeni.net/doku.php?id=public:hardware:rack:start&s[]=part ExoGENI Rack]
     55     * [https://wiki.exogeni.net/doku.php?id=public:hardware:workernode:start&s[]=part Worker Node]
     56     * [https://wiki.exogeni.net/doku.php?id=public:hardware:headnode:start&s[]=part Head Node]
     57     * [https://wiki.exogeni.net/doku.php?id=public:hardware:iscsi:start&s[]=part ExoGENI iSCSI]
     58     
     59
     60Power requirements are listed in the [https://wiki.exogeni.net/doku.php?id=public:hardware:rack:start&s[]=part ExoGENI Rack], [https://wiki.exogeni.net/doku.php?id=public:hardware:workernode:start&s[]=part Worker Node], and [https://wiki.exogeni.net/doku.php?id=public:hardware:headnode:start&s[]=part Head Node] pages.
     61
     62PDU requirements are specified in the [https://wiki.exogeni.net/doku.php?id=public:hardware:rack:start&s[]=part ExoGENI Rack] page.
     63
     64Transceivers are defined as site specific. Readers are instructed to confirm their site needs before purchasing any equipment.
     65
     66
     67== 3. ExoGENI Software Components Identification Documentation ==
     68
     69'''The goal of this evaluation:'''
     70Find 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.
     71
     72'''Evaluation Results:'''
     73None found!
    4974
    5075 4.ExoGENI and OS Upgrade Plans
    5176
    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.
     77'''The goal of this evaluation:'''
     78Find documentation that explanations how and when ExoGENI 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.
    5379
    54  5. ExoGENI Software Components Functional Description and Access to Source code.
    5580
    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.
     81'''Evaluation Results:'''
     82None found!
    5783
    58  6. ExoGENI Rack Resources Usage and Policy Documentation
     84== 5. ExoGENI Software Components Functional Description and Access to Source code ==
    5985
    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.
     86'''The goal of this evaluation:'''
    6187
    62  7. ExoGENI Rack Resources Administration
     88Find documentation that provides a description of the ExoGENI software running on a standard rack, and explanation of how to get access to the source code of each piece of standard GENI software.
    6389
    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.
     90== 6. ExoGENI Rack Resources Usage and Policy Documentation ==
    6591
    66  8. ExoGENI Rack Administrative procedure for user accounts
     92'''The goal of this evaluation:'''
    6793
    68  * Procedure for creating new site administrator and operator accounts.
     94Find 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.
    6995
    70  9.  ExoGENI Rack Administrative procedure for rack operations
    71  * Procedure for changing IP addresses for all rack components.
     96== 7. ExoGENI Rack Resources Administration ==
    7297
    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.
     98'''The goal of this evaluation:'''
    7599
    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.
     100Find 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.
    78101
    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).
     102== 8. ExoGENI Rack Administrative procedure for user accounts ==
    81103
    82  12. ExoGENI Rack Site Operations documentation
     104'''The goal of this evaluation:'''
    83105
    84  * Technical plan for handing off primary rack operations to site operators at all sites.
     106Find documentation that provides a procedure for creating new site administrator and operator accounts.
    85107
    86  13. Site Specific ExoGENI Deployment Details Data should include:
     108== 9.  ExoGENI Rack Administrative procedure for rack operations ==
    87109
    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:
     110'''The goal of this evaluation:'''
     111
     112Find documentation that provides a procedure for changing IP addresses for all rack components.
     113
     114== 10. ExoGENI Rack Administrative procedure for rack scheduled shutdown ==
     115
     116'''The goal of this evaluation:'''
     117
     118Find documentation that provides a procedure for cleanly shutting down an entire rack in case of a scheduled site outage.
     119
     120==  11. ExoGENI Rack Administrative procedure for Emergency Stop. ==
     121'''The goal of this evaluation:'''
     122
     123Find documentation that provides a procedure for performing a shutdown operation on any type of sliver on a rack, in support of an Emergency Stop request.
     124
     125== 12. ExoGENI Rack Administrative procedure for health status ==
     126
     127'''The goal of this evaluation:'''
     128
     129Find 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).
     130
     131== 13. ExoGENI Rack Site Operations documentation ==
     132
     133'''The goal of this evaluation:'''
     134
     135Find documentation that provides a Technical plan for handing off primary rack operations to site operators at all sites.
     136
     137== 14. Site Specific ExoGENI Deployment Data ==
     138
     139'''The goal of this evaluation:'''
     140
     141Find 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:
     142
    89143   1.  Part numbers and quantities of PDUs, with NEMA input power connector types, and an inventory of which equipment connects to which PDU.
    90144   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)