Matt, thanks, I'm agree with hadoop_version to version transition in v2 api.
On Tue, Feb 18, 2014 at 5:02 AM, Matthew Farrellee <m...@redhat.com> wrote: > 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. > > 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. > > to that end, i've added 'verifying hadoop_version -> version' as a work > item for both the v2-api-impl and v2-client. > > https://blueprints.launchpad.net/savanna/+spec/v2-api-impl > > and > > https://blueprints.launchpad.net/python-savannaclient/+spec/v2-client > > best, > > > matt > > > On 02/17/2014 04:23 PM, Alexander Ignatov wrote: > >> Agree to rename this legacy field to 'version'. Adding to John's words >> about HDP, Vanilla plugin is able to run different hadoop versions by >> doing some manipulations with DIB scripts :-) So the right name of this >> field should be 'version' as version of engine of concrete plugin. >> >> Regards, >> Alexander Ignatov >> >> >> >> On 18 Feb 2014, at 01:01, John Speidel <jspei...@hortonworks.com >> <mailto:jspei...@hortonworks.com>> wrote: >> >> Andrew +1 >>> >>> The HDP plugin also returns the HDP distro version. The version needs >>> to make sense in the context of the plugin. >>> Also, many plugins including the HDP plugin will support deployment of >>> several hadoop versions. >>> >>> -John >>> >>> >>> On Mon, Feb 17, 2014 at 2:36 PM, Andrew Lazarev <alaza...@mirantis.com >>> <mailto:alaza...@mirantis.com>> wrote: >>> >>> IDH uses version of IDH distro and there is no direct mapping >>> between distro version and hadoop version. E.g. IDH 2.5.1 works >>> with apache hadoop 1.0.3. >>> >>> I suggest to call the field as just 'version' everywhere and >>> assume this version as plugin specific property. >>> >>> Andrew. >>> >>> >>> On Mon, Feb 17, 2014 at 5:06 AM, Matthew Farrellee >>> <m...@redhat.com <mailto:m...@redhat.com>> wrote: >>> >>> $ savanna plugins-list >>> +---------+----------+--------__-------------------+ >>> | name | versions | title | >>> +---------+----------+--------__-------------------+ >>> >>> | vanilla | 1.2.1 | Vanilla Apache Hadoop | >>> | hdp | 1.3.2 | Hortonworks Data Platform | >>> +---------+----------+--------__-------------------+ >>> >>> >>> above is output from the /plugins endpoint - >>> http://docs.openstack.org/__developer/savanna/userdoc/__ >>> rest_api_v1.0.html#plugins >>> >>> <http://docs.openstack.org/developer/savanna/userdoc/ >>> rest_api_v1.0.html#plugins> >>> >>> the question is, should the version be the version of the >>> plugin or the version of hadoop the plugin installs? >>> >>> i ask because it seems like we have version == plugin version >>> for hdp and version == hadoop version for vanilla. >>> >>> the documentation is somewhat vague on the subject, mostly >>> stating "version" without qualification. however, the json >>> passed to the service references "hadoop_version" and the >>> arguments in the client are called "hadoop_version" >>> >>> fyi, this could be complicated by the idh and spark plugins. >>> >>> best, >>> >>> >>> matt >>> >>> _________________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.__org >>> <mailto:OpenStack-dev@lists.openstack.org> >>> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__ >>> openstack-dev >>> >>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/ >>> openstack-dev> >>> >>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> <mailto:OpenStack-dev@lists.openstack.org> >>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> CONFIDENTIALITY NOTICE >>> NOTICE: This message is intended for the use of the individual or >>> entity to which it is addressed and may contain information that is >>> confidential, privileged and exempt from disclosure under applicable >>> law. If the reader of this message is not the intended recipient, you >>> are hereby notified that any printing, copying, dissemination, >>> distribution, disclosure or forwarding of this communication is >>> strictly prohibited. If you have received this communication in error, >>> please contact the sender immediately and delete it from your system. >>> Thank You._______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> <mailto:OpenStack-dev@lists.openstack.org> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
