<div dir="ltr">Hi Sergey<div>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:</div><div>(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.</div><div>(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 </div><div class="gmail_extra"><br><div class="gmail_quote">2015-05-12 0:49 GMT+08:00 Sergey Lukjanov <span dir="ltr"><<a href="mailto:slukjanov@mirantis.com" target="_blank">slukjanov@mirantis.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>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).</div><div><br></div><div>Thanks.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, May 11, 2015 at 6:39 PM, lu jander <span dir="ltr"><<a href="mailto:juvenboy1987@gmail.com" target="_blank">juvenboy1987@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi, All<div>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.</div><div><br></div><div>here is the bp, <a href="https://blueprints.launchpad.net/sahara/+spec/improve-oozie-share-lib" target="_blank">https://blueprints.launchpad.net/sahara/+spec/improve-oozie-share-lib</a> </div><div>I will write a spec soon after scheduled edp jobs bp.</div></div>
<br></div></div>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>Sincerely yours,<br>Sergey Lukjanov<br>Sahara Technical Lead<br>(OpenStack Data Processing)<br>Principal Software Engineer<br>Mirantis Inc.</div>
</font></span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>