Re: [Gluster-users] Use GlusterFS as storage for images of virtual machines - available issues

[Sankarshan Mukhopadhyay]

On Wed, Nov 27, 2019 at 6:10 PM Ravishankar N  wrote:
>
>
> On 27/11/19 5:52 pm, Dmitry Melekhov wrote:
> > 27.11.2019 16:16, Ravishankar N пишет:
> >> [Re-adding the mailing-list]
> >>
> >> On 27/11/19 5:35 pm, Gregor Burck wrote:
> >>> Hi Ravi,
>  https://lists.gluster.org/pipermail/gluster-users/2019-July/036858.html
> 
> >>> yes, seem so.
> >>> So I've to took it in the init secure for a normal shotdown in may
> >>> debian system.
> >>> I wonder why there is no gracefull funktion in the normal setup?
> >>> Think the issue isn't so unnormal, to switch one node down,...
> >> I think we need to provide a way to run this script (or provide a
> >> prompt to the admin to run it) when a shutdown/ reboot is invoked. If
> >> you have any ideas to make this work in a generic way for most linux
> >> distributions, patches are welcome :-).  I myself am not too
> >> well-versed in init scripts.
> >
> > I opened bug for this several years ago, it was closed several times
> > as won't fix.
> >
> > Funny, isn't it?
>
> Aged bugs getting closed due to low priority or lack of resources is
> always something that will happen I suppose. But you are absolutely free
> to re-open them multiple times or even send fixes, call out the
> maintainers if they don't respond for patch reviews etc.

Can one of the bugs closed be added to this thread?


Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/441850968

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Posting a set of conversations around troubleshooting Gluster

[Sankarshan Mukhopadhyay]

is the link to the play list. We are at this point 2 episodes in.

I'd like to (a) keep this first pass as basic introduction to
troubleshooting (b) focus on the components which seem complicated
enough.

Requesting for feedback on which components we should cover next.
Please reply to this thread. Additionally, as an administrator/user,
if you have a set of scripts/tools which you use to troubleshoot and
would like to talk about them, let me know and we will set up a
conversation.
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] [request for feedback] starting a small series about troubleshooting GlusterFS

[Sankarshan Mukhopadhyay]

We've often seen threads on this list (and others) around
troubleshooting a component within GlusterFS leading to a bit of
back-and-forth while the minimum data sets are collected. In order to
increase the understanding and familiarity, we started off a series
with the first one being around a general approach to collecting data
for troubleshooting. You can listen to the episode at


The desired end outcome is that if we talk about something that is not
yet documented or, incompletely/inaccurately documented, we'll fix the
shortcomings with the documentation.

I'm also looking forward to feedback on what can be covered and would
be relevant. Please respond here or, on Twitter (@Gluster)
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Upgrade testing to gluster 6

[Sankarshan Mukhopadhyay]

Quite a considerable amount of detail here. Thank you!

On Fri, Mar 29, 2019 at 11:42 AM Hari Gowtham  wrote:
>
> Hello Gluster users,
>
> As you all aware that glusterfs-6 is out, we would like to inform you
> that, we have spent a significant amount of time in testing
> glusterfs-6 in upgrade scenarios. We have done upgrade testing to
> glusterfs-6 from various releases like 3.12, 4.1 and 5.3.
>
> As glusterfs-6 has got in a lot of changes, we wanted to test those portions.
> There were xlators (and respective options to enable/disable them)
> added and deprecated in glusterfs-6 from various versions [1].
>
> We had to check the following upgrade scenarios for all such options
> Identified in [1]:
> 1) option never enabled and upgraded
> 2) option enabled and then upgraded
> 3) option enabled and then disabled and then upgraded
>
> We weren't manually able to check all the combinations for all the options.
> So the options involving enabling and disabling xlators were prioritized.
> The below are the result of the ones tested.
>
> Never enabled and upgraded:
> checked from 3.12, 4.1, 5.3 to 6 the upgrade works.
>
> Enabled and upgraded:
> Tested for tier which is deprecated, It is not a recommended upgrade.
> As expected the volume won't be consumable and will have a few more
> issues as well.
> Tested with 3.12, 4.1 and 5.3 to 6 upgrade.
>
> Enabled, disabled before upgrade.
> Tested for tier with 3.12 and the upgrade went fine.
>
> There is one common issue to note in every upgrade. The node being
> upgraded is going into disconnected state. You have to flush the iptables
> and the restart glusterd on all nodes to fix this.
>

Is this something that is written in the upgrade notes? I do not seem
to recall, if not, I'll send a PR

> The testing for enabling new options is still pending. The new options
> won't cause as much issues as the deprecated ones so this was put at
> the end of the priority list. It would be nice to get contributions
> for this.
>

Did the range of tests lead to any new issues?

> For the disable testing, tier was used as it covers most of the xlator
> that was removed. And all of these tests were done on a replica 3 volume.
>

I'm not sure if the Glusto team is reading this, but it would be
pertinent to understand if the approach you have taken can be
converted into a form of automated testing pre-release.

> Note: This is only for upgrade testing of the newly added and removed
> xlators. Does not involve the normal tests for the xlator.
>
> If you have any questions, please feel free to reach us.
>
> [1] 
> https://docs.google.com/spreadsheets/d/1nh7T5AXaV6kc5KgILOy2pEqjzC3t_R47f1XUXSVFetI/edit?usp=sharing
>
> Regards,
> Hari and Sanju.
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] [Event CfP Announce] DevConf events India and US in the month of August 2019

[Sankarshan Mukhopadhyay]

2 editions of DevConf have their CfPs open

[1] DevConf India : https://devconf.info/in (event dates 02, 03 Aug
2019, Bengaluru)
[2] DevConf USA : https://devconf.info/us/ (event dates 15 -17 Aug,
2019, Boston)

The DevConf events are well curated to get a good mix of developers
and users. This note is to raise awareness and encourage submission of
talks around Gluster, containerized storage and similar.
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-infra] Gluster HA

[Sankarshan Mukhopadhyay]

[This email was originally posted to the gluster-infra list. Since
that list is used for coordination between members who work on the
infrastructure of the project, I am redirecting it to gluster-users
for better visibility and responses.]

On Thu, Mar 28, 2019 at 1:13 AM Guy Boisvert
 wrote:
