So here's what I have done so far: 1. Created new cluster based on RHEL 6. 2. Created resources and services from scratch to match that in the old cluster (fsid, mount points, everything). I am using Congra (luci/ricci) just to ensure I am using the right syntax. 3. Gave access to storage volumes (iscsi) to new cluster node 4. pvscan/vgscan/lvscan 5. Disabled NFS services on old cluster 6. Enabled the NFS services on the new cluster
That's it. Life's good for the volumes on the cluster. I am yet to transfer my postgres stuff but I am moving from 8.3 to 9.0 so that will be a new volume and postgres installation so nothing exciting there. On Mon, Jan 9, 2012 at 8:04 AM, Alan Brown <a...@mssl.ucl.ac.uk> wrote: > On 09/01/12 13:34, Fabio M. Di Nitto wrote: > > Something i forgot to mention in the other email, is that for example, >> you can just move the LUNs from your SAN from one cluster to another >> assuming you are running GFS2 and that will work. >> > > And assuming that you have 2 clusters. This might be a possiblity shortly. > > > It would be _nice_ to have NFSv4 support working and supported in a GFS2 >>> cluster. >>> >> >> Steven can answer to this one.. but I think the point is more >> active/active vs active/passive (IIRC from previous discussions). >> > > We break up NFS serving into one service (ip) per FS. > > Any given FS is only served from one node because NFSv3 doesnt play nicely > with anything else, including other instances of itself. > > Bringing all the NFS services all onto one node is perfectly possible but > it's still a bunch of individual services. > > Running all NFS on one box turns into a choke point several times/day due > to the loads involved. The protocol just doesn't scale very well. > > > > > > > -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/**mailman/listinfo/linux-cluster<https://www.redhat.com/mailman/listinfo/linux-cluster> >
-- Linux-cluster mailing list Linux-cluster@redhat.com https://www.redhat.com/mailman/listinfo/linux-cluster
