similar to: Gluster Community Meeting 2017-06-07

This is a (late) reminder about today's meeting. The meeting begins in ~20 minutes from now. The meeting notepad is at https://bit.ly/gluster-community-meetings and currently has no topics for discussion. If you have anything to be discussed please add it to the pad. ~kaushal

Hi All, This a reminder about today's meeting. The meeting will start later today at 1500UTC. Please add topics and updates to the meeting pad at https://bit.ly/gluster-community-meetings Thanks.

Hey all! In the spirit of trying something new with the Community Meeting, this next one is changing a bit. I'm calling it 'Gluster Global Meetup' for lack of a better name (names welcomed) - and we're putting it on a video call. Same time as the community meeting, but a little different on the format. Here's a video call link for this that I'll add to the community

Hi all, This a reminder about today's meeting. The meeting will start later today at 15:00 UTC. You can convert that to a local time with the following command in your terminal: $ date -d '15:00 UTC' Because the meeting is an open floor, topics and updates need to be added to the meeting pad at: https://bit.ly/gluster-community-meetings Hope to see you later online, Niels

Hi all, The meeting minutes and logs for the community meeting held on Wednesday are available at the links below. [1][2][3][4] We had a good showing this meeting. Thank you everyone who attended this meeting. Our next meeting will be on 19th July. Everyone is welcome to attend. The meeting note pad is available at [5] to add your topics for discussion. Thanks, Kaushal [1]: Minutes:

This is combined update for the last two community meetings (because I forgot to send out the update for the earlier meeting, my bad). # Community Meeting 2017-08-02 There weren't any explicit topics of discussion, but we had updates on action items and releases. The logs and minutes are available at [1][2][3]. The minutes are also available at the end of this mail. # Community Meeting

!!REMINDER!! Community meeting is back after 4 weeks off. Today's community meeting is scheduled in about 3 hours from now, at 1500UTC. Please add any topics you want to discuss and any updates you want to share with the community into the meeting pad at https://bit.ly/gluster-community-meetings See you in #gluster-meeting! ~kaushal

Just so I am clear the upgrade process will be as follows: upgrade all clients to 4.0 rolling upgrade all servers to 4.0 (with GD1) kill all GD1 daemons on all servers and run upgrade script (new clients unable to connect at this point) start GD2 ( necessary or does the upgrade script do this?) I assume that once the cluster had been migrated to GD2 the glusterd startup script will be smart

On Fri, Nov 3, 2017 at 8:50 PM, Alastair Neil <ajneil.tech at gmail.com> wrote: > Just so I am clear the upgrade process will be as follows: > > upgrade all clients to 4.0 > > rolling upgrade all servers to 4.0 (with GD1) > > kill all GD1 daemons on all servers and run upgrade script (new clients > unable to connect at this point) > > start GD2 ( necessary or

After nearly 3 months, we have another preview release for GlusterD-2.0. The highlights for this release are, - GD2 now uses an auto scaling etcd cluster, which automatically selects and maintains the required number of etcd servers in the cluster. - Preliminary support for volume expansion has been added. (Note that rebalancing is not available yet) - An end to end functional testing framework

Gluster Monthly Newsletter, May 2017 Important happenings for Gluster for May: --- 3.11 Release! Our 3.11 release is officially out! https://blog.gluster.org/2017/05/announcing-gluster-3-11/ Note that this is a short term supported release. 3.12 is underway with a feature freeze date of July 17, 2017. --- Gluster Summit 2017! Gluster Summit 2017 will be held in Prague, Czech Republic on October

Il 5 lug 2017 11:31 AM, "Kaushal M" <kshlmster at gmail.com> ha scritto: - Preliminary support for volume expansion has been added. (Note that rebalancing is not available yet) What do you mean with this? Any differences in volume expansion from the current architecture? -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, Nov 2, 2017 at 4:00 PM, Amudhan P <amudhan83 at gmail.com> wrote: > if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access > volume without any challenge? > > I am asking this because 4.0 comes with DHT2? Very short answer, yes. Your volumes will remain the same. And you will continue to access them the same way. RIO (as DHT2 is now known as) developers

does RIO improves folder listing and rebalance, when compared to 3.x? if yes, do you have any performance data comparing RIO and DHT? On Thu, Nov 2, 2017 at 4:12 PM, Kaushal M <kshlmster at gmail.com> wrote: > On Thu, Nov 2, 2017 at 4:00 PM, Amudhan P <amudhan83 at gmail.com> wrote: > > if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access > > volume

if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access volume without any challenge? I am asking this because 4.0 comes with DHT2? On Thu, Nov 2, 2017 at 2:26 PM, Kaushal M <kshlmster at gmail.com> wrote: > We're fast approaching the time for Gluster-4.0. And we would like to > set out the expected upgrade strategy and try to polish it to be as > user

Did you run autogen.sh after installing libxml2-devel? On Mon, Jan 22, 2018 at 11:10 AM, Raghavendra G <raghavendra.hg at gmail.com> wrote: > All, > > # ./configure > <success lines removed> > configure: error: libxml2 devel libraries not found > > # ls /usr/lib64/libxml2.so > /usr/lib64/libxml2.so > > # ls /usr/include/libxml2/ > libxml > > #

Sorry, I meant RedHat's Gluster Storage Server 3.2 which is latest and greatest. On Wed, Aug 2, 2017 at 9:28 AM, Kaushal M <kshlmster at gmail.com> wrote: > On Wed, Aug 2, 2017 at 5:07 PM, Mark Connor <markconnor64 at gmail.com> > wrote: > > Can the glusterd daemon be restarted on all storage nodes without causing > > any disruption to data being served or the

Quick meeting last week: Just noting that we now have a projects board to note what's in progress on the Community Issue queue, https://github.com/gluster/community/projects/1 Glustered announced! https://github.com/gluster/community/issues/19 has details about the event, and gluster.org has a public event for this now. http://www.gluster.org/events/glustered/ Minutes on the wiki:

We're fast approaching the time for Gluster-4.0. And we would like to set out the expected upgrade strategy and try to polish it to be as user friendly as possible. We're getting this out here now, because there was quite a bit of concern and confusion regarding the upgrades between 3.x and 4.0+. --- ## Background Gluster-4.0 will bring a newer management daemon, GlusterD-2.0 (GD2),

On Thu, Nov 2, 2017 at 7:53 PM, Darrell Budic <budic at onholyground.com> wrote: > Will the various client packages (centos in my case) be able to > automatically handle the upgrade vs new install decision, or will we be > required to do something manually to determine that? We should be able to do this with CentOS (and other RPM based distros) which have well split glusterfs