|
Hello, I have two ec2-instances with CentOS and I want to create a cluster infrastructure with nfs-ganesha, pacamaker and corosnyc. I read different instructions but in some points I am not really sure how to do. At the moment my configuration is not running. The system says: Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the trusted pool. Do you still want to continue? (y/n) y This will take a few minutes to complete. Please wait .. nfs-ganesha : success But nothing happen. Ganesha is not starting. I think there is a problem with my ganesha-ha.conf file. 1.
What about that Virtual IPs? How I can create them (maybe /etc/hosts) ??? 2.
Should I use always use the same ganesha.ha.conf file on all nodes or should I change entries. You can see as follows my two ganesha.ha.conf files First ec2-instance: # Name of the HA cluster created. # must be unique within the subnet HA_NAME="ganesha-ha-360" # # The gluster server from which to mount the shared data volume. HA_VOL_SERVER="ec2-52-209-xxx-xxx.eu-west-1.compute.amazonaws.com" # # N.B. you may use short names or long names; you may not use IP addrs. # Once you select one, stay with it as it will be mildly unpleasant to # clean up if you switch later on. Ensure that all names - short and/or # long - are in DNS or /etc/hosts on all machines in the cluster. # # The subset of nodes of the Gluster Trusted Pool that form the ganesha # HA cluster. Hostname is specified. HA_CLUSTER_NODES="ec2-52-209-xxx-xxx.eu-west-1.compute.amazonaws.com,ec2-52-18-xxx-xxx.eu-west-1.compute.amazonaws.com" #HA_CLUSTER_NODES="server1.lab.redhat.com,server2.lab.redhat.com,..." # # Virtual IPs for each of the nodes specified above. VIP_ec2-52-209-xxx-xxx.eu-west-1.compute.amazonaws.com="10.0.2.1" VIP_ec2-52-18-xxx-xxx.eu-west-1.compute.amazonaws.com="10.0.2.2" #VIP_server1_lab_redhat_com="10.0.2.1" #VIP_server2_lab_redhat_com="10.0.2.2" Second ec2-instance: # Name of the HA cluster created. # must be unique within the subnet HA_NAME="ganesha-ha-360" # # The gluster server from which to mount the shared data volume. HA_VOL_SERVER="ec2-52-18-xxx-xxx.eu-west-1.compute.amazonaws.com" # # N.B. you may use short names or long names; you may not use IP addrs. # Once you select one, stay with it as it will be mildly unpleasant to # clean up if you switch later on. Ensure that all names - short and/or # long - are in DNS or /etc/hosts on all machines in the cluster. # # The subset of nodes of the Gluster Trusted Pool that form the ganesha # HA cluster. Hostname is specified. HA_CLUSTER_NODES="ec2-52-18-xxx-xxx.eu-west-1.compute.amazonaws.com,ec2-52-209-xxx-xxx.eu-west-1.compute.amazonaws.com" #HA_CLUSTER_NODES="server1.lab.redhat.com,server2.lab.redhat.com,..." # # Virtual IPs for each of the nodes specified above. VIP_ec2-52-209-xxx-xxx.eu-west-1.compute.amazonaws.com="10.0.2.1" VIP_ec2-52-18-xxx-xxx.eu-west-1.compute.amazonaws.com="10.0.2.2" #VIP_server1_lab_redhat_com="10.0.2.1" #VIP_server2_lab_redhat_com="10.0.2.2" Thank you for your attention David Spisla Software Developer
Tel: +49 761-590 34 841
iTernity
GmbH Geschäftsführer: Ralf Steinemann |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
