Re: [Gluster-users] Signing off from Gluster

[Martin Toth]

Thanks for all. We will miss you!

BR!

> On 26 Apr 2019, at 17:25, Amye Scavarda  wrote:
> 
> It's been a delight to work with this community for the past few
> years, and as of today, I'm stepping away for a new opportunity. Amar
> Tumballi has already taken up several of the community initiatives
> that were in flight. You've already seen his work in creating new
> communication channels and meeting times, and I look forward to seeing
> what he does in the future!
> 
> Mike Perez, the Ceph Commmunity Lead, has graciously volunteered to
> support the community in the interim, and he's copied on this message
> as well. Stormy Peters, the Community Team Manager is also available
> for questions.
> 
> Thank you all!
> -- amye
> 
> -- 
> Amye Scavarda | a...@redhat.com | Gluster Community Lead
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users

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

[Gluster-users] Signing off from Gluster

[Amye Scavarda]

It's been a delight to work with this community for the past few
years, and as of today, I'm stepping away for a new opportunity. Amar
Tumballi has already taken up several of the community initiatives
that were in flight. You've already seen his work in creating new
communication channels and meeting times, and I look forward to seeing
what he does in the future!

Mike Perez, the Ceph Commmunity Lead, has graciously volunteered to
support the community in the interim, and he's copied on this message
as well. Stormy Peters, the Community Team Manager is also available
for questions.

Thank you all!
-- amye

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

[Gluster-users] Gluster Monthly Newsletter, April 2019

[Amye Scavarda]

Gluster Monthly Newsletter, April 2019

Upcoming Community Happy Hour at Red Hat Summit! Tue, May 7, 2019,
6:30 PM – 7:30 PM EDT
https://cephandglusterhappyhour_rhsummit.eventbrite.com has all the details.


Gluster 7 Roadmap
Discussion kicked off for our 7 roadmap on the mailing lists, see
[Gluster-users] GlusterFS v7.0 (and v8.0) roadmap discussion
https://lists.gluster.org/pipermail/gluster-users/2019-March/036139.html
for more details.


Community Survey Feedback is available! Come see how other people are
using Gluster and what features they’d like!
https://www.gluster.org/community-survey-feedback-2019/

Gluster Friday Five: Find our Friday Five podcast at
https://www.youtube.com/channel/UCfilWh0JA5NfCjbqq1vsBVA


Contributors

Top Contributing Companies:  Red Hat, Comcast, DataLab, Gentoo Linux,
Facebook, BioDec, Samsung, Etersoft

Top Contributors in April: Atin Mukherjee, Sanju Rakonde, Kotresh HR,
Pranith Kumar Karampuri, Kinglong Mee


Noteworthy Threads:

[Gluster-users] [Gluster-devel] Upgrade testing to gluster 6
https://lists.gluster.org/pipermail/gluster-users/2019-April/036229.html
[Gluster-users] Heketi v9.0.0 available for download
https://lists.gluster.org/pipermail/gluster-users/2019-April/036285.html
[Gluster-users] Proposal: Changes in Gluster Community meetings
https://lists.gluster.org/pipermail/gluster-users/2019-April/036337.html
[Gluster-users] XFS, WORM and the Year-2038 Problem
https://lists.gluster.org/pipermail/gluster-users/2019-April/036356.html
[Gluster-users] Community Happy Hour at Red Hat Summit
https://lists.gluster.org/pipermail/gluster-users/2019-April/036422.html
[Gluster-devel] Backporting important fixes in release branches
https://lists.gluster.org/pipermail/gluster-devel/2019-April/056041.html
[Gluster-devel] BZ updates
https://lists.gluster.org/pipermail/gluster-devel/2019-April/056153.html
[Gluster-users] One more way to contact Gluster team - Slack (gluster.slack.com)
https://lists.gluster.org/pipermail/gluster-users/2019-April/036440.html

Events:

