Volker A. Brandt wrote: > Hello Sundar, hello Andre! > > >>> http://www.opensolaris.org/os/project/caiman/auto_install/Design_doc_delta_for_AI_Spring_2009.pdf. >>> > [...] > > >> Section 1.2 >> >> Several uses of "could" in the paragraph beginning with "If DNS >> configuration is not possible..." Can you tighten this down >> to say what you intend to do for the spring release? >> >> For the DNS-naive like me, what are the implications of using DNS >> unicast? I believe I understand this means that an install client >> can reside on a different subnet than the server, but specifically >> which server functions (DHCP, DNS, TFTP, http) could be on a different >> subnet and which ones would have to be on the same subnet as the >> client (based on what little I know I'd assume DHCP at least would >> need to be on the local subnet while http can be anywhere). >> > > I would also be interested in this clarification. Specifically, my > personal opinion is that AI-style installations will typically be done > in medium to large infrastructures rather than in a home or developer > environment. > > Such large infrastructures tend to have different admins, if not > different departments, for network/DNS administration, and Solaris > management. In such environments, it is very difficult or impossible > (for non-technical reasons) to implement any changes in DNS. Therefore, > the install.conf method described in section 1.2 deservers the highest > priority IMHO. However, it's not really clear what you want to deliver > first. :-) > The file based configuration will be always created when a new service is started. If the customer wants to use unicast DNS, the DNS server should be updated with the service information. > Also, referring to the lookup sequence you describe while listing > the various alternatives, I think a better sequence would be: > > 1. use client-specific config (menu.lst.01NNN..., install.conf.01NNN... > likewise) > > 2. if #1 is not available, use AI server specific files (menu.lst, > install.conf) > > 3. if #2 is not available, look for TXT and SRV in DNS > > > 4. if #3 is not available, look for mDNS > > > > Regards -- Volker > The problem with your suggestion is that unicast DNS and multicast DNS will never be used since the file based configuration will be always there. If you really want to use file based approach, use the create-service to setup unicast DNS. This create right configuration in the menu.lst or install.conf files. If your network don't have a DNS server configured with the install service, the AI client will use the files for getting the information about the service to be used.
Thanks, Sundar -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090218/69eacee1/attachment.html>
