<div dir="ltr">It sounds little useful for dev/testing, I'm not really think that it's needed, but not -1 such addition to the REST API. </div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 30, 2014 at 7:52 PM, Trevor McKay <span dir="ltr"><<a href="mailto:tmckay@redhat.com" target="_blank">tmckay@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">My mistake, it's already there. I missed the distinction between set on<br>
startup and set per cluster.<br>
<br>
Trev<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, 2014-01-30 at 10:50 -0500, Trevor McKay wrote:<br>
> +1<br>
><br>
> How about an undocumented config?<br>
><br>
> Trev<br>
><br>
> On Thu, 2014-01-30 at 09:24 -0500, Matthew Farrellee wrote:<br>
> > i imagine this is something that can be useful in a development and<br>
> > testing environment, especially during the transition period from direct<br>
> > to heat. so having the ability is not unreasonable, but i wouldn't<br>
> > expose it to users via the dashboard (maybe not even directly in the cli)<br>
> ><br>
> > generally i want to reduce the number of parameters / questions the user<br>
> > is asked<br>
> ><br>
> > best,<br>
> ><br>
> ><br>
> > matt<br>
> ><br>
> > On 01/30/2014 04:42 AM, Dmitry Mescheryakov wrote:<br>
> > > I agree with Andrew. I see no value in letting users select how their<br>
> > > cluster is provisioned, it will only make interface a little bit more<br>
> > > complex.<br>
> > ><br>
> > > Dmitry<br>
> > ><br>
> > ><br>
> > > 2014/1/30 Andrew Lazarev <<a href="mailto:alazarev@mirantis.com">alazarev@mirantis.com</a><br>
> > > <mailto:<a href="mailto:alazarev@mirantis.com">alazarev@mirantis.com</a>>><br>
> > ><br>
> > > Alexander,<br>
> > ><br>
> > > What is the purpose of exposing this to user side? Both engines must<br>
> > > do exactly the same thing and they exist in the same time only for<br>
> > > transition period until heat engine is stabilized. I don't see any<br>
> > > value in proposed option.<br>
> > ><br>
> > > Andrew.<br>
> > ><br>
> > ><br>
> > > On Wed, Jan 29, 2014 at 8:44 PM, Alexander Ignatov<br>
> > > <<a href="mailto:aignatov@mirantis.com">aignatov@mirantis.com</a> <mailto:<a href="mailto:aignatov@mirantis.com">aignatov@mirantis.com</a>>> wrote:<br>
> > ><br>
> > > Today Savanna has two provisioning engines, heat and old one<br>
> > > known as 'direct'.<br>
> > > Users can choose which engine will be used by setting special<br>
> > > parameter in 'savanna.conf'.<br>
> > ><br>
> > > I have an idea to give an ability for users to define<br>
> > > provisioning engine<br>
> > > not only when savanna is started but when new cluster is<br>
> > > launched. The idea is simple.<br>
> > > We will just add new field 'provisioning_engine' to 'cluster'<br>
> > > and 'cluster_template'<br>
> > > objects. And profit is obvious, users can easily switch from one<br>
> > > engine to another without<br>
> > > restarting savanna service. Of course, this parameter can be<br>
> > > omitted and the default value<br>
> > > from the 'savanna.conf' will be applied.<br>
> > ><br>
> > > Is this viable? What do you think?<br>
> > ><br>
> > > Regards,<br>
> > > Alexander Ignatov<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > OpenStack-dev mailing list<br>
> > > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> > > <mailto:<a href="mailto:OpenStack-dev@lists.openstack.org">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>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > OpenStack-dev mailing list<br>
> > > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> > > <mailto:<a href="mailto:OpenStack-dev@lists.openstack.org">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>
> > ><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > OpenStack-dev mailing list<br>
> > > <a href="mailto:OpenStack-dev@lists.openstack.org">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>
> ><br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org">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>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Sincerely yours,</div><div>Sergey Lukjanov</div><div>Savanna Technical Lead</div><div>Mirantis Inc.</div></div>
</div>