Context Navigation

IG-MON-2

Timestamp:: 03/06/13 07:51:30 (11 years ago)
Author:: lnevers@bbn.com
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-MON-2

-                      v12
+                      v13
 || 1          || [[Color(green,Pass)]] ||                ||                                    ||
 || 2          || [[Color(green,Pass)]] ||                ||                                    ||
 || 3          ||                       ||                ||                                    ||
+|| 3          || [[Color(#98FB98,Pass: most criteria)]]||[https://openflow.stanford.edu/bugs/browse/FOAM-352 FOAM-352]||                                    ||
 || 4          ||                       ||                ||                                    ||
 …
 As an administrator determine ways to show Slice authorities for InstaGENI Compute and FOAM aggregates:
  * For InstaGENI Compute Resources there is one central definition for trusted slice authorities, which available at https://www.emulab.net/protogeni/authorities/salist.txt.  All InstaGENI racks use this global list of Trusted Authorities.  <<<TODO, determine if this information can be shown within the GPO Rack>>>
  * FOAM trusts root certificates, and certificates are placed in /opt/foam/etc/gcf-ca-certs, but presence of a certificate in this directory does not mean that the trust is configured.  Since there is no way to show all trusted roots at this time created FOAM ticket [https://openflow.stanford.edu/bugs/browse/FOAM-352 FOAM-352 bug].
+ * For InstaGENI compute resources aggregate there is one central definition for trusted slice authorities, which available at https://www.emulab.net/protogeni/authorities/salist.txt.  All InstaGENI racks use this global list of Trusted Authorities.  <<<TODO, determine if this information can be shown within the GPO Rack>>>
+ * FOAM trusts root certificates and certificates to be configured for trust are placed in /opt/foam/etc/gcf-ca-certs, but presence of a certificate in this directory does not mean that the trust is configured.  Since there is no way to show all trusted roots at this time created FOAM ticket [https://openflow.stanford.edu/bugs/browse/FOAM-352 FOAM-352 bug].