Come hear Mike Perez and Michael Aday talk about Cinder, Graffiti, and other OpenStack projects!
Today there are many different storage solutions to choose from. It can be overwhelming from a cloud provider's perspective to offer many options for their users, let alone provide a consistent set of tools with each vendor offering their own interface.
The OpenStack Block Storage project Cinder provides an API to talk to many different vendor solutions, in which other applications or OpenStack programs can talk to.
We'll first examine the difference between file, block and object storage.
That'll lead us into having an introduction to Cinder, and an opportunity to review the architecture, vendor driver plugin model, current features, and upcoming features for the Kilo release.
We will also talk about Graffiti, a fast growing OpenStack project with significant contributions from both HP and Intel. Graffiti has been picked up by Glance as a general purpose, integrated, metadata library and it provides labeling capabilities for high end hardware in OpenStack clouds – enabling OpenStack technology to see more than just commodity hardware and OpenStack cloud users to benefit from specialized hardware capabilities.
Using Graffiti, OpenStack users can better understand what is in their clouds, and create clouds that leverage the kind of specialized compute, high availability storage, and high end networking gear that most enterprises have implemented.
Come learn about these two excellent, interesting, and related projects!
Mike Perez has been an active contributor to the OpenStack project since 2010, and is the Program Technical Lead for the OpenStack block storage project Cinder. Mike is a senior developer for Datera, based in Mountain View, California. Prior to this, he was a senior developer at DreamHost, a Web hosting provider based in Los Angeles.
Michael Aday is a Director of Technical Partnerships for HP Helion working actively on Graffiti as well as HP Helion OpenStack.
Google hangout link will be posted here just before we begin, and also tweeted from @hpcloudangel.