"Fossies" - the Fresh Open Source Software Archive 
Member "ark-20050419/arksf1/webpages/coolness.htma" (26 May 2004, 4427 Bytes) of package /linux/privat/old/ark-arksf1-20050419.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style:
standard) with prefixed line numbers.
Alternatively you can here
view or
download the uninterpreted source code file.
1 <!-- -*-Mode: html;-*- -->
2 <!-- ............................................................
3 .
4 . Copyright (c) 2001,2003,2004, Will Partain
5 . All rights reserved.
6 .
7 . Redistribution and use in source and binary forms, with or
8 . without modification, are permitted provided that the
9 . following conditions are met:
10 .
11 . * Redistributions of source code must retain the above
12 . copyright notice, this list of conditions and the
13 . following disclaimer.
14 .
15 . * Redistributions in binary form must reproduce the above
16 . copyright notice, this list of conditions and the
17 . following disclaimer in the documentation and/or other
18 . materials provided with the distribution.
19 .
20 . * Neither the name of the Arusha Project nor the names of
21 . its contributors may be used to endorse or promote
22 . products derived from this software without specific prior
23 . written permission.
24 .
25 . THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
26 . CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
27 . INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
28 . MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
29 . DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
30 . CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
31 . SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
32 . NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
33 . LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
34 . HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
35 . CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
36 . OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
37 . SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
38 .
39 ............................................................ -->
40 <!-- $Revision: 1.7 $ -->
41 <!-- tag: Deep Coolnesses -->
42 <h1>Coolnesses of the Arusha Project</h1>
43
44 Our old friend Sigbjorn Finne used to say, ``The
45 coolness-to-usefulness ratio must always be greater than
46 one.'' The Arusha Project (ARK) passes this test, easily.
47 <p>
48 (Disclaimer: the current ARK code doesn't do all of this
49 cool stuff. The point is, the ARK framework and way of
50 thinking will make this stuff possible.)
51 <p>
52 <ul>
53 <li><em>One command</em> builds all packages for all platforms at
54 a site:
55 <pre>
56 % ark package reveal ALL
57 </pre>
58 <li>
59 A ``package'' that is your own sendmail config is handled
60 the same way as a package that is the FlexLM
61 license manager, which is handled the same way
62 as an open-source package:
63 <pre>
64 % ark package deploy sendmail-config flexlm--6.02 apache--2.0.45
65 </pre>
66 <li>
67 You can have multiple versions of a package active at once:
68 <pre>
69 % ark package reveal xemacs--21.4.12 xemacs--21.5.11
70 </pre>
71 <li>
72 Whether a package is local to a host, or whether a single
73 copy is shared among many hosts (e.g. by NFS) is completely configurable,
74 and managed automatically.
75 <p>
76 <li>
77 Hosts, users, ``disk chunks'', web sites, etc., can be
78 handled within <em>one framework</em>; so...
79 <pre>
80 % ark user create fourth-year-class
81 % ark host verify sparc-solaris7
82 </pre>
83 <li>
84 If you have ``at boot time'' actions associated with packages,
85 users, web sites, etc., they can all be done (in the right
86 order) with:
87 <pre>
88 # ark package at-boot --hosts=. --quiet ALL
89 # ark user at-boot --hosts=. --quiet ALL
90 # ark website at-boot --hosts=. --quiet ALL
91 </pre>
92 (Similarly for ``at shutdown time'', and much the same for
93 regular tasks to be done by `cron'...)
94 <p>
95 <li>
96 Most importantly, you can <strong>collaborate</strong> with
97 like-minded sysadmins (in `teams') on the stuff you agree about!
98 If, for example, you agree with how team Sidai does
99 Apache, then your total configuration effort might be:
100 <pre>
101 <package name="apache--2.0.45" xml-version="1">
102 <status>revealed</status>
103 <prototypes>
104 <prototype team="sidai" name="apache"/>
105 <prototype team="." name="ALL"/>
106 </prototypes>
107 <hosts-supported><list>
108 <item>sparc-solaris-web-server</item>
109 </list></hosts-supported>
110 </package>
111 </pre>
112 If, however, you disagreed with the Sidai folks on the
113 `install-bits' method, you would simply
114 override theirs by adding to the above:
115 <pre>
116 <install-bits>
117 <code><![CDATA[
118 # your code here: shell, Python, or Perl script
119 ]]></code></method>
120 </install-bits>
121 </pre>
122 </ul>
123 <p>
124 <strong>ToDo: the rest</strong>
125
126 <!-- the end -->