import repository from arizona
[raven.git] / webpage / storkasyum.html
1 <html>
2 <head>
3 <title> Stork Project </title>
4 <LINK href="stork.css" rel="stylesheet" type="text/css">
5
6
7 <style type="text/css">
8 dt {
9     font-weight: bold;
10     font-family: monospace;
11 </style>
12
13
14 </head>
15
16
17 <body>
18
19
20
21
22 <div class="display" align="center">
23         <table border="0">
24         <tr>
25                 <td width="170" valign="top">
26
27
28                                 <br/>
29                                 <table cellpadding="3" width="170" id="links" class="links">
30                                         <tr>
31                                                 <td align="right">
32
33
34                                                         <ul class="links">
35
36
37                                                                 <a href = "index.html"><h3>Stork</h3></a>
38                                                                 <li class="links"><a href="tutmain.html">Stork Tutorial</a></li>
39
40
41                                                                 <li class="links"><a href="advanced.html">Advanced Usage</a></li>
42                                                                 <li class="links"><a href="arch.html">Stork Architecture</a></li>
43                                                                 <li class="links"><a href="filelist.html">Stork File List</a></li>
44                                                                 <li class="links"><a href="about.html">About Us</a></li>
45                                                                 <li class="links"><a href="apps.html">Related Links</a></li>
46                                                                 <li class="links"><a href="contact.html">Contact Stork</a></li>
47                                                                 <h4>Links</h4>
48                                                                 <li class="links"><a href="http://appmanager.berkeley.intel-research.net/plcontrol/apps.php?appid=1029">
49                                                                 Slice Status</a></li>
50                                                                 <li class="links"><a href="https://stork-repository.cs.arizona.edu">Stork Repository</a></li>
51                                                         </ul>
52
53
54                                                  </td>
55                                         </tr>
56                                 </table>
57                                 <br/>
58                 </td>
59
60
61                 <td valign="top">
62                 <table class="info" cellpadding="0" width="700" >
63                 <tr  height="75"><td colspan="3"><img style="margin-left: -0px;" src="images/stork-header.png" alt="stork logo"/></td></tr>
64                 <tr  bgcolor="#444444" class="headerrow" width="100%" height="2">
65
66
67                         <th colspan="2"> Using Stork </th>
68
69
70                 </tr>
71                 <tr valign="top" align="left">
72
73
74                         <td>
75                                 <table cellpadding="8" id="content" class="content">
76                                         <tr>
77                                                 <td>
78
79
80                                                         <h1><a name = "top"></a>Using Stork in place of Yum
81                             or Apt</h1>
82                                                         Although Stork includes many advanced features such
83                             as security and automated package installation,
84                             Stork also makes an excellent replacement for the
85                             command-line package installation tools such as yum
86                             and apt.
87                             <p>Stork uses a repository located at
88                             <a href="http://stork-repository.cs.arizona.edu">
89                             http://stork-repository.cs.arizona.edu</a> and this
90                             repository is already populated with Fedora Core 2
91                             and Fedora Core 4 packages for PlanetLab V3 and V4
92                             nodes respectively. Although this tutorial
93                             concentrates primarily on using these pre-provided
94                             packages, there are mechanisms for adding your own
95                             packages to the repository and we direct you to the
96                             <a href="advanced.html">Advanced Usage</a> section
97                             for more information.</p>
98 <p><img src="blkfade.gif" width="100%"></img>
99                                                         <h2>Installing Stork on your Slice</h2>
100                                                         <p>[You may skip this section if stork is already
101                             installed and running on your Slice]</p>
102                                                         <p>In order to use Stork, it must first be installed
103                             on your Slice. We are currently working with the
104                             PlanetLab developers on an automated mechanism for
105                             enabling Stork, but for the time being you will need
106                             to manually run our initscript
107                             to install the stork packages on your nodes. You will
108                             need to do this on each node of your slice that you
109                             want to run Stork.</p>
110                                                         <p>Running the initscript requires root access, so
111                             be sure to do a '<code>su root</code>' if you have not done so
112                             already. </p>
113                                                         <p><code># wget
114                             http://www.cs.arizona.edu/stork/downloads/initscript</code></p>
115                                                         <p><code># ./initscript</code></p>
116                                                         <p>The stork initscript should download the stork
117                             packages to your node and install them. It will also
118                             start up a service called PacMan that automatically
119                             keeps the current version of stork up-to-date for
120                             you.</p>
121                                                         <p>Once the initscript has completed, you may start
122                             using Stork to install Fedora 2 / 4 packages from
123                             our repository immediately. You do not need to edit
124                             any of the Stork configuration files, trusted
125                             packages files, or keys unless you wish to configure
126                             Stork to install your own custom packages. </p>
127                                                         <p><img src="blkfade.gif" width="100%"></p>
128                                                         <h2>Manually managing packages with Stork</h2>
129                                                         The stork client tool can be used to manually
130                             install, remove, and upgrade packages. It does this
131                             through a command-line interface. You must be logged
132                             in as root to use the stork client tool.<p><b>
133                             Installing Packages:</b></p>
134                             <blockquote>
135                               <p>To install a package on a node,
136                                                                                                                 use the command:
137                                                         <br><b><code># stork <i>lynx</i></code></b>
138                               </p>
139                             </blockquote>
140
141
142                                                         <p><b>Removing Packages:</b><blockquote>
143
144
145                                                         <p>To remove a package from a node, use the option:
146                                                         <br><b><code># stork --remove <i>lynx</i></code></b>
147
148
149
150
151
152
153                                                         </blockquote>
154
155
156                                                         <p><b>Upgrading Packages:</b><blockquote>
157
158
159                                                         <p>To upgrade a package from a node, use the option:
160                                                         <br><b><code># stork --upgrade <i>lynx</i></code></b></blockquote>
161
162
163                                                         <p><b>Installing specific version numbers:</b><blockquote>
164
165
166                                                         <p>To install a specific version number of a
167                               package:<br>
168                               <b><code># stork --upgrade <i>lynx=1.0.3-11</i></code></b><p>
169                               <code><b><i>You may also use &gt;, &lt;, &gt;=, &lt;=
170                               relational operators:<br>
171                               </i>#<i>
172                               </i>stork --upgrade <i>
173                               lynx</i></b></code>&lt;=1.0-3-11</blockquote>
174
175
176
177
178
179
180                                                         <p>The stork client command-line tool has many
181                             options. For a complete reference, see the
182                             <a href="storkclient.html">Stork Client reference
183                             page</a>.
184                                                         <p><img src="blkfade.gif" width="100%"></p>
185                             <h2>Notes / Frequently Asked Questions</h2>
186                             <p>This section contains information on some
187                             important differences between Stork and Yum, and
188                             some issues that you might experience.</p>
189                             <h3>How does Stork choose which package to install?</h3>
190                             <blockquote>
191                               <p>Generally there may be more than one version of
192                               a package in our repository, as our repository
193                               contains both Fedora 2 and Fedora 4 packages.
194                               Stork has an automatic rule to decide whether your
195                               node is a PlanetLab V3 or V4 node and
196                               automatically prefer the appropriate version of
197                               the Fedora packages.&nbsp; </p>
198                               <p>If you want to read more about how Stork
199                               decides which version of a package to install,
200                               then consult the <a href="advanced.html">Advanced
201                               Topics</a> page and read more about Trusted
202                               Packages Files. </p>
203                             </blockquote>
204                             <h3>Error: &quot;Another copy of stork is already
205                             running...&quot;</h3>
206                             <blockquote>
207                               <p>Stork automatically starts a service called
208                               PacMan, which is responsible for automatically
209                               installing and updating packages. By default, it
210                               only maintains the Stork packages themselves.
211                               Periodically PacMan will wake up and run. When
212                               PacMan is running, the stork command line tool
213                               will be unavailable. If you get this error
214                               message, then we suggest you wait a few minutes
215                               and try again.&nbsp; You can deactivate PacMan by
216                               executing &quot;/etc/init.d/pacman.init stop&quot;. However,
217                               we encourage you not to do so as this will prevent
218                               your Slice from receiving important Stork updates
219                               and bug fixes. </p>
220                             </blockquote>
221                             <dl>
222                               <dd>&nbsp;</dd>
223                             </dl>
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244                                                         <center><a href = "index.html">Home</a>     <a href = "#top">Top</a></center>
245
246
247
248
249                                                 </td>
250                                         </tr>
251                                 </table>
252                         </td>
253                 </tr>
254
255
256        </table>
257        </td>
258
259
260      </tr>
261      <tr>
262         <td></td>
263         <td>
264                 <a href="http://www.planet-lab.org"><img style="border: 0px; border-style: none;" src="images/powered_by_pl_grey.png" alt="powered by planetlab"></a>
265
266
267                                         <a href="http://www.cs.arizona.edu"><img style="position:relative; left: 20px; border: 0px; border-style: none;" src="images/template_logo_small_grey.png" alt="University of Arizona, Computer Science logo"></a>
268
269
270
271
272
273
274
275
276
277
278         </td>
279      </tr>
280
281
282 </table>
283
284
285 </div>
286
287
288
289
290 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
291 </script>
292 <script type="text/javascript">
293 _uacct = "UA-1868232-1";
294 urchinTracker();
295 </script>
296 </body>
297 </html>