Joseph J VLcek wrote: > Sundar Yamunachari wrote: >> Hi, >> >> Ethan Quach and Sundar Yamunachari of the OpenSolaris installation >> team met with Liane Praza of the SMF team to discuss install >> requirements for SMF enhanced profiles. The meeting summary is posted >> at >> http://www.opensolaris.org/os/project/caiman/auto_install/ai_design/smf_enhanced_profiles_meeting.txt >>
(haven't reviewed yet. sorry.) > I think #4 of the installation team needs could be misconstrued. > > > 4. Need a mechanism to validate the user supplied profile. The syntax > validation can be done on the server. We are more interested in finding > out whether the service specified in the profile is available and the > parameters are settable. > > > I think we need to make it clearer that we are asking for 2 things: > 1- Confirm syntax Sure. No problem. (It's largely xml validation.) > 2- Prior to a reboot report which, if any, of the specified > configuration parameters can not be acted upon. Profiles today do not error when they contain configuration for services which don't exist on the system. They won't in the future either. Any more validation would require knowledge of the services which will be installed, along with the explicit version of each of those on the system, and a system to run the validation on which had all of these installed. As I understand it, all of these things are non-starters in the current AI design. So, I'd expect the fact that a syntacticly correct manifest won't fail to be applied is really what you need. > I have discussed this next issue with Ethan and Sundar but Sundar asked > to to capture it in an email: > > Need a mechanism to perform SMF configuration on an alternate root. Please be more specific about the need. IPS is moving us in a direction where configuration changes are made during the next boot, not directly on an alternate root. I'm hoping AI isn't asking the product to move back in the opposite direction. liane