>
> Hi,
>
>  New to this mailing list.  I'm seeking people advice for GlusterFS
> HA in the context of KVM Virtual Machines (VM) storage. We have 3 x KVM
> servers that use a 3 x GlusterFS nodes.  The Volumes are 3 way replicate.
>
>  My question is: You guys, what is your network architecture / setup
> for GlusterFS HA?  I read many articles on the internet. Many people are
> talking about bonding to a switch but i don't consider this as a good
> solution.  I'd like to have Gluster and KVM servers linked to at least 2
> switches to have switch / wire and network car redundancy.
>
>  I saw people using 2 x dumb switches with bonding mode 6 on their
> servers with mii monitoring.  It seems to be about good but it could
> append that mii is up but frames / packets won't flow. So it this case,
> i can't imagine how the servers would handle this.
>
>  Another setup is dual dumb switches and running Quagga on the
> servers (OSPF / ECMP).  This seems to be the best setup, what do you
> think?  Do you have experience with one of those setups?  What are your
> thoughts on this?  Ah and lastly, how can i search in the list?
>
>
> Thanks!
>
>
> Guy
>
> --
> Guy Boisvert, ing.
> IngTegration inc.
> http://www.ingtegration.com
> https://www.linkedin.com/pub/guy-boisvert/7/48/899/fr
>
> AVIS DE CONFIDENTIALITE : ce message peut contenir des
> renseignements confidentiels appartenant exclusivement a
> IngTegration Inc. ou a ses filiales. Si vous n'etes pas
> le destinataire indique ou prevu dans ce  message (ou
> responsable de livrer ce message a la personne indiquee ou
> prevue) ou si vous pensez que ce message vous a ete adresse
> par erreur, vous ne pouvez pas utiliser ou reproduire ce
> message, ni le livrer a quelqu'un d'autre. Dans ce cas, vous
> devez le detruire et vous etes prie d'avertir l'expediteur
> en repondant au courriel.
>
> CONFIDENTIALITY NOTICE : Proprietary/Confidential Information
> belonging to IngTegration Inc. and its affiliates may be
> contained in this message. If you are not a recipient
> indicated or intended in this message (or responsible for
> delivery of this message to such person), or you think for
> any reason that this message may have been addressed to you
> in error, you may not use or copy or deliver this message to
> anyone else. In such case, you should destroy this message
> and are asked to notify the sender by reply email.
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Transport endpoint is not connected failures in

[Sankarshan Mukhopadhyay]

On Wed, Mar 27, 2019 at 9:46 PM  wrote:
>
> Hello Amar and list,
>
>
>
> I wanted to follow-up to confirm that upgrading to 5.5 seem to fix the 
> “Transport endpoint is not connected failures” for us.
>
>
>
> We did not have any of these failures in this past weekend backups cycle.
>
>
>
> Thank you very much for fixing whatever was the problem.

As always, thank you for circling back to the list and sharing that
the issues have been addressed.
>
> I also removed some volume config options.  One or more of the settings was 
> contributing to the slow directory listing.
>
>
>
> Here is our current volume info.
>

This is very useful!

>
> [root@lonbaknode3 ~]# gluster volume info
>
>
>
> Volume Name: volbackups
>
> Type: Distribute
>
> Volume ID: 32bf4fe9-5450-49f8-b6aa-05471d3bdffa
>
> Status: Started
>
> Snapshot Count: 0
>
> Number of Bricks: 8
>
> Transport-type: tcp
>
> Bricks:
>
> Brick1: lonbaknode3.domain.net:/lvbackups/brick
>
> Brick2: lonbaknode4.domain.net:/lvbackups/brick
>
> Brick3: lonbaknode5.domain.net:/lvbackups/brick
>
> Brick4: lonbaknode6.domain.net:/lvbackups/brick
>
> Brick5: lonbaknode7.domain.net:/lvbackups/brick
>
> Brick6: lonbaknode8.domain.net:/lvbackups/brick
>
> Brick7: lonbaknode9.domain.net:/lvbackups/brick
>
> Brick8: lonbaknode10.domain.net:/lvbackups/brick
>
> Options Reconfigured:
>
> performance.io-thread-count: 32
>
> performance.client-io-threads: on
>
> client.event-threads: 8
>
> diagnostics.brick-sys-log-level: WARNING
>
> diagnostics.brick-log-level: WARNING
>
> performance.cache-max-file-size: 2MB
>
> performance.cache-size: 256MB
>
> cluster.min-free-disk: 1%
>
> nfs.disable: on
>
> transport.address-family: inet
>
> server.event-threads: 8
>
> [root@lonbaknode3 ~]#
>
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] recovery from reboot time?

[Sankarshan Mukhopadhyay]

On Tue, Mar 26, 2019 at 6:10 PM Alvin Starr  wrote:
>
> After almost a week of doing nothing the brick failed and we were able to 
> stop and restart glusterd and then could start a manual heal.
>
> It was interesting when the heal started the time to completion was just 
> about 21 days but as it worked through the 30 some entries it got faster 
> to the point where it completed in 2 days.
>
> Now I have 2 gfids that refuse to heal.
>

Do you need help from the developers on that topic?
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Help analise statedumps

[Sankarshan Mukhopadhyay]

On Tue, Mar 19, 2019 at 11:09 PM Pedro Costa  wrote:

> Sorry to revive old thread, but just to let you know that with the latest 5.4 
> version this has virtually stopped happening.
>
> I can’t ascertain for sure yet, but since the update the memory footprint of 
> Gluster has been massively reduced.
>
> Thanks to everyone, great job.

Good news is always fantastic to hear! Thank you for reviving the
thread and providing feedback.
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-Maintainers] Proposal to mark few features as Deprecated / SunSet from Version 5.0

[Sankarshan Mukhopadhyay]

Now that there are sufficient detail in place, could a Gluster team
member file a RHBZ and post it back to this thread?

