Open Stack

On Fri, Apr 28, 2017 at 11:11 AM, Paul Belanger <pabelanger at redhat.com>
wrote:

> On Wed, Apr 12, 2017 at 10:53:17PM -0400, Emilien Macchi wrote:
> > [adding more tags to make sure folks can see this thread]
> >
> > What we would like to hear from Deployment projects (Kolla, OSA, Helm,
> etc) is:
> >
> > 1) Is there any overlap with some ongoing efforts?
> > 2) Would you be interested by contributing to this effort?
> >
> Had a chance to look at this today, the main question I have, why are we
> building something from scratch? I know today there is both
> ansible-container
> and docker-compose, even linuxkit now.  Is that not something you could
> build
> off or work upstream?
>
> I did see anything in the documentation explaining why that was.
>
>
It forklifts logic that TripleO already uses to manage containers. Long
term TripleO will likely want to move to a widely adopted tool for
container orchestration. Now that our logic is in its own library we can
safely evolve it with the aim of switching in the future with minimal
disruption.



> > Any feedback is welcome,
> > Thanks.
> >
> > On Wed, Apr 12, 2017 at 10:25 PM, Steve Baker <sbaker at redhat.com> wrote:
> > > This is just a heads-up that in a week or so I intend to propose a new
> git
> > > repo to be hosted by OpenStack and adopted by the TripleO project.
> > >
> > > paunch [1] is a python library and CLI tool which forklifts the logic
> of the
> > > docker-cmd heat-agents hook[2] into its own project.
> > >
> > > The change to switch the docker-cmd hook to paunch[3] deletes a
> satisfying
> > > number of lines of code. Typically a hook is a thin wrapper over
> another
> > > configuration tool, and the docker-cmd hook was an unfortunate
> exception.
> > >
> > > The YAML format used by paunch is currently driven by the needs of
> TripleO
> > > and is derived from the docker compose v1 format. Over time I'd like to
> > > evolve the format to faithfully implement defacto standard formats,
> > > specifically to ease the transition for TripleO to orchestrate
> containers
> > > with kubernetes.
> > >
> > > At this point I wouldn't advocate for the CLI to be a generally used
> tool
> > > for single node container orchestration, but it will gain some commands
> > > aimed at making developing and deploying containerised TripleO easier.
> > >
> > > I'll wait for about a week to get feedback on this proposal, in the
> meantime
> > > I'll continue to develop and document the format within [1].
> > >
> > > cheers
> > >
> > > [1] https://github.com/steveb/paunch
> > > [2]
> > > https://github.com/openstack/heat-agents/tree/master/heat-
> config-docker-cmd
> > > [3] https://review.openstack.org/#/c/455845/
> > >
> > > ____________________________________________________________
> ______________
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
> unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
> >
> >
> > --
> > Emilien Macchi
> >
> > ____________________________________________________________
> ______________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170428/dc73b79e/attachment.html>