<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi Salvatore,</div>
<div><br>
</div>
<div>Two questions/remarks below.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Salvatore Orlando <<a href="mailto:sorlando@nicira.com">sorlando@nicira.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>onsdag 6 maj 2015 00:13<br>
<span style="font-weight:bold">To: </span>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] [neutron][api] Extensions out, Micro-versions in<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div>#5 Plugin/Vendor specific APIs</div>
<div><br>
</div>
<div>Neutron is without doubt the project with the highest number of 3rd party (OSS and commercial) integration. After all it was mostly vendors who started this project.</div>
<div>Vendors [4] use the extension mechanism to expose features in their products not covered by the Neutron API or to provide some sort of value-added service.</div>
<div>The current proposal still allows 3rd parties to attach extensions to the neutron API, provided that:</div>
<div>- they're not considered part of the Neutron API, in terms of versioning, documentation, and client support</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>BOB> There are today vendor specific commands in the Neutron CLI client. Such commands are prepended with the name of the vendor, like cisco_<command> and nec_<command>.</div>
<div>I think that makes it quite visible to the user that the command is specific to a vendor feature and not part of neutron core. Would it be possible to allow for that also going forward? I would think that from a user perspective it can be convenient to
be able to access vendor add-on features using a single CLI client.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir="ltr">
<div>- they do not redefine resources defined by the Neutron API.</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>BOB> Does “redefine" here include extending a resource with additional attributes?</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir="ltr">
<div>- they do not live in the neutron source tree</div>
<div>The aim of the provisions above is to minimize the impact of such extensions on API portability.</div>
<div><br>
</div>
<div>Thanks for reading and thanks in advance for your feedback,<br>
</div>
<div>Salvatore</div>
<div><br>
</div>
<div>The title of this post has been inspired by [2] (the message in the banner may be unintelligible to readers not fluent in european football)<br>
</div>
<div><br>
</div>
[1] <a href="https://review.openstack.org/#/c/136760/">https://review.openstack.org/#/c/136760/</a>
<div>[2] <a href="http://a.espncdn.com/combiner/i/?img=/photo/2015/0502/fc-banner-jd-1296x729.jpg&w=738&site=espnfc">http://a.espncdn.com/combiner/i/?img=/photo/2015/0502/fc-banner-jd-1296x729.jpg&w=738&site=espnfc</a></div>
<div>[3] <a href="http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/api-microversions.html">http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/api-microversions.html</a></div>
<div>[4] By "vendor" here we refer either to a cloud provider or a company providing Neutron integration for their products.</div>
</div>
</div>
</div>
</span>
</body>
</html>