Changes between Version 10 and Version 11 of GeniDesign

Timestamp:

10/31/12 13:50:16 (11 years ago)

Author:

Aaron Helsinger

Comment:

--

GeniDesign

@@ -13 +13 @@
 
  [wiki:GeniApi GENI API]::
-  The GENI API is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates.
+  The GENI API is an effort to enable interoperability between Control Frameworks/Clearinghouses and Aggregates. It includes the GENI Aggregate Manager API.
 
  [wiki:GeniIdentityAndAttributes Identity and Attributes]::
-  GENI requires a way of positively identifying experimenters and granting them access to tools and resources. Current control frameworks either maintain their own database of users or explicitly outsource this task to an identity provider. In addition to identifying experimenters, GENI needs information about attributes like institutional affiliation, project role, etc. 
+  GENI requires a way of positively identifying experimenters and granting them access to tools and resources. Current control frameworks either maintain their own database of users or explicitly outsource this task to an identity provider. In addition to identifying experimenters, GENI needs information about attributes like institutional affiliation, project role, etc. This includes discussion of Shibboleth.
 
  [wiki:GeniAuthorization Authorization]::
-  GENI requires an authorization solution that will allow architectural components (Clearinghouse, Aggregates) to determine the privileges of an experimenter. Experimenters can be granted privileges based on institutional affiliation, project role or membership attributes, for instance. Aggregates are expected to have local policies regarding resource access and use. 
+  GENI requires an authorization solution that will allow architectural components (Clearinghouse, Aggregates) to determine the privileges of an experimenter. Experimenters can be granted privileges based on institutional affiliation, project role or membership attributes, for instance. Aggregates are expected to have local policies regarding resource access and use. This includes discussion of ABAC as the long term authorization logic for GENI.
 
  [wiki:GeniRspec Resource Specification]::
-  In order to truly allow interoperability among multiple control frameworks and aggregates, GENI requires a common language for describing resources, resource requests, and reservations - a single, well defined RSpec schema. 
+  In order to truly allow interoperability among multiple control frameworks and aggregates, GENI requires a common language for describing resources, resource requests, and reservations - a single, well defined RSpec schema. GENI uses XML documents with a [http://www.geni.net/resources/rspec/ defined schema].
 
  [wiki:GeniNetworkStitching Network Stitching]::
-  A key architectural question for GENI has been how to connect the resources provided by multiple aggregates into a coherent network. The key objective is to enable automated and realtime network stitching for slices which span multiple aggregates. Ethernet VLANs have been identified as the initial network technology to provide slice level inter-aggregate connections and isolation. However, there are many architecture and design decisions still required. These include, how do you select the VLAN IDs to use and inform all necessary aggregates? How do you handle external networks which may be in between two GENI Aggregates of interest? Is the network stitching service a shared service which coordinates across aggregates, or are aggregates responsible for coordinating amongst themselves, or a hybrid model? How is stitching related information described and shared ? 
+  A key architectural question for GENI has been how to connect the resources provided by multiple aggregates into a coherent network. The key objective is to enable automated and realtime network stitching for slices which span multiple aggregates. Ethernet VLANs have been identified as the initial network technology to provide slice level inter-aggregate connections and isolation. GENI has identified several services, and an RSpec schema for communicating key information, which together constitute the GENI network stitching architecture.
 
  [wiki:GeniMgmtMonitor Monitoring & Management]::
-  Monitoring and management focuses on the ability to perceive what's happening within GENI in order to debug and troubleshoot problems.
+  Monitoring and management focuses on the ability to perceive what is happening within GENI in order to debug and troubleshoot problems.
 
  [wiki:GeniRacks GENI Racks]::