LXD support ? about ansible-container HOT 12 OPEN

Howdy! We're happy to accept additional container-engine/orchestration modules. Check out container/engine.py:BaseEngine for the interface and container/docker/engine.py for an implementation. Do note that the interface is not presently stable.

from ansible-container.

+1 for LXD support. We are using LXD in production at University of Mumbai and it would be really great if ansible-container could support LXD. We are currently building our images manually.

from ansible-container.

We use LXD containers and Ansible for our projects, so +1 for LXD support definitely.

from ansible-container.

+1

from ansible-container.

I have been a bit busy contributing to lxd_container module for ansible,
and I will be on holidays the next two week, and then will be at europycon.
If anyone wants to start contributing on this go ahead, I will not be
active on this during the next three weeks.

Note that I have some research in novafloss/lxdapi including the
tests/make_busybox script which creates a minimal bootable image in a short
and readable bash script, so that may be useful to whoever wants to get
started on this.

Best regards, to whoever reads this message :)
On Jul 1, 2016 11:54 AM, "Ishwar Kanse" [email protected] wrote:

+1 for LXD support. We are using LXD in production at University of Mumbai
and it would be really great if ansible-container could support LXD. We are
currently building our images manually.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#78 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAFxrGya433W6Qfh23OR6-kfhYdIxsyWks5qROO_gaJpZM4I7wp_
.

from ansible-container.

I'm just back at work and should start working on this, if anyone wants to
collaborate perhaps we could do a hangouts session or something alike.
On Jul 27, 2016 10:15 AM, "Dmitrii Korotovskii" [email protected]
wrote:

We use LXD containers and Ansible for our projects, so +1 for LXD support
definitely.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#78 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFxrA2BvnJ0O2Cu7EoLARMTkwnVAO8jks5qZxOZgaJpZM4I7wp_
.

from ansible-container.

I have started working on this, let's see how this looks like at the end of the week.

from ansible-container.

Hey @jpic, any luck here?

from ansible-container.

Hey @gregdek, I think so, basically PR #295 si not complete and some help with internals would be welcome.

Interrestingly, the lxd engine seems like it'll be better for a reference implementation than the docker one ie. instead of generating a compose file and calling compose, just make each lxc calls sequentially to build the containers and all, so it's a lot more straightforward. Another interresting major difference with docker is that each running lxd daemon includes image registry features so I would expect this to also help.

It would help if a core-developer that has a good vision of ansible-container internals could describe how they would imagine this implementation, what method of the driver should do what exactly, and so on.

from ansible-container.

Sorry for my above response it wasn't of great quality but I wanted to share the idea of working more closely together as soon as I could hehe what I mean is:

It would be great if a core developer could post an engine class skeleton with descriptive comments in methods to implement. Otherwise, I'm sure a one-hour call with a core dev would be enough to dive me into action.

Otherwise, if we were to go for the exact same architecture, then we can use the equivalent of compose for lxd ... which is an ansible role, ansible-boot-lxd (in progress of being completely extracted from ansible-role-boot). In this case, we'd be using a template to generate a script to generate containers by calling the CLI in Python with the ansible module, exactly like it's happening in docker. We've already done all the research on that, we literaly tried everything when we implemented the lxd_container module in ansible - and when I say we, i really mean @hnakamur in epic ansible/ansible-modules-extras#2208

However our experience with lxc (as the name of the command to manage lxd, not as the set of commands to manage system containers with a running daemon) is positive. The code in the lxd_container module does really clean exec calls and has an option to exit dumping output in various formats such as json. That CLI has been so well developed that honnestly, we don't need to encapsulate its usage in a separate package.

from ansible-container.

@jpic your PR was rejected (well, closed) at some point, so I'm presuming there's not that much movement here. What can we do to help?

from ansible-container.

Absolutely, i'm not working on this anymore.

from ansible-container.