On 08/04/2011 09:15 AM, Hugh Brock wrote:
On Thu, Aug 04, 2011 at 12:00:07PM +0100, Mark McLoughlin wrote:
> Wow, big thread :-)
> I'm a bit behind, but a few things make sense to me so far:
> - Aeolus Image Templates and Katello System Templates are similar
> concepts, so that sounds like an obvious good place for the
> projects to start working together
> - From the Aeolus side, we'd be delighted if Katello users could
> build Images from System Templates, such that the Images are
> available for launching in Conductor
> - The talk of Application Templates and Deployables being similar in
> concept, and that Deployables might make sense on baremetal, is all
> very interesting. That alone is a topic worthy of much more
> investigation and experimentation.
> - There is some overlap between the Katello Environment and Conductor
> Pool/Pool Family concepts. ISTM that Katello is ahead of Aeolus on
> this one. e.g. the idea of promoting an Image Build from dev to
> prod is not something that we support yet.
> - We can choose to avoid the need for shared identity between
> Katello-Conductor-Factory-Warehouse by using two-legged OAuth or
> X.509 client certificates. However, that would mean a) not exposing
> Warehouse/Factory to users b) implementing a Conductor API which
> aeolus-image would use instead and c) making Katello enforce
> permissions around who can do what with images.
c) might not actually be required, if we decide (as I think we should)
that images only get built within the context of a Conductor pool
> The big disconnect for me is trying to understand the motivation for the
> Catalog concept. Some guesses:
> - Perhaps we want Aeolus to consume Katello System Templates, rather
> the Katello build Images using Aeolus Image Templates. In that
> case, Conductor needs a UI to build Images from System Templates.
> The Catalog concept is the proposal - add a System Template to a
> Catalog, add the Catalog to a Pool, build the System Template for
> each Provider in the Pool
This first guess is pretty much what I'm after.
There are significant differences between an Aeolus image template and
a Katello system template, all tied to the fact that Katello system
templates are built post-boot on a running system, while Aeolus image
templates are built pre-boot (and the resulting build may then be
modified post-boot by assembly or deployable configuration).
Well to be fair the info in the template is kickstart info (build time)
and will include management data (post build)> So there is some overlap.