[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Where should info on how to add extra storage servers go?

On Sun, Mar 16, 2014 at 05:04:53PM +0100, Petter Reinholdtsen wrote:
> [Holger Levsen]
> > yeah. though the blog post needs some polishing before putting it
> > there.
> What in particular did you have in mind?  I did not notice anything
> myself, but then again as the author, I am probably blind to its
> flags.  Things to improve would be most welcome. :)
Take these steps to set up a dedicated storage server for user home 
directories and data:
(1) Add a new system of type server using GOsa² as outlined in section 
    GettingStarted. This example uses 'nas-server.intern' as the server 

    Once 'nas-server.intern' ist configured, check if the NFS export 
    points on the new storage server are exported to the relevant
    subnets or machines:

    root@tjener:~# showmount -e nas-server
    Export list for nas-server:

    Here everything on the backbone network is granted access to the 
    '/storage' export. This could be restricted to netgroup membership
    or single IP addresses to limit NFS access.

(2) Add automount information about 'nas-server.intern' in LDAP to allow 
    all clients to automatically mount the new export on request.

    This can't be done using GOsa², because automount configuration is 
    missing. Instead, use ldapvi and add the required LDAP objects using
    an editor:

    ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no

    When the editor shows 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 'nas-server.intern' exports, 
    removing the need to list individual mount points in LDAP.)

    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:/&

(3) Configure mounts on tjener (automount isn't used here to avoid 
    mounting loops).

    Create the mount directories using mkdir, edit tjener:/etc/fstab and run 
    "mount -a" to mount the 'nas-server.intern' exports.

Now users should be able to access the files on 'nas-server.intern' 
directly by just visiting the /tjener/nas-server/storage/ directory 
using any application on any workstation, LTSP client or LTSP server.


Attachment: signature.asc
Description: Digital signature

Reply to: