Ethan, Thanks for the review.
Ethan Quach wrote: > Sundar, > > 1.2 Use cases > > #6 - Can you elaborate a bit on how you see this use case as > being related to system configuration? No. It is not related to system configuration. The process of upgrading to the correct zpool version is similar to the system configuration setup and it is run on the first reboot after installation. Evan suggested this use case. > > #7 - If this use case falls outside the installer, why are we > mentioning it here? The process is similar to use case 2 and I want to capture that use case. > > > 1.3 - Are you defining these as the "minimum" set of system > configuration parameters that's expected to have been gathered, > one way or another, during the installation process? If so, I > don't think the networking parameters should really be on this > list. We have nwam for this don't we? These are minimum parameters needed for a useful system after installation. The user provided these parameters in the profile. We need support for setting up these parameters in the SMF. For example, the user could specify static IP for the system. > > "Language is required to allow the user to choose the > language to be used on the installed system." > > nit - This statement could probably be stated in a less cyclical > way. okay. I will change it to "The user should be allowed to choose the language to be used on the installed system." > > > 2.0 > > General comment - although its not explicitly mentioned, these > requirements, as stated, sound like you pretty much already have > in mind that smf enhanced profiles is the mechanism you're > looking for to fulfill them; for example #3. If that is the case, > can we explicitly state that somewhere, so that it's clear? > Otherwise these statements need to be much more generic. The requirements were derived with enhanced SMF profiles in mind. I will add a note there. Since it includes visual panels, it doesn't make sense to make it as a Enhanced SMF profiles requirements. > > #2 - Last sentence. Why is this a requirement for us? This is for providing feedback to the user before reboot. > > #4 - "the boot" -> "first boot" okay. > > > One more requirement we've mentioned is that the installer > needs to present this interface to the user in a scalable way. > The example given is the case where we've got an environment > with thousands of systems with static IP addresses. Requiring > the user to maintain a separate SC manifest for each of those > systems is not very user friendly. Agreed. Some of the per machine configuration like IP address can be gathered from the environment (from the booted IP address) and name service. There will be a follow-on project to deal with the install side specifications for system configuration setup. We can defer that scalability aspect to that project. Thanks, Sundar > > > thanks, > -ethan > > > Sundar Yamunachari wrote: >> Hi, >> >> The requirements for setting up system configuration is posted at >> http://www.opensolaris.org/os/project/caiman/auto_install/ai_design/system_configuration_parameter_requirements.pdf. >> >> Please review the document and provide your feedback before next >> Wednesday (06/10/09). >> >> Thanks, >> Sundar >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
