in Cloud Environment Contributors: Wednesday March 30, 2011

Transcription

1 RESTful based API for VRM in Cloud Environment Contributors: Chu JunSheng, B. Khasnabish, Meng Yu Wednesday March 30,

2 Outline VRM Requirements VRM in practice Problem Statements Issues for Discussion Next steps 2

3 VRM Requirements VRM requirements identified in Beijing meeting. JunSheng-et-al-IETF79-Cloud-VRM-Req-28Jan11.pdf Grouping virtual resources hierarchically is the efficient way to manage and schedule virtual resources. Resource Authentication and Authorization during resource access control and resource request. Support flexible virtual resources scheduling to satisfy different services/applications requirements. Support inter-cloud resources sharing to infinitely extend the cloud capabilities. 3

4 VRM Framework Interface-1: Used for resource request, status query, system configuration, etc. Interface-2: Used by Client to bind/utilize the allocated resources, system configuration, etc. Interface-3: Used for resource registration/deregistration, resource scheduling, monitoring, etc. 4

5 VRM in practice Industry&SDO API Function Description Resource Types IBM WebSphere REST API provide access to WebSphere Cloud groups, Hypervisors, CloudBurst JSON virtual images and patterns. Networks, Storage, VM, IP groups, IP addresses. Sun Cloud REST API create and manage cloud Cloud, VDC, Cluster, VM, vnet, JSON resources, including compute, Public Address, Backup, Volume, only storage, and networking. Snapshot, Network Interfaces Oracle Cloud Resource Model REST API JSON only interact with the resources to achieve provisioning, associating, modifying, and Cloud, VDC, Zone, Template, VM, Volume, vnet, Archive, Network Interface, Snapshot, Assembly VMware vsphere/ Infrastructure SOAP WSDL retiring i of entities. provide a way of interfacing with the Virtual Infrastructure. Instances, Scalability Groups. VDC, Cluster, Template, VM, Resource Pool, Datastore, Network VMware vcloud REST API provide support for API Versions, Log in/out, JSON, developers who are building Organizations, Network, XML interactive clients of VMware Catalog, vdc, Media Image, Cloud Director. vapptemplate. Rackspace Cloud REST API allow developers to build VM, Server Addresses, Server Server JSON their own solutions on top of Action, Flavor, Image, Backup Rackspace's infrastructure. schedules, shared IP Groups. OGF/OCCI REST API manage cloud infrastructure, resource types: Compute, XHTML5, include deployment, autonomic Network, Storage. sub-types: HTTP Header scaling and monitoring. NetworkInterface, StorageLink SNIA/CDMI REST API Container, Accounting, Data JSON Object(Files, Block Devices, provide the means to access cloud storage and to manage the data stored. Object Stores, Database Tables), Capability 5

6 Problem Statements In current virtualized cloud/data centre environment, multiple l hypervisors are deployed to Eliminate hypervisor vendor lock-in, Avoid service unavailability when some same type of hypervisor upgrade or patch failed. Satisfy different service requirements, such as better support and performance, disaster recovery, business continuity, security, etc. Offer customers multiple choices to select their preferred platforms. Disadvantages in current VRM model Different hypervisors provide different kinds of APIs. Different virtualization platforms provide different views of hierarchical resources. Different hypervisors have different ways to describe resource attributes. A unified VRM model is needed to aggregate and manage different kinds of resources provided by multiple hypervisors. Simple Lightweight g t hypervisor-agnostic. 6

7 Issues in VRM What kind of VRM model we need? Integrate resources provided by multiple hypervisors. Access control to resource registration. Resource scheduling to resource request. Resource binding and utilization to resource client. How to hierarchically organize virtual resources? Easy to migrate Services/Apps to VRM platform. Implement DC/LAN functions in VRM platform. Virtual resources sharing/isolation. Easy extend system capabilities. How to implement the interface in resource interactions? Simple. lightweight. Unified. Widely adopted in industries. 7

8 What need the group to do? Reach a consensus on the VRM model. Reach a consensus on the hierarchical resources organizing. Identify the necessary attributes of the resources. Identify basic resource functions VRM need support. Come up with a unified API to facilitate resource interactions. 8

9 VRM Model Function entities in VRM platform to perform functions such as resource (de-)register, resource provisioning, monitoring and configuring, etc. VRP (de-)registers to VRM. VRC inquires VRM to provide demanded resources. VRM checks the required resources from delivered resource pool. VRC interacts with VRP to bind and utilize the allocated resources. CSM monitors and administrates the cloud resource platform. 9

10 Hierarchy of Cloud Resources 10

11 Virtual Resource Management An unified REST API is provided for interaction among Resource Manager, Resource Client and Resource Provider. If a hypervisor need provide resources to the cloud, it ll support the API. Adaptor decouples the unified REST API from any particular hypervisor in multiple hypervisor environment. 11

12 What is REST? REST stands for Representational ti State t Transfer. Architecture style for distributed hypermedia systems. Focus on resources (not services). Client / Server mode. Lightweight and Simple (compare to RPC/SOAP/WS-*) REST principles Identification of resources Resources addressable. Resources hierarchically organized. A uniform, constrained interface in REST. Representation oriented, such as XML, JSON, XHTML, etc. Communicate statelessly in REST. Evolved in parallel with HTTP 1.1 HTTP basic authentication HTTP verbs (GET/PUT/POST/DELETE). HTTP response status codes. Data format and headers (Version, Content-Type, etc). Version:"X-CloudOPS-API-Version: 1.0" Content-Type: application/json (RFC 4627). 12

13 What is REST? Example Request: Retrieve attributes about a VM instance 345". GET /cloud123/vdcs/vdc234/vms/vm345 Host: cloudplatform.com Authorization: Basic xxxxxxxx Accept: application/vnd.ietf.cloud.vm+json X-CloudOPS-API-Version: 1.0 (username+ : +password) Example Response: HTTP/ OK Content-Type: application/vnd.ietf.cloud.vm+json Content-Length: nnn { "name" : vm345", "uri" : " "run_status status" : "STARTED", "description" : "This VM is deployed for web service" cpu : 2400, memory : 2048, disks : { [ /disk1, 128 ] }, volumes : {}, "back_up" : " } resource_state state : { state : READY }, created : March 24, :34:34 GMT, 13

14 Why is REST? Features of cloud resource Hierarchically organized. Assigned with addressable URIs. Accessed and described with http protocol. Operated statelessly. Cloud VRM and REST are made for each other. REST is becoming a preference for for resource management? IBM WebSphere CloudBurst Sun (Oracle) Cloud API VMware RackSpace OGF/OCCI SNIA/CDMI 14

15 Next Step Identify the indispensable resource attributes. Identify the basic actions on resources. Work on the draft draft-junsheng-cloud-vrm-00 15

16 Comments/Suggestions 16

17 17