| 115 | | * '''Requirement A.4''': Cross-GENI Monitoring |
| 116 | | * ''GENI monitoring is more than the sum of the monitoring at GENI’s parts. In order to know if GENI is working properly, additional monitoring is required beyond that done by each of its constituent pieces.'' |
| 117 | | * Must collect and synthesize additional operational statistics which indicate whether GENI is working |
| 118 | | * e.g. meso-scale ping tests, topology |
| 119 | | * Must collect cross-GENI stats |
| 120 | | * Must make cross-GENI stats available when needed |
| 121 | | |
| 122 | | * '''Requirement A.5''': Privacy |
| 123 | | * Preserve privacy of users (opt-in, experimenters, other users of resources) |
| 124 | | * [[Color(red,TBD – This is an area needing major discussion (NOT STARTED))]] |
| 125 | | |
| 126 | | * '''Requirement B.1''': Troubleshooting & Event Escalation |
| 127 | | * For both debugging and security problems: |
| 128 | | * '''Requirement B.1.1''': Must be possible to escalate events |
| 129 | | * '''Requirement B.1.2''': Meta-operations and aggregate operators must work together to resolve problems |
| 130 | | * Aggregates must advertise resources accurately |
| 131 | | * (threshold) statically --> [[Color(green,Fill out aggregate page (DONE))]] |
| 132 | | * (objective) dynamically --> [[Color(green,Advertise resources via AM API (DONE))]] |
| 133 | | * Aggregates notify meta-operations when resources are unavailable --> [[Color(orange,via e-mail (doing SOME of the time) (IN PROGRESS))]] |
| 134 | | * Aggregates cooperate with meta-operations on the resolution of security events |
| 135 | | * Aggregates cooperate with LLR on the resolution of security events |
| 136 | | |
| 137 | | |
| 138 | | |
| 139 | | * '''Requirement B.2''': Emergency Stop |
| 140 | | * Must be possible to do an emergency stop in case of a problem |
| 141 | | * Must maintain POC information at meta-operations |
| 142 | | * Aggregate --> [[Color(green,end contact info to GMOC (DONE))]] |
| 143 | | * Campus --> [[Color(green,send contact info to GMOC (DONE))]] |
| 144 | | * Experimenter --> [[Color(orange,slice e-mail (IN PROGRESS))]] |
| 145 | | * Other infrastructure --> [[Color(green,contacted by relevant campus (DONE))]] |
| 146 | | * Aggregates & Meta-operations must each have policies and procedures in place to support an emergency stop |
| 147 | | * --> [[Color(orange,Has been dry run (IN PROGRESS))]] |
| 148 | | |
| 149 | | * '''Requirements B.3, B.4, B.4''': Policy |
| 150 | | * '''Requirement B.3''': Organizations must manage GENI resources consistent with local policy and best practices (e.g security procedures, logging, backups, etc) |
| 151 | | * In general, follow local policy and procedures |
| 152 | | * Follow best practices which if not followed would affect other members of the GENI community |
| 153 | | * '''Requirement B.4''': Develop policies for monitoring |
| 154 | | * '''Requirement B.5''': All parties should implement agreed upon policies |
| 155 | | * Follow Aggregate Provider Agreement |
| 156 | | * Follow LLR |
| 157 | | * Follow other GENI policies as they come into effect |
| 158 | | |
| 159 | | * '''Requirement B.6''': Security |
| 160 | | * Secure GENI as a whole and secure the pieces of GENI |
| 161 | | * Two things we want to prevent: |
| 162 | | * Compromise of GENI resources |
| 163 | | * Use of GENI resources to compromise other entities |
| 164 | | * Two things we can do about this: |
| 165 | | * Follow best practices to hinder compromise |
| 166 | | * Detect and respond to compromise |
| 167 | | * Allow interesting research for which experimenters and operations have to coordinate for security and management reasons |
| 168 | | * Security experimentation BOF at GEC12 and session at GEC13!!! |
| 169 | | * --> [[Color(red,TBD – This is an area needing major discussion (NOT STARTED))]] |
| 170 | | |
| | 129 | * '''Requirement A.4''': Cross-GENI Monitoring |
| | 130 | * ''GENI monitoring is more than the sum of the monitoring at GENI’s parts. In order to know if GENI is working properly, additional monitoring is required beyond that done by each of its constituent pieces.'' |
| | 131 | * Must collect and synthesize additional operational statistics which indicate whether GENI is working |
| | 132 | * e.g. meso-scale ping tests, topology |
| | 133 | * Must collect cross-GENI stats |
| | 134 | * Must make cross-GENI stats available when needed |
| | 135 | |
| | 136 | * '''Requirement A.5''': Privacy |
| | 137 | * Preserve privacy of users (opt-in, experimenters, other users of resources) |
| | 138 | * [[Color(red,TBD – This is an area needing major discussion (NOT STARTED))]] |
| | 139 | |
| | 140 | * '''Requirement B.1''': Troubleshooting & Event Escalation |
| | 141 | * For both debugging and security problems: |
| | 142 | * '''Requirement B.1.1''': Must be possible to escalate events |
| | 143 | * '''Requirement B.1.2''': Meta-operations and aggregate operators must work together to resolve problems |
| | 144 | * Aggregates must advertise resources accurately |
| | 145 | * (threshold) statically --> [[Color(green,Fill out aggregate page (DONE))]] |
| | 146 | * (objective) dynamically --> [[Color(green,Advertise resources via AM API (DONE))]] |
| | 147 | * Aggregates notify meta-operations when resources are unavailable --> [[Color(orange,via e-mail (doing SOME of the time) (IN PROGRESS))]] |
| | 148 | * Aggregates cooperate with meta-operations on the resolution of security events |
| | 149 | * Aggregates cooperate with LLR on the resolution of security events |
| | 150 | |
| | 151 | |
| | 152 | |
| | 153 | * '''Requirement B.2''': Emergency Stop |
| | 154 | * Must be possible to do an emergency stop in case of a problem |
| | 155 | * Must maintain POC information at meta-operations |
| | 156 | * Aggregate --> [[Color(green,end contact info to GMOC (DONE))]] |
| | 157 | * Campus --> [[Color(green,send contact info to GMOC (DONE))]] |
| | 158 | * Experimenter --> [[Color(orange,slice e-mail (IN PROGRESS))]] |
| | 159 | * Other infrastructure --> [[Color(green,contacted by relevant campus (DONE))]] |
| | 160 | * Aggregates & Meta-operations must each have policies and procedures in place to support an emergency stop |
| | 161 | * --> [[Color(orange,Has been dry run (IN PROGRESS))]] |
| | 162 | |
| | 163 | * '''Requirements B.3, B.4, B.4''': Policy |
| | 164 | * '''Requirement B.3''': Organizations must manage GENI resources consistent with local policy and best practices (e.g security procedures, logging, backups, etc) |
| | 165 | * In general, follow local policy and procedures |
| | 166 | * Follow best practices which if not followed would affect other members of the GENI community |
| | 167 | * '''Requirement B.4''': Develop policies for monitoring |
| | 168 | * '''Requirement B.5''': All parties should implement agreed upon policies |
| | 169 | * Follow Aggregate Provider Agreement |
| | 170 | * Follow LLR |
| | 171 | * Follow other GENI policies as they come into effect |
| | 172 | |
| | 173 | * '''Requirement B.6''': Security |
| | 174 | * Secure GENI as a whole and secure the pieces of GENI |
| | 175 | * Two things we want to prevent: |
| | 176 | * Compromise of GENI resources |
| | 177 | * Use of GENI resources to compromise other entities |
| | 178 | * Two things we can do about this: |
| | 179 | * Follow best practices to hinder compromise |
| | 180 | * Detect and respond to compromise |
| | 181 | * Allow interesting research for which experimenters and operations have to coordinate for security and management reasons |
| | 182 | * Security experimentation BOF at GEC12 and session at GEC13!!! |
| | 183 | * --> [[Color(red,TBD – This is an area needing major discussion (NOT STARTED))]] |
| | 184 | |
| | 185 | |
| | 186 | |
