Chef and box provisioning


#1

I’m wondering how others on this list approach box provisioning, and other
fun stuff like IP management. In my current gig we go this route; hit up IP
plan in a browser, figure out the IP we need, jot it down, put notes in IP
plan about. Then RDP to a windows box, run the VMware client to setup a
new box, walk through that song and dance. After that, use the console in
VMware to setup the networking and reboot. From a workstation, knife
bootstrap, and after that, finally, chef. I know there are knife plugins to
utilize VMware, are there other (better?) ways to handle that? How are
others handling IP management? Can that be done via chef/knife too, or is
that just a matter of scripting something that curl can hit an API and
setup? Thanks for any input.


http://philcryer.com/


#2

When we were using vmware we had a base image with a static ‘template’ ip.
We just cloned this template then bootstrapped that ip right away. We then
logged in a manually updated the ips. Seems nicer than having to use the
vmware console to do that. Vmware support wasn’t around then so we never
had that route available. Hope this helps.

On Wed, Nov 20, 2013 at 8:52 AM, Phil Cryer phil@philcryer.com wrote:

I’m wondering how others on this list approach box provisioning, and other
fun stuff like IP management. In my current gig we go this route; hit up IP
plan in a browser, figure out the IP we need, jot it down, put notes in IP
plan about. Then RDP to a windows box, run the VMware client to setup a
new box, walk through that song and dance. After that, use the console in
VMware to setup the networking and reboot. From a workstation, knife
bootstrap, and after that, finally, chef. I know there are knife plugins to
utilize VMware, are there other (better?) ways to handle that? How are
others handling IP management? Can that be done via chef/knife too, or is
that just a matter of scripting something that curl can hit an API and
setup? Thanks for any input.


http://philcryer.com/


#3

This (older) post might be useful. -
http://www.jedi.be/blog/2011/03/29/provisioning-workflow-using-vsphere-puppet/

  • I boot the vm first into bios mode, to have the mac addresses created.
  • I fetch the macaddreses with the API
  • Then I register the mac addresses with omapi in dhcp.
  • then I boot in the administrative lan
  • based on the vm name, the postinstall of the inititial install will
    configure it to use the correct vlan for production.

some of the java code can be found at -

On 20/11/13 16:10, Nic Grayson wrote:

When we were using vmware we had a base image with a static 'template’
ip. We just cloned this template then bootstrapped that ip right away.
We then logged in a manually updated the ips. Seems nicer than having
to use the vmware console to do that. Vmware support wasn’t around
then so we never had that route available. Hope this helps.

On Wed, Nov 20, 2013 at 8:52 AM, Phil Cryer <phil@philcryer.com
mailto:phil@philcryer.com> wrote:

I'm wondering how others on this list approach box provisioning,
and other fun stuff like IP management. In my current gig we go
this route; hit up IP plan in a browser, figure out the IP we
need, jot it down, put notes in IP plan about.  Then RDP to a
windows box, run the VMware client to setup a new box, walk
through that song and dance. After that, use the console in VMware
to setup the networking and reboot. From a workstation, knife
bootstrap, and after that, finally, chef. I know there are knife
plugins to utilize VMware, are there other (better?) ways to
handle that? How are others handling IP management? Can that be
done via chef/knife too, or is that just a matter of scripting
something that curl can hit an API and setup? Thanks for any input.

-- 
http://philcryer.com/

#4

I see, and for that, you could have a base recipe setup the IP during
bootstrap, if it could get that info and plug it in.

On Wed, Nov 20, 2013 at 9:10 AM, Nic Grayson nic.grayson@banno.com wrote:

When we were using vmware we had a base image with a static ‘template’ ip.
We just cloned this template then bootstrapped that ip right away. We then
logged in a manually updated the ips. Seems nicer than having to use the
vmware console to do that. Vmware support wasn’t around then so we never
had that route available. Hope this helps.

On Wed, Nov 20, 2013 at 8:52 AM, Phil Cryer phil@philcryer.com wrote:

I’m wondering how others on this list approach box provisioning, and
other fun stuff like IP management. In my current gig we go this route; hit
up IP plan in a browser, figure out the IP we need, jot it down, put notes
in IP plan about. Then RDP to a windows box, run the VMware client to
setup a new box, walk through that song and dance. After that, use the
console in VMware to setup the networking and reboot. From a workstation,
knife bootstrap, and after that, finally, chef. I know there are knife
plugins to utilize VMware, are there other (better?) ways to handle that?
How are others handling IP management? Can that be done via chef/knife too,
or is that just a matter of scripting something that curl can hit an API
and setup? Thanks for any input.


http://philcryer.com/


http://philcryer.com/