Chef Metal - chef-boneyard/chef-summit-2014 GitHub Wiki

Thursday, Medina, 1330

What chef metal, is, spin up a chef zero servers, specific drivers, anything fog can chat to. Call to launch via ssh, and magical tunnel back to your chef zero server on your laptop.

Include in chef DK?

Hanlon?, re-refork of razor ( EMC, open source, to puppet labs ), rewritten by puppet labs. Project Zombie, Nick and Tom not happy, they rewrote and hence comes hanlon ( bare metal, pxe boot ).

idempotent way of describing your infrastructure. No orchestration model for now. "I will do the things you told me to do", or fail. Orchestration around evacuating the machine, not done.

You an turn off converge for metal,

4 stages

allocate, goes to aws, allocate, or reserves, grabs id, and stuffs into chef server ready, drivers sit and wait, for machine to come up, sometimes kick/reboot. ( minor bug that will kick the server, but fix coming ) store referential state. Name and label and reference, also works in docker.

( state held in chef server, ). Images in data bags.

Does it support yrun? In theory, yes. Support for vpc, not there yet ELB support. End goal, USE1 USW1, vpn and load balancer in the middle. Wish to support dns primitives.
Goal, to describe all your infrastructure in once place. Chef recipes. Trust the description will be used. Metal heat? Knife-kitchen-metal. Metal driver and Heat drivers coming. Just a chef client run.

First doing, provision from lappie, you can use chef-apply.
You are not going to put your keys in github right? Of course not. destroy action is possible, but you have to actually say "destroy". In your cookbook, has front end etc... metal clean recipe. but not for production.

Can do file upload when you declare your provisioner. ( ie put your keys here ) machine 'mario' do File

Background ,goals, to auto connect to a machine, as long as you have the keys, machine execute possible. ssh transport, and winrm transport for windows. expect(ish)?
Can multihop to remote machines, using keys that are local to each hop. Driver just talks to the docker API. Viral provisioning. Chefible? Nice expressive thing.

You can describe your environment,