atlas-dev mailing list archives

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


Nigel Jones commented on ATLAS-2012:

* Instructions as a twiki sounds good. I'll extend the patch for that (just getting rb setup)
* I think as a starting point, any backend that functions is ok... it could be berkely, could
be hive? Berkely may have a smaller footprint as it more portable. On that basis I'd be inclined
to agree
* If the image ends up being created after a full build,  do you think it's still valuable
to run the unit tests within the docker image. To some extent I agree, in case of any differences
between the container environment and the normal build environment. It will take more time,
and since the build should already be good might not be necessary but then if automated does
time matter. On balance I'd be inclined to agree so can make that change too

Thanks for the good points. will make those updates.

> Docker - image & hub - for Atlas
> --------------------------------
>                 Key: ATLAS-2012
>                 URL:
>             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

View raw message