jan damborsky wrote: > > Proposed final solution: > ------------------------ > I think that the final solution here is to worked out set of requirements > we would like to address and reconsider existing design and > implementation
Agreed, this definitely needs to be revisited. > 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? > > * 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? -ethan > > When those changes are applied, behavior for Sparc clients would be > similar > to the one for x86 clients. > > I have prepared preliminary fix with those changes and tested it for > Sparc as well as x86 clients. > > The preliminary webrev is available at following location: > http://cr.opensolaris.org/~dambi/bug-8130/ > > please let me know, if you think that this problem can be qualified > as stopper for 2009.06, if there are other related issues I have > not noticed and if solution mentioned above can be acceptable > or different approach should be taken. Any comments are highly > appreciated. > > Thank you very much in advance, > Jan > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
