<div dir="ltr">Matt,<div><br></div><div>thanks, I'm agree with hadoop_version to version transition in v2 api.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 18, 2014 at 5:02 AM, Matthew Farrellee <span dir="ltr"><<a href="mailto:matt@redhat.com" target="_blank">matt@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">ok, i spent a little time looking at what the change impacts and it looks like all the template validations we have currently require hadoop_version. additionally, the client uses the name and documentation references it.<br>
<br>
due to the large number of changes and the difficulty in providing backward compatibility, i propose that we leave it as is for the v1 api & client and we change it for the v2 api & client.<br>
<br>
to that end, i've added 'verifying hadoop_version -> version' as a work item for both the v2-api-impl and v2-client.<br>
<br>
<a href="https://blueprints.launchpad.net/savanna/+spec/v2-api-impl" target="_blank">https://blueprints.launchpad.<u></u>net/savanna/+spec/v2-api-impl</a><br>
<br>
and<br>
<br>
<a href="https://blueprints.launchpad.net/python-savannaclient/+spec/v2-client" target="_blank">https://blueprints.launchpad.<u></u>net/python-savannaclient/+<u></u>spec/v2-client</a><br>
<br>
best,<br>
<br>
<br>
matt<div class=""><br>
<br>
On 02/17/2014 04:23 PM, Alexander Ignatov wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Agree to rename this legacy field to ‘version’. Adding to John's words<br>
about HDP, Vanilla plugin is able to run different hadoop versions by<br>
doing some manipulations with DIB scripts :-) So the right name of this<br>
field should be ‘version’ as version of engine of concrete plugin.<br>
<br>
Regards,<br>
Alexander Ignatov<br>
<br>
<br>
<br>
On 18 Feb 2014, at 01:01, John Speidel <<a href="mailto:jspeidel@hortonworks.com" target="_blank">jspeidel@hortonworks.com</a><br></div>
<mailto:<a href="mailto:jspeidel@hortonworks.com" target="_blank">jspeidel@hortonworks.<u></u>com</a>>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Andrew +1<br>
<br>
The HDP plugin also returns the HDP distro version. The version needs<br>
to make sense in the context of the plugin.<br>
Also, many plugins including the HDP plugin will support deployment of<br>
several hadoop versions.<br>
<br>
-John<br>
<br>
<br>
On Mon, Feb 17, 2014 at 2:36 PM, Andrew Lazarev <<a href="mailto:alazarev@mirantis.com" target="_blank">alazarev@mirantis.com</a><br></div><div class="">
<mailto:<a href="mailto:alazarev@mirantis.com" target="_blank">alazarev@mirantis.com</a>><u></u>> wrote:<br>
<br>
IDH uses version of IDH distro and there is no direct mapping<br>
between distro version and hadoop version. E.g. IDH 2.5.1 works<br>
with apache hadoop 1.0.3.<br>
<br>
I suggest to call the field as just 'version' everywhere and<br>
assume this version as plugin specific property.<br>
<br>
Andrew.<br>
<br>
<br>
On Mon, Feb 17, 2014 at 5:06 AM, Matthew Farrellee<br></div><div class="">
<<a href="mailto:matt@redhat.com" target="_blank">matt@redhat.com</a> <mailto:<a href="mailto:matt@redhat.com" target="_blank">matt@redhat.com</a>>> wrote:<br>
<br>
$ savanna plugins-list<br></div>
+---------+----------+--------<u></u>__-------------------+<br>
| name | versions | title |<br>
+---------+----------+--------<u></u>__-------------------+<div class=""><br>
| vanilla | 1.2.1 | Vanilla Apache Hadoop |<br>
| hdp | 1.3.2 | Hortonworks Data Platform |<br></div>
+---------+----------+--------<u></u>__-------------------+<div class=""><br>
<br>
above is output from the /plugins endpoint -<br></div>
<a href="http://docs.openstack.org/__developer/savanna/userdoc/__rest_api_v1.0.html#plugins" target="_blank">http://docs.openstack.org/__<u></u>developer/savanna/userdoc/__<u></u>rest_api_v1.0.html#plugins</a><div class="">
<br>
<<a href="http://docs.openstack.org/developer/savanna/userdoc/rest_api_v1.0.html#plugins" target="_blank">http://docs.openstack.org/<u></u>developer/savanna/userdoc/<u></u>rest_api_v1.0.html#plugins</a>><br>
<br>
the question is, should the version be the version of the<br>
plugin or the version of hadoop the plugin installs?<br>
<br>
i ask because it seems like we have version == plugin version<br>
for hdp and version == hadoop version for vanilla.<br>
<br>
the documentation is somewhat vague on the subject, mostly<br>
stating "version" without qualification. however, the json<br>
passed to the service references "hadoop_version" and the<br>
arguments in the client are called "hadoop_version"<br>
<br>
fyi, this could be complicated by the idh and spark plugins.<br>
<br>
best,<br>
<br>
<br>
matt<br>
<br></div>
______________________________<u></u>___________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.<u></u>__org<br>
<mailto:<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.<u></u>openstack.org</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-dev</a><div class=""><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a>><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br></div>
<mailto:<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.<u></u>openstack.org</a>><div class=""><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
<br>
<br>
CONFIDENTIALITY NOTICE<br>
NOTICE: This message is intended for the use of the individual or<br>
entity to which it is addressed and may contain information that is<br>
confidential, privileged and exempt from disclosure under applicable<br>
law. If the reader of this message is not the intended recipient, you<br>
are hereby notified that any printing, copying, dissemination,<br>
distribution, disclosure or forwarding of this communication is<br>
strictly prohibited. If you have received this communication in error,<br>
please contact the sender immediately and delete it from your system.<br>
Thank You.__________________________<u></u>_____________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br></div>
<mailto:<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.<u></u>openstack.org</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote><div class="">
<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>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>