Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
MIME-Version: 1.0
From: Hitesh Kumar Dasika <hdasika@umail.iu.edu>
Date: Sat, 30 Sep 2017 14:24:53 -0400
Message-ID: <CAA8zoaGc4o8fUhF-pEAwG+m3h7u-M1kD3Djs_kCHDy=mWXyGww@mail.gmail.com>
Subject: [FALL-2017] Dockerizing Airavata PGA
To: dev@airavata.apache.org
Content-Type: multipart/alternative; boundary="94eb2c07398afc28e1055a6c41d6"
archived-at: Sat, 30 Sep 2017 18:24:58 -0000

--94eb2c07398afc28e1055a6c41d6
Content-Type: text/plain; charset="UTF-8"

Hello Dev

I am in the process of writing a Dockerfile for Dockerizing Airavata PGA
Gateway. My end goal is to replace the current ansible installation of
Airavata PGA Gateway with a Docker Container

PR which is still developing: https://github.com/apache/airavata/pull/122

Some Considerations that I want to make:

1. Through the ansible playbook, firewalld is installed and is configured.
But when the app is installed in a container, there is no need for
firewalld as we can access the container only through the port exposed. The
host system can be configured with firewalld which makes more sense.

2.  The second thing is default configurations which need to be copied.
There are many conf files and there are placeholders in those which are
replaced by ansible. Whereas in Docker container creation, such
configurations need to be copied without placeholders into the containers.
To achieve this, my plan is to include a volume which is mounted to the
container and that volume will have all the configuration files in it. The
user will have the option to change configurations in those files.

Any Suggestions would be appreciated.

@Gourav
The PR contains a single dockerfile for all the services. But won't it be
good if there are different containers with different components in them?
This approach will also be helpful for orchestration


Regards

Hitesh Kumar Dasika

--94eb2c07398afc28e1055a6c41d6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Dev<div><br></div><div>I am in the process of writin=
g a Dockerfile for Dockerizing Airavata PGA Gateway. My end goal is to repl=
ace the=C2=A0current ansible installation of Airavata PGA Gateway with a Do=
cker Container</div><div><br></div><div>PR which is still developing: <a hr=
ef=3D"https://github.com/apache/airavata/pull/122">https://github.com/apach=
e/airavata/pull/122</a><br></div><div><br></div><div>Some Considerations th=
at I want to make:</div><div><br></div><div>1. Through the ansible playbook=
, firewalld is installed and is configured. But when the app is installed i=
n a container, there is no need for firewalld=C2=A0as we can access the con=
tainer only through the port exposed. The host system can be configured wit=
h firewalld=C2=A0which makes more sense.</div><div><br></div><div>2.=C2=A0 =
The second thing is default configurations which need to be copied. There a=
re many conf files and there are placeholders in those which are replaced b=
y ansible. Whereas in Docker container creation, such configurations need t=
o be copied without placeholders into the containers. To achieve this, my p=
lan is to include a volume which is mounted to the container and that volum=
e will have all the configuration files in it. The user will have the optio=
n to change configurations in those files.</div><div><br></div><div>Any Sug=
gestions would be appreciated.</div><div><br></div><div>@Gourav</div><div>T=
he PR contains a single dockerfile=C2=A0for all the services. But won&#39;t=
 it be good if there are different containers with different components in =
them? This approach will also be helpful for orchestration</div><div><br></=
div><div><br></div><div><br></div><div>Regards</div><div><br></div><div>Hit=
esh Kumar Dasika=C2=A0</div><div><br></div><div><br></div><div><br></div></=
div>

--94eb2c07398afc28e1055a6c41d6--