[csw-users] NFS shared /opt anyone?
Fechner, Jon L.
Jon.Fechner at tellabs.com
Tue Oct 12 17:52:18 CEST 2010
We do not use a configuration management system for opencsw delivered packages. We don't use everything available from opencsw, only about 50 or so applications that are key to us and I don't think they are of a highly configurable nature.
We are in the purely NFS-share /opt camp.
Thanks,
Jon
-----Original Message-----
From: users-bounces+jon.fechner=tellabs.com at lists.opencsw.org [mailto:users-bounces+jon.fechner=tellabs.com at lists.opencsw.org] On Behalf Of Maciej (Matchek) Blizinski
Sent: Friday, October 08, 2010 5:06 PM
To: Questions and discussions
Subject: Re: [csw-users] NFS shared /opt anyone?
No dia 8 de Outubro de 2010 07:28, Fechner, Jon L.
<Jon.Fechner at tellabs.com> escreveu:
> Just a note to let you know we do share over NFS and are benefiting from it. We have one installation for Solaris 8, 9, and 10 (on sparc) and it allows us to easily keep all users on the same version of the tools.
>
> We do not plan on abandoning this approach so I hope support is continued.
>
> I would be interested to know what the significant compromises are in package delivery if you have time, but it is not pressing.
Here's one example. Suppose that you deliver configuration files to
/etc/opt/csw so that they are zone-local on sparse zones with shared
/opt/csw. If you do that, they configuration files are not available
on the shared NFS solution, because they aren't under the shared
/opt/csw directory. If you choose to deliver configuration files to
/opt/csw/etc, they are available, if not modifiable, in the shared NFS
solution. The downside is that you cannot modify then on sparse
non-global zones.
My position on the topic is that if you're using the shared NFS
solution, you can use a configuration management system such as puppet
or cfengine to deploy your configuration files to /etc/opt/csw. I
would assume that any larger Solaris installation requires such a
solution, but I heard that there is a deployment that does not use any
configuration management system, and it requires configuration files
under /opt/csw/etc.
There are also issues with alternatives, and generally class action scripts.
How are NFS-based deployments managing the configuration files, do you
guys use a configuration management system, or is it purely NFS-shared
/opt?
_______________________________________________
users mailing list
users at lists.opencsw.org
https://lists.opencsw.org/mailman/listinfo/users
============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================
More information about the users
mailing list