<content_template/> is used for replacement of <content/> on some <block_device/>.
There are three types of content templates:
filesystem
mapper source
none
Content is replaced, by some other content, by moving <content_template/> from <available_contents/> to <new_content/> of <content/>. It is module's responsibility to populate <available_contents/> with appropriate content_templates.
Content Template XML description:
<content_template type="content type" ... other content identifying attributes ...> <properties/>
</content>
Every <content_template/> has a “type”. Type can be one of:
“filesystem” - in which case “fs_type” attribute will be present. Currently supported filesystem types are: “swap”, “extended_fs” and “gfs”
“mapper_source” - in which case “mapper_type” attribute will be present. They define <mapper/> whose source this content is going to be.
“none” - meaning that current content will be destroyed.
<properties/> tag, which has
variables for children. Properties may
be different that properties of <content/> of the same type.
Some properties can be mutable.
Contents have different set
of properties defined.
Example of properties for Swap
Filesystem:
<properties>
<var mutable="true" name="fstab" type="boolean" value="true"/> <var mutable="true" name="swapon" type="boolean" value="true"/> <var illegal_chars="| \ /?.," max_length="16" min_length="0" mutable="true" name="label" reserved_words="" type="string" value=""/>
</properties>