<html><body>
<p><tt><font size="2">Georgy Okrokvertskhov <gokrokvertskhov@mirantis.com> wrote on 10/28/2013 02:18:42 PM:<br>
<br>
> <br>
> I believe the extensions you proposed will extend HOT software <br>
> components usability. In general I have only one concern related to <br>
> components naming. In your examples you have software components <br>
> like install_mysql (you got it from Steve's example) and configure_app. </font></tt><br>
<tt><font size="2">> I would say, that these components are not software components, but <br>
> some actions on software components. This is a small deviation from <br>
> declarative approach as in general declarative objects more or less <br>
> independent while actions are naturally have some sequence. For <br>
> example your configure_app should not be executed before install_app<br>
> and technically it is the same component on different stages. I <br>
> don't know what is inside puppet manifest in configure_app but it <br>
> might contain app installation phase or might not.</font></tt><br>
<tt><font size="2">> <br>
> From my perspective it will be better to add some concepts of <br>
> actions for components and have some predefined actions like <br>
> pre_install, install, post_install and probably some custom actions.<br>
> This will be more clear approach then declaring action as a software<br>
> component. This is quite typical approach in different PaaS solutions. </font></tt><br>
<br>
<tt><font size="2">I agree with you that the components in the proposal and our examples</font></tt><br>
<tt><font size="2">resemble more of actions. In fact, we actually find them similar to the</font></tt><br>
<tt><font size="2">concept of "automations" which is a generic term used to refer to any</font></tt><br>
<tt><font size="2">kind of script/recipes/etc. that does software install/configuration. So,</font></tt><br>
<tt><font size="2">I am open to a better name for them.</font></tt><br>
<br>
</body></html>