cinder status openstack shanghai

Post on 12-May-2015

752 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

China OpenStack User Group

TRANSCRIPT

OpenStack Cinder(Block Storage As A Service)

zhiteng.huang@intel.com

Agenda

● Project Status (Folsom)● What to Expect in Grizzly

Project Status (Folsom)

● Cinder – Block Storage As A Service● Broke-out from Nova during Folsom

– Nova-volume will be dropped in G'

● One of OpenStack core project● Nova-volume equivalent

Folsom Features

● Create Image From Volume● NFS Files as Virtual Block Devices● Persistent iSCSI Targets● Python-cinderclient● Improved API response data● Added More back-end drivers

What to Expect in Grizzly

● Cinder API 2.0● Volume Types and sophisticate scheduling● Backup to object storage● New protocol (FC) and new back-ends● Retention of image metadata for bootable volumes● Volume Resize● Volume Cloning Support● QoS● Better Integration with Celiometer● Better Xen Support

Cinder API 2.0

● Update metadata for volumes and snapshots● Filtering of API requests by attributes and metadata ● Delete volumes that have snapshots● List snapshots filtered by volume ID● Update /volumes and /volumes/details to match behavior of other openstack projects

● Update limits and quotas to key on volume_type and not be global● Change ID of volume types to be a UUID● Change all references to volume type in the API to use the UUID rather than the volume type name

● Change "display_name" attribute to "name" in the API for consistency with other services.

● Add a field to display what instance is being attached to when in the "attaching" state.

Under the surface

● Drivers clean-up● Multiple back-end supports● Host extension

Question?

top related