Re: HTCondor Extension Help

2020-10-13 Thread DImuthu Upeksha
Hi Daniel,

We only have tested ide integration on MacOS and Ubuntu. However I just
managed to reproduce your issue in Windows 10 with WSL2 enabled and
commits [5-9] done to the develop branch should fix those issues. You might
have to merge those changes to your fork to make it effective and I
recommend getting a fresh clone to avoid unexpected behaviors due to temp
files. Let us know if it works for you.

[5]
https://github.com/apache/airavata/commit/f9b9e203fc268db468977680ab511f88a3eadc99
[6]
https://github.com/apache/airavata/commit/3794421f01fdb4ef5c0199fdfc6cfc15c25d2e7a
[7]
https://github.com/apache/airavata/commit/f581b61d44eb9a848b866456acd63f29e2bbfc8e
[8]
https://github.com/apache/airavata/commit/9e30529d7545a1df0b9d94c2783d7d11c32d301d
[9]
https://github.com/apache/airavata/commit/b11d81182f915491187dcf9f3ede5beeb5ea94a2

Thanks
Dimuthu

On Tue, Oct 13, 2020 at 6:37 PM Daniel Shchur 
wrote:

> Hi Dimuthu,
>
>
>
> Windows 10 2004 19041.508
>
> Docker v19.03.13 running on WSL2 - Ubuntu 20.04
>
>
>
> - Daniel Shchur
>
>
>
> *From: *DImuthu Upeksha 
> *Sent: *Tuesday, October 13, 2020 5:34 PM
> *To: *Airavata Dev 
> *Cc: *daniellthibod...@gmail.com; Evan Palmer
> 
> *Subject: *Re: HTCondor Extension Help
>
>
>
> Hi Daniel,
>
>
>
> I'm trying to reproduce the error locally. Can you please send me the
> following information of your local setup.
>
>
>
> OS / version
>
> Docker version
>
>
>
> Thanks
>
> Dimuthu
>
>
>
> On Tue, Oct 13, 2020 at 5:32 PM Daniel Shchur <
> daniel.shc...@huskers.unl.edu> wrote:
>
> Hi Dimunth,
>
>
>
> We have been trying to get the PGA running; however, it seems to fail
> building currently during the optimize portion. This is after having
> started the resources stack and starting the JobEngineStarter and
> AiravataAPI. Those parts start up without a hitch. I also added in the
> hosts file changes.
>
>
>
> The error is:
>
>
>
> > php artisan optimize
>
> Generating optimized class loader
>
> Compiling common classes
>
> Compiling views
>
>
>
>
>
>
>   [ErrorException]
>
>
>   
> file_put_contents(/var/www/portals/default/app/storage/views/16ac8ea2e3f88487e87226a07d300af0):
> failed to open stream: No such file or directory
>
>
>
>
>
>
> optimize [--force] [--psr]
>
>
>
> Script php artisan optimize handling the post-install-cmd event returned
> with error code 1
>
> Any help would be greatly appreciated. Thanks!
>
>
>
> - Daniel Shchur
>
>
>
> *From: *DImuthu Upeksha 
> *Sent: *Friday, October 9, 2020 8:46 AM
> *To: *Airavata Dev 
> *Cc: *daniellthibod...@gmail.com; Evan Palmer
> 
> *Subject: *Re: HTCondor Extension Help
>
>
>
> Hi Daniel,
>
>
>
> Please send you PR to airavata:htcondor branch which I created yesterday.
> Then I also can help you to speed up the development process.
>
>
>
> Thanks
>
> Dimuthu
>
>
>
> On Thu, Oct 8, 2020 at 5:59 PM Daniel Shchur <
> daniel.shc...@huskers.unl.edu> wrote:
>
> Hi Dimuthu,
>
>
>
> That clears up a lot of confusion. Thank you!
>
>
>
> - Daniel Shchur
>
>
>
> *From: *DImuthu Upeksha 
> *Sent: *Thursday, October 8, 2020 4:58 PM
> *To: *Airavata Dev 
> *Cc: *daniellthibod...@gmail.com; Evan Palmer
> 
> *Subject: *Re: HTCondor Extension Help
>
>
>
> Hi Daniel,
>
>
>
> That's correct, we assume all job manager configurations have unique set
> of command types like job submission, cancellation, status checking etc.
> It's up to the end user to specify the exact command for each command type.
> For example, SLURM job submission command is sbatch. So the user has to
> specify that though the portal which will eventually be stored in the
> database.
>
>
>
> Thanks
>
> Dimuthu
>
>
>
>
>
> On Thu, Oct 8, 2020 at 5:14 PM Daniel Shchur <
> daniel.shc...@huskers.unl.edu> wrote:
>
> Hi Dimuthu,
>
>
>
> So, to be clear,
>
>
>
> The relevant job submission commands are registered at the client-side? As
> in, the front end interface and are not hardcoded into the backend?
>
>
>
> - Daniel Shchur
>
>
>
> *From: *DImuthu Upeksha 
> *Sent: *Thursday, October 8, 2020 4:12 PM
> *To: *Airavata Dev 
> *Cc: *daniellthibod...@gmail.com; Evan Palmer
> 
> *Subject: *Re: HTCondor Extension Help
>
>
>
> Hi Daniel,
>
>
>
> If you look at [2], it's where the protocol specific configuration object
> is created. Each implementation is a subclass of the
> JobManagerConfiguration interface [3]. So each implementation might have
> different execution commands and those are stored in the database and you
> can register them through PGA. Please look at the screenshot I sent
> earlier. Once helix figured out the right Configuration implementation, it
> invokes it at the [4]. Please let me know if this is clear
>
>
>
> [2]
> https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/submission/config/JobFactory.java#L106
> 

