On Tue, Aug 02, 2011 at 08:13:55PM -0400, Dmitri Pal wrote:
On 08/02/2011 07:07 AM, Hugh Brock wrote:
> The first mail in the thread has a pretty good description of what catalogs are and
what features they need to have for this iteration.
>
> In short:
>
> * A catalog is an admin-defined collection of deployables, which in the Katello
world are also known as application templates
>
> * A catalog can be added to 1 or more pools in Conductor by an administrator
>
> * If a catalog has been added to a pool, then users with permissions to launch
applications in that pool have the applications in the catalog available to them to
launch.
>
> Andy can expand further if need be...
>
Bullet one talks about templates, bullet three about images.
It does not answer the question about the template to image transition.
When do the templates turn into images? Automatically when catalog gets
associated with pool or there is a special user action? Can catalog
associated with a pool contain just templates for one deployable and
images for another or catalog deals with just templates and image
creation is more viewed as a launch step?
I *think* I said (maybe I didn't and just thought I did) that, when a
user adds a catalog to a pool, there needs to be UI somewhere that
will let the user see whether the images required for the deployables
in the catalog are in one of three states: built and ready; built, but
stale; or not built. The user should then be able to tell factory,
from a UI in Conductor, to build them.
This means: Really a catalog contains only deployables, that happen to
reference images that will eventually be in the warehouse
somewhere. In the early going building those images will be a user
task, hopefully from the UI; later, we may add some automation.
Does this make sense?
--H
--
== Hugh Brock, hbrock(a)redhat.com ==
== Engineering Manager, Cloud BU ==
== Aeolus Project: Manage virtual infrastructure across clouds. ==
==
http://aeolusproject.org ==
"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey