So here are my comments (I hope to not have any more)
In software spec schema,
software type - p5p should be included.
Target Schema:
Capturing the discussions here.
target_device - partition, slice and iscsi all need to collapsed
under disk.
While I am aware that multipool support currently does have support for
zpool logs or cache, I would like to understand how will this be
supported in the schema.
swap - zvol* so that one can have one or more zvols
should dump be (size|zvol) ?
-Sanjay
On 07/ 9/10 11:50 AM, Sarah Jelinek wrote:
On 07/ 9/10 10:43 AM, sanjay nadkarni wrote:
Thanks updating. I will take look again but was iSCSI also moved
under disk ?
Not yet. I haven't pushed those changes yet. I am waiting until all
comments are in before pushing the final changes. It will be moved
however,
sarah
*****
-Sanjay
On 07/ 9/10 02:47 AM, Matt Keenan wrote:
On 07/ 8/10 05:20 PM, Sarah Jelinek wrote:
On 07/ 8/10 07:39 AM, Matt Keenan wrote:
Sarah,
Quick comment, just looking at the target.dtd and the definition
for swap and dump.
Swap is defined with attribute "no_swap", if true do not create
swap. dump is also optional on an installed system, so should it
not also have a "no_swap" attribute.
Well.. I didn't make dump optional because some argue dump should
never be optional. Should we really allow users to not create a
dump device?
In the current implementation both dump and swap are optional, the
default of course is to create them, but if a size of "0" is
specified for either they will not be created.
Refer to the following discussion that took place on zfs-discuss WRT
size of swap and dump.
http://opensolaris.org/jive/message.jspa?messageID=254245
There are cases where Dump may not be required, agreed these could
be seen as corner cases but it's still allowable, therefore I think
the schema should allow for it aswell. But as I said the default
would remain in that dump is created.
cheers
Matt
cheers
Matt
On 07/ 3/10 12:12 AM, 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
_______________________________________________
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
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