On Wed, Mar 20, 2019 at 2:51 AM Jim Kinney  wrote:
>
> Volume Name: home
> Type: Replicate
> Volume ID: 5367adb1-99fc-44c3-98c4-71f7a41e628a
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp,rdma
> Bricks:
> Brick1: bmidata1:/data/glusterfs/home/brick/brick
> Brick2: bmidata2:/data/glusterfs/home/brick/brick
> Options Reconfigured:
> performance.client-io-threads: off
> storage.build-pgfid: on
> cluster.self-heal-daemon: enable
> performance.readdir-ahead: off
> nfs.disable: off
>
>
> There are 11 other volumes and all are similar.
>
>
> On Tue, 2019-03-19 at 13:59 -0700, Vijay Bellur wrote:
>
> Thank you for the reproducer! Can you please let us know the output of 
> `gluster volume info`?
>
> Regards,
> Vijay
>
> On Tue, Mar 19, 2019 at 12:53 PM Jim Kinney  wrote:
>
> This python will fail when writing to a file in a glusterfs fuse mounted 
> directory.
>
> import mmap
>
> # write a simple example file
> with open("hello.txt", "wb") as f:
> f.write("Hello Python!\n")
>
> with open("hello.txt", "r+b") as f:
> # memory-map the file, size 0 means whole file
> mm = mmap.mmap(f.fileno(), 0)
> # read content via standard file methods
> print mm.readline()  # prints "Hello Python!"
> # read content via slice notation
> print mm[:5]  # prints "Hello"
> # update content using slice notation;
> # note that new content must have same size
> mm[6:] = " world!\n"
> # ... and read again using standard file methods
> mm.seek(0)
> print mm.readline()  # prints "Hello  world!"
> # close the map
> mm.close()
>
>
>
>
>
>
>
> On Tue, 2019-03-19 at 12:06 -0400, Jim Kinney wrote:
>
> Native mount issue with multiple clients (centos7 glusterfs 3.12).
>
> Seems to hit python 2.7 and 3+. User tries to open file(s) for write on long 
> process and system eventually times out.
>
> Switching to NFS stops the error.
>
> No bug notice yet. Too many pans on the fire :-(
>
> On Tue, 2019-03-19 at 18:42 +0530, Amar Tumballi Suryanarayan wrote:
>
> Hi Jim,
>
> On Tue, Mar 19, 2019 at 6:21 PM Jim Kinney  wrote:
>
>
> Issues with glusterfs fuse mounts cause issues with python file open for 
> write. We have to use nfs to avoid this.
>
> Really want to see better back-end tools to facilitate cleaning up of 
> glusterfs failures. If system is going to use hard linked ID, need a mapping 
> of id to file to fix things. That option is now on for all exports. It should 
> be the default If a host is down and users delete files by the thousands, 
> gluster _never_ catches up. Finding path names for ids across even a 40TB 
> mount, much less the 200+TB one, is a slow process. A network outage of 2 
> minutes and one system didn't get the call to recursively delete several 
> dozen directories each with several thousand files.
>
>
>
> Are you talking about some issues in geo-replication module or some other 
> application using native mount? Happy to take the discussion forward about 
> these issues.
>
> Are there any bugs open on this?
>
> Thanks,
> Amar
>
>
>
>
> nfs
> On March 19, 2019 8:09:01 AM EDT, Hans Henrik Happe  wrote:
>
> Hi,
>
> Looking into something else I fell over this proposal. Being a shop that are 
> going into "Leaving GlusterFS" mode, I thought I would give my two cents.
>
> While being partially an HPC shop with a few Lustre filesystems,  we chose 
> GlusterFS for an archiving solution (2-3 PB), because we could find files in 
> the underlying ZFS filesystems if GlusterFS went sour.
>
> We have used the access to the underlying files plenty, because of the 
> continuous instability of GlusterFS'. Meanwhile, Lustre have been almost 
> effortless to run and mainly for that reason we are planning to move away 
> from GlusterFS.
>
> Reading this proposal kind of underlined that "Leaving GluserFS" is the right 
> thing to do. While I never understood why GlusterFS has been in feature crazy 
> mode instead of stabilizing mode, taking away crucial features I don't get. 
> With RoCE, RDMA is getting mainstream. Quotas are very useful, even though 
> the current implementation are not perfect. Tiering also makes so much sense, 
> but, for large files, not on a per-file level.
>
> To be honest we only use quotas. We got scared of trying out new performance 
> features that potentially would open up a new back of issues.
>
> Sorry for being such a buzzkill. I really wanted it to be different.
>
> Cheers,
> Hans Henrik
>
> On 19/07/2018 08.56, Amar Tumballi wrote:
>
> Hi all,
>
> Over last 12 years of Gluster, we have developed many features, and continue 
> to support most of it till now. But along the way, we have figured out better 
> methods of doing things. Also we are not actively maintaining some of these 
> features.
>
> We are now thinking of cleaning up some of these ‘unsupported’ features, and 
> mark them as 

Re: [Gluster-users] NFS export of gluster - solution

[Sankarshan Mukhopadhyay]

On Tue, Mar 19, 2019 at 9:25 AM Jiffin Thottan  wrote:
>
> Thanks Valerio for sharing the information
>
> - Original Message -
> From: "Valerio Luccio" 
> To: "gluster-users" 
> Sent: Monday, March 18, 2019 8:37:46 PM
> Subject: [Gluster-users] NFS export of gluster - solution
>
> So, I recently start NFS exporting of my gluster so that I could mount
> it from a legacy Mac OS X server. Every 24/36 hours the export seemed to
> freeze causing the server to seize up. The ganesha log was filled with
> errors related to RQUOTA. Frank Filz of the nfs-ganesha suggested that
> I'd try setting "Enable_RQUOTA = false;" in the NFS_CORE_PARAM config
> block of the ganesha.conf file and that seems to have done the trick, 5
> days and counting without a problem.
>

Does this configuration change need to be updated in any existing
documentation (for Gluster, nfs-ganesha)?
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-Maintainers] Release 6: Release date update

[Sankarshan Mukhopadhyay]

On Wed, Mar 13, 2019 at 7:55 AM Shyam Ranganathan  wrote:
>
> On 3/5/19 1:17 PM, Shyam Ranganathan wrote:
> > Hi,
> >
> > Release-6 was to be an early March release, and due to finding bugs
> > while performing upgrade testing, is now expected in the week of 18th
> > March, 2019.
> >
> > RC1 builds are expected this week, to contain the required fixes, next
> > week would be testing our RC1 for release fitness before the release.
>
> RC1 is tagged, and will mostly be packaged for testing by tomorrow.
>
> Expect package details in a day or two, to aid with testing the release.

Would be worth posting it out via Twitter as well. Do we plan to
provide any specific guidance on testing particular areas/flows? For
example, upgrade tests with some of the combinations - I recollect
Amar had published a spreadsheet of items - should we continue with
those?
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gluster.org Blog - Call for Posts: Sept 11-30

[Sankarshan Mukhopadhyay]

On Mon, Sep 10, 2018 at 10:57 PM Amye Scavarda  wrote:
>
> We're putting out a call for posts for the Gluster.org blog over the next few 
> months. Within the gluster ecosystem, we have a social-me...@gluster.org list 
> to help highlight posts, whether that's something that's already posted 
> elsewhere on the web or something that should go on the main gluster.org blog.
>
> However, the social-media@ list has editors on it as well to help your 
> content get out there!
>
> What are we looking for?
>
> Gluster-related topics!
>
> Specifically, if you submitted an abstract for a conference and are still 
> interested in writing on that topic, this is a great place for you!
> This will also help with upcoming calls for papers, like DevConf.CZ/FOSDEM. 
> (October 26 for DevConf.cz, FOSDEM may have a Software Defined Storage 
> DevRoom)
>
> This can also include: case studies, problems you've run into with Gluster 
> and resolved, features you're working on that you'd like to describe in more 
> detail.
>

In recent times I've seen a few posts on -users around troubleshooting
of scenarios. I was wondering (if the participant is willing) about
doing small conversations/interviews around monitoring/troubleshooting
that these practitioners are undertaking. And as an extension to that
- whether "Gluster in containers" is a thing that we see users
adopting/deploying.

