airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pankaj Saha <psa...@binghamton.edu>
Subject Re: Airavata Docker Available !!
Date Mon, 06 Jul 2015 15:13:52 GMT
I am so sorry , I have no intention to hide any docker code.I am attaching
the docker files here.I have never done git check in and trying to upload
files and its not working. I am trying to understand the git pull
request/setting up git directory etc.

My apology if I unnecessary delayed it.



On Mon, Jul 6, 2015 at 10:51 AM, Suresh Marru <smarru@apache.org> wrote:

> Hi Pankaj,
>
> Open source software can never be final. Once the software is final, the
> community is dead, because there is nothing for anyone to do. An important
> aspect for all the GSoC students to embrace is, these are not academic
> projects where you submit the final code. You are supposed to commit every
> few hours of code, you need to do the development in open. We have been
> lenient on this so far, but you have been holding off the docker work
> little too long. Please do commit the docker files in as in condition.
> Thats the only way you can engage others, otherwise you will loose everyone
> interest.
>
> Suresh
>
> On Mon, Jul 6, 2015 at 10:42 AM, Lahiru Ginnaliya Gamathige <
> glahiru@gmail.com> wrote:
>
>> Not sure what is the big deal here, Why don't you create a pull request
>> and every one can review it. It doesn't have to be finalized at all. People
>> will comment and you can follow the comments and after multiple reviews we
>> can  move ti to the the code base.
>>
>> I propose to create a folder struction like this and put the docker files.
>>
>> airavata/deploy/thrift, airavata/deploy/rabbitmq,
>> airavata/deploy/zookeeper. Create a directory for every image you build
>> with proper naming and add the Dockerfile and other scripts if there's any.
>>
>> Lahiru
>>
>> On Mon, Jul 6, 2015 at 7:03 AM, Pankaj Saha <psaha4@binghamton.edu>
>> wrote:
>>
>>> This docker file is not final yet as we have to automate the environment
>>> variable to replace the properties file.
>>> I believe in a hangout session we can walk through and fix this.
>>>
>>> On Mon, Jul 6, 2015 at 9:58 AM, Shameera Rathnayaka <
>>> shameerainfo@gmail.com> wrote:
>>>
>>>> Hi Pankaj,
>>>>
>>>> Let't do this via Apache way, upload these files to publicly accessible
>>>> place (as i mentioned in my previous reply) then invite everyone to review
>>>> it.
>>>>
>>>> Regards,
>>>> Shameera.
>>>>
>>>> On Mon, Jul 6, 2015 at 9:44 AM Pankaj Saha <psaha4@binghamton.edu>
>>>> wrote:
>>>>
>>>>> Hi Shameera,
>>>>> Please find the attached Dockerfile for Airavata Server.
>>>>> Please suggest changes.
>>>>>
>>>>>
>>>>> On Thu, Jul 2, 2015 at 5:50 PM, Shameera Rathnayaka <
>>>>> shameerainfo@gmail.com> wrote:
>>>>>
>>>>>> Hi Pankaj,
>>>>>>
>>>>>> Yes please share your works with community. Do you have specific
>>>>>> location to commit your works? If not you can use this location
>>>>>> https://github.com/apache/airavata-sandbox.  Let's try to  track
the
>>>>>> changes with VCS.
>>>>>>
>>>>>> @Suresh do we have specific location for this time gsoc students?
>>>>>>
>>>>>> Thanks,
>>>>>> Shameera.
>>>>>>
>>>>>> On Thu, Jul 2, 2015 at 5:24 PM Pankaj Saha <psaha4@binghamton.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Shameera
>>>>>>> Yes we can see the containers ip they way you suggested. What
I
>>>>>>> mentioned is another way in case you are already inside the container.
>>>>>>>
>>>>>>> Regarding java path variable yes we can do that with ENV in docker
>>>>>>> file. It was throwing some errors so i just commented that in
the docker
>>>>>>> file.
>>>>>>>
>>>>>>> I will send you the docker file in another email then we can
go
>>>>>>> through together  to improve it.
>>>>>>>
>>>>>>> I was trying mesos today and didnt have time to fix that. We
can do
>>>>>>> it later as we are already running late for the mesos implementation.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>> Pankaj
>>>>>>>  On 02-Jul-2015 5:12 PM, "Shameera Rathnayaka" <
>>>>>>> shameerainfo@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Pankaj,
>>>>>>>>
>>>>>>>> See my comments inline.
>>>>>>>>
>>>>>>>>
>>>>>>>>> docker attach server
>>>>>>>>>>
>>>>>>>>> awk 'NR==1 {print $1}' /etc/hosts    ---- note the ip
address of
>>>>>>>>>> the running container
>>>>>>>>>
>>>>>>>>>
>>>>>>>> can't we use "docker inspect --format '{{
>>>>>>>> .NetworkSettings.IPAddress }}' server " to get airavata server
docker
>>>>>>>> container ip ?
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> pico airavata-server.properties
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Replaces the below text as suggested below
>>>>>>>>> apiserver.server.host= *<current containers ip address>*
>>>>>>>>> default.registry.gateway=*default*
>>>>>>>>> rabbitmq.broker.url=amqp://*<rabbit MQ's ip address>*:5672
>>>>>>>>> save changes.
>>>>>>>>>
>>>>>>>>> pico /etc/bash.bashrc
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> add below lines at the end
>>>>>>>>>
>>>>>>>>> #JAVA_HOME
>>>>>>>>>> JAVA_HOME=/opt/jdk/jdk1.8.0_05
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> You can improve you docker file to add this variables using
ENV
>>>>>>>> command.
>>>>>>>>
>>>>>>>>
>>>>>>>>> export JAVA_HOME
>>>>>>>>>> PATH=$JAVA_HOME/bin:$PATH
>>>>>>>>>> export PATH
>>>>>>>>>
>>>>>>>>> save changes.
>>>>>>>>>
>>>>>>>>
>>>>>>>> How you install java 8?, There is a way to install java on
docker
>>>>>>>> which automatically available in PATH variable. You don't
have to set it
>>>>>>>> here. It is good if you can show us the Dockerfiles then
we can review
>>>>>>>> those files. is it available online ?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Shameera.
>>>>>>>>
>>>>>>>
>>>>>
>>>
>>
>

Mime
View raw message