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).
>
General comment: please clean up verb tenses and add appropriate
articles ("the"). This is somewhat difficult to read as-is, and as it's
primarily a document for communication to other teams of requirements,
it needs to be cleaner to be handed off to them.
1.0, second paragraph: Perhaps preface this with "In developing the
OpenSolaris installation architecture, the following principle is being
followed:".
1.0, third paragraph: It isn't at all obvious why a compelling
experience requires configuration during the first boot after
installation...
1.1: s/which/that/ s/produce/produces/
1.2, case 6: This could use some explanation of why this case is
expected to work, and what the differences are vs. an update from an
older release.
1.2 case 7: This use case doesn't appear to translate into any
requirements in section 2. It's also not completely clear how it
differs from case 2.
1.3 This section seems to be focused entirely on minimizing the set,
but doesn't seem to discuss any extensibility, either for different
OpenSolaris-based products or for future releases. For example, what if
we want to ship OpenSolaris pre-installed on a netbook that has only a
3G-cellular networking interface? Similarly, there appears to be an
eagerness to dispense with an initial user account and focus only on the
root account, whereas our best practices suggest making root a role and
defining administrative user accounts. As such, it seems this set of
parameters can't even reproduce the existing OpenSolaris installation;
are we asserting a change in direction here? Finally, some discussion
with the networking team on whether we should be setting up default
routers or instead/in addition configuring a routing protocol client
seems worth having; I'm not aware such a discussion has occurred?
Finally, a nit, but "DNS" here should be "DNS resolver" since it's the
client that's required, not the server.
2.0, requirement 2: What's the "server" here? I am assuming this means
"automated installation server", but that's overly specific, I think.
2.0 requirement 3: I'm not sure what a "property on the file" is here.
I presume the requirement here is that the mechanism make a best effort
at configuration, applying anything which can be, rather than failing
immediately on any error and not configuring other attributes which may
be correct.
2.0: Reiterating prior comments, there's nothing here about
extensibility, nor that would obviously satisfy case 7.
Dave