> Let me know if you have questions, this call for posts runs from September 
> 11th through September 30th. After that, I'll work with interested folks to 
> edit and publish to the gluster.org blog.
>
> Thanks!
> - amye
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade from 3.13 ?

[Sankarshan Mukhopadhyay]

On Fri, Sep 14, 2018 at 12:19 PM Nicolas SCHREVEL
 wrote:
>
> Le 13/09/2018 à 16:01, Shyam Ranganathan a écrit :
> > On 09/13/2018 09:52 AM, John Strunk wrote:
> >> I believe the ask is also around instructions for actually obtaining the
> >> new bits from the distros... what repos need to be changed (if any) and
> >> whether old packages need to be removed.
> > Agree, I was looking at that as the latter part of the question, with
> > the former around 3.13 missing in reference.
> >
> > I do not have enough Ubuntu fu to answer that one, so leaving that out
> > for now.
>
> OK i'll try theses steps then :
>
> 1. Like in upgrade Guide, i will stop Gluster and Services (Step 1,1
> from https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/)
> 2. Remove PPA 3.13 : sudo ppa-purge ppa:gluster/glusterfs-3.13 && sudo
> apt-get update
> 3. Add PPA 4.1 : sudo add-apt-repository ppa:gluster/glusterfs-4.1 &&
> sudo apt-get update
> 4. Install Gluster 4.1 : sudo apt-get install glusterfs-server

... and if these do work out for you, please let us know and we can
add the detail to the document. Shyam has an issue tracking this

___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gluster Documentation Hackathon - 7/19 through 7/23

[Sankarshan Mukhopadhyay]

Was a round-up/summary about this published to the lists?

On Wed, Jul 18, 2018 at 10:27 PM, Vijay Bellur  wrote:
> Hey All,
>
> We are organizing a hackathon to improve our upstream documentation. More
> details about the hackathon can be found at [1].
>
> Please feel free to let us know if you have any questions.
>
> Thanks,
> Amar & Vijay
>
> [1]
> https://docs.google.com/document/d/11LLGA-bwuamPOrKunxojzAEpHEGQxv8VJ68L3aKdPns/edit?usp=sharing
>



-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Subject: Help needed in improving monitoring in Gluster

[Sankarshan Mukhopadhyay]

On Mon, Jul 23, 2018 at 8:24 PM, Maarten van Baarsel
 wrote:
> On 23/07/18 16:03, Pranith Kumar Karampuri wrote:
>
>> We want gluster's monitoring/observability to be as easy as possible going
>> forward. As part of reaching this goal we are starting this initiative to
>> add improvements to existing apis/commands and create new apis/commands to
>> gluster so that the admin can integrate it with whichever monitoring tool
>> he/she likes. The gluster-prometheus project hosted at
>> https://github.com/gluster/gluster-prometheus is the direction in which we
>> feel metrics can be collected and distributed from a Gluster cluster
>> enabling analysis and visualization.
>>
>>
>> As a first step we want to hear from you what you feel needs to be
>> addressed.
>
>
> Regarding monitoring; I would love to see in my monitoring that
> geo-replication is working as intended; at the moment I'm faking georep
> monitoring by having a process touch a file (every server involved in
> gluster touches another file) on every volume and checking mtime on the
> slave.
>

I'd like to request that if possible, you elaborate on how you'd like
to see the "as intended" situation. What kind of data points and/or
visualization would aid you in arriving at that conclusion?
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Announcing Glusterfs release 3.12.8 (Long Term Maintenance)

[Sankarshan Mukhopadhyay]

On Thu, Apr 19, 2018 at 9:25 AM, Jiffin Tony Thottan
 wrote:
> The Gluster community is pleased to announce the release of Gluster 3.12.8
> (packages available at [1,2,3]).
>
> Release notes for the release can be found at [4].
>

The link to the release notes have a banner "You are viewing outdated
content. We have moved to docs.gluster.org." Perhaps that should be
the URL to use cf.
<https://docs.gluster.org/en/latest/release-notes/3.12.8/>


>
> [1] https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.8/
> [2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12
> [3] https://build.opensuse.org/project/subprojects/home:glusterfs
> [4] Release notes:
> https://gluster.readthedocs.io/en/latest/release-notes/3.12.8/
>
>



-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Replacing a third data node with an arbiter one

[Sankarshan Mukhopadhyay]

On Fri, Jan 26, 2018 at 7:05 AM, Ravishankar N  wrote:
>
>
> On 01/24/2018 07:20 PM, Hoggins! wrote:
>
> Hello,
>
> The subject says it all. I have a replica 3 cluster :
>
> gluster> volume info thedude
>
> Volume Name: thedude
> Type: Replicate
> Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 3 = 3
> Transport-type: tcp
> Bricks:
> Brick1: ngluster-1.network.hoggins.fr:/export/brick/thedude
> Brick2: ngluster-2.network.hoggins.fr:/export/brick/thedude
> Brick3: ngluster-3.network.hoggins.fr:/export/brick/thedude
> Options Reconfigured:
> cluster.server-quorum-type: server
> transport.address-family: inet
> nfs.disable: on
> performance.readdir-ahead: on
> client.event-threads: 8
> server.event-threads: 15
>
>
> ... and I would like to replace, say ngluster-2 with an arbiter-only
> node, without any data. Is that possible ? How ?
>
> Yes, you would need to reduce it to replica 2 and then convert it to
> arbiter.
> 1. Ensure there are no pending heals, i.e. heal info shows zero entries.
> 2. gluster volume remove-brick thedude replica 2
> ngluster-3.network.hoggins.fr:/export/brick/thedude force
> 3. gluster volume add-brick thedude replica 3 arbiter 1  the new arbiter brick>
>

Would it be good to have this small sequence of steps noted down
somewhere other than a mailing list archive? I imagine this is going
to be sought out by a few more users choosing this course.
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Adding a slack for communication?

[Sankarshan Mukhopadhyay]

On 09-Nov-2017 03:53, "Amye Scavarda"  wrote:

>From today's community meeting, we had an item from the issue queue:
https://github.com/gluster/community/issues/13

Should we have a Gluster Community slack team? I'm interested in
everyone's thoughts on this.


Will this be in addition to the Gitter.im channel which exists? Being
present on multiple popular places isn't a bad thing. Does Slack offer a
fully featured instance for communities?

- amye

--
Amye Scavarda | a...@redhat.com | Gluster Community Lead
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Gluster Health Report tool

[Sankarshan Mukhopadhyay]

On Thu, Oct 26, 2017 at 2:24 AM, Marcin Dulak  wrote:
> Hi,
>
> since people are suggesting nagios then I can't resist suggesting exporting
> the metrics in the prometheus format,
> or at least making the project into a library so
> https://github.com/prometheus/client_python could be used to export the
> prometheus metrics.
> There has been an attempt at https://github.com/ofesseler/gluster_exporter
> but it is not maintained anymore.
>

There is an on-going effort which provides a monitoring dashboard for
a Gluster cluster. Some detail at
<https://github.com/Tendrl/documentation/wiki/Metrics> At present the
stack is not consuming Prometheus, however, the team is looking at
switching over so as to make a more malleable dashboard. There is of
course a Gitter channel at <https://gitter.im/Tendrl/tendrl-devel>
Install+configure instructions for the latest release are at
<https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.3-(install-guide)>


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] NFS Ganesha

