Re: [Gluster-users] backupvolfile-server fqdn vs short

2015-07-23 Thread Alastair Neil
yes certain - the mount command is in the fstab and it uses all fully
qualified domain names.
btw Atin, gmail showed me an empy reply - had to use view original to see
your question, not sure why, are you sending plaintext?


gluster0.vsnet.gmu.edu:/digitalcorpora /var/www/digitalcorpora glusterfs
 _netdev,use-readdirp=no,backupvolfile-server=gluster1.vsnet.gmu.edu:g
 luster-2.vsnet.gmu.edu 0 0


On 23 July 2015 at 12:30, Atin Mukherjee atin.mukherje...@gmail.com wrote:

 -Atin
 Sent from one plus one
 On Jul 23, 2015 9:07 PM, Alastair Neil ajneil.t...@gmail.com wrote:
 
  I just had a curious failure.  I have a gluster 3.6.3 replica 3 volume
 which was mounted via an 3.6.3 client  from one of the nodes with the other
 two specified in the backupvolfile-server mount option.  In the fstab entry
 all the nodes are referenced by their fully qualified domain names.
 
  When I rebooted the primary node, the mount became detached because the
 client was trying to use the short name to communicate with the backup
 nodes and failing to resolve it.  This was fixed by adding the domain to
 the search in resolv.conf.  However I am curious as to why it should try
 and use the short name instead of the fqdn specified in the fstab entry?
 The nodes all have peer entries for hostname, ip address and fqdn.
 Are you sure you didn't use short name in your mount command?
 
  Thanks,  Alastair
 
 
  ___
  Gluster-users mailing list
  Gluster-users@gluster.org
  http://www.gluster.org/mailman/listinfo/gluster-users

___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Replace failed Node in a 4nodes Distributed-Replicate Volume

2015-07-23 Thread Luciano Facchinelli
Any idea on this ?

Regards

2015-07-23 17:16 GMT-03:00 Luciano Facchinelli lfacchine...@canal10.com.uy
:

 Any idea on this ?

 Regards

 Luciano

 2015-06-25 18:18 GMT-03:00 Luciano Facchinelli 
 facchinelli.luci...@gmail.com:

 Hi guys!

 I did a google search but i found a lot of information and i don't really
 know which one should i follow .

 My scenario is this :

 2 Volumes distributed-replicated
 4 Nodes / 2 brick on each
 Each node is running glusterfs 3.4.0

 One of those nodes, died, completely, so i'm planning a new install of OS
 on that node, recreate brick's folders and re-add it .

 Which steps should i follow in order to accomplish that task ?

 Is there any pitfall I should be aware of ?

 Thanks and regards form Uruguay, South America .



___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gentle Reminder.. (Was: [Gluster-devel] GlusterFS Documentation Improvements - An Update)

2015-07-23 Thread Humble Devassy Chirammal

This is still confising me a little. The presentations from the
Mediawiki instance have been put in the glusterdocs/presentations/
directory. If we should put them on the website instead, they should not
be part of glusterdocs. However, there is currently no page that I can
find on the website that lists the different presentations. The only
link that I can find is this one:

  http://gluster.readthedocs.org/en/latest/presentations/

Is that going to be replaced with an explanation (or pointer) on how to
get the presentation on the website?



Well, we are yet to finalize on it.  If we can render it on website we will
do the same. Otherwise it will be a pointer from website.


--Humble


On Fri, Jul 24, 2015 at 2:00 AM, Niels de Vos nde...@redhat.com wrote:

 On Wed, Jul 22, 2015 at 03:51:59PM +0530, Anjana Sriram wrote:
  Hello All,
 
  Thank you for the feedback and suggestions provided on the GlusterFS
  Documentation improvements. We have analyzed them and here's a proposal
 to
  address them:
 
  We plan to use three independent repos for our projects:
 
 ... snip
 
  /Static Documentation/: Currently, Mediawiki is read-only. We have ported
  most of the documents from Mediawiki. There few pages which do not
 qualify
  to be placed in the above three repos for example, Presentations  which
 will
  be considered to be placed on the website.

 This is still confising me a little. The presentations from the
 Mediawiki instance have been put in the glusterdocs/presentations/
 directory. If we should put them on the website instead, they should not
 be part of glusterdocs. However, there is currently no page that I can
 find on the website that lists the different presentations. The only
 link that I can find is this one:

   http://gluster.readthedocs.org/en/latest/presentations/

 Is that going to be replaced with an explanation (or pointer) on how to
 get the presentation on the website?

 Thanks,
 Niels


 
  Your thoughts and feedback are the major influences to our constant
 endeavor
  to make the community documentation better, effective, and useful. Please
  revert with your thoughts and feedback on the above proposal outlined by
  29th July 2015.
 
  Regards,
  Humble, Shravan, and Anjana
 
  On 06/22/2015 05:24 PM, Shravan Chandrashekar wrote:
  Hello all,
  
  We would like to finalize on the documentation contribution workflow by
 26th June 2015.
  As we have not yet received any comments/suggestion, we will confirm
 the recommend workflow after 26th June.
  
  
  Kindly provide your suggestion on how we can improve this workflow.
  
  Currently, mediawiki is read-only. We have ported most of the documents
 from mediawiki to the new repository [1].
  If you find any document which is not ported, feel free to raise this
 by opening an issue in [2] or if you would
  like to port your documents, send a pull request.
  
  
  
  [1] https://github.com/gluster/glusterdocs
  [2] https://github.com/gluster/glusterdocs/issues
  
  Regards,
  Shravan
  
  - Original Message -
  From: Humble Devassy Chirammal humble.deva...@gmail.com
  To: Gluster-users@gluster.org List gluster-users@gluster.org,
 Gluster Devel gluster-de...@gluster.org
  Sent: Wednesday, May 27, 2015 7:48:16 PM
  Subject: [Gluster-devel] GlusterFS Documentation Improvements - An
 Update
  
  
  Hello all,
  
  The GlusterFS documentation team is constantly working to improve the
 quality, findability, and usefulness of its documentation. Our goal is to
 increase community contribution, remove barriers that discourage
 contribution and give you the help you need, when and where you need it. As
 part of this strategy, we’ve just rolled out the revamped GlusterFS
 Documentation: gluster.readthedocs.org
  
  We started by curating content from various sources including
 gluster.org static HTML documentation, various blog posts and the
 Community wiki. We used readthedocs service to host the documentation and
 mkdocs to convert the Markdown source files to HTML pages. We also put our
 thought into classifying the documentation based on their content:
  
  
  
   * Quick Start Guide : A headstart guide for the beginners.
  
  
   * Installation Guide : Step by step instructions to install
 GlusterFS.
  
  
   * Administration Guide : Container for for all administrative
 actions.
  
  
   * Developer Guide : Container for all development related aspects.
  
  
   * Upgrade Guide : Contains guides to upgrade from older versions
 of GlusterFS.
  
  
   * Features : Container for all the features of GlusterFS
 introduced in various versions.
  
  
   * GlusterFS Tools : Contains information about the tools used in
 GlusterFS.
  
  
   * Troubleshooting Guide : Container for basic troubleshooting and
 debugging guides.
  
  
   * Images : Container for images (in .jpg or .png format) that are
 present inline the documentation pages.
  
  Doing so, we gain these benefits:
  
  
  
   * Version based 

