incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <>
Subject Storage Refactor Question
Date Tue, 05 Feb 2013 20:57:45 GMT
Hi everyone,

Edison has been working on enhancing CloudStack's storage component for
some time now.

One of the improvements is to no longer require large amounts of storage to
be provisioned upfront.  It's my understanding that with his changes you
can dynamically create a storage volume (a single LUN) to run a VM on or to
serve as a data disk.

My question is how this works from a user's point of view.  Does anyone
have any insight into this?

For example, today the admin creates a Primary Storage type ahead of the
user needing to use it.  The admin then associates it with a Compute and/or
a Disk Offering.  The user later elects to make use of a given Compute
and/or Disk Offering.

I'm curious how the flow will be with storage being dynamically allocated
when a user needs it.


*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
o: 303.746.7302
Advancing the way the world uses the

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message