Multisite NIS/Automount best practices?

From: Michael Coxe (mcoxe@opsware.com)
Date: Wed Jun 21 2006 - 13:33:19 EDT


Hello Sun admins,

I want to know what folks are doing to manage their multiple
site NIS/Automount maps & environments. Are there general
best practices? If so, neither the Sun Summaries archives nor
googling have offered a solution, or even a discussion.

Our situation is simple: 1 main site with 2 smaller, distant
development sites. NIS only, no NIS+. NIS servers on Solaris 9.

The passwd, shadow & group maps are universal and could be
pushed by the NIS master or pulled by secondaries.

The home directory map (auto_home) must be unique per site
(no NFS over wan, even with tcp). A growing number of users
have homes at more than 1 site, so it would be cool to have a
central, parsable master file containing all home paths, with
site specific maps generated from it via a script executed
by the /var/yp/Makefile.

Other maps such as /shared (OS/release specific bin/lib/src/etc)
and /clearcase are unique per site but are essentially static
and can be manually updated on the rare occasion.

So our needs primarily revolve around home directories. But
hopefully a solution would be adaptable to other map needs.
Will summarize replies with details, as I bet there are a number
of different solutions.

Regards,

  - michael

-- 
   Michael Coxe
   Opsware, Inc
   Sunnyvale, CA
   <mcoxe@opsware.com>
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers


This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:40:12 EDT