Open Stack

Hi Sergey
yes, it is based on job binaries. what we should do is provide a user
friendly interface, to let user know how to set oozie.libpath( may be we
can show it as "share lib path" in the job execution config horizon page)
 there are two scenarios as below:
(1) if Job A and Job B all need lib A, we can upload lib A through job
binary into sahara, then before we run Job A and B, user can set
oozie.libpath to the path where lib A exists.
(2) if Job A and Job B need system lib or other libs already exists in the
OS, user needs not to upload additional job binary

2015-05-12 0:49 GMT+08:00 Sergey Lukjanov <slukjanov at mirantis.com>:

> Hi,
>
> do you think it could be implemented based on job binaries? It sounds like
> it's a type of job binary that should be always uploaded to Oozie for the
> tenant where it lives. (A bit crazy, but could useful).
>
> Thanks.
>
> On Mon, May 11, 2015 at 6:39 PM, lu jander <juvenboy1987 at gmail.com> wrote:
>
>> Hi, All
>> Currently, oozie share lib is not well known and can be hardly used by
>> the users, so I think we can  make it less oozieness and more friendly for
>> the users, it can be used for running jobs which are using third party
>> libs. If many jobs use the same libs, oozie share lib can make it as a
>> common share lib.
>>
>> here is the bp,
>> https://blueprints.launchpad.net/sahara/+spec/improve-oozie-share-lib
>> I will write a spec soon after scheduled edp jobs bp.
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Sincerely yours,
> Sergey Lukjanov
> Sahara Technical Lead
> (OpenStack Data Processing)
> Principal Software Engineer
> Mirantis Inc.
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150512/023a8850/attachment.html>