similar to: pcs resources

I checked, and I have it like this: # Name of the HA cluster created. # must be unique within the subnet HA_NAME="ganesha-nfs" # # The gluster server from which to mount the shared data volume. HA_VOL_SERVER="tlxdmz-nfs1" # # 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

Hi, I've just created again the gluster with NFS ganesha. Glusterfs version 3.8 When I run the command gluster nfs-ganesha enable - it returns a success. However, looking at the pcs status, I see this: [root at tlxdmz-nfs1 ~]# pcs status Cluster name: ganesha-nfs Stack: corosync Current DC: tlxdmz-nfs2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum Last updated: Wed Dec 20

Hi, In your ganesha-ha.conf do you have your virtual ip adresses set something like this?: VIP_tlxdmz-nfs1="192.168.22.33" VIP_tlxdmz-nfs2="192.168.22.34" Renaud De?: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] De la part de Hetz Ben Hamo Envoy??: 20 d?cembre 2017 04:35 ??: gluster-users at gluster.org Objet?: [Gluster-users]

Hi, Okay. what happens if u run the command "gluster nfs-ganesha enable " again? Regards, Jiffin On Friday 08 December 2017 04:15 PM, Hetz Ben Hamo wrote: > There are no resources, there were error messages that I ignored > accidently. How do I recreate those resources? > > Thanks > > On Dec 8, 2017 12:14, "Jiffin Tony Thottan" <jthottan at redhat.com

Hi Jiffin, I looked at the document, and there are 2 things: 1. In Gluster 3.8 it seems you don't need to do that at all, it creates this automatically, so why not in 3.10? 2. The step by step guide, in the last item, doesn't say where exactly do I need to create the nfs-ganesha directory. The copy/paste seems irrelevant as enabling nfs-ganesha creates automatically the ganesha.conf and

Thanks Jiffin, Btw, the nfs-ganesha part in the release notes is having a wrong header, so it's not highlighted. One thing that it is still mystery to me: gluster 3.8.x does all what the release notes of 3.9 says - automatically. Any chance that someone could port it to 3.9? Thanks for the links On Wed, Dec 6, 2017 at 7:28 AM, Jiffin Tony Thottan <jthottan at redhat.com> wrote: >

Hi, On Monday 04 December 2017 07:43 PM, Hetz Ben Hamo wrote: > Hi Jiffin, > > I looked at the document, and there are 2 things: > > 1. In Gluster 3.8 it seems you don't need to do that at all, it > creates this automatically, so why not in 3.10? Kindly please refer the mail[1] and release note [2] for glusterfs-3.9 Regards, Jiffin [1]

> > > On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz at hetz.biz > <mailto:hetz at hetz.biz>> wrote: > > Hi Amar, > > If can say something about the development of GlusterFS - is that > there are 2 missing things: > > 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 > because someone [removed]

On Tue, Jan 2, 2018 at 2:36 PM, Hetz Ben Hamo <hetz at hetz.biz> wrote: > Hi Amar, > > If can say something about the development of GlusterFS - is that there > are 2 missing things: > > 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because > someone support to enable NFS-Ganesha. from the gluster command has been > vanished without

Hi, Small questoin: when running the P2v hard disk image, and I want to convert a phyical machine to oVirt, to which machine do I connect when the GUI starts? one of the nodes or the hosted engine? (i'm not talking about the URL). Thanks

Hi, I'm looking for a way to use virsh to connect to vCenter/VCSA and do some simple management of the VM's in case of power loss (I'm planning to run the script upon UPS/apcd event of power failure). Looking through the virsh documentation, I didn't find 2 things: 1. Login through a script (I don't see any user/password, specially since VCSA for example requires to use

Hi Amar, If can say something about the development of GlusterFS - is that there are 2 missing things: 1. Breakage between releases. I'm "stuck" using GlusterFS 3.8 because someone support to enable NFS-Ganesha. from the gluster command has been vanished without anything mentioned in the error message what other commands replaces it. Judging from other people's answers - the

On 07/12/2017 13:47, Hetz Ben Hamo wrote: > Out of curiosity,? did you write it or you found those > commands somewhere else? I wrote it, using what little experience of pcs I have so far - haven't actually been able to find any documented steps/instructions. :( Although this blog - http://www.tomvernon.co.uk/blog/2015/01/gluster-activepassive-cluster/ - suggested I was on the right

Hi, I spent the last few hours playing with virt-p2v, and here are few things that I found, please tell me on which to submit a bug report: 1. I created a boot image (without any parameters) and tested it using virt-manager. With QXL driver, when it loads the Xorg, it shows .. a blank screen (I tried it tens of times). With VirtIO it works. 2. RHV-Upload - I see that the

Hi, I've created a 2 node glusterFS test (Gluster 3.8). Without enabling NFS-Ganesha, when I try to mount from a client using glusterfs option - everything works. However, after enabling NFS-Ganesha, when I try to mount from a client using the glusterfs option (fuse), it fails with the following output (when using the log-file option): [2017-12-28 08:15:30.109110] I [MSGID: 100030]

Hi All, First of all, happy new year 2018! Hope all of your wishes come true this year, and hope you will have time for contributing to Gluster Project this year too :-) As a contributor and one of the maintainers of the project I would like to propose below plans for Gluster Project, and please share your feedback, and comments on them. - *Improved Automation to reduce the process burden*

HI, I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. I'm trying to create a very simple 2 nodes cluster to be used with NFS-ganesha. I've created the bricks and the volume. Here's the output: # gluster volume info Volume Name: cluster-demo Type: Replicate Volume ID: 9c835a8e-c0ec-494c-a73b-cca9d77871c5 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2

Hi guys I'm wondering if anyone here is using the GlusterFS OCF resource agents with Pacemaker on CentOS 7? yum install centos-release-gluster yum install glusterfs-server glusterfs-resource-agents The reason I ask is that there seem to be a few problems with them on 3.10, but these problems are so severe that I'm struggling to believe I'm not just doing something wrong. I created

On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote: > HI, > > I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. > > I'm trying to create a very simple 2 nodes cluster to be used with > NFS-ganesha. I've created the bricks and the volume. Here's the output: > > # gluster volume info > > Volume Name: cluster-demo > Type:

> > With the node in standby (just one is online in this example, but another > is configured), I then set up the resources: > > pcs node standby > pcs resource create gluster_data ocf:heartbeat:Filesystem > device="/dev/cl/lv_drbd" directory="/gluster" fstype="xfs" > pcs resource create glusterd ocf:glusterfs:glusterd > pcs resource create