Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.apache.org
Date: Wed, 15 Nov 2017 20:50:00 +0000 (UTC)
From: "ernie ostic (JIRA)" <jira@apache.org>
To: dev@atlas.apache.org
Message-ID: <JIRA.13091577.1501599723000.248778.1510779000892@Atlassian.JIRA>
In-Reply-To: <JIRA.13091577.1501599723000@Atlassian.JIRA>
References: <JIRA.13091577.1501599723000@Atlassian.JIRA> <JIRA.13091577.1501599723303@jira-lw-us.apache.org>
Subject: [jira] [Updated] (ATLAS-2012) Docker - image & hub - for Atlas
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Nov 2017 20:50:07 -0000


     [ https://issues.apache.org/jira/browse/ATLAS-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ernie ostic updated ATLAS-2012:
-------------------------------
    Attachment: graycol.gif


Thank you Nigel...

Just to add to your very good point #3 below....

3. We could publish the docker image from #2, for releases, to dockerhub,
making it near trivial for any developer to easily pull down and experiment
with Atlas. Full source of course would be provided/documented so that a
user could customize as needed for their environment plus of course improve
what is provided with the core project.   This would also support
governance-focused but non-developer professionals to immediately start
working with Atlas, understanding its APIs, etc.  This is assuming that the
docker image we publish already has quick_start run against it, and/or any
other content worthy of publishing in a "demonstrable" instance of Atlas.

Ernie


Ernie Ostic

Worldwide Technical Sales
InfoSphere Information Server
IBM Analytics

Cell: (617) 331 8238
---------------------------------------------------------------
Open IGC is here!

Extend the Catalog with custom objects and lineage definitions!
https://dsrealtime.wordpress.com/2015/07/29/open-igc-is-here/


From:	"Nigel Jones (JIRA)" <jira@apache.org>
To:	eostic@us.ibm.com
Date:	11/15/2017 01:18 AM
Subject:	[jira] [Commented] (ATLAS-2012) Docker - image & hub - for
            Atlas


    [
https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ATLAS-2D2012-3Fpage-3Dcom.atlassian.jira.plugin.system.issuetabpanels-3Acomment-2Dtabpanel-26focusedCommentId-3D16253009-23comment-2D16253009&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=BRpv_IJLfOPKPg5CMvWe7vPrIiVO97XiMOUrvOhs2KY&m=AXTVamH8UuQbAmxLD4tudT6dZmTkURlqmn3FxS_gU2Q&s=NPwVtS1bKQNgAohKia4zHMyxSxTD87FGa0WFdWM8Xa0&e=
 ]

Nigel Jones commented on ATLAS-2012:
------------------------------------

Looking at docker hub, for an individual to upload an image is pretty
simple.
However to allow multiple users (within the atlas community) to update the
image would require setting up an organization & then adding members

A number of projects though including zookeeper, flink, httpd, solr, storm
have 'official' images, guidelines for this are at
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_docker-2Dlibrary_official-2Dimages&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=BRpv_IJLfOPKPg5CMvWe7vPrIiVO97XiMOUrvOhs2KY&m=AXTVamH8UuQbAmxLD4tudT6dZmTkURlqmn3FxS_gU2Q&s=ZTcAvV3K8JUi4mmKqPUn2gNzdVvAfBJiC4NDoHSZ_yo&e=
. More review is required, but I think in the medium term this is what we
should target, this comes with it requirements around aspects like issue
tracking

In order to get an image uploaded promptly, a pragmatic approach is
probably to create an organization (adding any individual interested) and
upload as a contributed image in order to learn/verify the process, and
once we have something useful that meets the official requirements to work
towards migrating the image there.


https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ATLAS-2D2012&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=BRpv_IJLfOPKPg5CMvWe7vPrIiVO97XiMOUrvOhs2KY&m=AXTVamH8UuQbAmxLD4tudT6dZmTkURlqmn3FxS_gU2Q&s=GCN6S8TOWVgNDpUla2SgkOA27ALtj11H-HJGIDCIOqc&e=

atlas_docker.patch, atlas_docker1.patch, atlas_docker_2.patch
in a flexible manner, whether for development, production, or test
appeal
the Atlas build. This could be published on the wiki & it would make it
easier for developers to use Atlas within a docker environment - mostly by
addressing how to configure & start up
process. This builds on #1 by automating the creation of the image & making
it "just part of the build"
making it near trivial for any developer to easily pull down and experiment
with Atlas. Full source of course would be provided/documented so that a
user could customize as needed for their environment plus of course improve
what is provided with the core project
efforts in other teams to easily work together & be orchestrated


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


> Docker - image & hub - for Atlas
> --------------------------------
>
>                 Key: ATLAS-2012
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2012
>             Project: Atlas
>          Issue Type: New Feature
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>             Fix For: 1.0.0
>
>         Attachments: ATLAS-2012-Build-docker-image.patch, atlas_docker.patch, atlas_docker1.patch, atlas_docker_2.patch, graycol.gif
>
>
> Docker is increasingly become a standard way of easily running components in a flexible manner, whether for development, production, or test
> I feel there are a few things we can do with docker that will aid Atlas's appeal
> 1. We could provide a simple example of how to create a docker image from the Atlas build. This could be published on the wiki & it would make it easier for developers to use Atlas within a docker environment - mostly by addressing how to configure & start up
> 2. We could automatically generate a docker image as part of the build process. This builds on #1 by automating the creation of the image & making it "just part of the build"
> 3. We could publish the docker image from #2, for releases, to dockerhub, making it near trivial for any developer to easily pull down and experiment with Atlas. Full source of course would be provided/documented so that a user could customize as needed for their environment plus of course improve what is provided with the core project
> 4. We could work with other teams especially ranger, to allow similar efforts in other teams to easily work together & be orchestrated 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)