jan damborsky wrote: > Hi Ethan, > > > On 04/15/09 16:03, Ethan Quach wrote: >> >> jan damborsky wrote: >> >>> with respect to >>> >>> * what are desired install service scopes to be available >>> - currently for Sparc we can either explicitly associate install >>> service with particular client (identifying it by MAC address) >>> and use another one for rest of Sparc clients. More than one >>> service can't be created serving broader scope, since only >>> one /etc/netboot/wanboot.conf file can be created. >>> >>> * how Sparc client obtains location of AI images >>> - now it is spread across two places - one for boot_archive, >>> one for compressed archives. It should be consolidated, so >>> that it is less error prone and easier to maintain. >>> >>> Proposed fix for now: >>> --------------------- >>> For now any significant design changes are not appropriate, >>> since they would be too risky. Based on this I am thinking about >>> following temporary solution before final approach can be taken: >>> >>> * when new service is created, don't touch /etc/netboot/wanboot.conf >>> if it contains pointer to existing boot archive. It makes sure >>> that once /etc/netboot/wanboot.conf is created for one service, >>> it is not accidentaly overwritten by another service. So clients would >>> continue to use first service as a default (in cases 'create-client' >>> is not called) and mismatch would be avoided in this case. >> >> But if we create a second sparc service (say with build N+3, or N-3 >> for that matter), then clients trying to use the second sparc service >> will get a mismatch still, right? > > It depends on how the second service is created: > > [1] installadm create-service -n service_2 -s <ai_iso_2> <ai_image_2> > > In this case, the only way how client could use service_2 is to > associated > it with this service explicitly by calling 'create-client'.
But does a sparc create-service without the -i -c not create the /etc/netboot/wanboot.conf file? DHCP config is totally secondary. A user who just moderately knows what they are doing can subsequently manually add IP addresses associated with the service_2 macro created above. > > service_1 will continue to be used by default (if 'create-client' is not > called). > > Mismatch doesn't occur. > > [2] installadm create-service -n service_2 -i <IP_start_2> -c > <IP_pool_size_2> > -s <ai_iso_2> <ai_image_2> > > * /etc/netboot/wanboot.conf will still point to service_1 boot archive. > * two disjoint sets of IP pools will be available > one for service_1 associated with service_1 dhcp macro, > one for service_2 associated with service_2 dhcp macro > > New client connected to the network would obtain boot archive from > image_1, > but I am not sure how DHCP server behaves in this situation - from which > pool it will assign IP address ? Is this deterministic/supported > scenario ? Nope, its random. A client can be given an IP of either pool. Its not a deterministic scenario. I've yelled about this before, but its apparently a designed usage case. > > [3] installadm create-service -n service_2 -i <IP_start_1> -c > <IP_pool_size_1> > -s <ai_iso_2> <ai_image_2> > > In this case, IP pool for service_1 is replaced with IP pool for > service_2 > which would mean boot_archive is picked from image_1 and compressed > archives > from image_2 and mismatch would occur. What is expected result in this > case ? Would our calls to pntadm to set those IPs for service_2 macro fail since those IPs already exist in the table for service_1? -ethan > > >> >>> >>> * when service is deleted along with associated AI image (by passing >>> '-x' option) and if /etc/netboot/wanboot.conf file contains pointer >>> to boot archive in that image, /etc/netboot/wanboot.conf will be >>> deleted along with that AI image. It would avoid >>> /etc/netboot/wanboot.conf pointing to non-existent AI image. >> >> If clients were using a second sparc service, and had been falling back >> to whatever was being specified in /etc/netboot/wanboot.conf, then >> doing this would mean that these clients fail to get a wanboot.conf at >> all, right? > > Yes this is correct - but the client would fail later anyway when trying > to obtain boot archive, since in that case the default service was > removed > along with AI image and is no longer available. > > Thanks a lot ! > Jan >
