<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><br class="Apple-interchange-newline">
</span><br class="Apple-interchange-newline">
</div>
<br>
<div>
<div>On Aug 27, 2013, at 18:52 , Russell Bryant <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">On 08/27/2013 10:53 AM, Alessandro Pilotti wrote:<br>
<blockquote type="cite">That's IMO a different story: backporting a driver is usually quite<br>
trivial as it affects only one service (nova-compute) and one<br>
interaction point with Nova (the driver's interface). Between Havana and<br>
Grizzly for example, the entire Hyper-V driver can be backported without<br>
substantial issues. On the deployment side, we have to care only about<br>
updating the code which runs con the compute nodes, using vanilla<br>
OpenStack components on the controller and remaining nodes.<br>
<br>
Backporting the public APIs is a whole different story, it affects way<br>
more components that need to be deployed (nova-api as a minimum of<br>
course), with way more interaction points that might incur into patching<br>
hell.<br>
</blockquote>
<br>
Do you really know that? This is pretty hand wavy. I think you're<br>
making this backport out to be _way_ more complicated than it is. I<br>
don't see why it's any more complicated than a virt driver feature backport.<br>
</blockquote>
<div><br>
</div>
<div>
<div>No, that's why I used "might" instead of "will" :-)</div>
<div><br>
</div>
</div>
<div>More important than the coding issue, there's the deployment and support issue for additional components that need to be mantained outside of the main code repo.</div>
<div><br>
</div>
<blockquote type="cite">
<blockquote type="cite">What about publishing the API as blacklisted by default? This way it<br>
would be available only to users that enable it explicitly, while still<br>
supporting the scenario described above.</blockquote>
</blockquote>
<blockquote type="cite">It still makes no sense to me to merge an API for a feature that can't<br>
be used.<br>
</blockquote>
<div><br>
</div>
<div>This depends on the definition of "can't be used":</div>
<div><br>
</div>
<div>It's a feature that can't be used in the Havana code base, but I can assure you that we would do good use of it by backporting the "I" code.</div>
<div><br>
</div>
<br>
<blockquote type="cite"><br>
-- <br>
Russell Bryant<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>
</blockquote>
</div>
<br>
</body>
</html>