<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Mon, Oct 1, 2018 at 8:03 AM Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/01/2018 04:36 AM, John Garbutt wrote:<br>
> On Fri, 28 Sep 2018 at 00:46, Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a> <br>
> <mailto:<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>>> wrote:<br>
> <br>
> On 09/27/2018 06:23 PM, Matt Riedemann wrote:<br>
> > On 9/27/2018 3:02 PM, Jay Pipes wrote:<br>
> >> A great example of this would be the proposed "deploy template"<br>
> from<br>
> >> [2]. This is nothing more than abusing the placement traits API in<br>
> >> order to allow passthrough of instance configuration data from the<br>
> >> nova flavor extra spec directly into the nodes.instance_info<br>
> field in<br>
> >> the Ironic database. It's a hack that is abusing the entire<br>
> concept of<br>
> >> the placement traits concept, IMHO.<br>
> >><br>
> >> We should have a way *in Nova* of allowing instance configuration<br>
> >> key/value information to be passed through to the virt driver's<br>
> >> spawn() method, much the same way we provide for user_data that<br>
> gets<br>
> >> exposed after boot to the guest instance via configdrive or the<br>
> >> metadata service API. What this deploy template thing is is just a<br>
> >> hack to get around the fact that nova doesn't have a basic way of<br>
> >> passing through some collated instance configuration key/value<br>
> >> information, which is a darn shame and I'm really kind of<br>
> annoyed with<br>
> >> myself for not noticing this sooner. :(<br>
> ><br>
> > We talked about this in Dublin through right? We said a good<br>
> thing to do<br>
> > would be to have some kind of template/profile/config/whatever<br>
> stored<br>
> > off in glare where schema could be registered on that thing, and<br>
> then<br>
> > you pass a handle (ID reference) to that to nova when creating the<br>
> > (baremetal) server, nova pulls it down from glare and hands it<br>
> off to<br>
> > the virt driver. It's just that no one is doing that work.<br>
> <br>
> No, nobody is doing that work.<br>
> <br>
> I will if need be if it means not hacking the placement API to serve<br>
> this purpose (for which it wasn't intended).<br>
> <br>
> <br>
> Going back to the point Mark Goddard made, there are two things here:<br>
> <br>
> 1) Picking the correct resource provider<br>
> 2) Telling Ironic to transform the picked node in some way<br>
> <br>
> Today we allow the use Capabilities for both.<br>
> <br>
> I am suggesting we move to using Traits only for (1), leaving (2) in <br>
> place for now, while we decide what to do (i.e. future of "deploy <br>
> template" concept).<br>
> <br>
> It feels like Ironic's plan to define the "deploy templates" in Ironic <br>
> should replace the dependency on Glare for this use case, largely <br>
> because the definition of the deploy template (in my mind) is very <br>
> heavily related to inspector and driver properties, etc. Mark is looking <br>
> at moving that forward at the moment.<br>
<br>
That won't do anything about the flavor explosion problem, though, right <br>
John?<br></blockquote><div><br></div><div>Does nova still plan to allow passing additional desired traits into the server create request?</div><div>I (we?) was kind of banking on that to solve the Baskin Robbins thing.</div><div><br></div><div>// jim</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-jay<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div>