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?
--
Thank you,
Dmitri Pal
Sr. Engineering Manager IPA project,
Red Hat Inc.
-------------------------------
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/