From: Petter Reinholdtsen <pere@hungry.com>
Date: Wed, 12 Mar 2014 11:48:42 +0000 (+0000)
Subject: New post.
X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/cd840bdd3f0b86f080883f757a7d2dd020e62277?ds=inline;hp=14c30fcadbf6b05cee38bda48e476b5393e1e2cf

New post.
---

diff --git a/blog/data/2014-03-12-skolelinux-autofs.txt b/blog/data/2014-03-12-skolelinux-autofs.txt
new file mode 100644
index 0000000000..61819d508c
--- /dev/null
+++ b/blog/data/2014-03-12-skolelinux-autofs.txt
@@ -0,0 +1,83 @@
+Title: How to add extra storage servers in Debian Edu / Skolelinux
+Tags: english, debian edu, ldap
+Date: 2014-03-14 12:50
+
+<p>On larger sites, it is useful to use a dedicated storage server for
+storing user home directories and data.  The design for handling this
+in Debian Edu / Skolelinux, is to update the automount rules in LDAP
+and let the automount daemon on the clients take care of the rest.  I
+was reminded about the need to document this better when one of the
+customers of <a href="http://www.slxdrift.no/">Skolelinux Drift AS</a>,
+where I am on the board of directors, asked about how to do this.  The
+steps to get this working are the following:</p>
+
+<p><ol>
+
+<li>Add new storage server in DNS.  I use nas-server.intern as the
+example host here.</li>
+
+<li>Add automoun LDAP information about this server in LDAP, to allow
+all clients to automatically mount it on reqeust.</li>
+
+<li>Add the relevant entries in tjener.intern:/etc/fstab, because
+tjener.intern do not use automount to avoid mounting loops.</li>
+
+</ol></p>
+
+<p>DNS entries are added in GOsa², and not described here.  Follow the
+<a href="https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions
+in the manual</a> (Machine Management with GOsa² in section etting
+started).</p>
+
+<p>Ensure that the NFS export points on the server are exported to the
+relevant subnets or machines:</p>
+
+<p><blockquote><pre>
+root@tjener:~# showmount -e nas-server
+Export list for nas-server:
+/storage         10.0.0.0/8
+root@tjener:~#
+</pre></blockquote></p>
+
+<p>Here everything on the backbone network access.  With NFS it is
+better to limit it to netgroup membership to have some limits on the
+NFS access.</p>
+
+<p>The next step is to update LDAP.  This can not be done using GOsa²,
+because it lack a module for automount.  Instead, use ldapvi and add
+the required LDAP objects using an editor.</p>
+
+<p><blockquote><pre>
+ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no
+</pre></blockquote></p>
+
+<p>When the editor show up, add the following LDAP objects at the
+bottom of the document.  The "/&" part in the last LDAP object is a
+wild card matching everything the nas-server exports, removing the
+need to list individual mount points in LDAP.</p>
+
+<p><blockquote><pre>
+add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no
+objectClass: automount
+cn: nas-server
+automountInformation: -fstype=autofs --timeout=60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
+
+add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
+objectClass: top
+objectClass: automountMap
+ou: auto.nas-server
+
+add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
+objectClass: automount
+cn: /
+automountInformation: -fstype=nfs,tcp,rsize=32768,wsize=32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/&
+</pre></blockquote></p>
+
+<p>The last step to remember is to mount the relevant mount points in
+tjener.intern by adding them to /etc/fstab, creating the mount
+directories using mkdir and running "mount -a" to mount them.</p>
+
+<p>When this is done, your users should be able to access the files on
+the storage server directly by just visiting the
+/tjener/nas-server/storage/ directory using any application on any
+workstation, LTSP client or LTSP server.</p>