https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362008-01-16T22:56:32ZEcoinformatics RedmineKepler - Bug #3071: KAR files should be sent along with workflow to slaveshttps://projects.ecoinformatics.org/ecoinfo/issues/3071?journal_id=105072008-01-16T22:56:32ZChad Berkleyberkley@nceas.ucsb.edu
<ul></ul><p>kar files should be signed so that the recipient at least can know that they are coming from who they should be.</p> Kepler - Bug #3071: KAR files should be sent along with workflow to slaveshttps://projects.ecoinformatics.org/ecoinfo/issues/3071?journal_id=105082010-03-29T19:43:17Zjianwu jianwujianwu@sdsc.edu
<ul></ul><p>In the new KAR specification of the coming Kepler 2.0, KAR files can not include actor classes and jars. So parsing KAR files won't enable slave execute them if the actors are not in the suite of slave.</p>
<p>The current assumption of master-slave execution is that all actors in DistributedCompositeActor should also in the slave sides. Usually master and slave need to be in the same suite.</p>
<p>Using module mechanism of Kepler 2.0, published modules could be dynamically gotten by slave. Yet it is heavy requirement that the modules have to be published.</p>
<p>The current decision is to postpone this bug and ask master and slave nodes have the same suite (including master-slave module) before using DistributedCompositeActor.</p> Kepler - Bug #3071: KAR files should be sent along with workflow to slaveshttps://projects.ecoinformatics.org/ecoinfo/issues/3071?journal_id=105092013-03-27T21:22:11ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 3071</p>