import repository from arizona
[raven.git] / webpage / index.html
1 <html>
2 <head>
3 <title> Stork Project </title>
4 <LINK href="stork.css" rel="stylesheet" type="text/css">
5
6 </head>
7
8 <body>
9
10
11 <div class="display" align="center">
12         <table border="0">
13         <tr>
14                 <td width="170" valign="top">
15
16                                 <br/>
17                                 <table cellpadding="3" width="170" id="links" class="links">
18                                         <tr>
19                                                 <td align="right">
20
21                                                         <ul class="links">
22
23                                                                 <a href = "index.html"></a><h3>Stork</h3>
24                                                                 <li class="links"><a href="tutmain.html">Stork Tutorial</a></li>
25
26                                                                 <li class="links"><a href="advanced.html">Advanced Usage</a></li>
27                                                                 <li class="links"><a href="arch.html">Stork Architecture</a></li>
28                                                                 <li class="links"><a href="filelist.html">Stork File List</a></li>
29                                                                 <li class="links"><a href="about.html">About Us</a></li>
30                                                                 <li class="links"><a href="apps.html">Related Links</a></li>
31                                                                 <li class="links"><a href="contact.html">Contact Stork</a></li>
32                                                                 <h4>Links</h4>
33                                                                 <li class="links"><a href="http://appmanager.berkeley.intel-research.net/plcontrol/apps.php?appid=1029">
34                                                                 Slice Status</a></li>
35                                                                 <li class="links"><a href="https://stork-repository.cs.arizona.edu">Stork Repository</a></li>
36                                                         </ul>
37
38                                                  </td>
39                                         </tr>
40                                 </table>
41                                 <br/>
42                 </td>
43
44                 <td valign="top">
45
46                 <table class="info" cellpadding="0" width="700" >
47                 <tr  height="75"><td colspan="3"><img style="margin-left: -0px;" src="images/stork-header.png" alt="stork logo"/></td></tr>
48                 <tr  bgcolor="#444444" class="headerrow" width="100%" height="2">
49
50                         <th colspan="2"> Stork: An Overview </th>
51
52                 </tr>
53                 <tr valign="top" align="left">
54
55                         <td>
56                                 <table cellpadding="8" id="content" class="content">
57
58                                         <tr>
59                                                 <td>
60                                                         <h1> What is Stork? </h1>
61                                                         Stork is a software installation utility akin to yum and apt
62                                                         available for both users of <a href="https://www.planet-lab.org/" target="_blank">PlanetLab</a> and for home use. 
63                                                         Stork is bolstered by both its support of central management of
64                                                         package updates, and a novel security system that empowers users
65                                                         and package creators while reducing trust in a repository administrator.
66                                                         Stork provides a secure, scalable,
67                                                         effective way to maintain tarball and RPM packages and software on large
68                                                         networks.
69
70
71                                                         <h2>How do I use Stork?</h2>
72
73                                                         <p>The easiest way to use Stork is with the Stork Slice Manager, a GUI that will make package
74                                                         management and Stork installation on your PlanetLab slices quick and painless. To start now, see our
75                                                         <a href="tutgui.html">instructions for using the Stork Slice Manager</a>.</p>
76
77
78                                                         <h2> What does Stork offer? </h2>
79
80                                                         <p><li><b>Stork Saves Time and Space...</b></li>
81                                                         The "nest" is what Stork uses to share downloades and
82                                                         packages between multiple virtual machines. The nest is
83                                                         used to individually manage a node's
84                                                         package delivery. The
85                                                         nest also maintains an up-to-date status of the repository and your nodes,
86                                                         preventing multiple downloads of the same package on the same node. Even if
87                                                         you need to install multiple copies of a package, it only takes the space
88                                                         of a single copy, which Stork shares securely on your virtual machines. Stork's
89                                                         nest allows you to quickly and easily share packages between slices.
90                                                         <p><li><b>...And increases speed!</b></li>
91                                                         Stork
92                                                         increases download speed by using formats such as BitTorrent,
93                                                         Coral, FTP, CoBlitz, CoDeeN, or HTTP. The nest also regulates file-sharing
94                                                         between slices on a node, improving download speed and efficiency.
95
96                                                         <p><li><b>Large Network, Little Effort</b></li> It's easy to manage packages on a large number of
97                                                         machines using Stork.   A set of trusted administrators can divide nodes into groups and centrally manage which packages are installed on different node groups.
98                                                         This removes the hassle of needing to log onto multiple computers to update packages. Stork provides a number
99                                                         of simple commands to execute installations that affect all or just a subset of your nodes.
100                                                         <p><li><b>It's Secure!</b></li> Stork uses public-key encryption to provide
101                                                         package security. Stork packages are securely referenced,
102                                                         and package installation is controlled by a configuration file that
103                                                         allows users to specify exactly what software should run in a slice.
104                                                         We also have examined the <A HREF="http://www.cs.arizona.edu/people/justin/packagemanagersecurity/">security 
105                                                         of different package managers</A>.
106                                                         <p><li><b>Low-Upkeep Repository</b>
107                                                         <br>Stork's repository allows users to add packages without needing to trust each other, eliminating the need for a central repository administrator to decide
108                                                         which package versions are valid. In fact, the  administrator doesn't even need to verify that there is a consistent
109                                                         distribution of packages available - Stork will handle all of this! </li>
110                                                         <p><li><b>Reduces Load</b></li>
111                                                         Stork's package repository
112                                                         differs from convential repositories by using a publish/subscribe system,
113                                                         known as <b>PsEPR</b>. This method allows updates
114                                                         to be downloaded immediately, rather than having to wait in the traditional
115                                                         polling method. This also has the effect of reducing the load on the repository.</li>
116
117                                                         <h2> Removing Stork from your Slice </h2>
118
119                                                         If you are no longer using Stork, then you may remove Stork from your slice by
120                                                         going to the <a href="http://stork-repository.cs.arizona.edu">Stork Repository</a>,
121                                                         logging in, and selecting the "Slice Control" link on the left side of the page.
122                                                         Alternatively, Stork may be removed manually by going to PLC and setting the
123                                                         initscript attribute for your slice to "stork_stopscript".   <br><br>
124
125                                                         <center><a href = "index.html">Home</a>     <a href = "#top">Top</a></center>
126                                                 </td>
127
128                                         </tr>
129                                 </table>
130                         </td>
131                 </tr>
132
133        </table>
134        </td>
135
136      </tr>
137      <tr>
138         <td></td>
139
140         <td>
141                 <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>
142
143                 <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>
144
145
146
147
148
149
150
151         </td>
152      </tr>
153
154 </table>
155
156 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
157 </script>
158 <script type="text/javascript">
159 _uacct = "UA-1868232-1";
160 urchinTracker();
161 </script>
162
163 </div>
164
165
166
167 </body>
168 </html>
169
170