RE: HTCondor Extension Help

2020-10-13 Thread Daniel Shchur
Hi Dimuthu,

Windows 10 2004 19041.508
Docker v19.03.13 running on WSL2 - Ubuntu 20.04

- Daniel Shchur

From: DImuthu Upeksha
Sent: Tuesday, October 13, 2020 5:34 PM
To: Airavata Dev
Cc: daniellthibod...@gmail.com; Evan 
Palmer
Subject: Re: HTCondor Extension Help

Hi Daniel,

I'm trying to reproduce the error locally. Can you please send me the following 
information of your local setup.

OS / version
Docker version

Thanks
Dimuthu

On Tue, Oct 13, 2020 at 5:32 PM Daniel Shchur 
mailto:daniel.shc...@huskers.unl.edu>> wrote:
Hi Dimunth,

We have been trying to get the PGA running; however, it seems to fail building 
currently during the optimize portion. This is after having started the 
resources stack and starting the JobEngineStarter and AiravataAPI. Those parts 
start up without a hitch. I also added in the hosts file changes.

The error is:

> php artisan optimize
Generating optimized class loader
Compiling common classes
Compiling views


  [ErrorException]
  
file_put_contents(/var/www/portals/default/app/storage/views/16ac8ea2e3f88487e87226a07d300af0):
 failed to open stream: No such file or directory


optimize [--force] [--psr]

Script php artisan optimize handling the post-install-cmd event returned with 
error code 1

Any help would be greatly appreciated. Thanks!

- Daniel Shchur

From: DImuthu Upeksha
Sent: Friday, October 9, 2020 8:46 AM
To: Airavata Dev
Cc: daniellthibod...@gmail.com; Evan 
Palmer
Subject: Re: HTCondor Extension Help

Hi Daniel,

Please send you PR to airavata:htcondor branch which I created yesterday. Then 
I also can help you to speed up the development process.

Thanks
Dimuthu

On Thu, Oct 8, 2020 at 5:59 PM Daniel Shchur 
mailto:daniel.shc...@huskers.unl.edu>> wrote:
Hi Dimuthu,

That clears up a lot of confusion. Thank you!

- Daniel Shchur

From: DImuthu Upeksha
Sent: Thursday, October 8, 2020 4:58 PM
To: Airavata Dev
Cc: daniellthibod...@gmail.com; Evan 
Palmer
Subject: Re: HTCondor Extension Help

Hi Daniel,

That's correct, we assume all job manager configurations have unique set of 
command types like job submission, cancellation, status checking etc. It's up 
to the end user to specify the exact command for each command type. For 
example, SLURM job submission command is sbatch. So the user has to specify 
that though the portal which will eventually be stored in the database.

