Difference between revisions of "Fedcloud-tf:WorkGroups:Scenario1"
Jump to navigation
Jump to search
(→OCCI) |
|||
Line 40: | Line 40: | ||
== Available Open Standards == | == Available Open Standards == | ||
=== OCCI === | === OCCI === | ||
Developed by the [http://occi-wg.org/ Open Grid Forum], OCCI is a boundary protocol and API that acts as a service front-end to a provider’s internal management framework by exposing its resources. As of this writing (early 2015) the specification consist of three documents: | |||
* OCCI Core describing the formal definition of the the OCCI Core Model | |||
* OCCI Infrastructure defining the OCCI Infrastructure extension for the IaaS domain, defining additional resource types, their attributes and the actions that can be taken on each resource type | |||
* OCCI HTTP Rendering defining interaction with the OCCI Core Model using the RESTful OCCI API | |||
The OCCI Working Group is also working on additional specification, currently in various stages of progress: | |||
* OCCI XML Rendering | |||
* OCCI JSON Rendering | |||
* OCCI Billing and Monitoring | |||
* OCCI PaaS extension | |||
* OCCI SLAs extension | |||
=== CIMI === | === CIMI === | ||
Revision as of 15:15, 3 February 2015
Main | Roadmap and Innovation | Technology | For Users | For Resource Providers | Media |
Scenario 1: Virtual Machine Management
Role | Institution | Name |
---|---|---|
Scenario leader | CESNET | Boris Parák |
Collaborator | CESNET | Zdeněk Šustr |
Collaborator | GWDG | Piotr Kasprzak |
Collaborator | IFCA | Enol Fernández |
Collaborator | GRNET | Kostas Koumantaros |
Activities
Ongoing Issues
Interoperability
Authentication
Deployment
Support for new platforms & public providers
Available Open Standards
OCCI
Developed by the Open Grid Forum, OCCI is a boundary protocol and API that acts as a service front-end to a provider’s internal management framework by exposing its resources. As of this writing (early 2015) the specification consist of three documents:
- OCCI Core describing the formal definition of the the OCCI Core Model
- OCCI Infrastructure defining the OCCI Infrastructure extension for the IaaS domain, defining additional resource types, their attributes and the actions that can be taken on each resource type
- OCCI HTTP Rendering defining interaction with the OCCI Core Model using the RESTful OCCI API
The OCCI Working Group is also working on additional specification, currently in various stages of progress:
- OCCI XML Rendering
- OCCI JSON Rendering
- OCCI Billing and Monitoring
- OCCI PaaS extension
- OCCI SLAs extension