jan damborsky wrote: > Hi Ethan, > > > On 04/07/09 01:28, Ethan Quach wrote: >> So this really sounds like that when we add a manifest to >> an install service, we should validate it against the schema >> from the associated install image of that service, instead >> of any schema delivered with the SUNWinstalladm-tools >> package installed on that server. >> >> Does that sound correct? If so, I'll file a bug on this. > > That sounds pretty good - it would solve problem with compatibility > between AI manifest and installadm tools in clean way. I think there > might be one assumption we might need to take into account in order > to be able to go this way - I mean that only one AI image can be > associated with particular service, so that the location of schema > can be determined when manifest is being added to given install service. >
I think that's already mostly true today --that one install image is associated to an install service at any time, we'd used that install image. There maybe individual clients that have been specifically added to use this service, but pointed to some other install image. I don't think there's much we can do about this case because the client could have been added after the manifest has been added. With manifest versioning, we'd at least get a sensible error during client boot time for these cases. Swapping out an install image from an installer service after manifests have been added would fall under this same category. The manifest version check at client boot time should be good enough here, I'd think. thanks, -ethan > > Thank you, > Jan >
