On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow <harlo...@fastmail.com> wrote:

> Radical idea, have each project (not libraries) contain a dockerfile
> that builds the project into a deployable unit (or multiple dockerfiles
> for projects with multiple components) and then it becomes the projects
> responsibility for ensuring that the right code is in that dockerfile to
> move from release to release (whether that be a piece of code that does
> a configuration migration).
I've wondered about that approach, but worried about having the Docker
engine as a new dependency for each OpenStack node.  Would that matter?
 (Or are there other reasons why OpenStack nodes commonly already have
Docker on them?)
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to