[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=15496690#comment-15496690 ] ASF subversion and git services commented on AIRAVATA-2056: --- Commit 8474763b16288a571c787cb0d52c40afea62df48 in airavata's branch refs/heads/lahiru/AIRAVATA-2065 from Lahiru Ginnaliya Gamathige [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=8474763 ] [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 >Assignee: 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)
[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=15486395#comment-15486395 ] ASF subversion and git services commented on AIRAVATA-2056: --- Commit 6ec88cfd7d846fdd1175dba4b941ec49dc292999 in airavata's branch refs/heads/lahiru/AIRAVATA-2065 from Lahiru Ginnaliya Gamathige [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=6ec88cf ] [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 >Assignee: 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)
[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=15469994#comment-15469994 ] ASF subversion and git services commented on AIRAVATA-2056: --- Commit 9b372acffcab6eec2eef38d3e95e877341b189db in airavata's branch refs/heads/lahiru/AIRAVATA-2065 from Lahiru Ginnaliya Gamathige [ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=9b372ac ] [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 >Assignee: 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)
[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=15446210#comment-15446210 ] ASF subversion and git services commented on AIRAVATA-2056: --- Commit 91afea32dee2770e05447716ae29f3ce7655e36d 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=91afea3 ] [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 >Assignee: 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)
