Ethan Quach wrote: > > Michael Barrett wrote: >> From what I can tell it does set it up, but is serves out which ever >> image (macro) I checked in first. For example. When I setup the >> SPARC first, it installs my SPARC boxes fine. But when I then add in >> the x86 service, it still serves out the SPARC image to my x86 boxes. >> >> If I then delete the environment and check in the x86 image first, my >> x86 boxes install fine. But then when I check in my SPARC service, it >> serves out my x86 image to my SPARC boxes. > > The macros that installadm creates in the DHCP server doesn't > distinguish between architectures, so when it gets a request from > a client system for an IP address, it just randomly gives it one from > either pool of addresses. > > There is a way to add additional vendor-specific options to your > macros to signify architecture preference, but we didn't want AI > to rely on these definitions being defined in the DHCP server, and > hence AI doesn't use them. >
This was likely a poor choice, as there's likely to be lots of heterogeneous usage. Since we can tell which architecture the image is for, this data should go into per-architecture macros. > If you've got a heterogeneous environment, you have to use the > "installadm create-client ...." subcommand to create client specific > macros for each of your clients. > Or, configure DHCP to provide it in the client-class macros; you'll need to use dhtadm or dhcpmgr to do this since installadm can't. Dave
