On 08/ 3/10 01:37 PM, Andrew Gracey wrote:
Hi,

We have attached the first draft of the design document here
<http://hub.opensolaris.org/bin/view/Project+caiman/Network+Text+Installer>.
We would like feedback by August 10th.


Good start, some comments and questions. General comment is that it's helpful in commenting to have sections (and pages) numbered. Less of an issue in short documents, but still would be nice.

Purpose, last sentence: AI allows for setting up each install with unique configuration, the issue you're solving here is interactive configuration of a network-booted installation.

Requirements: #5 says that installadm is to be updated, but the Use Cases indicate no changes to installadm.

Solution, Server:
- Please be specific about the name of the finalizer script that is being modified
- Specifics about the package list would be useful to record
- Why does installadm need to manipulate the GRUB menu for interactive choices? Shouldn't these be included in the menu by the construction process? But, see later comment on client use case section.

Solution, Client:
- the "OK prompt" is properly known as the OBP (OpenBoot PROM) firmware
- AI and text installer are not "SMF scripts" but perhaps "executed by SMF services" - Can you elaborate on why we need to download a second copy of the boot archive? Is there not a relatively straightforward solution to this that wouldn't involve the extra tens of MB of re-transfer? - Why is modifying the text installer preferable to creating symlinks to needed files? - There isn't a better way to communicate to the GRUB menu ICT than deleting one of the files, which are generally assumed to be persistent by the existing design?

Use Cases:
In general, use cases should be much more specific about the goal or task, the inputs from the user, and the resulting actions. The Examples in http://hub.opensolaris.org/bin/view/Project+caiman/AI+Image+Management are closer to what we'd consider real use cases.

Use Cases, Client: Have you considered another alternative, which is that when the default menu item in GRUB is selected, or the default mode from SPARC when "boot net:dhcp" (no "- install") is used, the existing text-mode-menu is brought up? Is there an advantage to the approach proposed?

Dave

_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to