You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/08/21 07:59:20 UTC

[jira] [Commented] (AIRAVATA-2056) Jenkins bulid script for airavata push

    [ https://issues.apache.org/jira/browse/AIRAVATA-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429629#comment-15429629 ] 

ASF subversion and git services commented on AIRAVATA-2056:
-----------------------------------------------------------

Commit 0c2ecdba19ba8893ca9096202219173bee8c6923 in airavata's branch refs/heads/lahiru/airavata-docker from Lahiru Ginnaliya Gamathige
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=0c2ecdb ]

[AIRAVATA-2054][WIP] create docker images for airavata deployment components

1. Introduce Docker images for each deployment component of airavata.
2. Deployed those in docker hub repository (scigap),
	try: docker search scigap
3. Use exhibitor docker images intead of zookeeper which is a much better
compare to using vanilla zookeeper.
http://techblog.netflix.com/2012/04/introducing-exhibitor-supervisor-system.html

4. IMHO we should never use docker images from public repository, Everything
we should create our own docker images from public images and test with those and
move to production.

5. Added a simple script(airavata/build.sh) to build airavata docker components.

      ./build.sh [component-name] - This will build a docker image for given component.

This is a temporary script we can use until AIRAVATA-2056 which integrates docker push with some CI tool like jenkins.


> Jenkins bulid script for airavata push
> --------------------------------------
>
>                 Key: AIRAVATA-2056
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2056
>             Project: Airavata
>          Issue Type: Sub-task
>            Reporter: Lahiru Gunathilake
>
> When someone gives the branch and other parameters (airavata mode : all, orchestrator, gfac, api-server, environment-name : nightly, staging, production) compile that branch and create docker image and push those to docker registry. 
> So if we have already setup the environment with systemd units, we just have to restart the systemd unit after running this jenkins script, it will pull the latest changes and depoy all the changes for your branch.
> We don't need jenkins for other depenent components like exhibitor, rabbitmq.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)