Using a file as a device in ScaleIO

Kalle's playground

In most cases one would use the whole unformatted disk as a device for ScaleIO, but sometimes this is not possible. To use the free space from already partitioned disk ScaleIO sds component has a command line tool called create_file_storage. It is located in the ScaleIO sds component folder. Tool will create a pre-allocated file with specified size to a specified location.

Command to create file:

create_file_storage −−create_file −−size_gb <SIZE_IN_GB> −−file_name <FILE_NAME> 


create_file_storage −−create_file −−size_gb 120 −−file_name

create_file_storage command line

When adding a devices for SDS specify the full path of the file as the “Path” for the device.

File as device

The “file as device” options allows to start consuming free space for ScaleIO from disks that have existing partitions and existing file systems.

View original post

Run your stateful apps with Mesos and Docker

OLD - {code} by Dell EMC

Hot off the heels of ContainerCon/MesosCon we looked into how we could help support data persistence for the popular distributed systems manager. We trawled through a lot of documentation, and found that Marathon has a great Docker containerizer and also supports arbitrary options. Yay! Have we lost you yet?

Here’s how it works:

Mesos is a tool to abstract datacenter resources such as CPU, memory, storage and more. Marathon is used on top of Mesos to schedule applications on top of those resources, and those applications can be in Docker containers. As you might remember from previous posts, the EMC {code} team have worked on a Docker volume plugin called REX-Ray (new name suggestions welcome) to make sure that we can actually store data from our containerized applications. So, with all these pieces together, we should be able to create a volume using REX-ray, tie it to a container, have…

View original post 672 more words