1 In this section we will add read-only volume support to our OpenAFS cell.
3 At this point we should have the top-level directory structure:
6 yoyodyne.com/ -> root.cell
8 mayhem -> project.mayhem
13 == About volume groups ==
15 TODO: discussion about volume groups?
17 == Creating top level read-only volumes ==
19 Obtain admin credentials.
24 The <code>vos addsite</code> tool is used to declare read-only sites in
25 the VLDB. The first read-only site should match the location of the
26 read-only volume, i.e., the same fileserver and same partition on the
27 fileserver. Additional read-only sites should be declared on other
28 fileservers. Then, use <code>vos release</code> to distribute the files.
30 First, we create read-only volumes for the top level volumes.
32 vos addsite afs01 a root.afs
33 vos addsite afs02 a root.afs
37 vos addsite afs01 a root.cell
38 vos addsite afs02 a root.cell
42 Refresh your client's cache to be sure the paths are re-evaluated.
47 Now, the cache manager should resolve paths to the top level cell directory to
48 be served out of the read-only root.cell volume.
50 fs examine /afs/yoyodyne.com/
52 == Creating a read-only volume ==
54 Let's create read-only volumes for a volume in our cell.
56 vos addsite afs01 a project.mayhem
57 vos addsite afs02 a project.mayhem
58 vos release project.mayhem
60 fs examine /afs/yoyodyne.com/project/mayhem/
62 This path should now be served by the read-only copy of the volume. The files
63 reside on both fileservers, and clients may use either one. If one file server
64 is down, clients should automatically fail over to the other server.
66 == Accessing read-write data ==
68 In order to access the read-write volume we must use a path that has
69 a read-write mount point.
71 fs example /afs/.yoyodyne.com/project/mayhem/
73 Sine Nomine Associates Nov 2017