Changes between Version 9 and Version 10 of GeniRspec


Ignore:
Timestamp:
08/09/11 13:03:25 (10 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniRspec

    v9 v10  
    44
    55This topic was the focus of one of the software engineering sessions at GEC10, and the agenda wiki page has detailed minutes from the meeting: [wiki:GEC10RSpec GEC10 Meeting]
     6
     7This topic was also the subject of a session at GEC11, and detailed minutes from that meeting are [wiki:GEC11RSpec on the wiki].
     8
     9Current action items:
     10 - Evolve ontologies as needed
     11 - Develop storage and wireless ontologies
     12 - Further rollout of support for GENI RSpec schema
     13 - Adopt AM API revisions
     14 - Move GENI RSpec schemas to the geni.net namespace
     15
    616
    717== GEC10 RSpecs Engineering Meeting ==
     
    5363 * Other translators as necessary
    5464
     65== GEC11 RSpecs Session Summary ==
     66=== Meeting Summary ===
     67'''Aaron Helsinger''' described progress on deploying GENI RSpecs.
     68The 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.
    5569
     70'''Ilia Baldine''' described the compute ontology.
     71His next step is to encode it in NDL and merge that into his RSpec-to-NDL converter.
     72
     73Comments included
     74 - PG makes the hardware type and the available images orthogonal. May need to define subclouds. Needs investigation.
     75 - Unknown shortcuts requested at an AM Should fail or be ignored.
     76 - Shortcuts could be organized by features.
     77
     78'''Max Ott''' argued for several improvements:
     79 - use adaptations to make properties of the underlying fabric be constrains on the connecting AMs
     80 - model component lifecycle
     81 - keep the object model separate from its meaning
     82 - group resources
     83 - measurements must be in terms of same resources (coordinate with the I&M group)
     84
     85'''Hongwei Zhang''' described LENS, a representation of wireless sensor networks that explicitly represents all properties, including observables.
     86
     87'''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.
     88
     89Comments indicated the importance of representing security, how the storage is accessed (iSCSI?), and including basic properties like capacity in the UML.
     90
     91=== Proposed Next Steps ===
     92 - Evolve ontologies as needed
     93 - Develop storage and wireless ontologies
     94 - Further rollout of support for GENI RSpec schema
     95 - Adopt AM API revisions
     96 - Move GENI RSpec schemas to the geni.net namespace
     97