Hi, Alok,
Please see my comments inline:
Alok Aggarwal ??:
> Here is what I'm thinking of implementing in the AI engine
> as far as dry run functionality goes -
>
Can we have the step that getting manifest, I think it is just a call to:
/usr/bin/ai_get_manifest
With this step, we can test the criteria manifest that get various manifests
from server.
> - Parse and validate the manifest obtained from the AI
> webserver
> - Set up installation parameters based on the information
> in the manifest
> - Initiate target discovery to either select a target
> device specified in the manifest or pick a default target
> - Initiate target instantiation in dry run mode to do
> some sanity checking
Only checking or can we do actually target instantiation?
If not physically create partition or slice, maybe these features can
not be
verified.
Other checkings can includes:
- if mirror zfs root pool can be done
- if the given size swap can be created
> - Print out the installation parameters such as target
> device, IPS repo name/port, list of packages to be
> installed
>
Better also include partition and slice infos.
> Note that the IPS repo won't be contacted as part of this
> process so if there are problems with name resolution, etc.
> the dry run won't catch those.
>
Better also have following checkings:
- set the given keyboard
- set timezone
- create given user account
> Would this be sufficient for test purposes?
>
> Alok
--
Great Thanks & Best Regards
---
Jeffrey Huang SWAN: x51683, Ext: 0086-10-62673683
Solaris QE Group Email: jeffrey.huang at sun.com
China Engineering & Research Institute, Sun Microsystems
7/F Chuang Xin Plaza, Tsinghua Science Park, Beijing China
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20081220/8215dc61/attachment.html>
