Generated.

[homepage.git] / blog / archive / 2014 / 03 / 03.rss

diff --git a/blog/archive/2014/03/03.rss b/blog/archive/2014/03/03.rss
index a554e2dd17a111d670db585680a35af498b69494..8648a5174f79a5abe7df850f08ac077ad4f21af9 100644 (file)
--- a/blog/archive/2014/03/03.rss
+++ b/blog/archive/2014/03/03.rss
@@ -6,6 +6,94 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
 
        
+       <item>
+               <title>How to add extra storage servers in Debian Edu / Skolelinux</title>
+               <link>http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html</link>        
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html</guid>
+                <pubDate>Fri, 14 Mar 2014 12:50:00 +0100</pubDate>
+               <description>&lt;p&gt;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 &lt;a href=&quot;http://www.slxdrift.no/&quot;&gt;Skolelinux Drift AS&lt;/a&gt;,
+where I am on the board of directors, asked about how to do this.  The
+steps to get this working are the following:&lt;/p&gt;
+
+&lt;p&gt;&lt;ol&gt;
+
+&lt;li&gt;Add new storage server in DNS.  I use nas-server.intern as the
+example host here.&lt;/li&gt;
+
+&lt;li&gt;Add automoun LDAP information about this server in LDAP, to allow
+all clients to automatically mount it on reqeust.&lt;/li&gt;
+
+&lt;li&gt;Add the relevant entries in tjener.intern:/etc/fstab, because
+tjener.intern do not use automount to avoid mounting loops.&lt;/li&gt;
+
+&lt;/ol&gt;&lt;/p&gt;
+
+&lt;p&gt;DNS entries are added in GOsa², and not described here.  Follow the
+&lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted&quot;&gt;instructions
+in the manual&lt;/a&gt; (Machine Management with GOsa² in section etting
+started).&lt;/p&gt;
+
+&lt;p&gt;Ensure that the NFS export points on the server are exported to the
+relevant subnets or machines:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+root@tjener:~# showmount -e nas-server
+Export list for nas-server:
+/storage         10.0.0.0/8
+root@tjener:~#
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Here everything on the backbone network is granted access to the
+/storage export.  With NFSv3 it is slightly better to limit it to
+netgroup membership or single IP addresses to have some limits on the
+NFS access.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+ldapvi --ldap-conf -ZD &#39;(cn=admin)&#39; -b ou=automount,dc=skole,dc=skolelinux,dc=no
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;When the editor show up, add the following LDAP objects at the
+bottom of the document.  The &quot;/&amp;&quot; 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.&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+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:/&amp;
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;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 &quot;mount -a&quot; to mount them.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+</description>
+       </item>
+       
        <item>
                <title>Hvordan bør RFC 822-formattert epost lagres i en NOARK5-database?</title>
                <link>http://people.skolelinux.org/pere/blog/Hvordan_b_r_RFC_822_formattert_epost_lagres_i_en_NOARK5_database_.html</link>