[chef] Re: chef-metal vs chef-container?

["Julian C. Dunn" < >]

On Fri, Aug 29, 2014 at 12:54 PM, Ringo De Smet 
<
 >
 wrote:

> There is a lot going on with Chef and containers. More specifically, I see
> chef-metal (1) and chef-container (2) popping up. However, it's not quite
> clear how these 2 compare to each other. Are they complementary? Will they
> merge?
>
> (1) https://github.com/opscode/chef-metal
> (2) http://docs.getchef.com/containers.html
>
> Can a Chef person bring some enlightenment?

Chef Metal is intended to orchestrate a cluster, or an entire pile of
infrastructure, independent of the underlying machine technology (VMs
on EC2, VMs on Azure, VMWare VMs, containers, even bare metal). You
can mix and match.

For using containers with Chef Metal, it's likely that there will be
some crossover. For example, the chef-metal driver for containers may
use or integrate with some of the code we developed for containers. We
aren't totally sure yet as we haven't gotten there.

If you don't care about cluster orchestration, then you can ignore
Metal. But we still have folks interested in containers generally,
particularly application devs that don't care about a cluster, they
just want a runtime. Chef for Containers (chef-init and
knife-container specifically are the software components) helps bring
configuration management to containers, because a Dockerfile and
golden images aren't configuration management. That's the pitch.

HTH,

- Julian

-- 
[ Julian C. Dunn 
<
 >
          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]