emplate on the same
> SR.
> >>> >>>> >>>>> >>> This
> >>> >>>> >>>>> >>> will never
> >>> >>>> >>>>> >>> be the case for managed storag
t; multiple
>>> >>>> >>>>> >>> root
>>> >>>> >>>>> >>> disks.
>>> >>>> >>>>> >>>
>>> >>>> >>>>> >>> By the way, I just wa
t;>> >>>>> >>> how
>> >>>> >>>>> >>> OpenStack
>> >>>> >>>>> >>> handles storage by default.
>> >>>> >>>>> >
;>> >>> By the way, I am currently focused on XenServer, but also
> plan
> >>>> >>>>> >>> to
> >>>> >>>>> >>> implement
> >>>> >>>>>
gt; >>>>> >>>
>>>> >>>>> >>> * It consumes as much of the SR as it can unless you you want
>>>> >>>>> >>> extra
>>>> >>>>> >>> space
>>>> >>>>&
gt;> >>>>> >>> to
>>>> >>>>> >>> implement
>>>> >>>>> >>> support for this on KVM and ESX (although those may be outside
>>>> >>>>> >>> of
>>>>
ots.
>>> >>>>> >>>
>>> >>>>> >>>
>>> >>>>> >>> On Sat, Jan 25, 2014 at 3:43 AM, Marcus Sorensen
>>> >>>>> >>>
>>> >>>>> >>> wrote:
>>&g
; copy template from secondary storage directly onto root disk
>>> every
>>> >>>>> >>>> time, and copyPhysicalDisk really does nothing. If you can
>>> clone,
>>> >>>>> >>>> then
>>> >>>>&
ver now, and if so put the
>> >>>>> >>>> createDiskFromTemplate
>> >>>>> >>>> logic there, but you still probably need copyPhysicalDisk to do
>> >>>>> >>>> its
>> &g
now, but
>>>> > that call doesn't have to do any work on the agent-side, really.
>>>> >
>>>> >
>>>> > On Sat, Jan 25, 2014 at 12:47 AM, Mike Tutkowski
>>>> > wrote:
>>>> >> Just wanted to throw this
> it will be passed to createDiskFromTemplate in your storage adaptor
>>> >> > (for KVM), where you can call a clone of that and return it as the
>>> >> > root volume . There was once going to be template clone capabilities
>>> >> > in the st
o or so), so we still
>> have
>> >> > to call clone to our storage server from the agent side as of now,
>> but
>> >> > that call doesn't have to do any work on the agent-side, really.
>> >> >
>> >> >
>> >> &g
ing we're dealing with templates here and not
> an
> >> >> ISO), it is possible I may be able to circumvent a new table (or any
> >> >> existing table like template_spool_ref) entirely for managed storage.
> >> >>
> >> >> The purpo
7;re dealing with templates here and not an
>>> >> ISO), it is possible I may be able to circumvent a new table (or any
>>> >> existing table like template_spool_ref) entirely for managed storage.
>>> >>
>>> >> The purpose of a
a new table (or any
>> >> existing table like template_spool_ref) entirely for managed storage.
>> >>
>> >> The purpose of a table like template_spool_ref appears to be mainly to
>> >> make
>> >> sure we're not downloading the sample
a table like template_spool_ref appears to be mainly to
>> make
>> >> sure we're not downloading the sample template to an SR multiple times
>> (and
>> >> this doesn't apply in the case of managed storage since each root
>> volume
>> >&
ks!
> >>
> >>
> >> On Sat, Jan 25, 2014 at 12:39 AM, Mike Tutkowski
> >> wrote:
> >>>
> >>> Hi Edison and Marcus (and anyone else this may be of interest to),
> >>>
> >>> So, as of 4.3 I have added support for data disk
gt;> wrote:
>>>
>>> Hi Edison and Marcus (and anyone else this may be of interest to),
>>>
>>> So, as of 4.3 I have added support for data disks for managed storage for
>>> XenServer, VMware, and KVM (a 1:1 mapping between a CloudStack volume and a
&
tween a CloudStack volume and a
>> volume on a storage system). One of the most useful abilities this enables
>> is support for guaranteed storage quality of service in CloudStack.
>>
>> One of the areas I'm working on for CS 4.4 is root-disk support for
>> managed
disks for managed storage for
> XenServer, VMware, and KVM (a 1:1 mapping between a CloudStack volume and a
> volume on a storage system). One of the most useful abilities this enables
> is support for guaranteed storage quality of service in CloudStack.
>
> One of the areas I'm workin
support for guaranteed storage quality of service in CloudStack.
One of the areas I'm working on for CS 4.4 is root-disk support for managed
storage (both with templates and ISOs).
I'd like to get your opinion about something.
I noticed when we download a template to a XenServer SR that w
21 matches
Mail list logo
