Re: [Airavata] : Local Provider

[Ajinkya Dhamnaskar <ad...@umail.iu.edu>]

Hello,

This is regarding database changes that we had to make to fix Local
provider.

I have added SECURITY_PROTOCOL column in LOCAL_SUBMISSION table. So, if
someone does not want to build database from scratch use below commands to
add these changes without hampering existing data.

ALTER TABLE LOCAL_SUBMISSION ADD COLUMN SECURITY_PROTOCOL VARCHAR (255);

UPDATE LOCAL_SUBMISSION SET SECURITY_PROTOCOL = 'LOCAL';

ALTER TABLE LOCAL_SUBMISSION MODIFY COLUMN SECURITY_PROTOCOL VARCHAR (255)
NOT NULL;
Please revert if you have any questions.

On Thu, Sep 29, 2016 at 4:18 PM, Shameera Rathnayaka <shameerainfo@gmail.com
> wrote:

> Hi Ajinkay,
>
> In Airavata we use Java Executor Services comes with java concurrency
> package for thread management, so we have delegate thread creation and
> management to Java instead of doing it all by ourselves. To be specific we
> used Fixed ThreadPool Executor inside Airavata. There are both good and bad
> in Thread vs Processes. If we use processes to run this local jobs then you
> have to manage process creation and deletion all by yourself anyway it is
> not a good practice to write long running synchronous jobs so we can assume
> these synchronous jobs are small in execution time.
>
> Thanks,
> Shameera.
>
> On Thu, Sep 29, 2016 at 2:36 PM Ajinkya Dhamnaskar <ad...@umail.iu.edu>
> wrote:
>
>> Hello All,
>>
>> For local provider I was exploring different ways to submit and get the
>> job done. As, it is a local provider we need not to have monitoring system
>> in place, simply forking a job on different thread should serve the
>> purpose.
>>
>> But, to do so we need to keep investigation that thread. In my opinion,
>> ProcessBuilder in java would be handy in this case or if you have any other
>> suggestions please do let me know.
>>
>> Just want to know and use if there is any better way to this.
>>
>> Thanks in anticipation
>> --
>> Thanks and regards,
>>
>> Ajinkya Dhamnaskar
>> Student ID : 0003469679
>> Masters (CS)
>> +1 (812) 369- 5416
>>
> --
> Shameera Rathnayaka
>



-- 
Thanks and regards,

Ajinkya Dhamnaskar
Student ID : 0003469679
Masters (CS)
+1 (812) 369- 5416

Re: [Airavata] : Local Provider

[Lahiru Ginnaliya Gamathige <gl...@gmail.com>]

What is the standard procedure for doing database migrations ? Do we
release a migration script for each release ?

On Fri, Oct 7, 2016 at 8:12 AM, Ajinkya Dhamnaskar <ad...@umail.iu.edu>
wrote:

> Hello,
>
> This is regarding database changes that we had to make to fix Local
> provider.
>
> I have added SECURITY_PROTOCOL column in LOCAL_SUBMISSION table. So, if
> someone does not want to build database from scratch use below commands to
> add these changes without hampering existing data.
>
> ALTER TABLE LOCAL_SUBMISSION ADD COLUMN SECURITY_PROTOCOL VARCHAR (255);
>
> UPDATE LOCAL_SUBMISSION SET SECURITY_PROTOCOL = 'LOCAL';
>
> ALTER TABLE LOCAL_SUBMISSION MODIFY COLUMN SECURITY_PROTOCOL VARCHAR (255)
> NOT NULL;
> Please revert if you have any questions.
>
> On Thu, Sep 29, 2016 at 4:18 PM, Shameera Rathnayaka <
> shameerainfo@gmail.com> wrote:
>
>> Hi Ajinkay,
>>
>> In Airavata we use Java Executor Services comes with java concurrency
>> package for thread management, so we have delegate thread creation and
>> management to Java instead of doing it all by ourselves. To be specific we
>> used Fixed ThreadPool Executor inside Airavata. There are both good and bad
>> in Thread vs Processes. If we use processes to run this local jobs then you
>> have to manage process creation and deletion all by yourself anyway it is
>> not a good practice to write long running synchronous jobs so we can assume
>> these synchronous jobs are small in execution time.
>>
>> Thanks,
>> Shameera.
>>
>> On Thu, Sep 29, 2016 at 2:36 PM Ajinkya Dhamnaskar <ad...@umail.iu.edu>
>> wrote:
>>
>>> Hello All,
>>>
>>> For local provider I was exploring different ways to submit and get the
>>> job done. As, it is a local provider we need not to have monitoring system
>>> in place, simply forking a job on different thread should serve the
>>> purpose.
>>>
>>> But, to do so we need to keep investigation that thread. In my opinion,
>>> ProcessBuilder in java would be handy in this case or if you have any other
>>> suggestions please do let me know.
>>>
>>> Just want to know and use if there is any better way to this.
>>>
>>> Thanks in anticipation
>>> --
>>> Thanks and regards,
>>>
>>> Ajinkya Dhamnaskar
>>> Student ID : 0003469679
>>> Masters (CS)
>>> +1 (812) 369- 5416
>>>
>> --
>> Shameera Rathnayaka
>>
>
>
>
> --
> Thanks and regards,
>
> Ajinkya Dhamnaskar
> Student ID : 0003469679
> Masters (CS)
> +1 (812) 369- 5416
>