[cid:1752417fd05197e1881]
Thanks
Dimuthu


On Thu, Oct 8, 2020 at 5:14 PM Daniel Shchur 
mailto:daniel.shc...@huskers.unl.edu>> wrote:
Hi Dimuthu,

So, to be clear,

The relevant job submission commands are registered at the client-side? As in, 
the front end interface and are not hardcoded into the backend?

- Daniel Shchur

From: DImuthu Upeksha
Sent: Thursday, October 8, 2020 4:12 PM
To: Airavata Dev
Cc: daniellthibod...@gmail.com; Evan 
Palmer
Subject: Re: HTCondor Extension Help

Hi Daniel,

If you look at [2], it's where the protocol specific configuration object is 
created. Each implementation is a subclass of the JobManagerConfiguration 
interface [3]. So each implementation might have different execution commands 
and those are stored in the database and you can register them through PGA. 
Please look at the screenshot I sent earlier. Once helix figured out the right 
Configuration implementation, it invokes it at the [4]. Please let me know if 
this is clear

[2] 
https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/submission/config/JobFactory.java#L106
[3] 

Re: HTCondor Extension Help

2020-10-13 Thread DImuthu Upeksha
Hi Daniel,

I'm trying to reproduce the error locally. Can you please send me the
following information of your local setup.

OS / version
Docker version

Thanks
Dimuthu

On Tue, Oct 13, 2020 at 5:32 PM Daniel Shchur 
wrote:

> Hi Dimunth,
>
>
>
> We have been trying to get the PGA running; however, it seems to fail
> building currently during the optimize portion. This is after having
> started the resources stack and starting the JobEngineStarter and
> AiravataAPI. Those parts start up without a hitch. I also added in the
> hosts file changes.
>
>
>
> The error is:
>
>
>
> > php artisan optimize
>
> Generating optimized class loader
>
> Compiling common classes
>
> Compiling views
>
>
>
>
>
>
>   [ErrorException]
>
>
>   
> file_put_contents(/var/www/portals/default/app/storage/views/16ac8ea2e3f88487e87226a07d300af0):
> failed to open stream: No such file or directory
>
>
>
>
>
>
> optimize [--force] [--psr]
>
>
>
> Script php artisan optimize handling the post-install-cmd event returned
> with error code 1
>
> Any help would be greatly appreciated. Thanks!
>
>
>
> - Daniel Shchur
>
>
>
> *From: *DImuthu Upeksha 
> *Sent: *Friday, October 9, 2020 8:46 AM
> *To: *Airavata Dev 
> *Cc: *daniellthibod...@gmail.com; Evan Palmer
> 
> *Subject: *Re: HTCondor Extension Help
>
>
>
> Hi Daniel,
>
>
>
> Please send you PR to airavata:htcondor branch which I created yesterday.
> Then I also can help you to speed up the development process.
>
>
>
> Thanks
>
> Dimuthu
>
>
>
> On Thu, Oct 8, 2020 at 5:59 PM Daniel Shchur <
> daniel.shc...@huskers.unl.edu> wrote:
>
> Hi Dimuthu,
>
>
>
> That clears up a lot of confusion. Thank you!
>
>
>
> - Daniel Shchur
>
>
>
> *From: *DImuthu Upeksha 
> *Sent: *Thursday, October 8, 2020 4:58 PM
> *To: *Airavata Dev 
> *Cc: *daniellthibod...@gmail.com; Evan Palmer
> 
> *Subject: *Re: HTCondor Extension Help
>
>
>
> Hi Daniel,
>
>
>
> That's correct, we assume all job manager configurations have unique set
> of command types like job submission, cancellation, status checking etc.
> It's up to the end user to specify the exact command for each command type.
> For example, SLURM job submission command is sbatch. So the user has to
> specify that though the portal which will eventually be stored in the
> database.
>
>
>
> Thanks
>
> Dimuthu
>
>
>
>
>
> On Thu, Oct 8, 2020 at 5:14 PM Daniel Shchur <
> daniel.shc...@huskers.unl.edu> wrote:
>
> Hi Dimuthu,
>
>
>
> So, to be clear,
>
>
>
> The relevant job submission commands are registered at the client-side? As
> in, the front end interface and are not hardcoded into the backend?
>
>
>
> - Daniel Shchur
>
>
>
> *From: *DImuthu Upeksha 
> *Sent: *Thursday, October 8, 2020 4:12 PM
> *To: *Airavata Dev 
> *Cc: *daniellthibod...@gmail.com; Evan Palmer
> 
> *Subject: *Re: HTCondor Extension Help
>
>
>
> Hi Daniel,
>
>
>
> If you look at [2], it's where the protocol specific configuration object
> is created. Each implementation is a subclass of the
> JobManagerConfiguration interface [3]. So each implementation might have
> different execution commands and those are stored in the database and you
> can register them through PGA. Please look at the screenshot I sent
> earlier. Once helix figured out the right Configuration implementation, it
> invokes it at the [4]. Please let me know if this is clear
>
>
>
> [2]
> https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/submission/config/JobFactory.java#L106
> 
>
> [3]
> https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/submission/config/JobManagerConfiguration.java
> 
>
> [4]
> https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/submission/JobSubmissionTask.java#L78
> 

