Frank Ludolph wrote: > Sundar Yamunachari wrote: >> Susan Sohn wrote: >>> Notes from the meeting have been posted at: >>> >>> http://www.opensolaris.org/os/project/caiman/auto_install/ai_svc_scenario_mtg_0610.txt >>> >>> >> I have few questions on the various use cases in the notes. >> >> About the dhcp setup: >> >> When you setup the IP addresses, what macro will be assigned in >> the DHCP table? Will it be different for SPARC service and X86 >> service? How will you ensure that the client will get the address >> that correspond to the correct architecture? >> Does the architecture specific macros interfere with per client >> specific macros. If the DHCP server has a architecture specific macro >> that points a global service and a client specific setup that points >> to a different service, does the client specific macro override what >> is specified in the architecture macro? > The IP addresses are only used when setting up the AI controlled DHCP > server and only refer to the range of dynamic addresses that server > will manage. They do not control which service a booted machine will > be directed to. (Correct Jan?)
Yes, this is correct. DHCP IP address management and DHCP AI configuration would be independent and there will be no install service specific configuration present on DHCP server. The intent here is to minimize dependency of AI on DHCP. If AI is asked to create IP pool of addresses on SUN DHCP server, 'host' macro is assigned to them by default (also created by default) - please see 'Note' at the bottom of following document for more information: http://docs.sun.com/app/docs/doc/816-4554/dhcp-overview-14a?a=view Speaking about how AI specific DHCP setup might look like: Sparc: * only NBP name&location will be passed to client (URL to wanboot-cgi) x86: * NBP name&location (pxeGRUB) and menu.lst name will be passed to AI client Jan
