|
|
| (82 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| {{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}}
| | #REDIRECT[[Federated_Cloud_VM_Management]] |
| | |
| = Scenario 1: Virtual Machine Management =
| |
| | |
| {| border="1"
| |
| |-
| |
| ! 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 [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 ===
| |
| | |
| The Cloud Infrastructure Management Interface is a standard released by [http://dmtf.org/standards/cloud DMTF]. Similarly to OCCI, it also
| |
| consists of multiple specifications:
| |
| | |
| * CIMI Primer (DSP2027) v. 1.0.0
| |
| * CIMI (DSP0263) v. 1.1.0
| |
| * CIMI-CIM (DSP0264) v. 1.0.0
| |
| | |
| CIMI is a highly specific IaaS protocol, defining a wide range of attributes
| |
| applicable in the context of IaaS. This is what mainly distinguishes it from OCCI,
| |
| which is a much more light-weight, generic boundary-level protocol, relying on
| |
| its extensibility to cover specific areas.
| |
| | |
| == OGF's Open Cloud Computing Interface ==
| |
| | |
| OCCI was selected for the FedCloud environment for multiple reasons, chief among them its simplicity and the fact that other standards of that kind (such asi CIMI) have not been published until well after the initiative started.
| |
| | |
| == Available OCCI implementations ==
| |
| === Server ===
| |
| ==== rOCCI-server ====
| |
| | |
| rOCCI-server, part of the rOCCI Framework, is a stand-alone service providing "translation" between OCCI and proprietary cloud management frameworks, which are not otherwise OCCI-compatible. Individual types of clod management framework are provided through specific backends. The list of currently available backends is available in the [[ROCCI-server_Backend_development_status]] page.
| |
| | |
| ==== OCCI-OS ====
| |
| ==== snf-occi ====
| |
| === Client ===
| |
| ==== rOCCI-cli ====
| |
| === Library ===
| |
| ==== rOCCI-* ====
| |
| ==== pyssf ====
| |
| ==== jOCCI-* ====
| |
| | |
| == Interoperability Table ==
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.