Guys,
Thanks for the answer, and thank you Ethan for pointing out the order,
and the zfs properties 'native' and 'user-defined' !
I try to create a web form for the manifests, dumping it in a hash, edit
and write it out again. The hash is normally written to xml, with the
elements all sorted alphabetically.
I'll probably have to write a new XSLT file to get the xml output with
the right order. No problem.
Paul
On 12/15/11 01:45 PM, Ethan Quach wrote:
I think commas dictate strict order though, so the <be> sub-element
being first in his xml snippet will cause a syntactic failure
unfortunately.
Also, there's a semantic issue, see below ...
On 12/15/11 11:32, Drew Fisher wrote:
Paul,
The DTD definition for the <zpool> element looks like this:
<!ELEMENT zpool (vdev*, filesystem*, zvol*, pool_options?,
dataset_options?, be?)>
The "*" means 0 or more (as many as you want)
The "?" means 0 or 1
Your manifest below looks just fine.
-Drew
On 12/15/11 11:48 AM, Paul de Nijs wrote:
All,
for the <logical><zpool>.... </zpool></logical> part in the
ai_manifest, I assume that the elements for zpool can only have:
pool_options AND dataset_options elements
OR
vdev elements
OR
filesystem elements
OR
zvol elements
OR
be element (only one)
Is this correct ?
or can you have something crazy like:
<logical nodump="false" noswap="false">
<zpool name="myrpool" is_root="true" mountpoint="/path/to/mountpoint">
<be name="solaris11">
<options>
<option name="compression" value="on" />
<option name="dedup" value="on" />
</options>
</be>
<filesystem name="/export/home" action="create"
mountpoint="/export/home" />
<zvol name="swap" action="create" use="swap">
<options>
<option name="blabla" value="on" />
<option name="qqqqq" value="off" />
I believe this will cause failure at runtime. These options will get
treated as zfs properties that the installer will attempt to set on
the dataset when it creates it. Zfs properties can be "native" or
"user defined". Those names obviously aren't native properties, and
user defined properties must have a ":" in them. See zfs(1M).
-ethan
</options>
<size val="700mb" />
</zvol>
<zvol name="dump" action="create" use="dump">
<size val="700mb" />
</zvol>
</zpool>
</logical>
Thanks
Paul
--
Paul de Nijs | Principal Software Engineer | Performance
Technologies | +1.503.495.7882
Oracle Strategic Applications Engineering (SAE)
3295 NW 211th Terrace | Hillsboro, OR 97124-7110
_______________________________________________
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
--
Paul de Nijs | Principal Software Engineer | Performance Technologies |
+1.503.495.7882
Oracle Strategic Applications Engineering (SAE)
3295 NW 211th Terrace | Hillsboro, OR 97124-7110
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
