On Fri, Jan 10, 2014 at 11:01 AM, Imre Farkas <ifar...@redhat.com> wrote: > On 01/10/2014 04:27 PM, Jay Dobies wrote: >>> There's few pieces of concepts which I think is missing from the list: >>> - overclouds: after Heat successfully created the stack, Tuskar needs to >>> keep track whether it applied the post configuration steps (Keystone >>> initialization, registering services, etc) or not. It also needs to know >>> the name of the stack (only 1 stack named 'overcloud' for Icehouse). >> >> >> I assumed this sort of thing was captured by the resource status, though >> I'm far from a Heat expert. Is it not enough to assume that if the >> resource started successfully, all of that took place? >> > > I am also far from a Heat expert, I just had a some really hard times when I > previously expected from my Tuskar deployed overcloud that it's ready to > use. :-) > > In short, having the resources started is not enough, Heat stack-create is > only a part of the deployment story. There was a few emails on the mailing > list about this: > http://lists.openstack.org/pipermail/openstack-dev/2013-December/022217.html > http://lists.openstack.org/pipermail/openstack-dev/2013-December/022887.html > > There was also a discussion during the last TripleO meeting in December, > check the topic 'After heat stack-create init operations (lsmola)' > http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-12-17-19.02.log.html
Thanks for posting the links :) Very helpful. There are some really good points there in the irc log about *not* doing what I suggested with the local machine os-refresh-config scripts :). So, I think it's likely that Tuskar will need to orchestrate this setup in some fasion. -- -- James Slagle -- _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