[Sankarshan Mukhopadhyay]

On Thu, Jul 6, 2017 at 10:04 PM, Anthony Valentine
 wrote:
> Hello!
>
>
>
> I am attempting to setup a Gluster install using Ganesha for NFS using the
> guide found here
> http://blog.gluster.org/2015/10/linux-scale-out-nfsv4-using-nfs-ganesha-and-glusterfs-one-step-at-a-time/
>
>
>
> The Gluster portion is working fine, however when I try to setup Ganesha I
> have a problem.  The guide says to run ‘gluster nfs-ganesha enable’ however
> when I do, I get the following error:
>
>
>
> [root@glustertest1 ~]# gluster nfs-ganesha enable
>
> unrecognized word: nfs-ganesha (position 0)
>
>
>
> Has this command changed?  If so, what is the new command?  If not, why
> would I be getting this error?
>
>
>
> Is there a more recent guide that I should be following?
>

<http://lists.gluster.org/pipermail/gluster-devel/2016-July/050077.html>
: using gdeploy to set up NFS Ganesha might lead to better results.


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Idea: Alternate Release process

[Sankarshan Mukhopadhyay]

ow what you guys think.
>>>>>>
>>>>> This reduces the number of versions that we need to maintain,
>>>>> which I like.
>>>>> Having official test (beta) releases should help get features
>>>>> out to
>>>>> testers hand faster,
>>>>> and get quicker feedback.
>>>>>
>>>>> One thing that's still not quite clear to is the issue of backwards
>>>>> compatibility.
>>>>> I'm still thinking it thorough and don't have a proper answer to
>>>>> this yet.
>>>>> Would a new release be backwards compatible with the previous
>>>>> release?
>>>>> Should we be maintaining compatibility with LTS releases with the
>>>>> latest release?
>>>>
>>>> Each LTS release will have seperate list of features to be
>>>> enabled. If we make any breaking changes(which are not backward
>>>> compatible) then it will affect LTS releases as you mentioned.
>>>> But we should not break compatibility unless it is major version
>>>> change like 4.0. I have to workout how we can handle backward
>>>> incompatible changes.
>>>>
>>>>> With our current strategy, we at least have a long term release
>>>>> branch,
>>>>> so we get some guarantees of compatibility with releases on the
>>>>> same branch.
>>>>>
>>>>> As I understand the proposed approach, we'd be replacing a stable
>>>>> branch with the beta branch.
>>>>> So we don't have a long-term release branch (apart from LTS).
>>>>
>>>> Stable branch is common for LTS releases also. Builds will be
>>>> different using different list of features.
>>>>
>>>> Below example shows stable release once in 6 weeks, and two LTS
>>>> releases in 6 months gap(3.8 and 3.12)
>>>>
>>>> LTS 1 : 3.83.8.1  3.8.2  3.8.3   3.8.4   3.8.5...
>>>> LTS 2 :  3.123.12.1...
>>>> Stable: 3.83.93.10   3.113.123.13...
>>>>>
>>>>> A user would be upgrading from one branch to another for every
>>>>> release.
>>>>> Can we sketch out how compatibility would work in this case?
>>>>
>>>> User will not upgrade from one branch to other branch, If user
>>>> interested in stable channel then upgrade once in 6 weeks. (Same
>>>> as minor update in current release style)
>>>>>
>>>>>
>>>>> This approach work well for projects like Chromium and Firefox,
>>>>> single
>>>>> system apps
>>>>>   which generally don't need to be compatible with the previous
>>>>> release.
>>>>> I don't understand how the Rust  project uses this (I am yet to
>>>>> read
>>>>> the linked blog post),
>>>>> as it requires some sort of backwards compatibility. But it too
>>>>> is a
>>>>> single system app,
>>>>> and doesn't have the compatibility problems we face.
>>>>>
>>>>> Gluster is a distributed system, that can involve multiple
>>>>> different
>>>>> versions interacting with each other.
>>>>> This is something we need to think about.
>>>>
>>>> I need to think about compatibility, What new problems about the
>>>> compatibility with this approach compared to our existing release
>>>> plan?
>>>>>
>>>>>
>>>>> We could work out some sort of a solution for this though.
>>>>> It might be something very obvious I'm missing right now.
>>>>>
>>>>> ~kaushal
>>>>>
>>>>>> --
>>>>>> regards
>>>>>> Aravinda

-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Show and Tell sessions for Gluster 4.0

[Sankarshan Mukhopadhyay]

On Mon, May 9, 2016 at 11:55 AM, Atin Mukherjee  wrote:
> 1. We use the weekly community meeting slot once in a month
> or 2. Have a dedicated separate slot (probably @ 12:00 UTC, last
> Thursday of each month)

[2] would be nicer to set up a calendar for.


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] question about how to handle bugs filed against End-Of-Life versions of glusterfs

[Sankarshan Mukhopadhyay]

[for reference]

On Wed, Sep 16, 2015 at 6:35 PM, Kaleb S. KEITHLEY  wrote:
> As an example, Fedora simply closes any remaining open bugs when the
> version reaches EOL. It's incumbent on the person who filed the bug to
> reopen it if it still exists in newer versions.

<https://fedoraproject.org/wiki/BugZappers/HouseKeeping> - All bugs
for EOL releases are automatically closed on the EOL date after
providing a warning in the bug comments, 30 days prior to EOL.

<https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#End_of_Life_.28EOL.29_product>
- The bug is reported against a version of Fedora that is no longer
maintained.Thank you for your bug report.We are sorry, but the Fedora
Project is no longer releasing bug fixes or any other updates for this
version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect
this, but please reopen it if the problem persists after upgrading to
the latest version of Fedora, which is available
from:http://fedoraproject.org/get-fedora





-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [RfC] proposed changes to the weekly news letter

[Sankarshan Mukhopadhyay]

