atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Jones (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-2012) Docker - image & hub - for Atlas
Date Wed, 16 Aug 2017 14:21:00 GMT

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

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

Having considered the switch to berkeley, can I suggest we stick with hbase *for now* and
consider switching in a further jira. WHilst berkeley is more lightweight and independent
of other hadoop components, it brings with it an additional license concern (gpl). So I propose
to leave as hbase.

I'll also note that though I'll change to run the unit tests, currently the return code from
the build isn't checked.. but I still think it's valuable to get this in as a sample and then
iterate?

> 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
>         Attachments: atlas_docker1.patch, atlas_docker_2.patch, atlas_docker.patch
>
>
> 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)

Mime
View raw message