Changes between Version 2 and Version 3 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-7
- Timestamp:
- 01/24/13 09:30:55 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-ADM-7
v2 v3 46 46 47 47 == 1. InstaGENI Rack Installation Documentation == 48 49 '''The goal of this evaluation:''' 50 51 To 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). 52 53 54 '''Evaluation Results:''' 55 48 56 49 == 2. InstaGENI Rack Part List Documentation == 57 == 2. InstaGENI Rack Part List Documentation == 58 59 60 '''The goal of this evaluation:''' 61 62 To find a summary InstaGENI 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. 63 64 65 '''Evaluation Results:''' 66 50 67 51 68 == 3. InstaGENI Software Components Identification Documentation == 52 69 70 71 '''The goal of this evaluation:''' 72 73 Find 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. 74 75 '''Evaluation Results:''' 76 77 53 78 == 4. InstaGENI and OS Upgrade Plans == 54 79 55 == 5. InstaGENI Software Components Functional Description and Access to Source code ==56 80 57 == 6. InstaGENI Rack Resources Usage and Policy Documentation == 81 '''The goal of this evaluation:''' 82 83 Find documentation that explains how and when InstaGENI 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. 84 85 86 '''Evaluation Results:''' 87 88 == 5. InstaGENI Software Components Functional Description and Access to Source code == 89 '''The goal of this evaluation:''' 90 91 Find documentation that provides a description of the InstaGENI software running on a standard rack, and explanation of how to get access to the source code of each piece of standard GENI software. 92 93 '''Evaluation Results:''' 94 95 96 == 6. InstaGENI Rack Resources Usage and Policy Documentation == 97 '''The goal of this evaluation:''' 98 99 Find 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. 100 101 102 '''Evaluation Results:''' 103 58 104 59 105 == 7. InstaGENI Rack Resources Administration == 60 106 107 '''The goal of this evaluation:''' 108 109 Find 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. 110 111 '''Evaluation Results:''' 112 61 113 == 8. InstaGENI Rack Administrative procedure for user accounts == 62 114 115 '''The goal of this evaluation:''' 116 117 Find documentation that provides a procedure for creating new site administrator and operator accounts. 118 119 '''Evaluation Results:''' 120 63 121 == 9. InstaGENI Rack Administrative procedure for rack operations == 122 123 '''The goal of this evaluation:''' 124 125 Find documentation that provides a procedure for changing IP addresses for all rack components. 126 127 '''Evaluation Results:''' 64 128 65 129 == 10. InstaGENI Rack Administrative procedure for rack scheduled shutdown == 130 131 '''The goal of this evaluation:''' 132 133 Find documentation that provides a procedure for cleanly shutting down an entire rack in case of a scheduled site outage. 134 135 '''Evaluation Results:''' 136 66 137 67 138 == 11. InstaGENI Rack Administrative procedure for Emergency Stop. == 68 139 140 '''The goal of this evaluation:''' 141 142 Find 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. 143 144 '''Evaluation Results:''' 145 69 146 == 12. InstaGENI Rack Administrative procedure for health status == 70 147 148 '''The goal of this evaluation:''' 149 150 Find 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). 151 152 '''Evaluation Results:''' 153 71 154 == 13. InstaGENI Rack Site Operations documentation == 72 155 156 '''The goal of this evaluation:''' 157 158 Find documentation that provides a Technical plan for handing off primary rack operations to site operators at all sites. 159 160 '''Evaluation Results:''' 161 162 163 73 164 == 14. Site Specific InstaGENI Deployment Data == 74 165 75 ~ 166 167 '''The goal of this evaluation:''' 168 169 Find 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: 170 171 1. Part numbers and quantities of PDUs, with NEMA input power connector types, and an inventory of which equipment connects to which PDU. 172 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) 173 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. 174 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.) 175 176 '''Evaluation Results:''' 177