Hi all,
Im kicking the tires with managed storage with under 4.11.2 with KVM and
Datera as primary storage.
My first attempt at creating a VM from a template stored on NFS secondary
failed silently. Looking at the SSVM cloud logs I saw no exception. The VM
root disks gets properly created on
arrays have a special
> understanding of CloudStack and expose additional configuration options.
>
> Local storage
> - Unless explicitly configured for use with CS, this is unused. Any
> existing local storage on a XenServer host when the host is added to
> CloudStack will be los
rstanding of CloudStack and expose additional configuration options.
Local storage
- Unless explicitly configured for use with CS, this is unused. Any
existing local storage on a XenServer host when the host is added to
CloudStack will be lost.
In the case of everything *except* PreSetup, I think
So essentially, CS is categorizing managed storage as something it needs to
make a series of API calls etc to in order to set up and configure it?
Whereas unmanaged is something it expects you to provide settings for when
adding, and expects you to have set it up yourself prior to adding?
*Jeff
My understanding is that managed storage are managed by a cloudstack
plugin, e.g. where cloudstack does something on the actual storage
(provision a lun or something), whilst unmanaged is managed outside of
cloudstack (for instance by you).
An example of a manged storage is Solidfire, an example
Hi,
Is there anywhere in the mailing list, documentation, etc about what
exactly "managed storage" means? Or can someone explain the difference
between managed and unmanaged? The API docs say that it means whether or
not the storage is "managed by CloudStack." This isn't
