On 19/07/13 8:47 AM, "Mike Tutkowski" wrote:
>When we use the word "template" here, do we mean both templates (like
>OVAs)
>and ISOs?
Yes, that¹s correct.
>
>Thanks!
>
>
>On Wed, Jun 5, 2013 at 5:07 PM, Marcus Sorensen
>wrote:
>
>> Thanks, I have one follow-up:
>>
>> On Tue, Jun 4, 2013 at 1
When we use the word "template" here, do we mean both templates (like OVAs)
and ISOs?
Thanks!
On Wed, Jun 5, 2013 at 5:07 PM, Marcus Sorensen wrote:
> Thanks, I have one follow-up:
>
> On Tue, Jun 4, 2013 at 12:10 AM, Nitin Mehta
> wrote:
> > All the public templates will be replicated to all
Thanks, I have one follow-up:
On Tue, Jun 4, 2013 at 12:10 AM, Nitin Mehta wrote:
> All the public templates will be replicated to all the secondary storage
> for redundancy but private templates and uploaded volumes should be kept
> in one of the randomly chosen secondary storage. Snapshots will
All the public templates will be replicated to all the secondary storage
for redundancy but private templates and uploaded volumes should be kept
in one of the randomly chosen secondary storage. Snapshots will be
randomly copied to one of the secondary storage (the chain of incremental
snapshots ar
Anyone?
We are also noticing that if we register a template, that template is
registered and ready, but becomes unusable if the URL for the template
stops working at any time. Seems like we attempt to red download it every
so often. So no one-time registration. Is this by design?
On May 31, 2013 2
Sort of embarrassed to ask this, but I'm unclear on a few of the
aspects of secondary storage.
1) I can see that if I add multiple secondary storage locations, they
each get a copy of the registered templates. Are these copied from one
secondary storage to another, or from the url of the registere
