atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ernie ostic (JIRA)" <>
Subject [jira] [Commented] (ATLAS-2012) Docker - image & hub - for Atlas
Date Sat, 26 Aug 2017 20:38:00 GMT


ernie ostic commented on ATLAS-2012:

Nigel.  This is huge.   Thank you.  Once we have a simple way for people to test different
builds, we can more easily expect to see a ramp-up in the number of participants ---- such
as governance and data professionals who are interested in Atlas, but who don't have the deep
java skills or open source experience, or simply don't have the time to invest but want to
work with the most recent build.  Until now their only viable option is to wait for a vendor
to create a VMware or similar image.    

> Docker - image & hub - for Atlas
> --------------------------------
>                 Key: ATLAS-2012
>                 URL:
>             Project: Atlas
>          Issue Type: New Feature
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>         Attachments: ATLAS-2012-Build-docker-image.patch, atlas_docker1.patch, atlas_docker_2.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

View raw message