> -----Original Message----- > From: fedora-devel-list-bounces@xxxxxxxxxx > [mailto:fedora-devel-list-bounces@xxxxxxxxxx]On Behalf Of Doug Ledford > Sent: Thursday, January 08, 2009 2:15 PM > To: Development discussions related to Fedora > Subject: Re: Summary of the 2009-01-06 Packaging Committee meeting > < big snip > ... > > True on both counts. Of course, given clusters, totally irrelevant > points. They don't back up individual /etc directories on any of the > cluster nodes. All the nodes are set up so that they can be installed > by the cluster manager, and they can be reinstalled as needed. Nodes > are disposable. Also, they *do* mount /usr read-only in lots of > clusters, and they couldn't care less that default files are in there. > If they need to edit them, they go to the cluster disk controller node > and edit it where it isn't read-only and then all the nodes see the > changes. More commonly, the batch scheduler they use has its own > private data directory on the controlling node and it writes the > necessary files on the fly (or passes the options entirely on the > command line) based upon what nodes it intends to start the > job on. My > point is that these "we care about single node issues" simply do not > exist in clusters, and *can't* exist or they make the cluster > unmaintainable. > This should be something the Fedora HPC SIG should be deciding. You and I both know installing multiple MPIs and other apps can make things a mess in a big hurry. Shawn. > -- > Doug Ledford <dledford@xxxxxxxxxx> > GPG KeyID: CFBFF194 > http://people.redhat.com/dledford > > Infiniband specific RPMs available at > http://people.redhat.com/dledford/Infiniband > > -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