On Wed, Aug 19, 2015 at 3:30 PM, Niels de Vos  wrote:
> On Wed, Aug 19, 2015 at 12:23:35PM +0530, Sankarshan Mukhopadhyay wrote:
>> On Wed, Aug 19, 2015 at 10:34 AM, Niels de Vos  wrote:
>> > On Wed, Aug 19, 2015 at 09:58:03AM +0530, Sankarshan Mukhopadhyay wrote:
>> >> <https://public.pad.fsfe.org/p/mock-gluster-weekly-news> is a set of
>> >> changes - introduction of more sections (to have a larger group of
>> >> contributors/editors); a new template (includes download, outreach and
>> >> so forth URLs)
>> >
>> > Thanks for the ideas! I've added some notes and references in the
>> > etherpad too.
>>
>> Thank you. Essentially, I am looking at understanding the following
>> (in no particular order)
>>
>> (+) is this form of the template useful to have
>> (+) can we use this template to have multiple contributors for the
>> various sections
>>
>> If the feedback is "yes/sort of", can we seek more volunteer contributors?
>
> Yes, I think this should work and allows multiple contributors without
> issues.

Alright. So, what would be the next step from here? Would the project
be interested in adopting this template for future newsletters? And
how does the call for volunteers for the different sections usually
work out?


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [RfC] proposed changes to the weekly news letter

[Sankarshan Mukhopadhyay]

On Wed, Aug 19, 2015 at 10:34 AM, Niels de Vos  wrote:
> On Wed, Aug 19, 2015 at 09:58:03AM +0530, Sankarshan Mukhopadhyay wrote:
>> <https://public.pad.fsfe.org/p/mock-gluster-weekly-news> is a set of
>> changes - introduction of more sections (to have a larger group of
>> contributors/editors); a new template (includes download, outreach and
>> so forth URLs)
>
> Thanks for the ideas! I've added some notes and references in the
> etherpad too.

Thank you. Essentially, I am looking at understanding the following
(in no particular order)

(+) is this form of the template useful to have
(+) can we use this template to have multiple contributors for the
various sections

If the feedback is "yes/sort of", can we seek more volunteer contributors?

The pondering about the Twitter handle(s)/IRC nick was around whether
it would make sense to add one/both so as to make readers aware and
familiar with the individuals and their social presence. So, a line
like "Atin indicates that the "failed after update on centos 7"
http://article.gmane.org/gmane.comp.file-systems.gluster.user/21924
could actually be a split-brain issue and suggests a recovery path"
would include Atin's Twitter handle or, IRC nick in parentheses.

I am not familiar with which page on the new docs page has the
features link. The section is proposed to be added so as to highlight
a clear feature path to any readers of the weekly news. My general
assumption is that acquiring more and new readers is an implied goal.
The FB and other social media presence is available in the "Get in
Touch" section at the end.

Does the project have any "Easy Fix" bugs we can view via a query and
thus encourage new contributors to take a look at?


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] [RfC] proposed changes to the weekly news letter

[Sankarshan Mukhopadhyay]

<https://public.pad.fsfe.org/p/mock-gluster-weekly-news> is a set of
changes - introduction of more sections (to have a larger group of
contributors/editors); a new template (includes download, outreach and
so forth URLs)

-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Gluster News of the week #30/2015

[Sankarshan Mukhopadhyay]

On Tue, Aug 18, 2015 at 6:02 PM, M S Vishwanath Bhat  wrote:
>
>
> On 18 August 2015 at 08:09, Sankarshan Mukhopadhyay
>  wrote:

>> Who can help me see how this plays out by adding a few lines and text
>> around the commits?
>
>
> I just added few lines of commits which happened in last week. We might have
> to select the major commits in case there are many.

Thank you! I'll try to work through some more threads across the
various lists and add. At present I am somewhat stumped around
discovering more "news" pieces. The #gluster on Twitter isn't the very
best source.


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Gluster News of the week #30/2015

[Sankarshan Mukhopadhyay]

On Tue, Aug 18, 2015 at 12:44 AM, M S Vishwanath Bhat  wrote:
>
>
> On 17 August 2015 at 21:44, Sankarshan Mukhopadhyay
>  wrote:

