<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 13/08/12 07:30 PM, James Labocki
wrote:<br>
</div>
<blockquote
cite="mid:713002230.8961790.1344882634730.JavaMail.root@redhat.com"
type="cite">
<pre wrap="">Sorry for posting across both lists, but this involves both aeolus and katello.
Last week a few of us were discussing the ability to import/export deployables within aeolus for sharing between differing implementations.
The attached photo 1.JPG provides a high level diagram of some of the problems we believe exist in achieving this today. Please note that I used enterprise nomenclature, so I think that:
- System Engine = Katello
- Component Outline = Assembly
- Blueprint = Deployable
- AppForm = Deployment
We found the following areas differ between implementations and would need to be accounted for. Note this this was not an exhaustive exercise and I'm sure we missed some areas.
- Providers paths are different in katello
- Certificates are different in system templates
- Repositories are different in system templates
- Deployables and their services are tightly coupled (not shareable)
- Clouds, Cloud Resource Zones, and Catalogs are different in aeolus
There seem to be a few approaches that we can use.
#1 Create an import/export tool that prompts users for various implementation specific areas (repository names, certificate locations, etc).
#2 Use the work Francesco has been doing on templates.aeolusproject.org to solve the problem by having it integrated into aeolus and contain the logic that would abstract environment differences from end users.
#3 Allow users to import/export the corresponding images along with the blueprint (this does not help with ongoing management through katello).
#4 Change the template/image/assembly/deployment model to allow for users to easily create an application blueprint from someone elses environment.
#5 Create some consistency in implementation (share system templates via ACME_Corporation org in katello for example).
I'm curious as to what approaches are being considered in both aeolus and katello to allow for users to share their system templates and deployables with minimal effort. </pre>
</blockquote>
I'm not sure if there were any conversations regarding sharing of
templates between Katello and Aeolus. Personally, I think #5 looks
the most interesting. Both projects could have different internal
implementations of templates, but we should see if we can agree on
exchange format at the very least.<br>
<br>
-d <br>
<blockquote
cite="mid:713002230.8961790.1344882634730.JavaMail.root@redhat.com"
type="cite"><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
katello-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:katello-devel@redhat.com">katello-devel@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/katello-devel">https://www.redhat.com/mailman/listinfo/katello-devel</a></pre>
</blockquote>
<br>
<br>
</body>
</html>