Open Stack

Hi.

It would be great to meet in any case.

We've been exploring Atomic system containers (as in 'atomic install
--system ...') for our internal plugins at CERN, and having some
issues with runc and selinux definitions plus some atomic command
bugs. It's mostly due to the config.json being a hard one to build
manually (or the config.json.template passed to Atomic), especially
after we've got used to the nice docker usability by now :) In any
case the atomic blog posts are incredibly useful, thanks for that!

To explain why we're trying this: we're running all our internal
plugins inside containers (this is for support of internal systems we
add to upstream Magnum). Running them in docker is problematic for two
reasons:
* they are visible to the users of the cluster (which is confusing,
and allows them to easily shoot themselves in the foot by killing
them)
* they cause a race condition when restarting docker if volumes were
previously created, as docker tries to make the volumes available
before launching any container

Having them managed by systemd and run directly in runc solves both of
the issues above. I understand docker 1.13 has a new plugin API which
might (or maybe not) help with this, but i haven't had time to try it
(all of the above is with docker 1.12).

Cheers,
  Ricardo

On Wed, Jan 18, 2017 at 7:18 PM, Josh Berkus <jberkus at redhat.com> wrote:
> Magnum Devs:
>
> Is there going to be a magnum team meeting around OpenStack Summit in
> Boston?
>
> I'm the community manager for Atomic Host, so if you're going to have
> Magnum meetings, I'd like to send you some Atomic engineers to field any
> questions/issues at the Summit.
>
> --
> --
> Josh Berkus
> Project Atomic
> Red Hat OSAS
>
> __________________________________________________________________________
> 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