>> And now, a very primitive first draft of what it could look like -
>> <https://public.pad.fsfe.org/p/mock-gluster-weekly-news>
>>
>> (If the pad does get borked, here's the content pasted)
>>
>> Feedback welcome and appreciated.
>
>
> +1 This seems better.

Thank you!

> In commit logs we can mention about the major bug fixes and feature commits
> of the past week.

Who can help me see how this plays out by adding a few lines and text
around the commits?




-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Gluster News of the week #30/2015

[Sankarshan Mukhopadhyay]

On Mon, Aug 17, 2015 at 10:35 AM, sankarshan
 wrote:
> On Mon, 17 Aug 2015 06:27:53 +0200, Niels de Vos wrote:
>
>> It would be good to have some standard structure that includes
>> interesting statistics.
>
> I'm not absolutely sure about the statistics but I was thinking about
> highlighting specific threads that are interesting.

And now, a very primitive first draft of what it could look like -
<https://public.pad.fsfe.org/p/mock-gluster-weekly-news>

(If the pad does get borked, here's the content pasted)

Feedback welcome and appreciated.

/s

=== BEGIN ===

This is the work-in-progress mock "Gluster Weekly News" pad.

The proposed approach is to (a) break out the weekly news into
sections (b) addition of content to the sections can be managed by
specific contributors


Week 33: 17-23 August - assigned blog poster for this week:


== News about the Gluster Project from around the world

TBD: work out more avenues than just #gluster on Twitter

== Conversations from the mailing lists

Avra responded to a query around backup -
http://article.gmane.org/gmane.comp.file-systems.gluster.user/21936
suggesting that snapshots of the volume is a preferred "good" approach

Atin indicates that the "failed after update on centos 7"
http://article.gmane.org/gmane.comp.file-systems.gluster.user/21924
could actually be a split-brain issue and suggests a recovery path

Interesting thread around a single node cluster -
http://article.gmane.org/gmane.comp.file-systems.gluster.user/21912
with Kaushal deducing that the issue might be due to name
resolution/FQDN being at fault. More
athttp://article.gmane.org/gmane.comp.file-systems.gluster.user/21940


== Commit Logs



== Meetup News and Events

http://kvmforum2015.sched.org/event/43b9efa496fa5ecf0effa0e98ce2aeba -
Martin Sivak talks about oVirt and Gluster - Hyperconvergence

http://www.meetup.com/glusterfs-India/events/01221/ - GlusterFS
group has a meetup at Bangalore; distaf and more will be talked about




-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Gluster News of the week #30/2015

[Sankarshan Mukhopadhyay]

On Thu, Aug 13, 2015 at 9:31 PM, M S Vishwanath Bhat  wrote:
> You can find the gluster news of the week #30/2015 below
>
> https://medium.com/@msvbhat/gluster-news-of-the-week-30-2015-30452f44a144

Thanks.

> You should be able to see the same in www.planet.gluster.org very shortly.
>
> If you have anything that needs to be mentioned in news of the week, please
> add them here at https://public.pad.fsfe.org/p/gluster-weekly-news

I didn't want to mess up the template but I was wondering whether
expanding the content of the Weekly Newsletter would be a nice thing
to do? For example, <http://llvmweekly.org/issue/84> mixes "news about
the project" with some notes about commits. For Gluster we could
consider "news about Gluster", "summary of some discussions from
lists" etc. I'll try to pull together a mock newsletter (with content)
and post it back, if the idea about expanding seems nice.



-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

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

[Sankarshan Mukhopadhyay]

On Mon, Jun 22, 2015 at 5:24 PM, Shravan Chandrashekar
 wrote:
> 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.

There are a couple of aspects which need to be quickly looked through.

(a) a write-up of somewhat detail providing an overview of the new
workflow; how contributors can participate; reviewing mechanism for
patches against documentation; merge and release paths/cadence

(b) at <http://review.gluster.org/#/c/11129/> Niels has a comment
about "about design of structures used in the code" and how he thinks
that it is appropriate if "it stays part of the sources and does not
move out."

He also says "For example, I would like to document some of the memory
layout structures and functions, but this documentation will include
source-code comments and a .txt or .md file with additional details.
Spitting that makes it more difficult to keep in sync."

In this particular example, I'd probably say that it would be better
that such documentation is also part of the docs repo. It lends itself
to re-use as and when required (this particular example seems re-use
friendly).

I'd request that this switch-over to the new workflow and repositories
go ahead with the absolute "documentation" content. Examples/cases
like the above mentioned by Niels can be resolved via discussion and
probably not block the switch.

> 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




-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] GlusterFS Documentation Improvements - An Update

[Sankarshan Mukhopadhyay]

On Wed, May 27, 2015 at 7:48 PM, Humble Devassy Chirammal
 wrote:
> Whats changing for community members?
>
> A very simplified contribution workflow.
>
> - How to Contribute?
>
> Contributing to the documentation requires a github account. To edit on
> github, fork the repository (see top-right of the screen, under your
> username). You will then be able to make changes easily. Once done, you can
> create a pull request and get the changes reviewed and merged into the
> official repository.
> With this simplified workflow, the documentation is no longer maintained in
> gluster/glusterfs/docs directory but it has a new elevated status in the
> form of a new project: gluster/glusterdocs
> (https://github.com/gluster/glusterdocs) and currently this project is being
> maintained by Anjana Sriram, Shravan and Humble.

Thanks for writing this up. Can this workflow/sequence be also visited
from the repo of the docs? It would perhaps be required to put this as
"How to contribute?"

> - What to Contribute
>
> Really, anything that you think has value to the GlusterFS developer
> community. While reading the docs you might find something incorrect or
> outdated. Fix it! Or maybe you have an idea for a tutorial, or for a topic
> that isn’t covered to your satisfaction. Create a new page and write it up!

+ FAQs and Common Issues/Known Issues etc

> Whats Next?
>
> Since the GlusterFS documentation has a new face-lift, MediaWiki will no
> longer be editable but will only be READ ONLY view mode. Hence, all the
> work-in-progress design notes which were maintained on MediaWiki will be
> ported to the GitHub repository and placed in "Feature Plans" folder. So,
> when you want to upload your work in progess documents you must do a pull
> request after the changes are made. This outlines the change in workflow as
> compared to MediaWiki.

It would be of benefit and advantage to have the read-only mode turned
on. This would help avoid 'split-brains' and also create a single
incoming path for content that needs to be maintained as part of the
Documentation community.

> A proposal:
>
> Another way to maintain work-in-progress documents in Google docs (or any
> other colloborative editing tool) and link them as an index entry in Feature
> Plans page on GitHub. This can be an excellent way to track a document
> through multiple rounds of collaborative editing in real time.

This is a sound idea as well :)


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Updated website needs your help for content!

[Sankarshan Mukhopadhyay]

On Wed, Apr 29, 2015 at 7:04 PM, Tuomas Kuosmanen  wrote:
> * How would be the best way to install? We need to write the
> instructions, and those should be simple and still sensible
> so that you get a real, functional setup in the end that you
> can use. Maybe some example use cases, like making an office
> NAS with replication, or something?
>
> I guess the install guide is something people are working on
> already, so that could help on this part.

and perhaps exploring the ways to get started with install. That is, a
quick start guide that begins at where to download from and takes the
user on a journey to a functional set up (using some sensible
defaults?)

-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] How to search frequently asked questions in gluster mailing lists.

[Sankarshan Mukhopadhyay]

On Sat, Apr 18, 2015 at 8:35 PM, Justin Clift  wrote:
> On 18 Apr 2015, at 16:01, Niels de Vos  wrote:
>> On Sat, Apr 18, 2015 at 03:14:41PM +0100, Justin Clift wrote:
>>> On 18 Apr 2015, at 07:49, Raghavendra Talur  
>>> wrote:
>>> 
>>>> Use the second search box, the one below "Google search for Gluster".
>>>> Works for me on both Chrome and Firefox on Android and Fedora 21.
>>>> Please try again and let me know :)
>>>
>>> Errr, which second search box? :)
>>>
>>>  http://ded.ninja/gluster/custom_google_search_screenshot.png
>>
>> This one, use Fedora and Firefox?
>>
>>http://i.imgur.com/cCGmOdK.png
>
> Are you guys not using ad blockers?

I have Ad blocker extensions enabled on Chrome Version 42.0.2311.90
(64-bit) and I do see the custom search box as in screenshot put up by
Niels.


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Guidelines for posting in our mailing lists

[Sankarshan Mukhopadhyay]

On Fri, Apr 17, 2015 at 5:46 PM, Niels de Vos  wrote:
> I tend to use gmane.org for searching. The archives are available there
> too:
>
> http://news.gmane.org/gmane.comp.file-systems.gluster.user

It would be nice to have a link to the gmane.org archives in the list
email footer.


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] How to search frequently asked questions in gluster mailing lists.

[Sankarshan Mukhopadhyay]

On Sat, Apr 18, 2015 at 7:44 PM, Justin Clift  wrote:
> Errr, which second search box? :)
>
>   http://ded.ninja/gluster/custom_google_search_screenshot.png

On Chrome I see a search box under the "Google search for Gluster"



-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Guidelines for posting in our mailing lists

[Sankarshan Mukhopadhyay]

On Fri, Apr 17, 2015 at 11:56 AM, Vijay Bellur  wrote:
> I wonder if we should evolve guidelines for posting in the lists along the
> lines of the Fedora one [1]. It could be useful for new entrants in the
> community to understand our mailing list etiquette.

