similar to: Gluster Monthly Newsletter, September 2017

Gluster Monthly Newsletter, August 2017 -- Great news! We?ve released 3.12! https://www.gluster.org/3-12/announcing-glusterfs-release-3-12-0-long-term-maintenance/ This is a major release that will be Long Term Stable. Notable feature highlights are: - Ability to mount sub-directories using the Gluster native protocol (FUSE) - Brick multiplexing enhancements that help scale

Hi, On Wed, Nov 1, 2017 at 5:32 PM, Amye Scavarda <amye at redhat.com> wrote: > Welcome to an exceptionally busy month for Gluster! > > Gluster Summit > Thanks to all who attended this year's Gluster Summit. As you can see, > conversations are continuing to happen, with notes from the Birds of a > Feather sessions starting to come into the mailing lists. If something

Welcome to an exceptionally busy month for Gluster! Gluster Summit Thanks to all who attended this year's Gluster Summit. As you can see, conversations are continuing to happen, with notes from the Birds of a Feather sessions starting to come into the mailing lists. If something sparked your interest, please post about it! We'll be posting recordings of the talks as we're able to, and

Gluster Monthly Newsletter, January 2018 4.0 is coming! We?re currently tracking for a 4.0 release at the end of February, which means our next edition will be all about 4.0! This weekend, we have a busy schedule at FOSDEM with a Software Defined Storage DevRoom on Sunday - https://fosdem.org/2018/schedule/track/software_defined_storage/ with Gluster-4.0 and GD2 - Learn what's in

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

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? It?s a little unclear that things will continue without interruption because of the way you describe the change from GD1 to GD2, since it sounds like it stops GD1. Early days, obviously, but if you could

I installed GD2 1.0/1.1, but they are both not working, does anyone knows why? Great Thanks! With GD 1.0 I got: ======================================================== RuntimeError unknown symbol "gdImageSquareToCircle" RAILS_ROOT: /home/virtual/site1/fst/var/www/html/imodesite/public/../config/.. Application Trace | Framework Trace | Full Trace

Hi Amudhan, Please go through the following that would clarify up-gradation concerns from DHT to RIO in 4.0 1. RIO would not deprecate DHT. Both DHT and RIO would co-exist. 2. DHT volumes would not be migrated to RIO. DHT volumes would still be using DHT code. 3. The new volume creation should specifically opt for RIO volume once RIO is in place. 4. RIO should be perceived as

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

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

Hello! We're restarting regular GD2 updates. This is the first one, and I expect to send these out every other week. In the last month, we've identified a few core areas that we need to focus on. With solutions in place for these, we believe we're ready to start more deeper integration with glusterfs, that would be requiring changes in the rest of the code base. As of release

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

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

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

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),

This is an automated email from the git hooks/post-receive script. unknown user pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new c10f929 ornl video c10f929 is described below commit c10f92988b176fab93f5f37f0f37f39c654c180f Author: rbowen <rbowen at rcbowen.com> AuthorDate: Mon May 20 09:09:43

Hi all, Thanks for a great response to the Call for Proposals, we had an overwhelming amount. I'll be publishing the schedule as soon as we confirm with our speakers. However, another deadline is coming up for us to make sure that we're getting everything lined up in time: application for travel. https://www.gluster.org/events/summit2017/ has the link for registration, if you've not

This is an automated email from the git hooks/post-receive script. shaunm pushed a commit to branch main in repository centos/centos.org. The following commit(s) were added to refs/heads/main by this push: new 22e55e6 Add post about Connect 2024, remove old posts 22e55e6 is described below commit 22e55e6b8d076aac3150d67243db046469503bbd Author: Shaun McCance <shaunm at redhat.com>

This is an automated email from the git hooks/post-receive script. unknown user pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new f75007f Update front page. new 568ab86 Merge branch 'master' of ssh://git.centos.org/centos/centos.org f75007f is described below commit

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