Red Hat Summit, May 4-6, 2019 - https://www.redhat.com/en/summit/2019
Open Source Summit and KubeCon + CloudNativeCon Shanghai, June 24-26,
2019 https://www.lfasiallc.com/events/kubecon-cloudnativecon-china-2019/
DevConf India, August 2- 3 2019, Bengaluru  - https://devconf.info/in
DevConf USA, August 15-17, 2019, Boston -  https://devconf.info/us/

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

Re: [Gluster-users] [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

[Michael Scherer]

Le vendredi 26 avril 2019 à 04:59 -0500, Scott Worthington a écrit :
> Hello, are you not _BOTH_ Red Hat FTEs or contractors?

We do, that was just a turn of phrase to be more generic.

> On Fri, Apr 26, 2019, 3:16 AM Michael Scherer 
> wrote:
> 
> > Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan
> > a
> > écrit :
> > > Hi All,
> > > 
> > > We wanted to move to Slack from IRC for our official
> > > communication
> > > channel
> > > from sometime, but couldn't as we didn't had a proper URL for us
> > > to
> > > register. 'gluster' was taken and we didn't knew who had it
> > > registered.
> > > Thanks to constant ask from Satish, Slack team has now agreed to
> > > let
> > > us use
> > > https://gluster.slack.com and I am happy to invite you all there.
> > > (Use this
> > > link
> > > <
> > > 
> > 
> > 
https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
> > > > 
> > > 
> > > to
> > > join)
> > > 
> > > Please note that, it won't be a replacement for mailing list. But
> > > can
> > > be
> > > used by all developers and users for quick communication. Also
> > > note
> > > that,
> > > no information there would be 'stored' beyond 10k lines as we are
> > > using the
> > > free version of Slack.
> > 
> > Aren't we concerned about the ToS of slack ? Last time I did read
> > them,
> > they were quite scary (like, if you use your corporate email, you
> > engage your employer, and that wasn't the worst part).
> > 
> > Also, to anticipate the question, my employer Legal department told
> > me
> > to not setup a bridge between IRC and slack, due to the said ToS.
> > 
> > --
> > Michael Scherer
> > Sysadmin, Community Infrastructure
> > 
> > 
> > 
> > ___
> > Gluster-users mailing list
> > Gluster-users@gluster.org
> > https://lists.gluster.org/mailman/listinfo/gluster-users
-- 
Michael Scherer
Sysadmin, Community Infrastructure





signature.asc
Description: This is a digitally signed message part
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Gluster 5 Geo-replication Guide

[Shon Stephens]

Dear All,
 Is there a good, step by step guide for setting up geo-replication
with Glusterfs 5? The docs are a difficult to decipher read, for me, and
seem more feature guide than actual instruction.

Thank you,
Shon
-- 

SHON STEPHENS

SENIOR CONSULTANT

Red Hat 

T: 571-781-0787M: 703-297-0682

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

Re: [Gluster-users] [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

[Harold Miller]

Amar,

Thanks for the clarification.  I'll go climb back into my cave. :)

Harold

On Fri, Apr 26, 2019 at 9:20 AM Amar Tumballi Suryanarayan <
atumb...@redhat.com> wrote:

>
>
> On Fri, Apr 26, 2019 at 6:27 PM Kaleb Keithley 
> wrote:
>
>>
>>
>> On Fri, Apr 26, 2019 at 8:21 AM Harold Miller  wrote:
>>
>>> Has Red Hat security cleared the Slack systems for confidential /
>>> customer information?
>>>
>>> If not, it will make it difficult for support to collect/answer
>>> questions.
>>>
>>
>> I'm pretty sure Amar meant as a replacement for the freenode #gluster and
>> #gluster-dev channels, given that he sent this to the public gluster
>> mailing lists @gluster.org. Nobody should have even been posting
>> confidential and/or customer information to any of those lists or channels.
>> And AFAIK nobody ever has.
>>
>>
> Yep, I am only talking about IRC (from freenode, #gluster, #gluster-dev
> etc).  Also, I am not saying we are 'replacing IRC'. Gluster as a project
> started in pre-Slack era, and we have many users who prefer to stay in IRC.
> So, for now, no pressure to make a statement calling Slack channel as a
> 'Replacement' to IRC.
>
>
>> Amar, would you like to clarify which IRC channels you meant?
>>
>>
>
> Thanks Kaleb. I was bit confused on why the concern of it came up in this
> group.
>
>
>
>>
>>> On Fri, Apr 26, 2019 at 6:00 AM Scott Worthington <
>>> scott.c.worthing...@gmail.com> wrote:
>>>
 Hello, are you not _BOTH_ Red Hat FTEs or contractors?


> Yes! but come from very different internal teams.
>
> Michael supports Gluster (the project) team's Infrastructure needs, and
> has valid concerns from his perspective :-) I, on the other hand, bother
> more about code, users, and how to make sure we are up-to-date with other
> technologies and communities, from the engineering view point.
>
>
>> On Fri, Apr 26, 2019, 3:16 AM Michael Scherer 
 wrote:

> Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan a
> écrit :
> > Hi All,
> >
> > We wanted to move to Slack from IRC for our official communication
> > channel
> > from sometime, but couldn't as we didn't had a proper URL for us to
> > register. 'gluster' was taken and we didn't knew who had it
> > registered.
> > Thanks to constant ask from Satish, Slack team has now agreed to let
> > us use
> > https://gluster.slack.com and I am happy to invite you all there.
> > (Use this
> > link
> > <
> >
> https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
> > >
> > to
> > join)
> >
> > Please note that, it won't be a replacement for mailing list. But can
> > be
> > used by all developers and users for quick communication. Also note
> > that,
> > no information there would be 'stored' beyond 10k lines as we are
> > using the
> > free version of Slack.
>
> Aren't we concerned about the ToS of slack ? Last time I did read them,
> they were quite scary (like, if you use your corporate email, you
> engage your employer, and that wasn't the worst part).
>
> Also, to anticipate the question, my employer Legal department told me
> to not setup a bridge between IRC and slack, due to the said ToS.
>
>
> Again, re-iterating here. Not planning to use any bridges from IRC to
> Slack. I re-read the Slack API Terms and condition. And it makes sense.
> They surely don't want us to build another slack, or abuse slack with too
> many API requests made for collecting logs.
>
> Currently, to start with, we are not adding any bots (other than github
> bot). Hopefully, that will keep us under proper usage guidelines.
>
> -Amar
>
>
>> --
> Michael Scherer
> Sysadmin, Community Infrastructure
>
>
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users

 ___
 Gluster-users mailing list
 Gluster-users@gluster.org
 https://lists.gluster.org/mailman/listinfo/gluster-users
>>>
>>>
>>>
>>> --
>>>
>>> HAROLD MILLER
>>>
>>> ASSOCIATE MANAGER, ENTERPRISE CLOUD SUPPORT
>>>
>>> Red Hat
>>>
>>> 
>>>
>>> har...@redhat.comT: (650)-254-4346
>>> 
>>> TRIED. TESTED. TRUSTED. 
>>> ___
>>> Gluster-users mailing list
>>> Gluster-users@gluster.org
>>> https://lists.gluster.org/mailman/listinfo/gluster-users
>>
>>
>
> --
> Amar Tumballi (amarts)
>


-- 

HAROLD MILLER

ASSOCIATE MANAGER, ENTERPRISE CLOUD SUPPORT

Red Hat



har...@redhat.comT: (650)-254-4346

TRIED. TESTED. TRUSTED. 

Re: [Gluster-users] [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

[Amar Tumballi Suryanarayan]

On Fri, Apr 26, 2019 at 6:27 PM Kaleb Keithley  wrote:

>
>
> On Fri, Apr 26, 2019 at 8:21 AM Harold Miller  wrote:
>
>> Has Red Hat security cleared the Slack systems for confidential /
>> customer information?
>>
>> If not, it will make it difficult for support to collect/answer questions.
>>
>
> I'm pretty sure Amar meant as a replacement for the freenode #gluster and
> #gluster-dev channels, given that he sent this to the public gluster
> mailing lists @gluster.org. Nobody should have even been posting
> confidential and/or customer information to any of those lists or channels.
> And AFAIK nobody ever has.
>
>
Yep, I am only talking about IRC (from freenode, #gluster, #gluster-dev
etc).  Also, I am not saying we are 'replacing IRC'. Gluster as a project
started in pre-Slack era, and we have many users who prefer to stay in IRC.
So, for now, no pressure to make a statement calling Slack channel as a
'Replacement' to IRC.


> Amar, would you like to clarify which IRC channels you meant?
>
>

Thanks Kaleb. I was bit confused on why the concern of it came up in this
group.



>
>> On Fri, Apr 26, 2019 at 6:00 AM Scott Worthington <
>> scott.c.worthing...@gmail.com> wrote:
>>
>>> Hello, are you not _BOTH_ Red Hat FTEs or contractors?
>>>
>>>
Yes! but come from very different internal teams.

Michael supports Gluster (the project) team's Infrastructure needs, and has
valid concerns from his perspective :-) I, on the other hand, bother more
about code, users, and how to make sure we are up-to-date with other
technologies and communities, from the engineering view point.


> On Fri, Apr 26, 2019, 3:16 AM Michael Scherer  wrote:
>>>
 Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan a
 écrit :
 > Hi All,
 >
 > We wanted to move to Slack from IRC for our official communication
 > channel
 > from sometime, but couldn't as we didn't had a proper URL for us to
 > register. 'gluster' was taken and we didn't knew who had it
 > registered.
 > Thanks to constant ask from Satish, Slack team has now agreed to let
 > us use
 > https://gluster.slack.com and I am happy to invite you all there.
 > (Use this
 > link
 > <
 >
 https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
 > >
 > to
 > join)
 >
 > Please note that, it won't be a replacement for mailing list. But can
 > be
 > used by all developers and users for quick communication. Also note
 > that,
 > no information there would be 'stored' beyond 10k lines as we are
 > using the
 > free version of Slack.

 Aren't we concerned about the ToS of slack ? Last time I did read them,
 they were quite scary (like, if you use your corporate email, you
 engage your employer, and that wasn't the worst part).

 Also, to anticipate the question, my employer Legal department told me
 to not setup a bridge between IRC and slack, due to the said ToS.


Again, re-iterating here. Not planning to use any bridges from IRC to
Slack. I re-read the Slack API Terms and condition. And it makes sense.
They surely don't want us to build another slack, or abuse slack with too
many API requests made for collecting logs.

Currently, to start with, we are not adding any bots (other than github
bot). Hopefully, that will keep us under proper usage guidelines.

-Amar


> --
 Michael Scherer
 Sysadmin, Community Infrastructure



 ___
 Gluster-users mailing list
 Gluster-users@gluster.org
 https://lists.gluster.org/mailman/listinfo/gluster-users
>>>
>>> ___
>>> Gluster-users mailing list
>>> Gluster-users@gluster.org
>>> https://lists.gluster.org/mailman/listinfo/gluster-users
>>
>>
>>
>> --
>>
>> HAROLD MILLER
>>
>> ASSOCIATE MANAGER, ENTERPRISE CLOUD SUPPORT
>>
>> Red Hat
>>
>> 
>>
>> har...@redhat.comT: (650)-254-4346
>> 
>> TRIED. TESTED. TRUSTED. 
>> ___
>> Gluster-users mailing list
>> Gluster-users@gluster.org
>> https://lists.gluster.org/mailman/listinfo/gluster-users
>
>

-- 
Amar Tumballi (amarts)
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

[Kaleb Keithley]

On Fri, Apr 26, 2019 at 8:21 AM Harold Miller  wrote:

> Has Red Hat security cleared the Slack systems for confidential / customer
> information?
>
> If not, it will make it difficult for support to collect/answer questions.
>

I'm pretty sure Amar meant as a replacement for the freenode #gluster and
#gluster-dev channels, given that he sent this to the public gluster
mailing lists @gluster.org. Nobody should have even been posting
confidential and/or customer information to any of those lists or channels.
And AFAIK nobody ever has.

Amar, would you like to clarify which IRC channels you meant?


> Harold Miller, Associate Manager,
> Red Hat, Enterprise Cloud Support
> Desk - US (650) 254-4346
>
>
>
> On Fri, Apr 26, 2019 at 6:00 AM Scott Worthington <
> scott.c.worthing...@gmail.com> wrote:
>
>> Hello, are you not _BOTH_ Red Hat FTEs or contractors?
>>
>> On Fri, Apr 26, 2019, 3:16 AM Michael Scherer 
>> wrote:
>>
>>> Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan a
>>> écrit :
>>> > Hi All,
>>> >
>>> > We wanted to move to Slack from IRC for our official communication
>>> > channel
>>> > from sometime, but couldn't as we didn't had a proper URL for us to
>>> > register. 'gluster' was taken and we didn't knew who had it
>>> > registered.
>>> > Thanks to constant ask from Satish, Slack team has now agreed to let
>>> > us use
>>> > https://gluster.slack.com and I am happy to invite you all there.
>>> > (Use this
>>> > link
>>> > <
>>> >
>>> https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
>>> > >
>>> > to
>>> > join)
>>> >
>>> > Please note that, it won't be a replacement for mailing list. But can
>>> > be
>>> > used by all developers and users for quick communication. Also note
>>> > that,
>>> > no information there would be 'stored' beyond 10k lines as we are
>>> > using the
>>> > free version of Slack.
>>>
>>> Aren't we concerned about the ToS of slack ? Last time I did read them,
>>> they were quite scary (like, if you use your corporate email, you
>>> engage your employer, and that wasn't the worst part).
>>>
>>> Also, to anticipate the question, my employer Legal department told me
>>> to not setup a bridge between IRC and slack, due to the said ToS.
>>>
>>> --
>>> Michael Scherer
>>> Sysadmin, Community Infrastructure
>>>
>>>
>>>
>>> ___
>>> Gluster-users mailing list
>>> Gluster-users@gluster.org
>>> https://lists.gluster.org/mailman/listinfo/gluster-users
>>
>> ___
>> Gluster-users mailing list
>> Gluster-users@gluster.org
>> https://lists.gluster.org/mailman/listinfo/gluster-users
>
>
>
> --
>
> HAROLD MILLER
>
> ASSOCIATE MANAGER, ENTERPRISE CLOUD SUPPORT
>
> Red Hat
>
> 
>
> har...@redhat.comT: (650)-254-4346
> 
> TRIED. TESTED. TRUSTED. 
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

[Harold Miller]

Has Red Hat security cleared the Slack systems for confidential / customer
information?

If not, it will make it difficult for support to collect/answer questions.


Harold Miller, Associate Manager,
Red Hat, Enterprise Cloud Support
Desk - US (650) 254-4346



On Fri, Apr 26, 2019 at 6:00 AM Scott Worthington <
scott.c.worthing...@gmail.com> wrote:

> Hello, are you not _BOTH_ Red Hat FTEs or contractors?
>
> On Fri, Apr 26, 2019, 3:16 AM Michael Scherer  wrote:
>
>> Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan a
>> écrit :
>> > Hi All,
>> >
>> > We wanted to move to Slack from IRC for our official communication
>> > channel
>> > from sometime, but couldn't as we didn't had a proper URL for us to
>> > register. 'gluster' was taken and we didn't knew who had it
>> > registered.
>> > Thanks to constant ask from Satish, Slack team has now agreed to let
>> > us use
>> > https://gluster.slack.com and I am happy to invite you all there.
>> > (Use this
>> > link
>> > <
>> >
>> https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
>> > >
>> > to
>> > join)
>> >
>> > Please note that, it won't be a replacement for mailing list. But can
>> > be
>> > used by all developers and users for quick communication. Also note
>> > that,
>> > no information there would be 'stored' beyond 10k lines as we are
>> > using the
>> > free version of Slack.
>>
>> Aren't we concerned about the ToS of slack ? Last time I did read them,
>> they were quite scary (like, if you use your corporate email, you
>> engage your employer, and that wasn't the worst part).
>>
>> Also, to anticipate the question, my employer Legal department told me
>> to not setup a bridge between IRC and slack, due to the said ToS.
>>
>> --
>> Michael Scherer
>> Sysadmin, Community Infrastructure
>>
>>
>>
>> ___
>> Gluster-users mailing list
>> Gluster-users@gluster.org
>> https://lists.gluster.org/mailman/listinfo/gluster-users
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users



-- 

HAROLD MILLER

ASSOCIATE MANAGER, ENTERPRISE CLOUD SUPPORT

Red Hat



har...@redhat.comT: (650)-254-4346

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

Re: [Gluster-users] [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

[Scott Worthington]

Hello, are you not _BOTH_ Red Hat FTEs or contractors?

On Fri, Apr 26, 2019, 3:16 AM Michael Scherer  wrote:

> Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan a
> écrit :
> > Hi All,
> >
> > We wanted to move to Slack from IRC for our official communication
> > channel
> > from sometime, but couldn't as we didn't had a proper URL for us to
> > register. 'gluster' was taken and we didn't knew who had it
> > registered.
> > Thanks to constant ask from Satish, Slack team has now agreed to let
> > us use
> > https://gluster.slack.com and I am happy to invite you all there.
> > (Use this
> > link
> > <
> >
> https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
> > >
> > to
> > join)
> >
> > Please note that, it won't be a replacement for mailing list. But can
> > be
> > used by all developers and users for quick communication. Also note
> > that,
> > no information there would be 'stored' beyond 10k lines as we are
> > using the
> > free version of Slack.
>
> Aren't we concerned about the ToS of slack ? Last time I did read them,
> they were quite scary (like, if you use your corporate email, you
> engage your employer, and that wasn't the worst part).
>
> Also, to anticipate the question, my employer Legal department told me
> to not setup a bridge between IRC and slack, due to the said ToS.
>
> --
> Michael Scherer
> Sysadmin, Community Infrastructure
>
>
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Expanding brick size in glusterfs 3.7.11

[Strahil]

I have gluster bricks ontop of thin LVM and when I resized my LV, everything 
went live and without issues.
As gluster is working ontop the File System, it relies on the information from 
it (in my case XFS).
Just make sure that bricks for replica volumes have the same size (verify with 
'df /brick/path').

Best Regards,
Strahil NikolovOn Apr 26, 2019 04:05, Pat Haley  wrote:
>
>
> Hi,
>
> Last summer we added a new brick to our gluster volume (running 
> glusterfs 3.7.11).  The new brick was a new server with with 12 of 24 
> disk bays filled (we couldn't afford to fill them all at the time).  
> These 12 disks are managed in a hardware RAID-6.  We have recently been 
> able to purchase another 12 disks.  We would like to just add these new 
> disks to the existing hardware RAID and thus expand the size of the 
> brick.  If we can successfully add them to the hardware RAID like this, 
> will gluster have any problems with the expanded brick size?
>
> --
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Pat Haley  Email:  pha...@mit.edu
> Center for Ocean Engineering   Phone:  (617) 253-6824
> Dept. of Mechanical Engineering    Fax:    (617) 253-8125
> MIT, Room 5-213    http://web.mit.edu/phaley/www/
> 77 Massachusetts Avenue
> Cambridge, MA  02139-4301
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] [Gluster-devel] One more way to contact Gluster team - Slack (gluster.slack.com)

[Michael Scherer]

Le vendredi 26 avril 2019 à 13:24 +0530, Amar Tumballi Suryanarayan a
écrit :
> Hi All,
> 
> We wanted to move to Slack from IRC for our official communication
> channel
> from sometime, but couldn't as we didn't had a proper URL for us to
> register. 'gluster' was taken and we didn't knew who had it
> registered.
> Thanks to constant ask from Satish, Slack team has now agreed to let
> us use
> https://gluster.slack.com and I am happy to invite you all there.
> (Use this
> link
> <
> https://join.slack.com/t/gluster/shared_invite/enQtNjIxMTA1MTk3MDE1LWIzZWZjNzhkYWEwNDdiZWRiOTczMTc4ZjdiY2JiMTc3MDE5YmEyZTRkNzg0MWJiMWM3OGEyMDU2MmYzMTViYTA
> >
> to
> join)
> 
> Please note that, it won't be a replacement for mailing list. But can
> be
> used by all developers and users for quick communication. Also note
> that,
> no information there would be 'stored' beyond 10k lines as we are
> using the
> free version of Slack.

Aren't we concerned about the ToS of slack ? Last time I did read them,
they were quite scary (like, if you use your corporate email, you
engage your employer, and that wasn't the worst part). 

Also, to anticipate the question, my employer Legal department told me
to not setup a bridge between IRC and slack, due to the said ToS.
 
-- 
Michael Scherer
Sysadmin, Community Infrastructure





signature.asc
Description: This is a digitally signed message part
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] One more way to contact Gluster team - Slack (gluster.slack.com)

[Amar Tumballi Suryanarayan]

Hi All,

We wanted to move to Slack from IRC for our official communication channel
from sometime, but couldn't as we didn't had a proper URL for us to
register. 'gluster' was taken and we didn't knew who had it registered.
Thanks to constant ask from Satish, Slack team has now agreed to let us use
https://gluster.slack.com and I am happy to invite you all there. (Use this
link

to
join)

Please note that, it won't be a replacement for mailing list. But can be
used by all developers and users for quick communication. Also note that,
no information there would be 'stored' beyond 10k lines as we are using the
free version of Slack.

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

Re: [Gluster-users] Expanding brick size in glusterfs 3.7.11

[Ashish Pandey]

Pat, 
I would like to see the final configuration of your gluster volume after you 
added bricks on new node. 

You mentioned that - 
"The new brick was a new server with with 12 of 24 disk bays filled (we 
couldn't afford to fill them all at the time). These 12 disks are managed in a 
hardware RAID-6." 

If all the new bricks are on one new node then probably that is not a good 
situation to be in . 

@Pascal, I agree with your suggestion.. 
"long story short.. i'd consider creating a second raid acorss your 12 new 
disks and adding this as a second brick to gluster storage.. that's what 
gluster's for after all .. to scale your storage :) in the case of raid 6 you 
will loose the capacity of two disks but you will gain alot in terms of 
redundancy and dataprotection." 


--- 
Ashish 

- Original Message -

From: "Pascal Suter"  
To: gluster-users@gluster.org 
Sent: Friday, April 26, 2019 11:52:22 AM 
Subject: Re: [Gluster-users] Expanding brick size in glusterfs 3.7.11 



I may add to that that i have expanded linux filesystems (xfs and ext4) both 
via LVM and some by adding disks to a hardware raid. from the OS point of view 
it does not make a difference, the procedure once the block device on which the 
filesytem resides is expanded is prettymuch the same and so far always worked 
like a charm. 


one word of caution though: i've just recently had a case with a raid 6 across 
12 disks (1TB, a 5 year old RAID array) where during a planned power outage a 
disk failed, when turnging the storage back on, a second failed right after 
that and the third failed during rebuild. luckily this was a retired server 
used for backup only, so no harm done.. but this just shows us, that under the 
"ritght" circumstances, multi disk failures are possible. the more disks you 
have in your raidset the higher the chance of a disk failure.. by doubling the 
amount of disks in your raidset you double the chance of a disk failure and 
therefore a double or tripple disk failure as well. 


long story short.. i'd consider creating a second raid acorss your 12 new disks 
and adding this as a second brick to gluster storage.. that's what gluster's 
for after all .. to scale your storage :) in the case of raid 6 you will loose 
the capacity of two disks but you will gain alot in terms of redundancy and 
dataprotection. 


also you will not have the performance impact of the raid expansion.. this is 
usually a rather long process which will eat a lot of your performance while 
it's ongoing. 


of course, if you have mirrored bricks, that's a different story, but i assume 
you don't. 
cheers 
Pascal 

On 26.04.19 05:35, Jim Kinney wrote: 


I've expanded bricks using lvm and there was no problems at all with gluster 
seeing the change. The expansion was performed basically simultaneously on both 
existing bricks of a replica. I would expect the raid expansion to behave 
similarly. 

On April 25, 2019 9:05:45 PM EDT, Pat Haley  wrote: 


Hi,

Last summer we added a new brick to our gluster volume (running 
glusterfs 3.7.11).  The new brick was a new server with with 12 of 24 
disk bays filled (we couldn't afford to fill them all at the time).  
These 12 disks are managed in a hardware RAID-6.  We have recently been 
able to purchase another 12 disks.  We would like to just add these new 
disks to the existing hardware RAID and thus expand the size of the 
brick.  If we can successfully add them to the hardware RAID like this, 
will gluster have any problems with the expanded brick size?

-- 

Pat Haley  Email: pha...@mit.edu Center for Ocean 
Engineering   Phone:  (617) 253-6824
Dept. of Mechanical EngineeringFax:(617) 253-8125
MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue
Cambridge, MA  02139-4301 

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




-- 
Sent from my Android device with K-9 Mail. All tyopes are thumb related and 
reflect authenticity. 
___
Gluster-users mailing list Gluster-users@gluster.org 
https://lists.gluster.org/mailman/listinfo/gluster-users 



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

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

Re: [Gluster-users] Expanding brick size in glusterfs 3.7.11

[Pascal Suter]

I may add to that that i have expanded linux filesystems (xfs and ext4) 
both via LVM and some by adding disks to a hardware raid. from the OS 
point of view it does not make a difference, the procedure once the 
block device on which the filesytem resides is expanded is prettymuch 
the same and so far always worked like a charm.


one word of caution though: i've just recently had a case with a raid 6 
across 12 disks (1TB, a 5 year old RAID array) where during a planned 
power outage a disk failed, when turnging the storage back on, a second 
failed right after that and the third failed during rebuild. luckily 
this was a retired server used for backup only, so no harm done.. but 
this just shows us, that under the "ritght" circumstances, multi disk 
failures are possible. the more disks you have in your raidset the 
higher the chance of a disk failure.. by doubling the amount of disks in 
your raidset you double the chance of a disk failure and therefore a 
double or tripple disk failure as well.


long story short.. i'd consider creating a second raid acorss your 12 
new disks and adding this as a second brick to gluster storage.. that's 
what gluster's for after all .. to scale your storage :) in the case of 
raid 6 you will loose the capacity of two disks but you will gain alot 
in terms of redundancy and dataprotection.


also you will not have the performance impact of the raid expansion.. 
this is usually a rather long process which will eat a lot of your 
performance while it's ongoing.


of course, if you have mirrored bricks, that's a different story, but i 
assume you don't.


cheers
Pascal

On 26.04.19 05:35, Jim Kinney wrote:
I've expanded bricks using lvm and there was no problems at all with 
gluster seeing the change. The expansion was performed basically 
simultaneously on both existing bricks of a replica. I would expect 
the raid expansion to behave similarly.


On April 25, 2019 9:05:45 PM EDT, Pat Haley  wrote:

Hi,

Last summer we added a new brick to our gluster volume (running
glusterfs 3.7.11).  The new brick was a new server with with 12 of 24
disk bays filled (we couldn't afford to fill them all at the time).
These 12 disks are managed in a hardware RAID-6.  We have recently been
able to purchase another 12 disks.  We would like to just add these new
disks to the existing hardware RAID and thus expand the size of the
brick.  If we can successfully add them to the hardware RAID like this,
will gluster have any problems with the expanded brick size?

-- 


Pat Haley  Email:  pha...@mit.edu
Center for Ocean Engineering   Phone:  (617) 253-6824
Dept. of Mechanical EngineeringFax:(617) 253-8125
MIT, Room 5-213http://web.mit.edu/phaley/www/
77 Massachusetts Avenue
Cambridge, MA  02139-4301

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


--
Sent from my Android device with K-9 Mail. All tyopes are thumb 
related and reflect authenticity.


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