blob: 1fcf82c27f2ea2a8ae14cccf02b37227e98655f3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
|
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:py="http://genshi.edgewall.org/" xml:lang="en">
<xsd:annotation>
<xsd:documentation>
bundle schema for bcfg2
Narayan Desai, Argonne National Laboratory
</xsd:documentation>
</xsd:annotation>
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="xml.xsd"/>
<xsd:import namespace="http://genshi.edgewall.org/"
schemaLocation="genshi.xsd"/>
<xsd:include schemaLocation="atom.xsd"/>
<xsd:include schemaLocation="pathentry.xsd"/>
<xsd:include schemaLocation="rules.xsd"/>
<xsd:include schemaLocation="types.xsd"/>
<xsd:include schemaLocation="servicetype.xsd"/>
<xsd:group name="bundleElements">
<xsd:choice>
<xsd:group ref="py:genshiElements"/>
<xsd:element name='Package' type='PackageStructure'>
<xsd:annotation>
<xsd:documentation>
Abstract implementation of a Package entry. The full
specification will be generated by a plugin such as
Packages.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='Path' type='PathEntry'>
<xsd:annotation>
<xsd:documentation>
Abstract implementation of a Path entry. The entry will
either be handled by Cfg, TGenshi, or another
Generator plugin; or handled by Rules, in which case
the full specification of this entry will be included in
Rules.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='Service' type='StructureEntry'>
<xsd:annotation>
<xsd:documentation>
Abstract implementation of a Service entry. The full
specification will be included in Rules.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='Action' type='StructureEntry'>
<xsd:annotation>
<xsd:documentation>
Abstract implementation of an Action entry. The full
specification will be included in Rules.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='SELinux' type='SELinuxStructure'>
<xsd:annotation>
<xsd:documentation>
Abstract implementation of an SELinux entry. The
full specification will be included in Rules.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='POSIXUser' type='StructureEntry'>
<xsd:annotation>
<xsd:documentation>
Abstract description of a POSIXUser entry.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='POSIXGroup' type='StructureEntry'>
<xsd:annotation>
<xsd:documentation>
Abstract description of a POSIXGroup entry.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='PostInstall' type='StructureEntry'>
<xsd:annotation>
<xsd:documentation>
PostInstall entries are deprecated in favor of Action
entries. Actions can do everything PostInstall entries can
do and more.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='BoundPackage' type='PackageType'>
<xsd:annotation>
<xsd:documentation>
Fully bound description of a software package to be managed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='BoundPath' type='PathType'>
<xsd:annotation>
<xsd:documentation>
Fully bound description of a filesystem path to be handled
by the POSIX driver.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='BoundService' type='ServiceType'>
<xsd:annotation>
<xsd:documentation>
Fully bound description of a system service to be managed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='BoundAction' type='ActionType'>
<xsd:annotation>
<xsd:documentation>
Fully bound description of a command to be run.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='BoundSELinux' type='SELinuxType'>
<xsd:annotation>
<xsd:documentation>
Fully bound description of an SELinux entry.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='BoundPOSIXUser' type='POSIXUserType'>
<xsd:annotation>
<xsd:documentation>
Fully bound description of a POSIXUser entry.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='BoundPOSIXGroup' type='POSIXGroupType'>
<xsd:annotation>
<xsd:documentation>
Fully bound description of a POSIXGroup entry.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='Group' type='GroupType'>
<xsd:annotation>
<xsd:documentation>
Elements within Group tags only apply to clients that are
members of that group (or vice-versa; see #element_negate
below)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='Client' type='GroupType'>
<xsd:annotation>
<xsd:documentation>
Elements within Client tags only apply to the named client
(or vice-versa; see #element_negate below)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name='Bundle' type='BundleType'>
<xsd:annotation>
<xsd:documentation>
Nesting Bundle tags is allowed in order to support
XInclude within Bundles.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:group>
<xsd:complexType name='GroupType'>
<xsd:choice minOccurs='0' maxOccurs='unbounded'>
<xsd:group ref="bundleElements"/>
</xsd:choice>
<xsd:attribute type='xsd:string' name='name' use='required'>
<xsd:annotation>
<xsd:documentation>The group name</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute type='xsd:string' name='negate'>
<xsd:annotation>
<xsd:documentation>
Negate the sense of this group; i.e., entries within this
tag are only used on clients that are not members of the
group
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attributeGroup ref="py:genshiAttrs"/>
</xsd:complexType>
<xsd:complexType name='BundleType'>
<xsd:choice minOccurs='0' maxOccurs='unbounded'>
<xsd:group ref="bundleElements"/>
</xsd:choice>
<xsd:attribute type='xsd:string' name='description' />
<xsd:attribute type='xsd:string' name='name'/>
<xsd:attribute type='xsd:string' name='version'/>
<xsd:attribute type='xsd:string' name='origin'/>
<xsd:attribute type='xsd:string' name='revision'/>
<xsd:attributeGroup ref="py:genshiAttrs"/>
<xsd:attribute ref="xml:base"/>
</xsd:complexType>
<xsd:element name='Bundle' type='BundleType'>
<xsd:annotation>
<xsd:documentation>
A bundle describes a group of inter-dependent configuration
entries, such as the combination of packages, configuration
files, and service activations that comprise typical Unix
daemons. Bundles are used to add groups of configuration
entries to the inventory of client configurations, as opposed
to describing particular versions of those entries. For
example, a bundle could say that the configuration file
``/etc/passwd`` should be included in a configuration, but
will not describe the particular version of ``/etc/passwd``
that a given client will receive.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:schema>
|
