I'm testing DRBL for deployment on our office network, with Ubuntu server and clients. The wording of the DRBL documentation led me to believe that DRBL had its own DHCP server built in, when it really appears to be "whatever DHCP implementation you put on the machine yourself and let DRBL configure". (The Ubuntu APT package really ought to have its dependencies configured properly so dhcp and tfptd-hpa are pulled down at the same time!). Is that the correct way to think about it?
If yes, can I edit the config files of dhcp3-server in the normal way (as if DRBL wasn't there) to set up the assignment of IPs to MAC addresses? What we are thinking is that we might write a script that assigns IPs on the .3 subnet (storage LAN, no current dhcp setup) based on a machine's IP on the .2 subnet (internet LAN, DHCP run by an existing gateway). I also think having to build the MAC-to-IP list by network booting the machines while running drblpush on the server is annoying; I can't just shut down machines on a whim since they're being used, either in person or by someone via remote SSH. I'd like a way to do it that's less disruptive to all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, you can edit that in normal way if you know how DRBL works.
I suggest that you can let "drblpush -i" to configure that, then modify the generated dhcpd.conf as you want.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you explain what happens when drblpush -i is run, as far as files written? Does it attempt to write anything to the client machines (which I don't want yet)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Does it attempt to write anything to the client machines" -> "drlbpush -i" will modify the configuration files of DHCP, TFTP, NFS, and NIS, and it will generate the files for clients. Those files are located in the path:
/tftpboot/node_root/
/tftpboot/nodes/
/tftpboot/nbi_image/
on the server.
It will not write any files on your client's hard drive, unless you want it to generate a swap file as virtual memory.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm testing DRBL for deployment on our office network, with Ubuntu server and clients. The wording of the DRBL documentation led me to believe that DRBL had its own DHCP server built in, when it really appears to be "whatever DHCP implementation you put on the machine yourself and let DRBL configure". (The Ubuntu APT package really ought to have its dependencies configured properly so dhcp and tfptd-hpa are pulled down at the same time!). Is that the correct way to think about it?
If yes, can I edit the config files of dhcp3-server in the normal way (as if DRBL wasn't there) to set up the assignment of IPs to MAC addresses? What we are thinking is that we might write a script that assigns IPs on the .3 subnet (storage LAN, no current dhcp setup) based on a machine's IP on the .2 subnet (internet LAN, DHCP run by an existing gateway). I also think having to build the MAC-to-IP list by network booting the machines while running drblpush on the server is annoying; I can't just shut down machines on a whim since they're being used, either in person or by someone via remote SSH. I'd like a way to do it that's less disruptive to all.
Yes, you can edit that in normal way if you know how DRBL works.
I suggest that you can let "drblpush -i" to configure that, then modify the generated dhcpd.conf as you want.
Steven.
Can you explain what happens when drblpush -i is run, as far as files written? Does it attempt to write anything to the client machines (which I don't want yet)?
"Does it attempt to write anything to the client machines" -> "drlbpush -i" will modify the configuration files of DHCP, TFTP, NFS, and NIS, and it will generate the files for clients. Those files are located in the path:
/tftpboot/node_root/
/tftpboot/nodes/
/tftpboot/nbi_image/
on the server.
It will not write any files on your client's hard drive, unless you want it to generate a swap file as virtual memory.
Steven.