It would be good to have a set of guidelines which enable the new
participants find their way around the community and learn about
interactions.


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] Revamping the GlusterFS Documentation...

[Sankarshan Mukhopadhyay]

On Mon, Mar 23, 2015 at 12:31 PM, Shravan Chandrashekar
 wrote:
> Hence, we started by curating content from various sources including
> gluster.org static HTML documentation, glusterfs github repository,
> various blog posts and the Community wiki. We also felt the need to improve
> the community member's experience with Gluster documentation. This led us to
> put some thought into the user interface. As a result we came up with a page
> which links all content into a single landing page:
>
> http://www.gluster.org/community/documentation/index.php/Staged_Docs
>
> This is just our first step to improve our community docs and enhance the
> community contribution towards documentation.

This is a strong first step. Thank you for pulling this together. The
feedback at 
<https://www.gluster.org/pipermail/gluster-users/2015-March/021275.html>
would indicate that there is a need to put together a blueprint for a
workflow that makes it more easy to contribute, administer and
maintain in a state of publication-readiness.


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gluster project site revamp update

[Sankarshan Mukhopadhyay]

On Tue, Apr 7, 2015 at 9:42 PM, Soumya Deb  wrote:

> I've put together some more stuff on the site.
> Staging URL: http://code.debs.io/glusterweb/

The addition of new aspects/content to the staging site is not
immediately obvious. If you are publishing/deploying the content from
a repo, can you add the link to a Changelog of sorts?

> Also, we probably can go on without the event-map - not much to show.

The present count of events may be less -> nil. This is expected to
change substantially with the upcoming release. It would be helpful
for a new visitor to be able to use the event-map feature aligned with
events for the new release (release parties; get-together; meetups
etc)

> - Sankarshan Mukhopadhyay  wrote:
>> On Mon, Mar 30, 2015 at 5:28 PM, Soumya Deb  wrote:
>> > Here's the staging page: http://code.debs.io/glusterweb/
>>
>> This looks nice and is a good change from the current look-n-feel.
>
> Thanks, glad that you liked the change.
>
>> I wonder if you would consider figuring out how to include the "Try"
>> (ie. download and experience the functionality for yourself) link in a
>> manner that is immediately obvious. In other words, the landing page
>> would thus end up providing the following detail for various persona
>> of visitors - (a) how to download; install and set-up; (b) what is the
>> latest release and where is the project release timeline; (c) any
>> specific social media links relevant to the project; (d) how to get
>> involved; (e) where does the community get together.

I wanted to draw out a conversation around the personas. The new
aspects to the web-asset are intended to address specific
requirements. It would be good to have those requirements enumerated.
This helps (i) in explaining the design thinking you are exercising;
(ii) allow new contributors with various paths to get on-board and
send patches.

> a. how to download; install and set-up
> Was thinking about something like TryStack, or an interactive sandboxed
> temporary environment to showcase the features of Gluster FS to the user
> could be a way to go. Spinning up couple of small VMs with Gluster FS
> preinstalled (or better lxc/docker/rocket/container images) with preset
> scripts/demos shouldn't be too expensive. But it does need a lot of work.
> We can start with video tutorial serie, may be & go up from there. But
> this is where we need to listen to more ideas from the rest of us.

It would be good to list down the options which can be imagined and
thereafter short-listed for the presence in the page.

> b. what is the latest release and where is the project release timeline
> Great that you asked; working on a timeline on the landing page itself.
> Should be on the next update that I'll send.

+1

> c. any specific social media links relevant to the project
> Please check out the brand new footer. It should serve for now.

+1

> d. how to get involved
> For the time being, I was thinking of showing masthead from the landing
> page & linking them to docs.gluster.org/contribute/.
> On the page, that section is after the event map, as "Be part of..."

I think it is time to think about ways to replace filler text on the
page(s) with actual desired content.

I do realize that a part of my feedback overlaps with design/layout
decisions and actual view/presentation layers of the design itself.

> Reading docs may not be 'cool' for newcomers now a days & interactive
> get-involved section featuring functional areas may work in future.

For example, a simpler design that drives a message similar to
<https://fedoraproject.org/wiki/Join> may be good.

> I've had written about the need of the change, but yes - I've missed out
> mentioning the key requirements. // http://blog.debs.io/3

It would probably be worthwhile to turn that post into a part of the
code repository as well.

> So the idea behind this gluster.org revamp project was to ensure:
> 1. It to have lower entry barrier for development contributions
> 2. It to have near zero technical debts or technolgy-lock-ins
> 3. It should be easy to fix, demonstrate/stage & reiterate
> 4. It should play well across platform and formfactors
> 5. It should not provide redundant/broken contents
> 6. It should help gain project participation
> 7. It should not look/feel 'off' in 2016

To ease the flow of administration of the site and updates to the
content (or, parts thereof) should also be a goal.

Once the remaining filler text is replaced with actual content, how do
you think you are doing against your criteria?

> The very reason for choosing static HTML/CSS/JS, not abstracting the
> codes with coffee script, less/sass etc, having compile/build/deploy
> cycles, not loading it up 

Re: [Gluster-users] Gluster project site revamp update

[Sankarshan Mukhopadhyay]

On Mon, Mar 30, 2015 at 5:28 PM, Soumya Deb  wrote:
> Here's the staging page: http://code.debs.io/glusterweb/

This looks nice and is a good change from the current look-n-feel. I
wonder if you would consider figuring out how to include the "Try"
(ie. download and experience the functionality for yourself) link in a
manner that is immediately obvious. In other words, the landing page
would thus end up providing the following detail for various persona
of visitors - (a) how to download; install and set-up; (b) what is the
latest release and where is the project release timeline; (c) any
specific social media links relevant to the project; (d) how to get
involved; (e) where does the community get together.

> Here's the source code: https://github.com/debloper/glusterweb
>
> Here's some key-factors for the motivation to start anew:
> 1. This is a completely a static site - no server side, or static-site 
> generation involved
> 2. Which means, one only needs to know just about HTML/CSS/JS/Git to start 
> contributing in it
> 3. Which also means, the entry barrier is so low, even student community 
> easily can contribute
> 4. One just needs to fork, edit & push to get a live staging on 
> .github.io/glusterweb
> 5. Managing/maintaining the site becomes trivially easy - so is the 
> code-review (Pull Requests)

I was wondering if you have a set of baseline requirements that you
are designing against. And whether those can also be referenced in
order to provide the commentary/narrative structure to the designs you
are putting up for feedback.

> The setup is such that it plays well with the new URLs to the documentation, 
> blog, code repos etc. makes contribution really easy for everyone and doesn't 
> require much overhead on the devop side as well - it's as WYSIWYG as it gets.




-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users