Hi Sarah,
A few things that still need to be changed -
a) GRUB menu customization section from dc_spec.
I do realize that GRUB2 is going to change
some things in this area but still we need a
way to specify custom grub menu entries.
b) iso sort file specification from the dc_spec
c) dc_instance should have an additional attribute
along the lines of "incremental_media(true|false)"
to support fixing defect 6794
d) Are primary_source/secondary_source in the dc_spec
the equivalent of the current post_install_repo_default_authority
and addl_authority?
If so, I think it would be better to abstract
these out as a software_spec section. The reason
for this is - DC is going to leverage the transfer
module to set the ips attributes. So, even if it
is specified in the dc_spec section, DC internally
will have to instantiate the appropriate Transfer
class, retrieve the ips attributes from the dc_spec
section and set them in the Transfer object.
Seems like it woul be just be simpler to abstract them
out as a software_spec action.
e) Where do IPS attributes such as, say, generate_ips_search_index,
get specified in the DC manifest?
f) I don't believe the VM creation needs stuff like compression,
boot_archive and max_size attributes in the vm_img section.
The entire vmc manifest is a fairly stripped down version of
the current DC manifest - just has a target section and a
finalizer/execution section.
Thanks,
Alok
On Fri, 2 Jul 2010, Sarah Jelinek wrote:
Hi All,
I updated the AI/DC schemas and the design document to reflect the comments
received in the initial design review. If you want to see the specific
changes, please use the .odt file and set the show changes and you will see
the edits.
The areas I modified were:
-Target dtd. This is based on feedback plus discussions about the use cases
for AI. You will see a high level disk object now, that encapsulates the
partitions, slices or other parts. The new AI schema supports mutliple disks
and pools. And, the associated components.
-Execution dtd. We are no longer embedded software in the checkpoint
elements. The software spec now has a name which much match the checkpoint
name to differentiate different software data for multiple transfer
checkpoints.
-Software spec dtd. This now has elements and attributes for facets, and
better publisher/origin definition.
-I removed the extraneous definitions that were in text for each of the
schemas. The schemas themselves should be sufficient.
-I added the dtd's as well as example instance documents to the gate for
reference.
Please review and send comments. I would like to close this out by COB
7/9/10.
Thank you,
sarah
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
