Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-23 Thread Jonathan Gazeley
On 22/02/11 16:51, David Kavanagh wrote: I thought about DHCP for static addresses. I'd need the MAC for each machine though This is why we have a small pool fully dynamic IP addresses for our build system that doesn't require any MAC registration. The subnet is only able to talk to the PXE

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-23 Thread Ohad Levy
On Wed, Feb 23, 2011 at 11:17 AM, Jonathan Gazeley jonathan.gaze...@bristol.ac.uk wrote: On 22/02/11 16:51, David Kavanagh wrote: I thought about DHCP for static addresses. I'd need the MAC for each machine though This is why we have a small pool fully dynamic IP addresses for our build

RE: [Puppet Users] provisioning bare metal (best practices)

2011-02-23 Thread Jennings, Jared L CTR USAF AFMC 46 SK/CCI
+1 for Cobbler. At my site, we don't kickstart on the production network, in order to avoid the case where a not-fully-secured machine is exposed to network attacks. My kickstart network is all in one room, and so is easier to secure, logically and physically. On such a network, automatic

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-23 Thread David Kavanagh
Jared, Are you suggesting separate physical subnet, or simply a logical subnet on the same physical network (using netmask)? David On Wed, Feb 23, 2011 at 10:37 AM, Jennings, Jared L CTR USAF AFMC 46 SK/CCI jared.jennings@eglin.af.mil wrote: +1 for Cobbler. At my site, we don't kickstart

RE: [Puppet Users] provisioning bare metal (best practices)

2011-02-23 Thread Jennings, Jared L CTR USAF AFMC 46 SK/CCI
Jared, Are you suggesting separate physical subnet, or simply a logical subnet on the same physical network (using netmask)? Mine's physically separate. I think it's what is required (google UNIX STIG; see section 12.6), and it simplifies configuration and usage (this network does this thing;

[Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread David Kavanagh
I'm about to start playing with Kickstart. I never really had to provision bare servers beyond a normal OS install, so I need something to use along with Puppet. Is there a general consensus on what the best option is? I'd need to set up the node with IP/hostname/role. (I have a custom fact for

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread Trevor Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Why not use DHCP? This is what it's for. The general standard that I've seen is DHCP + KS + modification scripts/puppet/whatever Trevor On 02/22/2011 10:47 AM, David Kavanagh wrote: I'm about to start playing with Kickstart. I never really had to

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread Jonathan Gazeley
We have a small pool of DHCP IP addresses for use only in the build process. This is our process: 1. We boot the servers from PXE network boot 2. They get one of the temporary IPs 3. They start a CentOS network install using a kickstart file with the bare minimum of packages selected,

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread Mohit Chawla
Foreman could come in handy. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread Brian Gallew
Never forget the DHCP does NOT necessarily mean dynamic addresses. Depending upon your corporate culture, it may be perfectly acceptable for DHCP to hand out statically assigned addresses to your hosts. This would allow your build process to be easy, and you can have the host never DHCP again

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread David Kavanagh
I thought about DHCP for static addresses. I'd need the MAC for each machine though. For now, I'm worrying about plugging some media or doing network boot on machines by hand. I suppose I'll need to do something on the host to indicate what the machine role will be. In any case, I could simply use

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread vagn scott
Oh, great timing! I'm working on pretty much the same question. I have used FAI and Opsware, and homebrewed scripts to do provisioning in the past. I have never been all that happy with any of them, and am taking another look at the problem to try to get to as simple and portable a solution

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread James A. Peltier
- Original Message - | I thought about DHCP for static addresses. I'd need the MAC for each | machine snip This is not necessarily true. If you configure the client to send a requested hostname it will not require you to register the MAC address, although, as per the usual this is a

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread Thomas Bellman
James A. Peltier wrote: This is not necessarily true. If you configure the client to send a requested hostname it will not require you to register the MAC address, although, as per the usual this is a security risk since anyone on the network could pose as a machine if they knew that was the

Re: [Puppet Users] provisioning bare metal (best practices)

2011-02-22 Thread Russell Jackson
On 02/22/2011 10:14 AM, James A. Peltier wrote: - Original Message - | I thought about DHCP for static addresses. I'd need the MAC for each | machine snip This is not necessarily true. If you configure the client to send a requested hostname it will not require you to register