> > About creating clones, we have made another approach. > > Every server configures the network/ip itself at every boot, > Configures the network at *every* boot? Why not just at first boot? Do > you > never put the real IP address, host name and other values in /etc?
Pretty much DHCP, without the DHCP process. Let me pose the question differently: As long as the server has some immutable identity (in this case, the VM userid) and some reliable way to configure itself based on that immutable ID, why *would* you hardcode all that stuff inside the guest? Given the intense dependence of Linux on Z on the network, short of widespread integration of the IUCV console driver, you *want* that stuff outside the Linux system where you can easily fix it if it gets horked somehow or you need to change it. There are arguments for moving fstabs and other such goodies outside too. Personally (as I said yesterday at Marist), this is what DHCP is for, but Aglad's system works equally well, and is probably a good example of why a hypervisor is so handy. You *can* get this stuff outside the guests and use a highly developed hypervisor as part of the control infrastructure. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
