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
