[OpenAFS] How to Upgrade 1.6. to 1.8

[Jose M Calhariz]

--OyGHelhMAXQFDxua
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I have upgraded my cell from OpenAFS 1.6 into AuriStorFS, like 1.8,
with the help of the company and I am happy.  So somethings apply,
others do not.

On Sun, Nov 10, 2024 at 11:12:28AM +0100, Hirste wrote:
> Hi all,
>=20
> I have to update an existing single server installation from 1.6. to 1.8.
>=20
> A brief overview of the situation:
>=20
> Existing Machine: Ubuntu Xenial, AFS Version 1.6.23 (through PPA) =3DafsA
>=20
> Target Machine: Ubuntu Noble with AFS Version 1.8.10 (from Distro Repo) a=
fsB
>=20
> The Data ar provided via a handful of vdisks, each beeing a single AFS
> volume, summing up to=A0 +3 TB.
>=20
> Clients: Ubuntu Focal, AFS Client Version 1.8.10 (through PPA, ugly Kerbe=
ros
> hack to allow weak crypto)
>=20
> This is an inherited setup, I would describe my AFS abilities and knowled=
ge
> as weak / not to good.
>=20
>=20
> What I would have done without advise or help:
>=20
> 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.
>=20
> 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.
>=20
>=20
> Instead I think it would be better to
>=20
>  * 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?)

Yes, specially if the volumes are not big or with heavy writes.  Your
clients will see small delays only.


>  * move the other AFS roles (database server, binary distribution
>    machine, system control machine)
>    from afsA to afsB

Too much complex.

Instead demote afsA as file server, and keep it as afs database
server.  Downgrade the hardware of afsA, as a database server does not
need much resources.  What it need is to be 100% available.

If you do not have, add two more afs database servers.  The
recommendation is to have three.  With 3 database servers you can
temporarily loose one of them and the cell will keep working.


>  * demote afsA

Upgrade afsA as a database server from 1.6 into 1.8.  Do your best to
remove the hack that allow weak crypto.  There is no need for it on
the last 1.6 versions or 1.8.

Consider to buy commercial support, IMHO this list now have very litle
traffic to be a reliable source of help.

I have much more to talk about your upgrade and there will be some
traps, specially for some one without experience.

>=20
> I am currently reading and trying to understand
> https://docs.openafs.org/AdminGuide but would appreciate
> help from experienced users.
>=20
> 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?
>=20
> Appreciate any help and advise.
>=20
> Hirste
>=20
>=20
>=20
>=20
>


Kind regards
Jose M Calhariz


--=20
--

Cachorro mordido de cobra tem medo at=E9 de ling=FC=ED=E7a.

--Rubens Morais

--OyGHelhMAXQFDxua
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEERkvHzUOf7l6LQJigNIp3jWiF748FAmczcZYACgkQNIp3jWiF
74/rqBAAijW1Tt7TQY5hUL8fmdsbrT60WMpt1SG+Y+z2+jit6Qvy1YgGwb3Zn55T
EMSjhQvaGdupogHo83L0mPUnZJYXCN+12lYZt/imzarOwZY+8p3+6CFaCbVnjqxP
l5Er9bptLNJEDYF+qMQYKKhyVS7ybu4k6ctJNkACiSUhu2TqFxd8vFcnHGS179HK
b66cKjNW46UehihVVG11vVOUjE97E2j1kDZU84ms7NQNqG0CpyBv9ryBAyuf4Nmu
mcZJ8FOKyI+B2p8OKHwCsaHEXWYxo0shoZeIHFBH+Kle+bNE+gQAgZDtVaI0NMU0
x2NJePtNps1cfsd2Av6asYK5E9eBEyvbAuoC0AqJaxyFpSB8K2rgvoymJsXbeXbP
tm6SARYxBhcX181Q3PCLN4rRyJEkukfhYwegTmglDliEAw+AmMRVPGjk+y6ANuYb
YJte54IfOtwBczHiSZ++OPmFk4/Wc26JycikuGmX38qp9nTNBX+uHFeSpD6E2BF9
KS8KBij+LHEIhz2Aih7XlDY2N/ZBg9hrez0VqpiXUNJmuItSqybZalfCASWeEAHz
7OgLKKi+wVaCY4zOuDRmpNJLhusLf9hW9KRgcasUazNGQvBv8ibSOdHd9Et1/XdT
Bp+8sKExWms7LdcUenSVm+V3p4yl5VPHzNWuSotXGPSI0warqqg=
=E01r
-----END PGP SIGNATURE-----

--OyGHelhMAXQFDxua--