<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">That's an important question, and I've seen it being asked many times before, often regarding the Murano project, which also hides Heat templates under the hood: people were asking why do they need yet another abstraction layer on top of the familiar and powerful tool such as Heat.</div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I believe that the difference is the target audience of the projects. It seems to me that Heat's primary users are the people who will write their own templates - or use the existing ones but having a deep understanding of how their work.</div>
<div class="gmail_default" style="font-size:small">Meanwhile, the end-users of Solum are application developers, they do not need (and, probably, do not want at all) to worry about infrastructure-specific tools, frameworks and APIs - and they are probably not going to write the Heat (or HOT) templates on their own: they need a higher-level tooling for that. And that is exactly the place where Solum will come into play, generating these templates for them.</div>
<div class="gmail_extra"><br clear="all"><div><div dir="ltr"><font>--<br></font><div dir="ltr"><font>Regards,<br>Alexander Tivelkov</font></div></div></div>
<br><br><div class="gmail_quote">2013/11/14 Georgy Okrokvertskhov <span dir="ltr"><<a href="mailto:gokrokvertskhov@mirantis.com" target="_blank">gokrokvertskhov@mirantis.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,<div><br></div><div>I think that Heat is mostly focused on deployment even with new software configs and convergence. HOT template is quite "static" description of desired state we want to achieve and it is up to Heat engine how to achieve this state.</div>
<div><br></div><div>Solum is focused on managing the process of converting source code to some deployable entity (image or container). The power of Solum is an ability to fully describe and control the process of building and testing of application. Some of the stages of build and testing process might require actual deployment and stack creation, but this is not an ultimate goal of the Solum. </div>
<div><br></div><div>If someone will try to use just Heat for building process description they will figure out quickly that they need different templates for different build\testing stages. As Heat itself can't modify templates you will need some external mechanism for template creation, and this is what Solum actually does.</div>
<div><br></div><div>Thanks</div><div>Georgy</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Thu, Nov 14, 2013 at 11:08 AM, Christopher Armstrong <span dir="ltr"><<a href="mailto:chris.armstrong@rackspace.com" target="_blank">chris.armstrong@rackspace.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div>On Thu, Nov 14, 2013 at 11:04 AM, Sam Alba <span dir="ltr"><<a href="mailto:sam.alba@gmail.com" target="_blank">sam.alba@gmail.com</a>></span> wrote:<br>
</div><div class="gmail_extra"><div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Jay,<br>
<br>
I think Heat is an ingredient for Solum. When you build a PaaS, you<br>
need to control the app at different levels:<br>
<br>
#1 describing your app (basically your stack)<br>
#2 Pushing your code<br>
#3 Deploying it<br>
#4 Controlling the runtime (restart, get logs, scale, changing<br>
resources allocation, etc...)<br>
<br>
I think Heat is a major component for step 3. But I think Heat's job<br>
ends at the end of the deployment (the status of the stack is<br>
"COMPLETED" in Heat after processing the template correctly). It's<br>
nice though to rely on Heat's template generation for describing the<br>
stack, it's one more thing to delegate to Heat.<br>
<br>
In other words, I see Heat as an engine for deployment (at least in<br>
the context of Solum) and have something on top to manage the other<br>
steps.<br></blockquote><div><br></div></div><div>I'd say that Heat does (or should do) more than just the initial deployment -- especially with recent discussion around healing / convergence.</div><span><font color="#888888"><div>
<br></div></font></span></div><span><font color="#888888">-- <br>
<div dir="ltr"><div>IRC: radix</div>Christopher Armstrong<div>Rackspace</div></div>
</font></span></div></div>
<br></div></div><div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></div></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Georgy Okrokvertskhov<br>
Technical Program Manager,<br>Cloud and Infrastructure Services,<br>
Mirantis<br>
<a href="http://www.mirantis.com/" target="_blank">http://www.mirantis.com</a><br>
Tel. +1 650 963 9828<br>
Mob. +1 650 996 3284<br>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>