Archive

Archive for the ‘OpenAFS’ Category

OpenAFS 1.4.12 release candidate 2

February 1st, 2010

The OpenAFS Gatekeepers announce the availability of the second release candidate for OpenAFS version 1.4.12.

[...]

A large number of bugfixes, including in the Linux cache manager and the fileserver, are included, as well as a Preferences Pane for MacOS.
Since 1.4.12 pre1, several Rx bugs including computing connection idle times have been fixed; support for Kerberos 1.8 DES enabling has been added; and support for updated Linux kernel kmem cache creation is now available.

[Quelle: Derrick via openafs-annouce]

OpenAFS-Client on Ubuntu 9.10 “Karmic Koala”

January 31st, 2010

After installing my favourite window manager, next thing I’ll need is the OpenAFS-Client.

The installation of the client on modern Linux distributions is pretty straight forward.

  1. get the packages
  2. compile the kernel module
  3. mess around in some config files

First step: get the packages
sudo apt-get install
openafs-client openafs-doc openafs-modules-source openafs-krb5 krb5-clients krb5-config krb5-user krb5-doc

(Yes, we’ll install the -doc-Packages, because everyone likes documentation)

Next step: build the kernel module
Maybe you’ll need some more packages for this step:
sudo apt-get install module-assistant build-essential
Now start the module assistant, to build the openafs-module.
sudo module-assistant

m-a

The first entries “UPDATE” and “PREPARE” could take a few minutes, because eventually missing packages (e.g. kernel sources or headers, or the compiler-chain) will be installed. “SELECT” will open the next window, where you should search the module and select it.

build

Now build the module. The next question will be “would you like to install the build module?”, but you should now have a guess what to do ;-)
You should now exit the module assistant.

Last step: the config files
Open /etc/krb5.conf and edit the sections containing the following:

1
2
3
4
5
6
7
8
9
10
11
12
[libdefaults]
        default_realm = MYCELL.NET
[realms]
        MYCELL.NET = {
                kdc = kdc1.mycell.net
                kdc = kdc2.mycell.net
                admin_server = kdc1.mycell.net
                default_domain = mycell.net
        }
[domain_realm]
        .mycell.net = MYCELL.NET
        mycell.net = MYCELL.NET

You should translate mycell.net to your local cell settings, but you already knew that, right? Ask your AFS Admin, if you are not sure about the correct values.

You may also take a look at /etc/openafs/afs.conf.client, /etc/openafs/ThisCell and /etc/openafs/CellServDB, but in most cases there’s no need to change something within these three files. If you need to get an updated version of /etc/openafs/CellServDB, just get it via FTP from grand.central.org.
wget -O /etc/openafs/CellServDB
ftp://ftp.central.org/pub/cellservdb/CellServDB

The very last step: restart the client
sudo /etc/init.d/openafs-client restart
Stopping AFS services:.
Starting AFS services: openafs afsd.
afsd: All AFS daemons started.

You’re done! kinit and aklog will be your best friends from now on! :-)

, ,

OpenAFS 1.5.69 released

January 20th, 2010

1.5.69 is the recommended production-ready release of OpenAFS for Microsoft Windows users. It supports all Microsoft Windows operating systems from Windows 2000 through Windows 7 and Windows Server 2008 R2 including both 32-bit and 64-bit architectures. The 1.5.69 release continues the recent efforts at optimizing the performance of the Windows client and improving its scalability. The 1.5.69 Windows client is fully compatible with all AFS server versions.

For UNIX, Linux, and MacOS X (including Snow Leopard) the recommended production-ready release of OpenAFS is 1.4.11.

Please visit openafs.org/windows for up to date information on the status of the OpenAFS for Windows client.

[Quelle: Derrick via openafs-annouce]

Das Changelog findet sich wie immer auf openafs.org.

OpenAFS 1.4.12 release candidate 1

January 13th, 2010

The OpenAFS Gatekeepers announce the availability of the first release candidate for OpenAFS version 1.4.12.

[...]

A large number of bugfixes, including in the Linux cache manager and the fileserver, are included, as well as a Preferences Pane for MacOS.

[Quelle: Derrick via openafs-annouce]

OpenAFS Newsletter – Dezember 2009

December 15th, 2009

Eine neue Ausgabe des OpenAFS Newsletters ist online: Dezember 2009.

OpenAFS 1.5.68 released

December 9th, 2009

1.5.68 is the recommended production-ready release of OpenAFS for Microsoft Windows users. It supports all Microsoft Windows operating systems from Windows 2000 through Windows Vista SP1 and Windows Server 2008 including both 32-bit and 64-bit architectures. The 1.5.68 release continues the recent efforts at optimizing the performance of the Windows client and improving its scalability.

For UNIX, Linux, and MacOS X (including Snow Leopard) the recommended production-ready release of OpenAFS is 1.4.11. The 1.5.68 Windows client is fully compatible with all AFS server versions.

[Quelle: Jeff via openafs-annouce]

This production release is a major release. Important changes since
1.5.66 (there was no 1.5.67) include:

  • Set the DOS Readonly attribute on a file/directory whenever the unix mode combined with the mask 0200 is true. Previously there was a discrepency between the mask used for test

OpenAFS: NetInfo & NetRestrict

November 25th, 2009

Wenn ein Volume-Server an mehr als ein IP-Netz angebunden ist, bindet sich der OpenAFS Dienst an alle verfügbaren IP-Interfaces. Leider kann dies zu ungewollten und recht schlecht debugbaren Problemen in der VLDB führen.

# vos listaddrs
volserver01.standort1.example.com
192.168.0.1
volserver02.standort1.example.com
192.168.0.2
volserver01.standort2.example.com

Die Lösung bieten hier die zwei Dateien NetInfo und NetRestrict, unter Debian in /var/lib/openafs/local/ zu finden.

# cat /var/lib/openafs/local/NetInfo
1.2.3.4
# cat /var/lib/openafs/local/NetRestrict
192.168.0.1

Die Einträge in diesen beiden Dateien sagen in etwa folgendes:
Lieber vos, Du darfst Dich an die IP-Adresse 1.2.3.4 binden, aber lass’ die Finger weg von 192.168.0.1!

Mehrere IP-Adressen einfach in mehrere Zeilen schreiben, jeder nur ein Kreuz. Ob die Konfiguration funktioniert hat, sieht man nach einem Neustart z.B. mittels /etc/init.d/openafs-fileserver restart mit dem Befehl vos listaddrs.

# vos listaddrs
volserver01.standort1.example.com
volserver02.standort1.example.com
volserver01.standort2.example.com

Wer sich sein OpenAFS-Paket selbst gebaut hat, und/oder auf transarc-Pfade steht, der findet den richtigen Ort für die beiden Files in /usr/afs/local.