CR 7130777 is asking for a method by which to opt out of automated DHCP configuration changes performed by the AI software when installadm is used to create and delete services and clients. I've discussed a possible solution with Ethan and I wanted to send it out to the team to see if anyone had any other ideas or objections to this one before I pursue it.
Overview The installadm CLI has options for configuring an ISC DHCP server and automatically adding the proper subnet entry for the user during the 'create-service' command. This is the only explicit request that the user can make for DHCP configuration automation. If we keep this automation in place, it would be ideal to remove it from the 'create-service' command, and add a specific set of options to configure DHCP. However, that's not something we'll be doing for U1, if at all. Given there isn't another facility in place to request assistance with DHCP configuration management, it was decided for any commands which would require changes to the DHCP configuration that, if a local ISC DHCP server was discovered, those changes would be committed automatically. It was expected that ISC DHCP servers managed outside the scope of the install software's automation would be located on other servers. Therefore, it was assumed that in taking care of the automated configuration functionality, it would not be likely to cause issues for other, non-automated configurations. As it turns out, this isn't the case. There seem to be at least enough people managing ISC DHCP servers and AI servers on the same machine that we need to provide a way for these users to opt out of the configuration changes. Proposed solution The actions which will cause a local DHCP configuration to be automatically updated are 'create-service', 'delete-service', 'create-client' and 'delete-client'. Rather than add a new switch to each of these commands, I'd prefer to add a single boolean SMF property to the AI service, 'manage-dhcp' or similar. The '-i' and '-c' options will behave as they are currently do for 'create-service', but will issue a warning if 'manage-dhcp' is not set to true. For all implicit automated configuration changes, if the property is true, we will behave as we currently do. If set to false, then we'll not attempt to update the configuration at all. I believe that this value should default to false, so that default behavior out of the box is to not alter any configuration unless requested to do so. Please let me know what you think, thanks. Jesse _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
