On 10/4/2016 10:28 AM, Andreas Ladanyi wrote: > Hi, > > i have the following situation: > > old server infrastructure: > > ================ > > 1 Server: MIT Kerberos server REALM A, OpenLDAP server (without > principals), OpenAFS 1.6 server cell A > > > new server infrastructure: > > ================= > > 1. Server: FreeIPA 4 server REALM B > > 2. Server: OpenAFS 1.6 Server cell B > > > old user client system setup: > > ===================== > > Ubuntu 16.04, MIT Kerberos client using REALM A, OpenLDAP client, > OpenAFS 1.6 client, using cell A > > > plan of new user client system infrastructure (the user client hardware > wont change): > > ===================================================== > > Ubuntu 16.04, FreeIPA client 4 using REALM B, OpenAFS 1.6 client using > cell B > > > I read the thread: > https://lists.openafs.org/pipermail/openafs-info/2009-March/031004.html > > So if i understand the thread and man pages correctly i could do the > following steps:
Step 0. Shutdown all of the AFS services on the server you want to relocate to a new cell. > 1. change entries CellServDB / ThisCell on the old OpenAFS server > (current config is Cell A) to Cell B. And you need to install the keys from Cell B onto the fileserver. > 2. restart OpenAFS bos server on the old server of Cell A. When the fileserver starts it will (if properly configured) register itself with the Location Service in Cell B. You will be able to see it listed using vos listaddrs This registration will only register the fileserver's UUID and its IPv4 addresses. It will not register the vice partitions or any of the volumes that are located on those vice partitions. To add the volumes to the Location Service you will have to execute the vos syncvldb -server <address> I suggest you use the -dryrun and -verbose options the first time to execute it so you can confirm the desired behavior. Once the volumes are listed in the Location Service and are visible using vos listvldb you can then move them. > 3. On the old AFS Server ( now Cell B ), do a: > > vos move -localauth (as super user from the old server) volumename from > old OpenAFS server (which is now Cell B) to new OpenAFS server (Cell B) > > > So i have some questions: > > Why to use vos synvldb like mentioned in the thread 031004 ? I think > vos move should change the vldb entries on the old and the new server ? Answered above. > Whats up with the different REALMs (REALM A and B) on the old and the > new server ? I know there are two different afs/cell@REALM service > principals for the bos server to run, on the old server > afs/cell_a@REALM_A and on the new server afs/cell_b@REALM_B. So could i > simply move the volumes as root from the old openafs server changed from > cell A to cell B and realm A to new server system cell B / realm B ? AFS servers do not know or care about the realms. The servers within a cell all must share the same server configuration (ThisCell, CellServDB, and keys). You cannot move a volume between cells with the OpenAFS vos command. With AuriStorFS it is possible to copy volumes between cells. A volume once copied can be removed from the source if that is desired. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
