On 01/18/11 01:07 PM, Alok Aggarwal wrote:
Hi Dermot,
On Tue, 18 Jan 2011, Dermot McCluskey wrote:
The app/target controller decides whether the reported errors are
"soft" (interim state change is okay) or "hard" (interim state is
a hard failure). After the app/target controller has made all the
necessary changes to Target.DESIRED, it calls
ti.final_validation() which validates Target.DESIRED completely
and stores any errors thus found in the error service.
I assumed that final_validation() would be a method of the Target
class, not the ti library? Am I incorrect?
Correct.
That's a bit ambiguous ;) : Are you saying Correct, that I'm incorrect,
or Correct that final_validation() is a method of Target?
final_validation() is a method of Target, not TI.
[1] Target.DESIRED needs to reflect the state of the targets
in the DOC as they should be laid out by TI. So, if
Right. I think we need a precise definition of what layouts are
acceptable to TI, which I think are a subset of the possible layouts
supported by the DTD. For example, and using XML notation,
*before* the proposed "device referencing" changes to the schema
are enacted, I think your example code below would result in
something like the following objects in the DOC.
Okay, what would help in clarifying what's allowed and what's not.
Sample XMLs or something else?
Yes, absolutely. I would like to see examples of what
TI expects to find in the "desired targets" section of the DOC.
Okay, we'll have something for you as soon as the schema
is agreed upon.
Sorry, I won't be able to answer that, my brain has
already switched over to the new format :) Want to
retry it with new format?
Well - we don't have an agreed new DTD yet ;) but I'll give it a go.
Will TI work (in future) if it finds this in "desired targets"?
<!-- start -->
<target name="desired targets">
<disk>
<disk_name name="c0t0d0" type="ctd" zpool="mypool"/>
<partition action="use-existing" part_type="191"/>
<partition name="1" action="create" part_type="primary">
<slice action="preserve" name="1"/>
<slice action="preserve" name="2"/>
<size val="..."/>
</partition>
</disk>
<logical>
<zpool name="mypool" action="create" is_root="True">
<dataset>
<filesystem name="mypool/user1" action="create">
</dataset>
</zpool>
</logical>
</target>
<!-- end -->
Yes, it will. Am I missing a subtlety that you're trying
to point out here?
My question with this manifest is what would you expect it to do? Does
it use the whole disk for the zpool? If so, zpool <disk> will do a whole
disk partition so why are you specifying partition and slice info for
the disk?
Jean
Alok
_______________________________________________
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
