<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">Le 28/09/2015 12:35, Duncan Thomas a
écrit :<br>
</div>
<blockquote
cite="mid:CAOyZ2aHo-mU99ktue_W0qUt1Du6uY--ANDceQ4xufKf5LBB64w@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 28 September 2015 at 12:35,
Sylvain Bauza <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sbauza@redhat.com" target="_blank">sbauza@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">About the
maintenance burden, I also consider that patching
clients is far more easier than patching an API unless I
missed something.<span class="HOEnZb"><font
color="#888888"><br>
<br>
</font></span></div>
</blockquote>
<div><br>
</div>
<div>I think I very much disagree there - patching a central
installation is much, much easier than getting N customers
to patch M different libraries, even assuming the fix is
available for any significant subset of the M libraries,
plus making sure that new customers use the correct
libraries, plus helping any customers who have some sort
of roll-your-own library do the new right thing...</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Well, having N versions of clients against one single API version is
just something we manage since the beginning. I don't really see why
it suddently becomes so difficult to manage it.<br>
<br>
<br>
<blockquote
cite="mid:CAOyZ2aHo-mU99ktue_W0qUt1Du6uY--ANDceQ4xufKf5LBB64w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>I think there's a definite place for a simple API to do
infrastructure level orchestration without needing the
complexities of heat - these APIs are in nova because
they're useful - there's clear operator desire for them
and a couple of operators have been quite vocal about
their desire for them not to be removed. Great, let's keep
them, but form a team of people interested in getting them
right (get rid of fixed timeouts, etc), add any missing
pieces (like floating IPs for new VMs) and generally focus
on getting this piece of the puzzle right. Breaking
another small piece off nova and polishing it has been a
generally successful pattern.</div>
</div>
</div>
</div>
</blockquote>
<br>
I don't want to overthink what could be the right scope of that
future API but given the Heat mission statement [1] and its service
name 'orchestration', I don't see why this API endpoint should land
in the Nova codebase and couldn't be rather provided by the Heat
API. Oh sure, it would perhaps require another endpoint behind the
same service, but isn't that better than having another endpoint in
Nova ?<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://github.com/openstack/governance/blob/master/reference/projects.yaml#L482-L484">https://github.com/openstack/governance/blob/master/reference/projects.yaml#L482-L484</a><br>
<br>
<br>
<blockquote
cite="mid:CAOyZ2aHo-mU99ktue_W0qUt1Du6uY--ANDceQ4xufKf5LBB64w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>I remember Monty Taylor (copied) having a rant about
the lack of the perfect 'give me a VM with all its stuff
sorted' API. Care to comment, Monty?</div>
</div>
</div>
</div>
</blockquote>
<br>
Sounds you misunderstood me. I'm not against implementing this
excellent usecase, I just think the best place is not in Nova and
should be done elsewhere.<br>
<br>
<blockquote
cite="mid:CAOyZ2aHo-mU99ktue_W0qUt1Du6uY--ANDceQ4xufKf5LBB64w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>