=== RSpec ===

==== Organizer ====
  Aaron Helsinger, ''GENI Project Office''

==== Time ====
  Wed 1:00 - 2:30 pm

==== Dial In ====
 866-453-5550
 Participant pin: 6513886#

==== Description ====
  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.  The community will discuss progress on adopting common ontologies for GENI resources, and making aggregates speak ProtoGENI V2 RSpecs as the GENI Rspec format.

==== Agenda ==== 
 * Introduction and Status - Aaron Helsinger (20 minutes) [attachment:RSpecs-intro.pdf slides]
  * GEC10 Review
  * AM API Draft Revisions
  * GENI RSpecs rollout status and experiences
  * Future Work
 * RSpec Translator - Ilia Baldine (5 minutes)
 * Network and Compute Ontologies - Ilia Baldine (15 minutes) [attachment:GEC11-compute-ontology.pptx slides]
  * Description
  * Adoption
 * Invited Viewpoints on Ontologies
  * Max Ott (10 minutes) [attachment:"RSpec in 5 minutes - max.pdf" slides]
  * Hongwei Zhang (10 minutes) [attachment:"LENS Hongwei-Zhang.pptx" slides]
  * Mike Zink (10 minutes) [attachment:Storage-RSpec.ppt slides]
 * Discussion - All (10 minutes)
 * Conclusion - Aaron Helsinger (10 minutes) [attachment:RSpecs-Summary.pdf slides]

==== Meeting Summary ====
'''Aaron Helsinger''' described progress on deploying GENI RSpecs.
The schema is published, and support has been added to ProtoGENI and SFA (!PlanetLab). That support is rolling out to many sites, and the Omni and Flack tools support it. Support at Orca and !OpenFlow is in process. AM API revisions to codify support for these RSpecs are available in draft form.

'''Ilia Baldine''' described the compute ontology. 
His next step is to encode it in NDL and merge that into his RSpec-to-NDL converter.

Comments included
 - PG makes the hardware type and the available images orthogonal. May need to define subclouds. Needs investigation.
 - Unknown shortcuts requested at an AM Should fail or be ignored.
 - Shortcuts could be organized by features.

'''Max Ott''' argued for several improvements:
 - use adaptations to make properties of the underlying fabric be constrains on the connecting AMs
 - model component lifecycle
 - keep the object model separate from its meaning
 - group resources
 - measurements must be in terms of same resources (coordinate with the I&M group)

'''Hongwei Zhang''' described LENS, a representation of wireless sensor networks that explicitly represents all properties, including observables.

'''Mike Zink''' described the problem of representing storage resources - both in the cloud and attached to compute resources. He plans to start by representing cloud resources (as in Amazon S3/EBS), building a simple model and an RSpec extension.

Comments indicated the importance of representing security, how the storage is accessed (iSCSI?), and including basic properties like capacity in the UML.

==== Proposed Next Steps ====
 - Evolve ontologies as needed
 - Develop storage and wireless ontologies
 - Further rollout of support for GENI RSpec schema
 - Adopt AM API revisions
 - Move GENI RSpec schemas to the geni.net namespace


==== Background Reading ====
 * [wiki:GeniRspec RSpecs Design Activities]
 * ProtoGENI RSpecs description: https://www.protogeni.net/trac/protogeni/wiki/RSpec
 * Proposed AM API Changes to support requesting specific RSpec formats: [wiki:GAPI_AM_API_DRAFT AM API V2 Draft]
 * [attachment:ComputeOntology-071411.pdf Proposed Compute Resources ontology for GENI]
{{{
#!comment
network ontology, compute ontology, OF extension, stitching extension 
}}}
 * Orca NDL-OWL Models and RSpecs: https://geni-orca.renci.org/trac/wiki/NDL-OWL
 * Orca NDL-OWL Converter: http://geni-test.renci.org:11080/ndl-conversion/convert.jsp