Re: Setup a development environment for Airavata

2019-05-18 Thread Lahiru Jayathilake
Hi Marcus,

Thanks for the help. Upgrading Django to 2.x.x version, deleting db.sqlite3
file and re-starting from the beginning fixed the issue :)

Regards,
Lahiru

On Wed, 15 May 2019 at 02:36, Christie, Marcus Aaron 
wrote:

> Hi Lahiru,
>
>
>
> Looks like that Django issue got fixed in 2.x but not in 1.11 [1]. You can
> give 2.0.13 a try with “pip install Django==2.0.13”.
>
>
>
> However, if it’s only load_default_gateway that fails, you can just leave
> it out unless you need to have the wagtail CMS running.
>
>
>
> [1] https://github.com/django/django/pull/10733
>
>
>
> *From: *Lahiru Jayathilake 
> *Reply-To: *"dev@airavata.apache.org" 
> *Date: *Tuesday, May 14, 2019 at 12:18 PM
> *To: *"dev@airavata.apache.org" 
> *Subject: *Re: Setup a development environment for Airavata
>
>
>
> Hi Marcus,
>
>
>
> Yes "*python3 manage.py migrate*" ran successfully with no errors.
>
> Python version - 3.7.3
>
> OS - macOS Mojave version 10.14.4
>
>
>
> Regards,
>
> Lahiru
>
>
>
> On Tue, 14 May 2019 at 03:26, Christie, Marcus Aaron 
> wrote:
>
> Hi Lahiru,
>
>
>
> Did “python3 manage.py migrate” finish without errors?
>
>
>
> Also what version of python and what os are you using?
>
>
>
> Thanks,
>
>
>
> Marcus
>
> Sent from my iPhone
>
>
> On May 4, 2019, at 2:26 PM, Lahiru Jayathilake 
> wrote:
>
> Hi Everyone,
>
>
>
> I have been setting up the development environment and faced several
> issues and found the following solutions.
>
>
>
> 1. When running *org.apache.airavata.ide.integration.APIServerStarter*
>
> *Error* - [
> <https://mail.google.com/mail/u/1?ui=2=6205547991=0.1=msg-a:r1891336976375952133=att=safe=f_jv9rpwbx0>
>
> *error-APIServerStarter.pdf
> <https://mail.google.com/mail/u/1?ui=2=6205547991=0.1=msg-a:r1891336976375952133=att=safe=f_jv9rpwbx0>*
>
> ]
>
> *Solution* - Updated the *ide-integration/pom.xml *to have
> *org.apache.openjpa* plugin
>
>
>
> 
>
>
>
> Tried several times running the *APIServerStarter* and got the
> same error. After fixing the issue with afore-mentioned solution, I tried
> one more time reverting back and that time APIServerStarter ran as expected.
>
>
>
> 2. When running *pip install -r requirements.txt *in
> airavata-django-portal
>
> *Error* - [
> <https://mail.google.com/mail/u/1?ui=2=6205547991=0.4=msg-a:r1891336976375952133=att=safe=f_jv9rpwc13>
>
> *error-pillow.pdf
> <https://mail.google.com/mail/u/1?ui=2=6205547991=0.4=msg-a:r1891336976375952133=att=safe=f_jv9rpwc13>*
>
> ] because wagtail 2.0 has requirement of *Pillow<5.0,>=2.6.1*
>
> *Solution* - Added '*pillow==2.6.1*' in the *requirements.txt*
>
>
>
> 3. When running *python3 manage.py migrate *
>
> *Error - *[
>
> *error-django-verison.pdf
> <https://mail.google.com/mail/u/1?ui=2=6205547991=0.3=msg-a:r1891336976375952133=att=safe=f_jv9rpwc01>*
>
> ]
>
> *Solution* - Updated the version of Django to 1.11.20
>
>
>
> And now I am having the issue when running *python3 manage.py
> load_default_gateway *
>
> The error was [
>
> *error-no-such-table-wagtailcore_page__old.pdf
> <https://mail.google.com/mail/u/1?ui=2=6205547991=0.2=msg-a:r1891336976375952133=att=safe=f_jv9rpwc12>*
>
> ]  *django.db.utils.OperationalError: Problem installing fixtures: no
> such table: wagtailcore_page__old*
>
> I found an article related to this [1] according to the article, the
> problem is with sqlite version so I tried the solution which is downgrading
> sqlite (to 3.24.0) but still I am getting the same error. Can anyone help
> me with this?
>
>
>
> [1] - https://github.com/wagtail/wagtail/issues/4941
>
>
>
> Cheers!
>
> Lahiru
>
>
>
> On Fri, 15 Mar 2019 at 23:51, Christie, Marcus Aaron 
> wrote:
>
> Hi Keerthi,
>
>
>
> On Mar 15, 2019, at 2:15 PM, Keerthi N  wrote:
>
>
>
> It got resolved after npm version update. It was 3.6.2 previously and got
> updated to 6.9.0, everything works fine now.
>
>
>
>
>
> Glad to hear it. Can you please submit a PR to update the README [1]
> regarding prerequisites? I would suggest you add something about installing
> the latest LTS release of Node [2].  Thanks.
>
>
>
> [1]
> https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md
>
> [2] https://nodejs.org/en/download/
>
>
>
>
>
>
> --
>
> Lahiru Jayathilake
>
> Department of Computer Science and Engineering,
>
> Faculty of Engineering,
>
> University of Moratuwa
>
>
>
> [image:
> https://docs.google.com/uc?id=0B5tEBQ-dYBjOQndlTjdfUUNzTXM=download]
> <https://lk.linkedin.com/in/lahirujayathilake>
>
> 
>
> 
>
> 
>
> 
>
>
>
>
> --
>
> Lahiru Jayathilake
>
> Department of Computer Science and Engineering,
>
> Faculty of Engineering,
>
> University of Moratuwa
>
>
>
> [image:
> https://docs.google.com/uc?id=0B5tEBQ-dYBjOQndlTjdfUUNzTXM=download]
> <https://lk.linkedin.com/in/lahirujayathilake>
>


-- 
Lahiru Jayathilake
Department of Computer Science and Engineering,
Faculty of Engineering,
University of Moratuwa

<https://lk.linkedin.com/in/lahirujayathilake>


Re: Setup a development environment for Airavata

2019-05-14 Thread Christie, Marcus Aaron
Hi Lahiru,

 

Looks like that Django issue got fixed in 2.x but not in 1.11 [1]. You can give 
2.0.13 a try with “pip install Django==2.0.13”.

 

However, if it’s only load_default_gateway that fails, you can just leave it 
out unless you need to have the wagtail CMS running.

 

[1] https://github.com/django/django/pull/10733

 

From: Lahiru Jayathilake 
Reply-To: "dev@airavata.apache.org" 
Date: Tuesday, May 14, 2019 at 12:18 PM
To: "dev@airavata.apache.org" 
Subject: Re: Setup a development environment for Airavata

 

Hi Marcus, 

 

Yes "python3 manage.py migrate" ran successfully with no errors. 

Python version - 3.7.3

OS - macOS Mojave version 10.14.4

 

Regards,

Lahiru

 

On Tue, 14 May 2019 at 03:26, Christie, Marcus Aaron  wrote:

Hi Lahiru, 

 

Did “python3 manage.py migrate” finish without errors?

 

Also what version of python and what os are you using?

 

Thanks,

 

Marcus 

Sent from my iPhone


On May 4, 2019, at 2:26 PM, Lahiru Jayathilake  wrote:

Hi Everyone, 

 

I have been setting up the development environment and faced several issues and 
found the following solutions.

 

1. When running org.apache.airavata.ide.integration.APIServerStarter

Error - [ 

error-APIServerStarter.pdf

] 

Solution - Updated the ide-integration/pom.xml to have org.apache.openjpa plugin

 



 

Tried several times running the APIServerStarter and got the same error. After 
fixing the issue with afore-mentioned solution, I tried one more time reverting 
back and that time APIServerStarter ran as expected.

 

2. When running pip install -r requirements.txt in airavata-django-portal

Error - [ 

error-pillow.pdf

] because wagtail 2.0 has requirement of Pillow<5.0,>=2.6.1

Solution - Added 'pillow==2.6.1' in the requirements.txt

 

3. When running python3 manage.py migrate 

Error - [ 

error-django-verison.pdf

]

Solution - Updated the version of Django to 1.11.20 

 

And now I am having the issue when running python3 manage.py 
load_default_gateway 

The error was [ 

error-no-such-table-wagtailcore_page__old.pdf

]  django.db.utils.OperationalError: Problem installing fixtures: no such 
table: wagtailcore_page__old

I found an article related to this [1] according to the article, the problem is 
with sqlite version so I tried the solution which is downgrading sqlite (to 
3.24.0) but still I am getting the same error. Can anyone help me with this?

 

[1] - https://github.com/wagtail/wagtail/issues/4941

 

Cheers!

Lahiru

 

On Fri, 15 Mar 2019 at 23:51, Christie, Marcus Aaron  wrote:

Hi Keerthi,



On Mar 15, 2019, at 2:15 PM, Keerthi N  wrote:

 

It got resolved after npm version update. It was 3.6.2 previously and got 
updated to 6.9.0, everything works fine now.

 

 

Glad to hear it. Can you please submit a PR to update the README [1] regarding 
prerequisites? I would suggest you add something about installing the latest 
LTS release of Node [2].  Thanks.

 

[1] 
https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md

[2] https://nodejs.org/en/download/

 


 

-- 

Lahiru Jayathilake 

Department of Computer Science and Engineering,

Faculty of Engineering,

University of Moratuwa

 










 

-- 

Lahiru Jayathilake 

Department of Computer Science and Engineering,

Faculty of Engineering,

University of Moratuwa

 




smime.p7s
Description: S/MIME cryptographic signature


Re: Setup a development environment for Airavata

2019-05-14 Thread Lahiru Jayathilake
Hi Marcus,

Yes "*python3 manage.py migrate*" ran successfully with no errors.
Python version - 3.7.3
OS - macOS Mojave version 10.14.4

Regards,
Lahiru

On Tue, 14 May 2019 at 03:26, Christie, Marcus Aaron 
wrote:

> Hi Lahiru,
>
> Did “python3 manage.py migrate” finish without errors?
>
> Also what version of python and what os are you using?
>
> Thanks,
>
> Marcus
>
> Sent from my iPhone
>
> On May 4, 2019, at 2:26 PM, Lahiru Jayathilake 
> wrote:
>
> Hi Everyone,
>
> I have been setting up the development environment and faced several
> issues and found the following solutions.
>
> 1. When running *org.apache.airavata.ide.integration.APIServerStarter*
> *Error* - [
> error-APIServerStarter.pdf
>
> 
> ]
> *Solution* - Updated the *ide-integration/pom.xml *to have
> *org.apache.openjpa* plugin
>
> 
>
> Tried several times running the *APIServerStarter* and got the
> same error. After fixing the issue with afore-mentioned solution, I tried
> one more time reverting back and that time APIServerStarter ran as expected.
>
> 2. When running *pip install -r requirements.txt *in
> airavata-django-portal
> *Error* - [
> error-pillow.pdf
>
> ]
>  because
> wagtail 2.0 has requirement of *Pillow<5.0,>=2.6.1*
> *Solution* - Added '*pillow==2.6.1*' in the *requirements.txt*
>
> 3. When running *python3 manage.py migrate *
> *Error - *[
> error-django-verison.pdf
> 
> ]
> *Solution* - Updated the version of Django to 1.11.20
>
> And now I am having the issue when running *python3 manage.py
> load_default_gateway *
> The error was [
> error-no-such-table-wagtailcore_page__old.pdf
> 
> ]  *django.db.utils.OperationalError: Problem installing fixtures: no
> such table: wagtailcore_page__old*
> I found an article related to this [1] according to the article, the
> problem is with sqlite version so I tried the solution which is downgrading
> sqlite (to 3.24.0) but still I am getting the same error. Can anyone help
> me with this?
>
> [1] - https://github.com/wagtail/wagtail/issues/4941
>
> Cheers!
> Lahiru
>
> On Fri, 15 Mar 2019 at 23:51, Christie, Marcus Aaron 
> wrote:
>
>> Hi Keerthi,
>>
>> On Mar 15, 2019, at 2:15 PM, Keerthi N  wrote:
>>
>> It got resolved after npm version update. It was 3.6.2 previously and got
>> updated to 6.9.0, everything works fine now.
>>
>>
>> Glad to hear it. Can you please submit a PR to update the README [1]
>> regarding prerequisites? I would suggest you add something about installing
>> the latest LTS release of Node [2].  Thanks.
>>
>> [1]
>> https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md
>> [2] https://nodejs.org/en/download/
>>
>>
>
> --
> Lahiru Jayathilake
> Department of Computer Science and Engineering,
> Faculty of Engineering,
> University of Moratuwa
>
> 
>
> 
>
> 
>
> 
>
> 
>
>

-- 
Lahiru Jayathilake
Department of Computer Science and Engineering,
Faculty of Engineering,
University of Moratuwa




Re: Setup a development environment for Airavata

2019-03-15 Thread Keerthi N
Hello Marcus,

It got resolved after npm version update. It was 3.6.2 previously and got
updated to 6.9.0, everything works fine now.

Thanks,
Keerthi

On Fri, Mar 15, 2019 at 2:11 PM Christie, Marcus Aaron 
wrote:

> Hi Keerthi,
>
> On Mar 15, 2019, at 11:16 AM, Keerthi N  wrote:
>
> The Django portal build is successful and has no errors, although it has
> couple of warnings (skipping failed optional dependency /chokidar/fsevents,
> not compatible with os:fsevents@1.2.7).
> There are no errors in the Network tab, but the cosole has all alerts that
> are appeared on screen as generated by vue Global Error Handler Type Error.
>
>
>
> Can you post the errors you are seeing in the console? They will likely be
> more detailed than on screen alerts.
>


Re: Setup a development environment for Airavata

2019-03-15 Thread Christie, Marcus Aaron
Hi Keerthi,

> On Mar 15, 2019, at 11:16 AM, Keerthi N  wrote:
> 
> The Django portal build is successful and has no errors, although it has 
> couple of warnings (skipping failed optional dependency /chokidar/fsevents, 
> not compatible with os:fsevents@1.2.7). 
> There are no errors in the Network tab, but the cosole has all alerts that 
> are appeared on screen as generated by vue Global Error Handler Type Error. 
> 
> 

Can you post the errors you are seeing in the console? They will likely be more 
detailed than on screen alerts.

smime.p7s
Description: S/MIME cryptographic signature


Re: Setup a development environment for Airavata

2019-03-15 Thread Keerthi N
Thanks Rohit and DImuthu.

On Fri, Mar 15, 2019 at 12:22 PM Achanta, Sai Rohith 
wrote:

> Hi Keerthi,
>
> Here <https://github.com/apache/airavata/pull/216> is the pull request
> for the updated database initialization script.  Try updating the script as
> per the change in the pull request and it might solve the issue.
>
> Thanks and Regards,
>
> Sai Rohith Achanta.
>
>
>
> *From: *DImuthu Upeksha 
> *Reply-To: *"dev@airavata.apache.org" 
> *Date: *Friday, March 15, 2019 at 12:17 PM
> *To: *Airavata Dev 
> *Subject: *Re: Setup a development environment for Airavata
>
>
>
> Hi Keerthi,
>
>
>
> For the database issue, we found the root cause. There was an issue in
> database initialization script and we fixed it. Rohith will soon send a PR
> and once it is applied, you can start recreating containers. Before running
> docker compose, please make sure to delete *database_data* (not
> database_scripts) directory to reset database data files.
>
>
>
> Thanks
>
> Dimuthu
>
>
>
> On Fri, Mar 15, 2019 at 11:24 AM Keerthi N  wrote:
>
> Hello Marcus,
>
>
>
> The Django portal build is successful and has no errors, although it has
> couple of warnings (skipping failed optional dependency /chokidar/fsevents,
> not compatible with os:fsevents@1.2.7).
>
> There are no errors in the Network tab, but the cosole has all alerts that
> are appeared on screen as generated by vue Global Error Handler Type Error.
>
>
>
> Thanks,
>
> Keerthi
>
>
>
> On Thu, Mar 14, 2019 at 5:19 PM Christie, Marcus Aaron 
> wrote:
>
> Hi Keerthi,
>
>
>
> On Mar 14, 2019, at 2:15 PM, Keerthi N  wrote:
>
>
>
> Yes you are right, I remember that and tried multiple times from start to
> finish but no difference. Can there be any other issue?
>
>
>
> Those errors in the Django portal looks like the Javascript code failed to
> build. Did you get any errors when you ran ./build_js.sh?
>
>
>
> Also are there any errors in the javascript console or in the Network
> requests tab of the developer tools?
>
>


Re: Setup a development environment for Airavata

2019-03-15 Thread Achanta, Sai Rohith
Hi Keerthi,

Here<https://github.com/apache/airavata/pull/216> is the pull request for the 
updated database initialization script.  Try updating the script as per the 
change in the pull request and it might solve the issue.

Thanks and Regards,
Sai Rohith Achanta.

From: DImuthu Upeksha 
Reply-To: "dev@airavata.apache.org" 
Date: Friday, March 15, 2019 at 12:17 PM
To: Airavata Dev 
Subject: Re: Setup a development environment for Airavata

Hi Keerthi,

For the database issue, we found the root cause. There was an issue in database 
initialization script and we fixed it. Rohith will soon send a PR and once it 
is applied, you can start recreating containers. Before running docker compose, 
please make sure to delete database_data (not database_scripts) directory to 
reset database data files.

Thanks
Dimuthu

On Fri, Mar 15, 2019 at 11:24 AM Keerthi N 
mailto:keerthi4...@gmail.com>> wrote:
Hello Marcus,

The Django portal build is successful and has no errors, although it has couple 
of warnings (skipping failed optional dependency /chokidar/fsevents, not 
compatible with os:fsevents@1.2.7).
There are no errors in the Network tab, but the cosole has all alerts that are 
appeared on screen as generated by vue Global Error Handler Type Error.

Thanks,
Keerthi

On Thu, Mar 14, 2019 at 5:19 PM Christie, Marcus Aaron 
mailto:machr...@iu.edu>> wrote:
Hi Keerthi,


On Mar 14, 2019, at 2:15 PM, Keerthi N 
mailto:keerthi4...@gmail.com>> wrote:

Yes you are right, I remember that and tried multiple times from start to 
finish but no difference. Can there be any other issue?

Those errors in the Django portal looks like the Javascript code failed to 
build. Did you get any errors when you ran ./build_js.sh?

Also are there any errors in the javascript console or in the Network requests 
tab of the developer tools?


Re: Setup a development environment for Airavata

2019-03-15 Thread DImuthu Upeksha
Hi Keerthi,

For the database issue, we found the root cause. There was an issue in
database initialization script and we fixed it. Rohith will soon send a PR
and once it is applied, you can start recreating containers. Before running
docker compose, please make sure to delete *database_data* (not
database_scripts) directory to reset database data files.

Thanks
Dimuthu

On Fri, Mar 15, 2019 at 11:24 AM Keerthi N  wrote:

> Hello Marcus,
>
> The Django portal build is successful and has no errors, although it has
> couple of warnings (skipping failed optional dependency /chokidar/fsevents,
> not compatible with os:fsevents@1.2.7).
> There are no errors in the Network tab, but the cosole has all alerts that
> are appeared on screen as generated by vue Global Error Handler Type Error.
>
> Thanks,
> Keerthi
>
> On Thu, Mar 14, 2019 at 5:19 PM Christie, Marcus Aaron 
> wrote:
>
>> Hi Keerthi,
>>
>> On Mar 14, 2019, at 2:15 PM, Keerthi N  wrote:
>>
>> Yes you are right, I remember that and tried multiple times from start to
>> finish but no difference. Can there be any other issue?
>>
>>
>> Those errors in the Django portal looks like the Javascript code failed
>> to build. Did you get any errors when you ran ./build_js.sh?
>>
>> Also are there any errors in the javascript console or in the Network
>> requests tab of the developer tools?
>>
>


Re: Setup a development environment for Airavata

2019-03-15 Thread Keerthi N
Hello Marcus,

The Django portal build is successful and has no errors, although it has
couple of warnings (skipping failed optional dependency /chokidar/fsevents,
not compatible with os:fsevents@1.2.7).
There are no errors in the Network tab, but the cosole has all alerts that
are appeared on screen as generated by vue Global Error Handler Type Error.

Thanks,
Keerthi

On Thu, Mar 14, 2019 at 5:19 PM Christie, Marcus Aaron 
wrote:

> Hi Keerthi,
>
> On Mar 14, 2019, at 2:15 PM, Keerthi N  wrote:
>
> Yes you are right, I remember that and tried multiple times from start to
> finish but no difference. Can there be any other issue?
>
>
> Those errors in the Django portal looks like the Javascript code failed to
> build. Did you get any errors when you ran ./build_js.sh?
>
> Also are there any errors in the javascript console or in the Network
> requests tab of the developer tools?
>


Re: Setup a development environment for Airavata

2019-03-14 Thread Christie, Marcus Aaron
Hi Keerthi,

> On Mar 14, 2019, at 2:15 PM, Keerthi N  wrote:
> 
> Yes you are right, I remember that and tried multiple times from start to 
> finish but no difference. Can there be any other issue?

Those errors in the Django portal looks like the Javascript code failed to 
build. Did you get any errors when you ran ./build_js.sh?

Also are there any errors in the javascript console or in the Network requests 
tab of the developer tools?

smime.p7s
Description: S/MIME cryptographic signature


Re: Setup a development environment for Airavata

2019-03-14 Thread Keerthi N
Yes you are right, I remember that and tried multiple times from start to
finish but no difference. Can there be any other issue?

On Thu, Mar 14, 2019 at 1:10 PM DImuthu Upeksha 
wrote:

> Hi Keerthi,
>
> I think this is related to the same issue that you have faced at the
> class. Some JPA entity classes were not optimized in the build time. Do not
> remove anything from persistence.xml and that will cause issues. Try
> running mvn clean install -DskipTests once for whole project.
>
> Dimuthu
>
> On Thu, Mar 14, 2019 at 1:05 PM Keerthi N  wrote:
>
>> Thanks DImuthu, that resolved error. Now maven build, docker-compose up
>> are successful but the APIServerStarter.java fails with RuntimeException:
>> Failed to initialize the expcatalog database and
>> openjpa.persistence.ArgumentException. I attached the error.  Just to check
>> I removed ExpermentSummary from persistence.xml in META, everything worked
>> fine but then Django portal have some alerts which I attached as well.
>> Please let me know next steps.
>>
>> Thanks,
>> Keerthi
>>
>>
>> On Thu, Mar 14, 2019 at 10:43 AM DImuthu Upeksha <
>> dimuthu.upeks...@gmail.com> wrote:
>>
>>> You might have some process running (local rabbitmq) acquiring port 5672
>>> and 15672. Search for the process id by netstat -tulpn | grep 5672. First
>>> you have to stop this process. Also make sure that all the ports mentioned
>>> here [5] are free in your machine. If nothing works, try restarting your
>>> laptop.
>>>
>>> [5]
>>> https://github.com/apache/airavata/blob/develop/modules/ide-integration/src/main/resources/docker-compose.yml
>>>
>>> Dimuthu
>>>
>>> On Thu, Mar 14, 2019 at 10:31 AM Keerthi N 
>>> wrote:
>>>
 Yes I have done that and executed docker system prune as well but the
 error still persists.

 On Thu, Mar 14, 2019 at 10:15 AM DImuthu Upeksha <
 dimuthu.upeks...@gmail.com> wrote:

> Hi Keerthi,
>
> You have to cleanup old resources by running "docker-compose down" and
> "docker-compose rm". You might be running docker-compose up more than 
> once.
> And make sure that, no related container is running in "docker ps" output.
>
> Dimuthu
>
> On Thu, Mar 14, 2019 at 9:59 AM Keerthi N 
> wrote:
>
>> Hello DImuthu,
>>
>> Thanks for fixing , but docker-compose up fails with error "Another
>> app is currently holding xtables lock" which can be due to use of port 22
>> for sshd in docker-compose and in recent modification for build. I 
>> attached
>> the screenshot for reference.
>>
>> Thanks,
>> Keerthi
>>
>> On Thu, Mar 14, 2019 at 12:33 AM DImuthu Upeksha <
>> dimuthu.upeks...@gmail.com> wrote:
>>
>>> Hi Keerthi,
>>>
>>> Build was fixed. You can try now after a git pull
>>>
>>> Dimuthu
>>>
>>> On Wed, Mar 13, 2019 at 5:20 PM Keerthi N 
>>> wrote:
>>>
 Hi DImuthu,

 Yes that works for docker-compose up. But the mvn build failed
 after git pull at Airavata load testing client. The error says actual 
 and
 formal arguments differ for init function in
 tools/load/StorageResourceManager.java and
 modules/airavata-helix/agent-impl/sshj-agent/SSHJStorageAdaptor.java, 
 which
 is true. The confusing part is maven build was successful before git 
 pull.
 I attached the screenshots please suggest the changes.

 On Wed, Mar 13, 2019 at 2:11 PM DImuthu Upeksha <
 dimuthu.upeks...@gmail.com> wrote:

> Hi Keerthi,
>
> Can you try now?
>
> Dimuthu
>
> On Wed, Mar 13, 2019 at 12:50 PM Keerthi N 
> wrote:
>
>> Hello DImuthu,
>>
>> The "docker-compose up" step fails with pull access denied for
>> *dimuthuupe/sshd:1.0* image. Please grant the necessary
>> permissions.
>>
>> Thanks,
>> Keerthi
>>
>> On Wed, Mar 13, 2019 at 2:51 AM DImuthu Upeksha <
>> dimuthu.upeks...@gmail.com> wrote:
>>
>>> Hi Folks,
>>>
>>> Since Airavata is a multi server platform with lots of
>>> components and configurations, it is quite challenging for a new 
>>> developer
>>> to get started with the code base and setup a running Airavata 
>>> deployment
>>> locally. To address that, we came up with a standalone deployment 
>>> guide [1]
>>> which utilizes a VirtualBox VM and Ansible scripts to setup a 
>>> deployment
>>> locally. Even though this fulfilled the requirements for some 
>>> extent, we
>>> found that the amount of configuration was still little bit 
>>> overwhelming
>>> and software update process was not realtime as binaries were 
>>> deployed in a
>>> VM.
>>>
>>> Due to above 

Re: Setup a development environment for Airavata

2019-03-14 Thread DImuthu Upeksha
Hi Keerthi,

I think this is related to the same issue that you have faced at the class.
Some JPA entity classes were not optimized in the build time. Do not remove
anything from persistence.xml and that will cause issues. Try running mvn
clean install -DskipTests once for whole project.

Dimuthu

On Thu, Mar 14, 2019 at 1:05 PM Keerthi N  wrote:

> Thanks DImuthu, that resolved error. Now maven build, docker-compose up
> are successful but the APIServerStarter.java fails with RuntimeException:
> Failed to initialize the expcatalog database and
> openjpa.persistence.ArgumentException. I attached the error.  Just to check
> I removed ExpermentSummary from persistence.xml in META, everything worked
> fine but then Django portal have some alerts which I attached as well.
> Please let me know next steps.
>
> Thanks,
> Keerthi
>
>
> On Thu, Mar 14, 2019 at 10:43 AM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> You might have some process running (local rabbitmq) acquiring port 5672
>> and 15672. Search for the process id by netstat -tulpn | grep 5672. First
>> you have to stop this process. Also make sure that all the ports mentioned
>> here [5] are free in your machine. If nothing works, try restarting your
>> laptop.
>>
>> [5]
>> https://github.com/apache/airavata/blob/develop/modules/ide-integration/src/main/resources/docker-compose.yml
>>
>> Dimuthu
>>
>> On Thu, Mar 14, 2019 at 10:31 AM Keerthi N  wrote:
>>
>>> Yes I have done that and executed docker system prune as well but the
>>> error still persists.
>>>
>>> On Thu, Mar 14, 2019 at 10:15 AM DImuthu Upeksha <
>>> dimuthu.upeks...@gmail.com> wrote:
>>>
 Hi Keerthi,

 You have to cleanup old resources by running "docker-compose down" and
 "docker-compose rm". You might be running docker-compose up more than once.
 And make sure that, no related container is running in "docker ps" output.

 Dimuthu

 On Thu, Mar 14, 2019 at 9:59 AM Keerthi N 
 wrote:

> Hello DImuthu,
>
> Thanks for fixing , but docker-compose up fails with error "Another
> app is currently holding xtables lock" which can be due to use of port 22
> for sshd in docker-compose and in recent modification for build. I 
> attached
> the screenshot for reference.
>
> Thanks,
> Keerthi
>
> On Thu, Mar 14, 2019 at 12:33 AM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Keerthi,
>>
>> Build was fixed. You can try now after a git pull
>>
>> Dimuthu
>>
>> On Wed, Mar 13, 2019 at 5:20 PM Keerthi N 
>> wrote:
>>
>>> Hi DImuthu,
>>>
>>> Yes that works for docker-compose up. But the mvn build failed after
>>> git pull at Airavata load testing client. The error says actual and 
>>> formal
>>> arguments differ for init function in
>>> tools/load/StorageResourceManager.java and
>>> modules/airavata-helix/agent-impl/sshj-agent/SSHJStorageAdaptor.java, 
>>> which
>>> is true. The confusing part is maven build was successful before git 
>>> pull.
>>> I attached the screenshots please suggest the changes.
>>>
>>> On Wed, Mar 13, 2019 at 2:11 PM DImuthu Upeksha <
>>> dimuthu.upeks...@gmail.com> wrote:
>>>
 Hi Keerthi,

 Can you try now?

 Dimuthu

 On Wed, Mar 13, 2019 at 12:50 PM Keerthi N 
 wrote:

> Hello DImuthu,
>
> The "docker-compose up" step fails with pull access denied for
> *dimuthuupe/sshd:1.0* image. Please grant the necessary
> permissions.
>
> Thanks,
> Keerthi
>
> On Wed, Mar 13, 2019 at 2:51 AM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Folks,
>>
>> Since Airavata is a multi server platform with lots of components
>> and configurations, it is quite challenging for a new developer to 
>> get
>> started with the code base and setup a running Airavata deployment 
>> locally.
>> To address that, we came up with a standalone deployment guide [1] 
>> which
>> utilizes a VirtualBox VM and Ansible scripts to setup a deployment 
>> locally.
>> Even though this fulfilled the requirements for some extent, we 
>> found that
>> the amount of configuration was still little bit overwhelming and 
>> software
>> update process was not realtime as binaries were deployed in a VM.
>>
>> Due to above mentioned issues, we have explored possible
>> alternatives for VM based deployment and reduce the setup time with 
>> less or
>> no configurations. As a solution, we came up with a new module [2] 
>> for
>> Airavata which can start all the Airavata and all other supportive
>> components within the IDE. This module 

Re: Setup a development environment for Airavata

2019-03-14 Thread DImuthu Upeksha
You might have some process running (local rabbitmq) acquiring port 5672
and 15672. Search for the process id by netstat -tulpn | grep 5672. First
you have to stop this process. Also make sure that all the ports mentioned
here [5] are free in your machine. If nothing works, try restarting your
laptop.

[5]
https://github.com/apache/airavata/blob/develop/modules/ide-integration/src/main/resources/docker-compose.yml

Dimuthu

On Thu, Mar 14, 2019 at 10:31 AM Keerthi N  wrote:

> Yes I have done that and executed docker system prune as well but the
> error still persists.
>
> On Thu, Mar 14, 2019 at 10:15 AM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Keerthi,
>>
>> You have to cleanup old resources by running "docker-compose down" and
>> "docker-compose rm". You might be running docker-compose up more than once.
>> And make sure that, no related container is running in "docker ps" output.
>>
>> Dimuthu
>>
>> On Thu, Mar 14, 2019 at 9:59 AM Keerthi N  wrote:
>>
>>> Hello DImuthu,
>>>
>>> Thanks for fixing , but docker-compose up fails with error "Another app
>>> is currently holding xtables lock" which can be due to use of port 22
>>> for sshd in docker-compose and in recent modification for build. I attached
>>> the screenshot for reference.
>>>
>>> Thanks,
>>> Keerthi
>>>
>>> On Thu, Mar 14, 2019 at 12:33 AM DImuthu Upeksha <
>>> dimuthu.upeks...@gmail.com> wrote:
>>>
 Hi Keerthi,

 Build was fixed. You can try now after a git pull

 Dimuthu

 On Wed, Mar 13, 2019 at 5:20 PM Keerthi N 
 wrote:

> Hi DImuthu,
>
> Yes that works for docker-compose up. But the mvn build failed after
> git pull at Airavata load testing client. The error says actual and formal
> arguments differ for init function in
> tools/load/StorageResourceManager.java and
> modules/airavata-helix/agent-impl/sshj-agent/SSHJStorageAdaptor.java, 
> which
> is true. The confusing part is maven build was successful before git pull.
> I attached the screenshots please suggest the changes.
>
> On Wed, Mar 13, 2019 at 2:11 PM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Keerthi,
>>
>> Can you try now?
>>
>> Dimuthu
>>
>> On Wed, Mar 13, 2019 at 12:50 PM Keerthi N 
>> wrote:
>>
>>> Hello DImuthu,
>>>
>>> The "docker-compose up" step fails with pull access denied for
>>> *dimuthuupe/sshd:1.0* image. Please grant the necessary permissions.
>>>
>>> Thanks,
>>> Keerthi
>>>
>>> On Wed, Mar 13, 2019 at 2:51 AM DImuthu Upeksha <
>>> dimuthu.upeks...@gmail.com> wrote:
>>>
 Hi Folks,

 Since Airavata is a multi server platform with lots of components
 and configurations, it is quite challenging for a new developer to get
 started with the code base and setup a running Airavata deployment 
 locally.
 To address that, we came up with a standalone deployment guide [1] 
 which
 utilizes a VirtualBox VM and Ansible scripts to setup a deployment 
 locally.
 Even though this fulfilled the requirements for some extent, we found 
 that
 the amount of configuration was still little bit overwhelming and 
 software
 update process was not realtime as binaries were deployed in a VM.

 Due to above mentioned issues, we have explored possible
 alternatives for VM based deployment and reduce the setup time with 
 less or
 no configurations. As a solution, we came up with a new module [2] for
 Airavata which can start all the Airavata and all other supportive
 components within the IDE. This module mainly contains 2 parts. Java 
 code
 to start Airavata server components and docker composer configuration 
 to
 load rest of the supportive components as docker containers such as
 Database, Zookeeper, Keycloak, Kafka, RabbitMQ and a custom SSHD 
 server.

 In addition to that, it contains instructions on how to start and
 connect our new user portal (Django portal) and old portal (PGA) to
 Airavata so that you can straightaway tryout Airavata with less 
 trouble.
 Aiaravata database comes with pre loaded data which contains a simple 
 Echo
 application and one of our test JestStream cluster details. So you do 
 not
 need to worry about those configurations as well.

 To guide you more, I have created a short screencast [3] that
 covers main steps mentioned in the Readme [4] file. However you have to
 thoroughly follow each and every step mentioned in the Readme file in 
 order
 to make everything work without any issue.

 Since this is a new implementation with very limited amount of
 testing, it is 

Re: Setup a development environment for Airavata

2019-03-14 Thread Keerthi N
Yes I have done that and executed docker system prune as well but the
error still persists.

On Thu, Mar 14, 2019 at 10:15 AM DImuthu Upeksha 
wrote:

> Hi Keerthi,
>
> You have to cleanup old resources by running "docker-compose down" and
> "docker-compose rm". You might be running docker-compose up more than once.
> And make sure that, no related container is running in "docker ps" output.
>
> Dimuthu
>
> On Thu, Mar 14, 2019 at 9:59 AM Keerthi N  wrote:
>
>> Hello DImuthu,
>>
>> Thanks for fixing , but docker-compose up fails with error "Another app
>> is currently holding xtables lock" which can be due to use of port 22
>> for sshd in docker-compose and in recent modification for build. I attached
>> the screenshot for reference.
>>
>> Thanks,
>> Keerthi
>>
>> On Thu, Mar 14, 2019 at 12:33 AM DImuthu Upeksha <
>> dimuthu.upeks...@gmail.com> wrote:
>>
>>> Hi Keerthi,
>>>
>>> Build was fixed. You can try now after a git pull
>>>
>>> Dimuthu
>>>
>>> On Wed, Mar 13, 2019 at 5:20 PM Keerthi N  wrote:
>>>
 Hi DImuthu,

 Yes that works for docker-compose up. But the mvn build failed after
 git pull at Airavata load testing client. The error says actual and formal
 arguments differ for init function in
 tools/load/StorageResourceManager.java and
 modules/airavata-helix/agent-impl/sshj-agent/SSHJStorageAdaptor.java, which
 is true. The confusing part is maven build was successful before git pull.
 I attached the screenshots please suggest the changes.

 On Wed, Mar 13, 2019 at 2:11 PM DImuthu Upeksha <
 dimuthu.upeks...@gmail.com> wrote:

> Hi Keerthi,
>
> Can you try now?
>
> Dimuthu
>
> On Wed, Mar 13, 2019 at 12:50 PM Keerthi N 
> wrote:
>
>> Hello DImuthu,
>>
>> The "docker-compose up" step fails with pull access denied for
>> *dimuthuupe/sshd:1.0* image. Please grant the necessary permissions.
>>
>> Thanks,
>> Keerthi
>>
>> On Wed, Mar 13, 2019 at 2:51 AM DImuthu Upeksha <
>> dimuthu.upeks...@gmail.com> wrote:
>>
>>> Hi Folks,
>>>
>>> Since Airavata is a multi server platform with lots of components
>>> and configurations, it is quite challenging for a new developer to get
>>> started with the code base and setup a running Airavata deployment 
>>> locally.
>>> To address that, we came up with a standalone deployment guide [1] which
>>> utilizes a VirtualBox VM and Ansible scripts to setup a deployment 
>>> locally.
>>> Even though this fulfilled the requirements for some extent, we found 
>>> that
>>> the amount of configuration was still little bit overwhelming and 
>>> software
>>> update process was not realtime as binaries were deployed in a VM.
>>>
>>> Due to above mentioned issues, we have explored possible
>>> alternatives for VM based deployment and reduce the setup time with 
>>> less or
>>> no configurations. As a solution, we came up with a new module [2] for
>>> Airavata which can start all the Airavata and all other supportive
>>> components within the IDE. This module mainly contains 2 parts. Java 
>>> code
>>> to start Airavata server components and docker composer configuration to
>>> load rest of the supportive components as docker containers such as
>>> Database, Zookeeper, Keycloak, Kafka, RabbitMQ and a custom SSHD server.
>>>
>>> In addition to that, it contains instructions on how to start and
>>> connect our new user portal (Django portal) and old portal (PGA) to
>>> Airavata so that you can straightaway tryout Airavata with less trouble.
>>> Aiaravata database comes with pre loaded data which contains a simple 
>>> Echo
>>> application and one of our test JestStream cluster details. So you do 
>>> not
>>> need to worry about those configurations as well.
>>>
>>> To guide you more, I have created a short screencast [3] that covers
>>> main steps mentioned in the Readme [4] file. However you have to 
>>> thoroughly
>>> follow each and every step mentioned in the Readme file in order to make
>>> everything work without any issue.
>>>
>>> Since this is a new implementation with very limited amount of
>>> testing, it is expected for you to come up with various issues in the
>>> process and please let us know about them so that we can improve this
>>> further. Or if you can directly contribute, it is highly appreciated.
>>>
>>> [1]
>>> https://docs.google.com/document/d/1dFhajiYlPtNymIKbMvCXeLivLHujLjvE107QyUDEgdA/edit?usp=sharing
>>> [2]
>>> https://github.com/apache/airavata/tree/develop/modules/ide-integration
>>> [3] https://youtu.be/nMlrYTqAKd0
>>> [4]
>>> https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md
>>>
>>> Thanks
>>> Dimuthu
>>>
>>


Re: Setup a development environment for Airavata

2019-03-14 Thread DImuthu Upeksha
Hi Keerthi,

You have to cleanup old resources by running "docker-compose down" and
"docker-compose rm". You might be running docker-compose up more than once.
And make sure that, no related container is running in "docker ps" output.

Dimuthu

On Thu, Mar 14, 2019 at 9:59 AM Keerthi N  wrote:

> Hello DImuthu,
>
> Thanks for fixing , but docker-compose up fails with error "Another app is
> currently holding xtables lock" which can be due to use of port 22
> for sshd in docker-compose and in recent modification for build. I attached
> the screenshot for reference.
>
> Thanks,
> Keerthi
>
> On Thu, Mar 14, 2019 at 12:33 AM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Keerthi,
>>
>> Build was fixed. You can try now after a git pull
>>
>> Dimuthu
>>
>> On Wed, Mar 13, 2019 at 5:20 PM Keerthi N  wrote:
>>
>>> Hi DImuthu,
>>>
>>> Yes that works for docker-compose up. But the mvn build failed after git
>>> pull at Airavata load testing client. The error says actual and formal
>>> arguments differ for init function in
>>> tools/load/StorageResourceManager.java and
>>> modules/airavata-helix/agent-impl/sshj-agent/SSHJStorageAdaptor.java, which
>>> is true. The confusing part is maven build was successful before git pull.
>>> I attached the screenshots please suggest the changes.
>>>
>>> On Wed, Mar 13, 2019 at 2:11 PM DImuthu Upeksha <
>>> dimuthu.upeks...@gmail.com> wrote:
>>>
 Hi Keerthi,

 Can you try now?

 Dimuthu

 On Wed, Mar 13, 2019 at 12:50 PM Keerthi N 
 wrote:

> Hello DImuthu,
>
> The "docker-compose up" step fails with pull access denied for
> *dimuthuupe/sshd:1.0* image. Please grant the necessary permissions.
>
> Thanks,
> Keerthi
>
> On Wed, Mar 13, 2019 at 2:51 AM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Folks,
>>
>> Since Airavata is a multi server platform with lots of components and
>> configurations, it is quite challenging for a new developer to get 
>> started
>> with the code base and setup a running Airavata deployment locally. To
>> address that, we came up with a standalone deployment guide [1] which
>> utilizes a VirtualBox VM and Ansible scripts to setup a deployment 
>> locally.
>> Even though this fulfilled the requirements for some extent, we found 
>> that
>> the amount of configuration was still little bit overwhelming and 
>> software
>> update process was not realtime as binaries were deployed in a VM.
>>
>> Due to above mentioned issues, we have explored possible alternatives
>> for VM based deployment and reduce the setup time with less or no
>> configurations. As a solution, we came up with a new module [2] for
>> Airavata which can start all the Airavata and all other supportive
>> components within the IDE. This module mainly contains 2 parts. Java code
>> to start Airavata server components and docker composer configuration to
>> load rest of the supportive components as docker containers such as
>> Database, Zookeeper, Keycloak, Kafka, RabbitMQ and a custom SSHD server.
>>
>> In addition to that, it contains instructions on how to start and
>> connect our new user portal (Django portal) and old portal (PGA) to
>> Airavata so that you can straightaway tryout Airavata with less trouble.
>> Aiaravata database comes with pre loaded data which contains a simple 
>> Echo
>> application and one of our test JestStream cluster details. So you do not
>> need to worry about those configurations as well.
>>
>> To guide you more, I have created a short screencast [3] that covers
>> main steps mentioned in the Readme [4] file. However you have to 
>> thoroughly
>> follow each and every step mentioned in the Readme file in order to make
>> everything work without any issue.
>>
>> Since this is a new implementation with very limited amount of
>> testing, it is expected for you to come up with various issues in the
>> process and please let us know about them so that we can improve this
>> further. Or if you can directly contribute, it is highly appreciated.
>>
>> [1]
>> https://docs.google.com/document/d/1dFhajiYlPtNymIKbMvCXeLivLHujLjvE107QyUDEgdA/edit?usp=sharing
>> [2]
>> https://github.com/apache/airavata/tree/develop/modules/ide-integration
>> [3] https://youtu.be/nMlrYTqAKd0
>> [4]
>> https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md
>>
>> Thanks
>> Dimuthu
>>
>


Re: Setup a development environment for Airavata

2019-03-13 Thread DImuthu Upeksha
Hi Keerthi,

Build was fixed. You can try now after a git pull

Dimuthu

On Wed, Mar 13, 2019 at 5:20 PM Keerthi N  wrote:

> Hi DImuthu,
>
> Yes that works for docker-compose up. But the mvn build failed after git
> pull at Airavata load testing client. The error says actual and formal
> arguments differ for init function in
> tools/load/StorageResourceManager.java and
> modules/airavata-helix/agent-impl/sshj-agent/SSHJStorageAdaptor.java, which
> is true. The confusing part is maven build was successful before git pull.
> I attached the screenshots please suggest the changes.
>
> On Wed, Mar 13, 2019 at 2:11 PM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Keerthi,
>>
>> Can you try now?
>>
>> Dimuthu
>>
>> On Wed, Mar 13, 2019 at 12:50 PM Keerthi N  wrote:
>>
>>> Hello DImuthu,
>>>
>>> The "docker-compose up" step fails with pull access denied for
>>> *dimuthuupe/sshd:1.0* image. Please grant the necessary permissions.
>>>
>>> Thanks,
>>> Keerthi
>>>
>>> On Wed, Mar 13, 2019 at 2:51 AM DImuthu Upeksha <
>>> dimuthu.upeks...@gmail.com> wrote:
>>>
 Hi Folks,

 Since Airavata is a multi server platform with lots of components and
 configurations, it is quite challenging for a new developer to get started
 with the code base and setup a running Airavata deployment locally. To
 address that, we came up with a standalone deployment guide [1] which
 utilizes a VirtualBox VM and Ansible scripts to setup a deployment locally.
 Even though this fulfilled the requirements for some extent, we found that
 the amount of configuration was still little bit overwhelming and software
 update process was not realtime as binaries were deployed in a VM.

 Due to above mentioned issues, we have explored possible alternatives
 for VM based deployment and reduce the setup time with less or no
 configurations. As a solution, we came up with a new module [2] for
 Airavata which can start all the Airavata and all other supportive
 components within the IDE. This module mainly contains 2 parts. Java code
 to start Airavata server components and docker composer configuration to
 load rest of the supportive components as docker containers such as
 Database, Zookeeper, Keycloak, Kafka, RabbitMQ and a custom SSHD server.

 In addition to that, it contains instructions on how to start and
 connect our new user portal (Django portal) and old portal (PGA) to
 Airavata so that you can straightaway tryout Airavata with less trouble.
 Aiaravata database comes with pre loaded data which contains a simple Echo
 application and one of our test JestStream cluster details. So you do not
 need to worry about those configurations as well.

 To guide you more, I have created a short screencast [3] that covers
 main steps mentioned in the Readme [4] file. However you have to thoroughly
 follow each and every step mentioned in the Readme file in order to make
 everything work without any issue.

 Since this is a new implementation with very limited amount of testing,
 it is expected for you to come up with various issues in the process and
 please let us know about them so that we can improve this further. Or if
 you can directly contribute, it is highly appreciated.

 [1]
 https://docs.google.com/document/d/1dFhajiYlPtNymIKbMvCXeLivLHujLjvE107QyUDEgdA/edit?usp=sharing
 [2]
 https://github.com/apache/airavata/tree/develop/modules/ide-integration
 [3] https://youtu.be/nMlrYTqAKd0
 [4]
 https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md

 Thanks
 Dimuthu

>>>


Re: Setup a development environment for Airavata

2019-03-13 Thread DImuthu Upeksha
Hi Keerthi,

Can you try now?

Dimuthu

On Wed, Mar 13, 2019 at 12:50 PM Keerthi N  wrote:

> Hello DImuthu,
>
> The "docker-compose up" step fails with pull access denied for
> *dimuthuupe/sshd:1.0* image. Please grant the necessary permissions.
>
> Thanks,
> Keerthi
>
> On Wed, Mar 13, 2019 at 2:51 AM DImuthu Upeksha <
> dimuthu.upeks...@gmail.com> wrote:
>
>> Hi Folks,
>>
>> Since Airavata is a multi server platform with lots of components and
>> configurations, it is quite challenging for a new developer to get started
>> with the code base and setup a running Airavata deployment locally. To
>> address that, we came up with a standalone deployment guide [1] which
>> utilizes a VirtualBox VM and Ansible scripts to setup a deployment locally.
>> Even though this fulfilled the requirements for some extent, we found that
>> the amount of configuration was still little bit overwhelming and software
>> update process was not realtime as binaries were deployed in a VM.
>>
>> Due to above mentioned issues, we have explored possible alternatives for
>> VM based deployment and reduce the setup time with less or no
>> configurations. As a solution, we came up with a new module [2] for
>> Airavata which can start all the Airavata and all other supportive
>> components within the IDE. This module mainly contains 2 parts. Java code
>> to start Airavata server components and docker composer configuration to
>> load rest of the supportive components as docker containers such as
>> Database, Zookeeper, Keycloak, Kafka, RabbitMQ and a custom SSHD server.
>>
>> In addition to that, it contains instructions on how to start and connect
>> our new user portal (Django portal) and old portal (PGA) to Airavata so
>> that you can straightaway tryout Airavata with less trouble. Aiaravata
>> database comes with pre loaded data which contains a simple Echo
>> application and one of our test JestStream cluster details. So you do not
>> need to worry about those configurations as well.
>>
>> To guide you more, I have created a short screencast [3] that covers main
>> steps mentioned in the Readme [4] file. However you have to thoroughly
>> follow each and every step mentioned in the Readme file in order to make
>> everything work without any issue.
>>
>> Since this is a new implementation with very limited amount of testing,
>> it is expected for you to come up with various issues in the process and
>> please let us know about them so that we can improve this further. Or if
>> you can directly contribute, it is highly appreciated.
>>
>> [1]
>> https://docs.google.com/document/d/1dFhajiYlPtNymIKbMvCXeLivLHujLjvE107QyUDEgdA/edit?usp=sharing
>> [2]
>> https://github.com/apache/airavata/tree/develop/modules/ide-integration
>> [3] https://youtu.be/nMlrYTqAKd0
>> [4]
>> https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md
>>
>> Thanks
>> Dimuthu
>>
>


Setup a development environment for Airavata

2019-03-13 Thread DImuthu Upeksha
Hi Folks,

Since Airavata is a multi server platform with lots of components and
configurations, it is quite challenging for a new developer to get started
with the code base and setup a running Airavata deployment locally. To
address that, we came up with a standalone deployment guide [1] which
utilizes a VirtualBox VM and Ansible scripts to setup a deployment locally.
Even though this fulfilled the requirements for some extent, we found that
the amount of configuration was still little bit overwhelming and software
update process was not realtime as binaries were deployed in a VM.

Due to above mentioned issues, we have explored possible alternatives for
VM based deployment and reduce the setup time with less or no
configurations. As a solution, we came up with a new module [2] for
Airavata which can start all the Airavata and all other supportive
components within the IDE. This module mainly contains 2 parts. Java code
to start Airavata server components and docker composer configuration to
load rest of the supportive components as docker containers such as
Database, Zookeeper, Keycloak, Kafka, RabbitMQ and a custom SSHD server.

In addition to that, it contains instructions on how to start and connect
our new user portal (Django portal) and old portal (PGA) to Airavata so
that you can straightaway tryout Airavata with less trouble. Aiaravata
database comes with pre loaded data which contains a simple Echo
application and one of our test JestStream cluster details. So you do not
need to worry about those configurations as well.

To guide you more, I have created a short screencast [3] that covers main
steps mentioned in the Readme [4] file. However you have to thoroughly
follow each and every step mentioned in the Readme file in order to make
everything work without any issue.

Since this is a new implementation with very limited amount of testing, it
is expected for you to come up with various issues in the process and
please let us know about them so that we can improve this further. Or if
you can directly contribute, it is highly appreciated.

[1]
https://docs.google.com/document/d/1dFhajiYlPtNymIKbMvCXeLivLHujLjvE107QyUDEgdA/edit?usp=sharing
[2] https://github.com/apache/airavata/tree/develop/modules/ide-integration
[3] https://youtu.be/nMlrYTqAKd0
[4]
https://github.com/apache/airavata/blob/develop/modules/ide-integration/README.md

Thanks
Dimuthu