[node-devel] Docker in the land of Node (plugin and build-system)

[Fabian Deutsch]

Hey,

Docker is somewhat a hype these days.

And docker can also be found in the Node land. In two ways actually.

First:
Ryan added some Dockerfiles which you can use to build ovirt-node-iso
within a Docker container. That is great. Because it separates the host
OS from the to-be-build-OS.
Ref: http://gerrit.ovirt.org/#/c/24679/

Second:
I just added a (draft) plugin which adds Docker to an existing Node ISO
and runs it in "host mode", that means Docker will be bound to a public
port (4243 in out case) and users can use it from remote using:

$ docker -H $NODEADDR:4243 info

This has the benefit of having the solid nature of Node as a base and
the flexibility of Docker on top.
Ref: http://gerrit.ovirt.org/#/c/25370/


Both ways need testing, and the latter can not be easily tested yet, as
systemd (aka Fedora image) is required.

- fabian

[Mike Burns]

Post by Fabian Deutsch
Hey,
Docker is somewhat a hype these days.
And docker can also be found in the Node land. In two ways actually.
Ryan added some Dockerfiles which you can use to build ovirt-node-iso
within a Docker container. That is great. Because it separates the host
OS from the to-be-build-OS.
Ref: http://gerrit.ovirt.org/#/c/24679/

Very nice. So does this removes livecd-tools from the build process?
or does it run livecd-tools through Docker?

Post by Fabian Deutsch
I just added a (draft) plugin which adds Docker to an existing Node ISO
and runs it in "host mode", that means Docker will be bound to a public
$ docker -H $NODEADDR:4243 info
This has the benefit of having the solid nature of Node as a base and
the flexibility of Docker on top.
Ref: http://gerrit.ovirt.org/#/c/25370/

IIUC, this would allow containers to run locally on ovirt-node. Is
there any management interface for this? Is this a roadmap item for
engine to consume? Or is it to make Node an option for another
container-based virtualization management tool?

Post by Fabian Deutsch
Both ways need testing, and the latter can not be easily tested yet, as
systemd (aka Fedora image) is required.
- fabian

[Fabian Deutsch]

Post by Mike Burns

Post by Fabian Deutsch
Hey,
Docker is somewhat a hype these days.
And docker can also be found in the Node land. In two ways actually.
Ryan added some Dockerfiles which you can use to build ovirt-node-iso
within a Docker container. That is great. Because it separates the host
OS from the to-be-build-OS.
Ref: http://gerrit.ovirt.org/#/c/24679/

Very nice. So does this removes livecd-tools from the build process?
or does it run livecd-tools through Docker?

No, livecd-tools are still used, they are run within Docker.

Post by Mike Burns

Post by Fabian Deutsch
I just added a (draft) plugin which adds Docker to an existing Node ISO
and runs it in "host mode", that means Docker will be bound to a public
$ docker -H $NODEADDR:4243 info
This has the benefit of having the solid nature of Node as a base and
the flexibility of Docker on top.
Ref: http://gerrit.ovirt.org/#/c/25370/

IIUC, this would allow containers to run locally on ovirt-node. Is
there any management interface for this?

This should as it uses default Docker features (HTTP Rest API). It
should be possible to use it with e.g. shipyard
(http://shipyard-project.com/).

It also seems that OpenStack is using the HTTP Rest API of Docker
(https://wiki.openstack.org/wiki/Docker).

Tho I must say that I have not tested both yet.

Post by Mike Burns
Is this a roadmap item for
engine to consume? Or is it to make Node an option for another
container-based virtualization management tool?

No, Engine is not targeting Docker afaik.

And yes, it was more about to show that Node can also host other
container based virtualization solutions.

This was just a small excursion while I played with docker, because I am
still looking for a lightweight hypervisor which is easy to use in a
home lab.

So something like a libvirt-standalone or (now) docker plugin, or maybe
it's lxc ...

- fabian

Post by Mike Burns

Post by Fabian Deutsch
Both ways need testing, and the latter can not be easily tested yet, as
systemd (aka Fedora image) is required.
- fabian