Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of shadowsor@gmail.com
 designates 74.125.82.175 as permitted sender)
MIME-Version: 1.0
Date: Wed, 7 Nov 2012 10:17:15 -0700
Message-ID: 
 <CALFpzo6=-Z40QBkAdKqEUucwGTfFbH-x6F1QgFS58tFC5qqyiQ@mail.gmail.com>
Subject: template copy to primary
From: Marcus Sorensen <shadowsor@gmail.com>
To: "cloudstack-dev@incubator.apache.org"
 <cloudstack-dev@incubator.apache.org>
Content-Type: multipart/alternative; boundary=f46d043c80f2d79d7804cdeae355

--f46d043c80f2d79d7804cdeae355
Content-Type: text/plain; charset=ISO-8859-1

Again, forgive my ignorance if I don't understand how this works for all
storage types, but it seems that when a template is first used in a cluster
we copy the template to primary storage first and use that for all
subsequent. Should we add an enhancement to be able to tag templates that
should be cached on primary vs ones that should be copied direct from
secondary storage whenever used?

 I'm thinking about scale, if I've got 20 templates that are used a lot by
everyone, then I want those cached, but if my users are making 1000
templates and only use each once or twice, I don't want them to go to my
primary storage. Especially with CLVM or another raw style storage where we
actually use the whole physical size of the template.

--f46d043c80f2d79d7804cdeae355--