[OpenAFS] How to Upgrade 1.6. to 1.8
Hirste
norgay@hirschhofer.net
Sun, 10 Nov 2024 11:12:28 +0100
This is a multi-part message in MIME format.
--------------lIrql6KSgT5XHCIQjtLT66DY
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Hi all,
I have to update an existing single server installation from 1.6. to 1.8.
A brief overview of the situation:
Existing Machine: Ubuntu Xenial, AFS Version 1.6.23 (through PPA) =afsA
Target Machine: Ubuntu Noble with AFS Version 1.8.10 (from Distro Repo) afsB
The Data ar provided via a handful of vdisks, each beeing a single AFS
volume, summing up to +3 TB.
Clients: Ubuntu Focal, AFS Client Version 1.8.10 (through PPA, ugly
Kerberos hack to allow weak crypto)
This is an inherited setup, I would describe my AFS abilities and
knowledge as weak / not to good.
What I would have done without advise or help:
Setup the new server, add vdisks as the origin machine has, rsyncing the
data, repointing DNS entries
so that no changes on the clients are needed (some of them beeing road
warriors on laptops), demoting afsA.
This will lead to a significant downtime since rsync will take its time.
Since there are no changes in Client Configuration
there could ba an easy way back.
Instead I think it would be better to
* add afsB to the existing cell (beeing only an additional file server)
* Migrating the AFS Volumes in an AFS manner to afsB (does this work
online?)
* move the other AFS roles (database server, binary distribution
machine, system control machine)
from afsA to afsB
* demote afsA
I am currently reading and trying to understand
https://docs.openafs.org/AdminGuide but would appreciate
help from experienced users.
Is it possible to have mixed fileserver versions ( 1.6 vs. 1.8) in a
Cell? What are caveats?
Is there a better strategy with less risk to migrate the server?
Appreciate any help and advise.
Hirste
--------------lIrql6KSgT5XHCIQjtLT66DY
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi all,</p>
<p>I have to update an existing single server installation from 1.6.
to 1.8.</p>
<p>A brief overview of the situation:<br>
</p>
<p>Existing Machine: Ubuntu Xenial, AFS Version 1.6.23 (through PPA)
=afsA<br>
</p>
<p>Target Machine: Ubuntu Noble with AFS Version 1.8.10 (from Distro
Repo) afsB<br>
</p>
<p>The Data ar provided via a handful of vdisks, each beeing a
single AFS volume, summing up to +3 TB.<br>
</p>
<p>Clients: Ubuntu Focal, AFS Client Version 1.8.10 (through PPA,
ugly Kerberos hack to allow weak crypto)</p>
<p>This is an inherited setup, I would describe my AFS abilities and
knowledge as weak / not to good.<br>
</p>
<p><br>
</p>
<p>What I would have done without advise or help:<br>
<br>
Setup the new server, add vdisks as the origin machine has,
rsyncing the data, repointing DNS entries<br>
so that no changes on the clients are needed (some of them beeing
road warriors on laptops), demoting afsA.<br>
</p>
<p>This will lead to a significant downtime since rsync will take
its time. Since there are no changes in Client Configuration<br>
there could ba an easy way back.<br>
</p>
<p><br>
</p>
<p>Instead I think it would be better to <br>
</p>
<ul>
<li>add afsB to the existing cell (beeing only an additional file
server)<br>
</li>
<li>Migrating the AFS Volumes in an AFS manner to afsB (does this
work online?)<br>
</li>
<li>move the other AFS roles (database server, binary distribution
machine, system control machine) <br>
from afsA to afsB</li>
<li>demote afsA</li>
</ul>
<p>I am currently reading and trying to understand
<a class="moz-txt-link-freetext" href="https://docs.openafs.org/AdminGuide">https://docs.openafs.org/AdminGuide</a> but would appreciate<br>
help from experienced users.</p>
<p>Is it possible to have mixed fileserver versions ( 1.6 vs. 1.8)
in a Cell? What are caveats?<br>
Is there a better strategy with less risk to migrate the server?<br>
</p>
<p>Appreciate any help and advise.<br>
</p>
<p>Hirste<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>
--------------lIrql6KSgT5XHCIQjtLT66DY--