RE: HTCondor Extension Help

2020-10-13 Thread Daniel Shchur
Hi Dimunth,

We have been trying to get the PGA running; however, it seems to fail building 
currently during the optimize portion. This is after having started the 
resources stack and starting the JobEngineStarter and AiravataAPI. Those parts 
start up without a hitch. I also added in the hosts file changes.

The error is:

> php artisan optimize
Generating optimized class loader
Compiling common classes
Compiling views


  [ErrorException]
  
file_put_contents(/var/www/portals/default/app/storage/views/16ac8ea2e3f88487e87226a07d300af0):
 failed to open stream: No such file or directory


optimize [--force] [--psr]

Script php artisan optimize handling the post-install-cmd event returned with 
error code 1

Any help would be greatly appreciated. Thanks!

- Daniel Shchur

From: DImuthu Upeksha
Sent: Friday, October 9, 2020 8:46 AM
To: Airavata Dev
Cc: daniellthibod...@gmail.com; Evan 
Palmer
Subject: Re: HTCondor Extension Help

Hi Daniel,

Please send you PR to airavata:htcondor branch which I created yesterday. Then 
I also can help you to speed up the development process.

Thanks
Dimuthu

On Thu, Oct 8, 2020 at 5:59 PM Daniel Shchur 
mailto:daniel.shc...@huskers.unl.edu>> wrote:
Hi Dimuthu,

That clears up a lot of confusion. Thank you!

- Daniel Shchur

From: DImuthu Upeksha
Sent: Thursday, October 8, 2020 4:58 PM
To: Airavata Dev
Cc: daniellthibod...@gmail.com; Evan 
Palmer
Subject: Re: HTCondor Extension Help

Hi Daniel,

That's correct, we assume all job manager configurations have unique set of 
command types like job submission, cancellation, status checking etc. It's up 
to the end user to specify the exact command for each command type. For 
example, SLURM job submission command is sbatch. So the user has to specify 
that though the portal which will eventually be stored in the database.

[cid:1750d9ac7f2197e1881]
Thanks
Dimuthu


On Thu, Oct 8, 2020 at 5:14 PM Daniel Shchur 
mailto:daniel.shc...@huskers.unl.edu>> wrote:
Hi Dimuthu,

So, to be clear,

The relevant job submission commands are registered at the client-side? As in, 
the front end interface and are not hardcoded into the backend?

- Daniel Shchur

From: DImuthu Upeksha
Sent: Thursday, October 8, 2020 4:12 PM
To: Airavata Dev
Cc: daniellthibod...@gmail.com; Evan 
Palmer
Subject: Re: HTCondor Extension Help

Hi Daniel,

If you look at [2], it's where the protocol specific configuration object is 
created. Each implementation is a subclass of the JobManagerConfiguration 
interface [3]. So each implementation might have different execution commands 
and those are stored in the database and you can register them through PGA. 
Please look at the screenshot I sent earlier. Once helix figured out the right 
Configuration implementation, it invokes it at the [4]. Please let me know if 
this is clear

[2] 
https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/submission/config/JobFactory.java#L106
[3] 
https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/submission/config/JobManagerConfiguration.java
[4]