1 <?xml version="1.0"?> |
|
2 <!-- |
|
3 CDDL HEADER START |
|
4 |
|
5 The contents of this file are subject to the terms of the |
|
6 Common Development and Distribution License (the "License"). |
|
7 You may not use this file except in compliance with the License. |
|
8 |
|
9 You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE |
|
10 or http://www.opensolaris.org/os/licensing. |
|
11 See the License for the specific language governing permissions |
|
12 and limitations under the License. |
|
13 |
|
14 When distributing Covered Code, include this CDDL HEADER in each |
|
15 file and include the License file at usr/src/OPENSOLARIS.LICENSE. |
|
16 If applicable, add the following below this CDDL HEADER, with the |
|
17 fields enclosed by brackets "[]" replaced with your own identifying |
|
18 information: Portions Copyright [yyyy] [name of copyright owner] |
|
19 |
|
20 CDDL HEADER END |
|
21 |
|
22 Copyright (c) 2008, 2011, Oracle and/or its affiliates. All rights reserved. |
|
23 --> |
|
24 <!-- |
|
25 =============================================================================== |
|
26 DTD sample manifest for Automatic Installer input manifest specification. |
|
27 =============================================================================== |
|
28 --> |
|
29 <!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd"> |
|
30 <auto_install> |
|
31 <!-- |
|
32 "auto_reboot" set to "true" may be an issue for x86 machines. |
|
33 The boot order is not guaranteed and may cause unexpected |
|
34 behavior. If auto_reboot is not desired, set auto_reboot="false". |
|
35 |
|
36 The name of the manifest is obtained from (in this order): |
|
37 1) the name from the installadm add-manifest command line "-m" option. |
|
38 2) a name attribute in the manifest, e.g.: |
|
39 <ai_instance name="my_ai_manifest" auto_reboot="true"> |
|
40 3) manifest filename |
|
41 --> |
|
42 <ai_instance auto_reboot="true"> |
|
43 <!-- |
|
44 ======================================================================= |
|
45 <target> - selections for AI target Device specification |
|
46 |
|
47 Disk criteria are divided into three mutually exclusive groups: |
|
48 |
|
49 G1 - deterministic disk criteria |
|
50 ................................ |
|
51 * disk/iscsi parameters |
|
52 * disk/disk_name, with name_type attribute: |
|
53 one of ctd, volid, devpath or devid |
|
54 |
|
55 G2 - non-deterministic disk criteria |
|
56 .......................... |
|
57 * disk/disk_prop: Any of dev_type, dev_vendor or |
|
58 dev_size |
|
59 |
|
60 G3 - keyword disk criteria |
|
61 ........................... |
|
62 * disk/disk_keyword: "boot_disk" |
|
63 |
|
64 Schema ai.dtd enforces following policy: |
|
65 |
|
66 * criteria in group G1 are mutually exclusive - only |
|
67 one can be specified at a time |
|
68 |
|
69 * groups G1, G2 and G3 are mutually exclusive - i.e. |
|
70 if criteria from G1 is specified, no criteria |
|
71 from G2 or G3 are allowed and vice versa |
|
72 |
|
73 * multiple criteria from G2 can be specified |
|
74 ======================================================================= |
|
75 --> |
|
76 <target> |
|
77 <disk> |
|
78 <!-- G1 --> |
|
79 <!-- |
|
80 c#t#d# device name like c0t0d0 or |
|
81 MPXIO name like c0t2000002037CD9F72d0 |
|
82 --> |
|
83 <disk_name name="c1t0d0" name_type="ctd"/> |
|
84 <!-- volume name set for instance by means |
|
85 of format(1M) command |
|
86 --> |
|
87 <!-- |
|
88 <disk_name name="ai-disk" name_type="volid"/> |
|
89 --> |
|
90 <!-- device id - e.g. can be obtained by means of |
|
91 iostat(1M) -iEn |
|
92 --> |
|
93 <!-- |
|
94 <disk_name name="id1,cmdk@AST31000340NS=____________9QJ2LNYY" name_type="devid"/> |
|
95 --> |
|
96 <!-- device path under /devices directory, e.g. |
|
97 /pci@1e,600000/pci@0/pci@9/pci@0/scsi@1/sd@0,0 |
|
98 --> |
|
99 <!-- |
|
100 <disk_name name="/pci@0/pci@9/pci@0/scsi@1/sd@0,0" name_type="devpath"/> |
|
101 --> |
|
102 <!-- |
|
103 ISCSI target device |
|
104 |
|
105 <iscsi name="c0d2E0001010F68"> |
|
106 <ip>192.168.1.34</ip> |
|
107 </iscsi> |
|
108 --> |
|
109 <!-- G2 --> |
|
110 <!-- |
|
111 <disk_prop dev_vendor="hitachi" dev_size="20480mb"/> |
|
112 |
|
113 or |
|
114 |
|
115 <disk_prop dev_vendor="hitachi"/> |
|
116 |
|
117 or |
|
118 |
|
119 <disk_prop dev_size="20480mb"/> |
|
120 --> |
|
121 <!-- G3 --> |
|
122 <!-- |
|
123 <disk_keyword key="boot_disk"/> |
|
124 --> |
|
125 <!-- |
|
126 On X86 machines, Slices exist within partitions only |
|
127 --> |
|
128 <!-- |
|
129 Uncomment this to force AI to find an existing Solaris |
|
130 partition. |
|
131 --> |
|
132 <!-- |
|
133 <partition action="use_existing_solaris2"> |
|
134 <slice name="0"> |
|
135 <size val="20480mb"/> |
|
136 </slice> |
|
137 <slice name="4"> |
|
138 <size val="20480mb"/> |
|
139 </slice> |
|
140 </partition> |
|
141 |
|
142 or, use the following to create a Solaris partition |
|
143 --> |
|
144 <partition name="1" part_type="191"> |
|
145 <size start_sector="200" val="40960mb"/> |
|
146 <slice name="0"> |
|
147 <size val="20480mb"/> |
|
148 </slice> |
|
149 <slice name="4"> |
|
150 <size val="20480mb"/> |
|
151 </slice> |
|
152 </partition> |
|
153 <!-- Define some other partitions to create too --> |
|
154 <partition name="2" part_type="99"> |
|
155 <size start_sector="200" val="20480mb"/> |
|
156 </partition> |
|
157 <partition name="4" part_type="99"> |
|
158 <size start_sector="2000" val="20480mb"/> |
|
159 </partition> |
|
160 <!-- |
|
161 On SPARC systems, only specify the Slice layout. |
|
162 --> |
|
163 <!-- |
|
164 <slice name="0"> |
|
165 <size val="20480mb"/> |
|
166 </slice> |
|
167 <slice name="4"> |
|
168 <size val="20480mb"/> |
|
169 </slice> |
|
170 --> |
|
171 </disk> |
|
172 </target> |
|
173 <software name="ips" type="IPS"> |
|
174 <source> |
|
175 <publisher name="solaris"> |
|
176 <origin name="http://pkg.oracle.com/solaris/release"/> |
|
177 </publisher> |
|
178 </source> |
|
179 <!-- |
|
180 By default the latest build available, in the |
|
181 specified IPS repository, is installed. |
|
182 if another build is required, the build number has |
|
183 to be appended to the 'entire' package in following |
|
184 form: |
|
185 <name="[email protected]#"/> |
|
186 --> |
|
187 <software_data> |
|
188 <name>pkg:/entire</name> |
|
189 <name>pkg:/server_install</name> |
|
190 </software_data> |
|
191 </software> |
|
192 <add_drivers> |
|
193 <!-- |
|
194 Driver Updates: This section is for adding driver packages to the |
|
195 boot environment before the installation takes place. The |
|
196 installer can then access all devices on the system. The |
|
197 packages installed in the boot environment will also be installed |
|
198 on the target. |
|
199 |
|
200 A <search_all> entry performs a search for devices which are |
|
201 missing their drivers. A repository publisher and location |
|
202 may be specified, and that repository and its database will |
|
203 be used. If no publisher and location is specified, the |
|
204 configured repositories will be used. |
|
205 (See pkg publisher command.) If <addall> is specified as |
|
206 "true", then drivers the database says are third-party drivers |
|
207 will be added like all others; otherwise third-party drivers |
|
208 will not be added. |
|
209 |
|
210 <search_all addall="true"> |
|
211 <source> |
|
212 <publisher name="solaris"> |
|
213 <origin name="http://pkg.oracle.com/solaris/release"/> |
|
214 </publisher> |
|
215 </source> |
|
216 </search_all> |
|
217 |
|
218 <software> entries are user-provided specifications of packages |
|
219 needed in order to perform the install. types are P5I, SVR4, DU. |
|
220 A <software_data> action of "noinstall" inhibits adding to target. |
|
221 |
|
222 P5I: A pkg(5) P5I file, full path is in the source/publisher/origin. |
|
223 Path may be to a local file or an http or ftp specification. |
|
224 <software> |
|
225 <source> |
|
226 <publisher> |
|
227 <origin |
|
228 name= |
|
229 "http://pkg.oracle.com/solaris/release/p5i/0/driver/firewire.p5i"/> |
|
230 </publisher> |
|
231 </source> |
|
232 <software_data type="P5I"/> |
|
233 </software> |
|
234 |
|
235 SVR4: An SVR4 package spec. The source/publisher/origin corresponds |
|
236 to the directory containing the packages. The |
|
237 software/software_data/name refers tp the package's top level |
|
238 directory or the package's datastream file. |
|
239 |
|
240 <software> |
|
241 <source> |
|
242 <publisher> |
|
243 <origin name="/export/package_dir"/> |
|
244 </publisher> |
|
245 </source> |
|
246 <software_data type="SVR4"> |
|
247 <name>my_disk_driver.d</name> |
|
248 </software_data> |
|
249 </software> |
|
250 |
|
251 DU: An ITU (Install Time Update) or Driver Update image. |
|
252 The source/publisher/origin refers to the path just above the |
|
253 image's DU directory (if expanded) or the name of the .iso image. |
|
254 All packages in the image will be added. |
|
255 |
|
256 <software> |
|
257 <source> |
|
258 <publisher> |
|
259 <origin name="/export/duimages/mydriver.iso"/> |
|
260 </publisher> |
|
261 </source> |
|
262 <software_data type="DU"/> |
|
263 </software> |
|
264 --> |
|
265 <search_all/> |
|
266 </add_drivers> |
|
267 </ai_instance> |
|
268 </auto_install> |
|