On Wed, Nov 23, 2011 at 07:21:37PM +0000, Dan White wrote:
---- Christian Horn chorn@fluxcoil.net wrote:
On Wed, Nov 23, 2011 at 12:54:58PM +0000, Dan White wrote:
I started out with a classic Cobbler Server, net/PXE-booting the clients to install. However, the folks controlling DHCP are pro-Microsoft/anti-Linux and are uncooperative. If I do my own DHCP, it will cause problems -- possibly technical problems, most definitely bureaucratic/security problems. So my intent is to find an alternate workflow that could remove the DHCP-related obstacle.
I am wondering if they could do just a static load of gpxe for you, and that could always hint on i.e. fetching something via http then from your cobbler box which you can control. Maybe reading up on what gpxe can do helps giving ideas.
Which "they" are you referring to ?
The admins of the dhcp server. They would for all the systems they pxeboot for you use the same entry. This could fetch things via http from always the same place on your cobbler system, and you would in that place provide the content for the exact system you want to deploy. Would be limited to just one system pxebooting at a time, the cobblersystem would at the one place just always offer the things for one system.
Also just a rough idea, could hang fast looking at details.
Christian