Learn how to configure OpenStack block storage the easy way

Screen Shot 2015-02-06 at 5.47.57 PM

Early this week we talked about OpenStack as a popular choice to deploy both to public and private clouds because of its unified platform. We explained that ElasticBox auto provisions your workloads predictably no matter where you deploy. Today, we talk about how to auto configure storage for your OpenStack deployments.

Storage for OpenStack

First of all, to configure storage in OpenStack, you need to activate Cinder or block storage. A nice thing about automating deployments through ElasticBox is you don’t have to configure disk storage separately. Along with the rest of the deployment, specify the volume storage with a simple add button and let ElasticBox do the brunt of the work like clockwork.

We’ll show how to add volumes when you set up your deployment in your private OpenStack cloud or publicly managed HP Cloud through the ElasticBox deployment profile. There are two types of volumes you can add, an image or a hard disk volume.

Hard volumes

Click Add in the Additional Volumes section and set the disk size for each volume. Extra volume for an instance means you can store information such as databases or logs. It means you can move data from one instance to another. Or just means get bigger disks for a particular instance type.

Screen Shot 2015-02-06 at 4.56.55 PM

Image volume

Image volumes are a special kind of volume. This type of volume lets you load your instance image and boot from it. The image volume typically stores the whole operating system and data that you’ll want to persist after you delete the instance. ElasticBox doesn’t delete the volume if you check the persist option. The persist option is perfect to not waste computing resources. Not only can you check for problems after destroying an instance, but you can also create snapshots, extend the volume before mounting to another instance and do more.

Wrapping up

Let’s face it. If you were doing this directly in OpenStack or HP Cloud, you’d have to create the volumes first. Then launch the instances, attach the volumes to them, and finally execute scripts to configure the volumes on them.

Managing OpenStack deployments is easier with ElasticBox. All there is the deployment profile where you add the volumes and the box with your workload where you put the scripts to configure the instances. This method lets you automate the manual steps and avoid errors. On the whole, it makes managing OpenStack volumes easy and programmatic.

Hacker News

Categories: Cloud Application Management, DevOps, ElasticBox, OpenStack
Tags: , , , ,