1 <?xml version="1.0" encoding="UTF-8"?>
3 <title>Installation Overview</title>
5 <para>This chapter describes the type of instructions provided in this
6 guide and the hardware and software requirements for installing
7 <trademark class="registered">AFS</trademark>.</para>
9 <para>Before beginning the installation of your cell's first machine,
10 read this chapter and the material from the <citetitle>OpenAFS
11 Administration Guide</citetitle> listed in <link
12 linkend="HDRWQ8">Recommended Reading List</link>. It is also best to
13 read through <link linkend="HDRWQ17">Installing the First AFS
14 Machine</link> before beginning the installation, so that you understand
15 the overall scope of the installation procedure. Similarly, before
16 installing additional server or client machines it is best to read
17 through <link linkend="HDRWQ99">Installing Additional Server
18 Machines</link> and <link linkend="HDRWQ133">Installing Additional
19 Client Machines</link>.</para>
21 <para>If you are already running a version of AFS, consult the upgrade
22 instructions in the <citetitle>OpenAFS Release Notes</citetitle> before
23 proceeding with the installation.</para>
26 <title>The Procedures Described in this Guide</title>
28 <para>This guide describes two types of installation procedures:
29 initial procedures (such as installing the first AFS machine or
30 incorporating AFS into the kernel) and as-needed procedures (such as
31 installing additional server machines or client machines).</para>
34 <title>Required Initial Procedures</title>
36 <para>You must perform the following basic procedures to start using
39 <sect3 id="Header_10">
40 <title>Incorporating AFS Into the Kernel</title>
42 <para>You must incorporate AFS modifications into the kernel of
43 every client machine. On some operating systems you must also
44 incorporate these modifications into the kernels of server machines.
46 the operating system, you either use a program for dynamic kernel
47 loading, build a new static kernel, or can choose between the
48 two. For your convenience, the instructions for incorporating AFS
49 into the kernel appear in full in every chapter where you need to
52 <primary>roles for first AFS machine</primary>
55 <primary>first AFS machine</primary>
56 <secondary>roles</secondary>
61 <sect3 id="Header_11">
62 <title>Installing the First AFS Machine</title>
64 <para>You install the first AFS machine in your cell to function
65 as both an AFS server and client machine. You can disable the
66 client functionality after completing the installation, if you
69 <para>The first server machine in a cell performs several
73 <para>It acts as the <emphasis>system control
74 machine</emphasis>, distributing certain
75 configuration files to the other server machines in the
80 <para>It may act as the <emphasis>binary distribution
81 machine</emphasis> for its system type, distributing AFS
82 binaries to other server machines of its system type</para>
86 <para>It acts as the first <emphasis>database server
87 machine</emphasis>, running the server processes that
88 maintain the AFS administrative databases</para>
93 <para>After you install server and client functionality, you
94 complete other procedures specific to the first machine, including
95 setting up the top levels of your cell's AFS filespace.</para>
99 <sect2 id="Header_12">
100 <title>As-needed Procedures</title>
102 <sect3 id="Header_13">
103 <title>Upgrading the Operating System</title>
105 <para>Upgrading the operating system requires you to take several
106 steps to protect data and AFS-modified binaries from being lost or
107 overwritten. For guidelines, see <link linkend="HDRWQ14">About
108 Upgrading the Operating System</link>.</para>
111 <sect3 id="Header_14">
112 <title>Installing Additional File Server Machines</title>
114 <para>See <link linkend="HDRWQ100">Installing an Additional File
115 Server Machine</link>.</para>
118 <sect3 id="Header_15">
119 <title>Configuring or Decommissioning Database Server Machines</title>
121 <para>See <link linkend="HDRWQ114">Installing Database Server
122 Functionality</link> and <link linkend="HDRWQ125">Removing
123 Database Server Functionality</link>.</para>
126 <sect3 id="Header_16">
127 <title>Installing Additional AFS Client Machines</title>
129 <para>See <link linkend="HDRWQ133">Installing Additional Client
130 Machines</link>.</para>
133 <sect3 id="Header_17">
134 <title>Building AFS from Source Code</title>
136 <para>See <link linkend="HDRWQ163">Appendix A, Building AFS from
139 <primary>background reading list</primary>
142 <primary>reading list for background information</primary>
150 <title>Recommended Reading List</title>
152 <para>To develop the best understanding of the overall scope of an
153 installation procedure, read through the entire chapter or section
154 that describes it before performing any actions.</para>
156 <para>In addition, familiarity with some basic AFS concepts can make
157 the installation more efficient, because you understand better the
158 purpose of the steps. The following is a prioritized list of material
159 to read before installing the first AFS machine. At minimum, read the
160 first chapter of the <citetitle>OpenAFS Administration
161 Guide</citetitle>. Then continue your reading in the indicated order,
162 as extensively as you can. It is more important at this point to read
163 the conceptual material in each section than the instructions.</para>
165 <para><emphasis role="bold">Selected Topics in the <emphasis>OpenAFS
166 Administration Guide</emphasis></emphasis>
169 <para>The chapter titled <emphasis>An Overview of AFS
170 Administration</emphasis></para>
174 <para>Selected sections in the <emphasis>Administering Server
175 Machines</emphasis> chapter: <emphasis>Local Disk Files on a
176 Server Machine</emphasis>, <emphasis>The Four Roles for a Server
177 Machine</emphasis>, <emphasis>Maintaining the Server CellServDB
178 File</emphasis></para>
182 <para>Selected sections in the <emphasis>Monitoring and
183 Controlling Server Processes</emphasis> chapter:
184 <emphasis>Controlling and Checking Process
185 Status</emphasis></para>
189 <para>Selected sections in the <emphasis>Managing Server
190 Encryption Keys</emphasis> chapter: <emphasis>About Server
191 Encryption Keys</emphasis></para>
195 <para>Selected sections in the <emphasis>Managing
196 Volumes</emphasis> chapter: <emphasis>About Volumes</emphasis>,
197 <emphasis>Creating Read/write Volumes</emphasis>,
198 <emphasis>Clones and Cloning</emphasis>, <emphasis>Mounting
199 Volumes</emphasis></para>
203 <para>Selected sections in the <emphasis>Administering Client
204 Machines and the Cache Manager</emphasis> chapter:
205 <emphasis>Overview of Cache Manager Customization</emphasis>,
206 <emphasis>Configuration and Cache-related Files on the Local
207 Disk</emphasis>, <emphasis>Determining the Cache Type, Size, and
208 Location</emphasis></para>
212 <para>Selected sections in the <emphasis>Managing Access Control
213 Lists</emphasis> chapter: <emphasis>Protecting Data in
214 AFS</emphasis></para>
216 </itemizedlist></para>
218 <para><emphasis role="bold">More Selected Topics in the
219 <emphasis>OpenAFS Administration Guide</emphasis></emphasis>
222 <para>Selected sections in the <emphasis>Managing
223 Volumes</emphasis> chapter: <emphasis>Creating and Releasing
224 Read-only Volumes (Replication)</emphasis>, <emphasis>Creating
225 Backup Volumes</emphasis></para>
229 <para>Selected sections in the <emphasis>Administering the
230 Protection Database</emphasis> chapter: <emphasis>About the
231 Protection Database</emphasis></para>
235 <para>Selected sections in the <emphasis>Administering User
236 Accounts</emphasis> chapter: <emphasis>The Components of an AFS
237 User Account</emphasis></para>
241 <para>Selected sections in the <emphasis>Managing Administrative
242 Privilege</emphasis> chapter: <emphasis>An Overview of
243 Administrative Privilege</emphasis></para>
250 <title>Requirements</title>
252 <para>You must comply with the following requirements to install AFS successfully. <indexterm>
253 <primary>root superuser</primary>
255 <secondary>as installer's login identity</secondary>
258 <sect2 id="Header_20">
259 <title>Login Identity</title>
261 <para>Log into the machine you are installing as the local superuser <emphasis role="bold">root</emphasis>. When instructed,
262 also authenticate with AFS as the administrative user <emphasis role="bold">admin</emphasis>. <indexterm>
263 <primary>overview</primary>
265 <secondary>general installation requirements</secondary>
266 </indexterm> <indexterm>
267 <primary>requirements</primary>
269 <secondary>general</secondary>
274 <title>General Requirements</title>
278 <para>You must have a Kerberos 5 realm running for your site, and
279 the ability to create new principals within that realm</para>
283 <para>You must have a NTP, or similar, timeservice running. Each AFS
284 machine should derive its system time from this timeservice</para>
288 <para>You must have an OpenAFS Binary Distribution for each system
289 type you are installing, or have built a binary from the supplied
290 source code. Unless otherwise noted, the Binary Distribution
291 includes software for both client and server machines.</para>
295 <para>All AFS machines that belong to a cell must be able to access each other via the network.</para>
299 <para>The machine must be running the standard, vendor-supplied version of the operating system supported by the current
300 version of AFS. The operating system must already be installed on the machine's root partition.</para>
304 <para>You must be familiar with the current operating system and disk configuration of the machine you are
309 <para>All hardware and non-AFS software on the machine must be functioning normally.</para>
313 <para>No critical processes can be running on the machine you are installing, because you may need to reboot it during the
319 <primary>file server machine</primary>
321 <secondary>requirements for installation</secondary>
325 <primary>requirements</primary>
327 <secondary>file server machine (general)</secondary>
332 <title>File Server Machine Requirements</title>
336 <para>Cell configuration is simplest if the first machine you install has the lowest IP address of any database server
337 machine you currently plan to install. If you later configure a machine with a lower IP address as a database server
338 machine, you must update the <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on all of your cell's client
339 machines before the installation. For further discussion, see <link linkend="HDRWQ114">Installing Database Server
340 Functionality</link>.</para>
344 <para>The partition mounted on the <emphasis role="bold">/usr</emphasis> directory must have at least 18 MB of disk space
345 <!-- XXX - Is this still true - how big are our binaries these days? -->
346 available for storing the AFS server binaries (stored by convention in the <emphasis role="bold">/usr/afs/bin</emphasis>
347 directory). If the machine is also a client, there must be additional local disk space available, as specified in <link
348 linkend="HDRWQ12">Client Machine Requirements</link>. The complete set of AFS binaries requires yet more space, but they
349 are normally stored in an AFS volume rather than on a machine's local disk.</para>
351 <para>More significant amounts of space on the partition are required by the administrative databases stored in the
352 <emphasis role="bold">/usr/afs/db</emphasis> directory and the server process log files stored in the <emphasis
353 role="bold">/usr/afs/logs</emphasis> directory. The exact requirement depends on many factors, such as the size of your
354 cell and how often you truncate the log files.</para>
358 <para>There must be at least one partition (or logical volume, if the operating system and AFS support them) dedicated
359 exclusively to storing AFS volumes. The total number and size of server partitions on all file server machines in the cell
360 determines how much space is available for AFS files.</para>
365 <primary>client machine</primary>
367 <secondary>requirements for installation</secondary>
371 <primary>requirements</primary>
373 <secondary>client machine</secondary>
378 <title>Client Machine Requirements</title>
382 <para>The partition mounted on the <emphasis role="bold">/usr</emphasis> directory must have at least 4 MB of disk space
383 available for storing the AFS client binaries and kernel library files (stored by convention in the <emphasis
384 role="bold">/usr/vice/etc</emphasis> directory). The complete set of AFS binaries requires more space, but they are
385 normally stored in an AFS volume rather than on a machine's local disk. For most system types, the instructions have you
386 copy only the one kernel library file appropriate for the machine you are installing. If you choose to store all of the
387 library files on the local disk, the space requirement can be significantly greater.</para>
391 <para>On a client machine that uses a disk cache, there must be enough free space on the cache partition (by convention,
392 mounted on the <emphasis role="bold">/usr/vice/cache</emphasis> directory) to accommodate the cache. The minimum
393 recommended cache size is 10 MB, but larger caches generally perform better.</para>
397 <para>On a client machine that uses a memory cache, there must be at least 5 MB of machine memory to devote to caching,
398 but again more memory generally leads to better performance. For further discussion, see the sections in <link
399 linkend="HDRWQ133">Installing Additional Client Machines</link> about configuring the cache.</para>
404 <primary>system types supported</primary>
408 <primary>supported system types</primary>
414 <title>Supported System Types</title>
416 <para>The <emphasis>OpenAFS Release Notes</emphasis> for each AFS release list the supported system types. Support for
417 subsequent revisions of an operating system often becomes available between AFS releases. The OpenAFS mailing lists can provide information regarding this interim support</para>
419 <para>It is the goal of OpenAFS to support AFS on a wide range of popular system types.
420 Furthermore, each time an operating system vendor releases a new general availability version of a supported operating system,
421 it is a goal to support AFS on it within a short time. Support can be delayed a bit longer if it is necessary to
422 generate completely new binaries.</para>
424 <para>It is not always possible to support AFS on every intermediate version of an operating system or for certain processor
425 types. In some cases, platform limitations make certain AFS functionality (such as file server or NFS/AFS translator
426 functionality) unavailable on one or more platforms. For a list of limitations, see the <emphasis>OpenAFS Release
427 Notes</emphasis> or ask on the OpenAFS mailing lists. <indexterm>
428 <primary>operating system upgrades</primary>
429 </indexterm> <indexterm>
430 <primary>upgrading the operating system</primary>
431 </indexterm> <indexterm>
432 <primary>AFS server partition</primary>
434 <secondary>protecting during operating system upgrade</secondary>
435 </indexterm> <indexterm>
436 <primary>files</primary>
438 <secondary>protecting during operating system upgrade</secondary>
443 <title>About Upgrading the Operating System</title>
445 <para>Whenever you upgrade an AFS machine to a different operating system, you must take several actions to maintain proper AFS
446 functionality. These actions include, but are not necessarily limited to, the following. <itemizedlist>
448 <para>On platforms running the inode fileserver, unmount the AFS server partitions (mounted at <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>
449 directories) on all file server machines, to prevent the vendor-supplied <emphasis role="bold">fsck</emphasis> program
450 from running on them when you reboot the machine during installation of the new operating system. Before upgrading the
451 operating system, it is prudent to comment out commands in the machine's initialization file that remount the server
452 partitions, to prevent them from being remounted until you can replace the standard <emphasis role="bold">fsck</emphasis>
453 program with the AFS-modified version. The instructions in this guide for installing AFS server machines explain how to
454 replace the <emphasis role="bold">fsck</emphasis> program. If you are unsure if your platform uses the inode fileserver, it is worth following this advice for all platforms.</para>
458 <para>Protect the AFS-modified versions of commands and configuration files from being overwritten by vendor-supplied
459 versions. These include <emphasis role="bold">vfsck</emphasis> (the AFS version of <emphasis role="bold">fsck</emphasis>), and configuration files such as the
460 one for the Pluggable Authentication Module (PAM). After you have successfully installed the operating system, remember to
461 move the AFS-modified commands and files back to the locations where they are accessed during normal functioning.</para>
465 I don't think OpenAFS has ever required the server partitions be reformatted
467 <para>Reformat the server partitions to accommodate AFS-specific information, in certain cases. The upgrade instructions
468 that accompany the new AFS binaries for an affected platform always detail the required procedure.</para>
471 </itemizedlist></para>
474 <primary>AFS Binary Distribution</primary>
478 <primary>Binary Distribution (AFS)</primary>
482 <primary>CD-ROM</primary>
484 <secondary>packaging of AFS Binary Distribution</secondary>
488 <primary>encryption files</primary>
490 <secondary>in AFS Binary Distribution</secondary>
495 <title>The OpenAFS Binary Distribution</title>
497 <para>Binary Distributions for supported systems may be downloaded from the OpenAFS website. The distributions are in the native packaging format for the system in question, and should generally be installed using your system's package management tools.</para>
499 <para>For those distributions provided as tar files, or those built from source, the instructions in this guide specify how to copy out both binaries and configuration files</para>
504 <title>How to Continue</title>
506 <para>If you are installing the first AFS machine in your cell, proceed to <link linkend="HDRWQ17">Installing the First AFS
507 Machine</link>.</para>
509 <para>If you are installing an additional file server machine, or configuring or decommissioning a database server machine,
510 proceed to <link linkend="HDRWQ99">Installing Additional Server Machines</link>.</para>
512 <para>If you are installing an additional client machine, proceed to <link linkend="HDRWQ133">Installing Additional Client
513 Machines</link>.</para>