Sundar Yamunachari ??:
> Hi,
>
> I sent out a list of tasks to be considered for the AI spring release
> in December 2009. Based on the feedback and priority of the tasks, we
> are planning to do the top six or seven tasks for the next release.
> The design document for the AI spring release is at
> http://www.opensolaris.org/os/project/caiman/auto_install/Design_doc_delta_for_AI_Spring_2009.pdf.
>
> This can be also accessed
Hi, Sundar,
I'd like also to give my ideas and thinks to AI manifest designs, hope
it can do some help, thanks.
General:
I feel the new design is getting more complicated for manifest settings.
AI's goal is simplification, but my feelings are: Even as QE of AI, it
still took me quite some time to understand the relationship of AI
manifest, criteria manifest and SC manifest, and then how make them work
together.
Now for the new design, we have:
- installadm set-criteria/clear-criteria (1.4.2)
- installadm add-manifest/remove-manifest (1.4.3)
If add-manifest/remove-manifest is still based criteria, probably these
2 are functioning roughly the same.
In new design we have both generic default manifest and specific default
manifest, needs to make them more clear in user document.
Others:
Section 1.4.1 Restructure criteria
Does that mean the:
<optional>
...
</optional> section will be ignored,
If yes, then seems it is functioning the same as 1.4.4 service default
manifest.
Section 1.4.3 Exporting manifests
installadm add-manifest [-d] -n <svcname> -m <manifest_name>
installadm remove-manifest -n <svcname> -m <manifest_name>
In the 2009.11 preview, 'add-manifest' command actually needs to pass in
criteria file name, while 'remove-manifest' passing in AI manifest name,
better make them consistent in next release.
Section 1.4.4 Default manifest
So after set/add-manifest default manifest, does the service has to restart
to make it effective?
Section 1.6 Format of ethernet address
I understand that we need to test both formats.
Section 2.1
Target device
target_device_install_slice_number also repeat the function of "create" in
<ai_device_vtoc_slices>, and easy to cause conflict, for example if
writing a manifest that install to slice 0 while creating slice 1.
target_deivce_size: seems the explanation should be size of disk, not
partition. And the default better be GB, hard for people to covert disk
size from GB to MB.
Delete Partition
for partition deleting, even start_sector and size is optional, seems
they are still not necessary.
--
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
