Hi, 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.
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. 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. Thanks Georgy On Thu, Nov 14, 2013 at 11:08 AM, Christopher Armstrong < chris.armstr...@rackspace.com> wrote: > On Thu, Nov 14, 2013 at 11:04 AM, Sam Alba <sam.a...@gmail.com> wrote: > >> Hi Jay, >> >> I think Heat is an ingredient for Solum. When you build a PaaS, you >> need to control the app at different levels: >> >> #1 describing your app (basically your stack) >> #2 Pushing your code >> #3 Deploying it >> #4 Controlling the runtime (restart, get logs, scale, changing >> resources allocation, etc...) >> >> I think Heat is a major component for step 3. But I think Heat's job >> ends at the end of the deployment (the status of the stack is >> "COMPLETED" in Heat after processing the template correctly). It's >> nice though to rely on Heat's template generation for describing the >> stack, it's one more thing to delegate to Heat. >> >> In other words, I see Heat as an engine for deployment (at least in >> the context of Solum) and have something on top to manage the other >> steps. >> > > I'd say that Heat does (or should do) more than just the initial > deployment -- especially with recent discussion around healing / > convergence. > > -- > IRC: radix > Christopher Armstrong > Rackspace > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Georgy Okrokvertskhov Technical Program Manager, Cloud and Infrastructure Services, Mirantis http://www.mirantis.com Tel. +1 650 963 9828 Mob. +1 650 996 3284
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
