Cinder Status Openstack Shanghai

1,283 views

Published on

China OpenStack User Group

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,283
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Cinder Status Openstack Shanghai

  1. 1. OpenStack Cinder(Block Storage As A Service) zhiteng.huang@intel.com
  2. 2. Agenda● Project Status (Folsom)● What to Expect in Grizzly
  3. 3. 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
  4. 4. 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
  5. 5. 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
  6. 6. 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.
  7. 7. Under the surface● Drivers clean-up● Multiple back-end supports● Host extension
  8. 8. Question?

×