Re: [Gluster-users] Setup with replica 3 for imagestorage

2015-07-23 Thread Gregor Burck
For now I made a setup with drbd and cman, ssem to work for me, even I hope to 
solve the problems with glusterfs. Cause there ar nice features in glusterfs 
and it is handy to setup.

If you still need some test from me, I'm on the list,  and I test glusterfs 
on...

bye

Gregor
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users


[Gluster-users] backupvolfile-server fqdn vs short

2015-07-23 Thread Alastair Neil
I just had a curious failure.  I have a gluster 3.6.3 replica 3 volume
which was mounted via an 3.6.3 client  from one of the nodes with the other
two specified in the backupvolfile-server mount option.  In the fstab entry
all the nodes are referenced by their fully qualified domain names.

When I rebooted the primary node, the mount became detached because the
client was trying to use the short name to communicate with the backup
nodes and failing to resolve it.  This was fixed by adding the domain to
the search in resolv.conf.  However I am curious as to why it should try
and use the short name instead of the fqdn specified in the fstab entry?
The nodes all have peer entries for hostname, ip address and fqdn.

Thanks,  Alastair
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] gluster in cloud environment

2015-07-23 Thread Atin Mukherjee
-Atin
Sent from one plus one
On Jul 23, 2015 3:41 PM, Timo Schaepe i...@timoschaepe.de wrote:

 Hey guys,

 we are trying to use gluster 3.6.4 in a cloud environment. Creating the
gluster itself is not a problem. Mounting the created vol from a machine in
the cloud infrastructure is not a problem. But when I am trying to mount
the created gluster vol from an external machine it fails. In the log files
of the client I can see that gluster is annoucing the bricks with the cloud
infrastructure internal ips, which are not accessible from outside of the
cloud. When I change the internal ips to the public domain names in
/var/lib/glusterd/gv0.tcp-fuse.vol on every cluster host it works seamless.
I definitely think that this is not the recommended way to solve this
problem. Of course it breaks, if I add another bricks to the gluster.

 Is there a possibility to change the annouced ip adresses?
 Or is there another way to solve this problem?
Probably in that case its better to peer probe using public domain name
instead of internal IP?

 Thanks,

 Timo
 ___
 Gluster-users mailing list
 Gluster-users@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] backupvolfile-server fqdn vs short

2015-07-23 Thread Atin Mukherjee
-Atin
Sent from one plus one
On Jul 23, 2015 9:07 PM, Alastair Neil ajneil.t...@gmail.com wrote:

 I just had a curious failure.  I have a gluster 3.6.3 replica 3 volume
which was mounted via an 3.6.3 client  from one of the nodes with the other
two specified in the backupvolfile-server mount option.  In the fstab entry
all the nodes are referenced by their fully qualified domain names.

 When I rebooted the primary node, the mount became detached because the
client was trying to use the short name to communicate with the backup
nodes and failing to resolve it.  This was fixed by adding the domain to
the search in resolv.conf.  However I am curious as to why it should try
and use the short name instead of the fqdn specified in the fstab entry?
The nodes all have peer entries for hostname, ip address and fqdn.
Are you sure you didn't use short name in your mount command?

 Thanks,  Alastair


 ___
 Gluster-users mailing list
 Gluster-users@gluster.org
 http://www.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] gluster in cloud environment

2015-07-23 Thread Timo Schaepe
Hey guys,

we are trying to use gluster 3.6.4 in a cloud environment. Creating the gluster 
itself is not a problem. Mounting the created vol from a machine in the cloud 
infrastructure is not a problem. But when I am trying to mount the created 
gluster vol from an external machine it fails. In the log files of the client I 
can see that gluster is annoucing the bricks with the cloud infrastructure 
internal ips, which are not accessible from outside of the cloud. When I change 
the internal ips to the public domain names in 
/var/lib/glusterd/gv0.tcp-fuse.vol on every cluster host it works seamless. I 
definitely think that this is not the recommended way to solve this problem. Of 
course it breaks, if I add another bricks to the gluster.

Is there a possibility to change the annouced ip adresses?
Or is there another way to solve this problem?

Thanks,

Timo
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users