[Gluster-devel] Review request - Gluster Eventing Feature

[Aravinda]

Hi,

I submitted patch for the new feature "Gluster Eventing", Please review 
the patch.


Patch:   http://review.gluster.org/14248
Design:  http://review.gluster.org/13115
Blog: http://aravindavk.in/blog/10-mins-intro-to-gluster-eventing
Demo:https://www.youtube.com/watch?v=urzong5sKqc

Thanks

--
regards
Aravinda

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

[Gluster-devel] REMINDER: Gluster Community Bug Triage meeting today at 12:00 UTC ~(in 2.0 hours)

[Saravanakumar Arumugam]

Hi, This meeting is scheduled for anyone interested in learning more 
about, or assisting with the Bug Triage. Meeting details: - location: 
#gluster-meeting on Freenode IRC ( 
https://webchat.freenode.net/?channels=gluster-meeting ) - date: every 
Tuesday - time: 12:00 UTC (in your terminal, run: date -d "12:00 UTC") - 
agenda: https://public.pad.fsfe.org/p/gluster-bug-triage Currently the 
following items are listed: * Roll Call * Status of last weeks action 
items * Group Triage * Open Floor Highly appreciate your participation. 
Thanks, Saravana


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

Re: [Gluster-devel] Suggest a feature redirect

[Amye Scavarda]

We get so much spam on the mailing list from unregistered users that
unfortunately, this would not be effective.

Here's what I'm thinking on further review:
We should have that link to a static page that describes how to submit a
patch and contribute back to the community, because that makes the feature
request actionable.
- amye

On Thu, May 19, 2016 at 3:33 PM, Raghavendra Talur 
wrote:

>
>
> On Thu, May 19, 2016 at 12:46 PM, Aravinda  wrote:
>
>>
>> regards
>> Aravinda
>>
>> On 05/19/2016 12:37 PM, Raghavendra Talur wrote:
>>
>>
>>
>> On Thu, May 19, 2016 at 12:10 PM, Vijay Bellur 
>> wrote:
>>
>>> On 05/19/2016 02:38 AM, Amye Scavarda wrote:
>>>


 On Thu, May 19, 2016 at 12:06 PM, Vijay Bellur < 
 vbel...@redhat.com
 > wrote:

 On Thu, May 19, 2016 at 2:21 AM, Raghavendra Talur
 mailto:rta...@redhat.com>> wrote:
 >
 >
 > On Wed, May 18, 2016 at 2:43 PM, Amye Scavarda >>> > wrote:
 >>
 >>
 >>
 >> On Wed, May 18, 2016 at 1:46 PM, Humble Devassy Chirammal
 >> mailto:humble.deva...@gmail.com>>
 wrote:
 >>>
 >>> Hi Amye,
 >>>
 >>> afaict, the feature proposal has start from glusterfs-specs
 >>> (http://review.gluster.org/#/q/project:glusterfs-specs) project
 under
 >>> review.gluster.org < 
 http://review.gluster.org>
 >>>
 >>> --Humble
 >>>
 >>>
 >>> On Wed, May 18, 2016 at 12:15 PM, Amye Scavarda <
 a...@redhat.com
 > wrote:
 
  Currently on the gluster.org < 
 http://gluster.org> website,
 we're directing the 'Suggest a
  feature' to the old mediawiki site for 'Features'.
 
 http://www.gluster.org/community/documentation/index.php/Features
 
  In an ideal world, this would go somewhere else. Where should
 this go?
  Let me know and I'll fix it.
  - amye
 
  --
  Amye Scavarda | a...@redhat.com >>> a...@redhat.com> |
 Gluster Community Lead
 
  ___
  Gluster-devel mailing list
  Gluster-devel@gluster.org 
  http://www.gluster.org/mailman/listinfo/gluster-devel
 >>>
 >>>
 >> Said another way, if you wanted to be able to have someone
 contribute a
 >> feature idea, what would be the best way?
 >> Bugzilla? A google form? An email into the -devel list?
 >>
 >
 > If it is more of a request from a user it should a bugzilla RFE.
 If the user
 > requested on -devel list without a bug, then one of the community
 devs
 > should file a bug for it.
 > If it is a proposal for a feature with design
 details/implementation ideas
 > then a patch to glusterfs-specs is encouraged.


 In any case opening a discussion on gluster-devel would be ideal to
 get the attention of all concerned.

 -Vijay


 So should this stay on the website in the first place?
 - amye


>>> Yes, the relevant workflow needs to be in the website. In the absence of
>>> that, newcomers to the community might find it difficult to understand our
>>> workflow.
>>
>>
>> Currently it is
>> 
>> 
>> 
>> Suggest a feature!
>> 
>> 
>>
>> which points to old wiki.
>>
>> Would it be better to have
>> Suggest a feature
>> there?
>>
>> Makes sense. Is it possible to send mail to this list without
>> registration? or moderator can verify the feature mail from unsubscribed
>> user and allow?
>>
>
> I did not think of this. I will let someone who knows how mailman works
> reply.
>
>
>>
>> Thanks,
>> Raghavendra Talur
>>
>>>
>>>
>>> -Vijay
>>>
>>>
>>>
>>>
>>
>>
>> ___
>> Gluster-devel mailing 
>> listGluster-devel@gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-devel
>>
>>
>>
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>



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

Re: [Gluster-devel] Suggest a feature redirect

[Sankarshan Mukhopadhyay]

On Wed, May 18, 2016 at 2:43 PM, Amye Scavarda  wrote:

> Said another way, if you wanted to be able to have someone contribute a
> feature idea, what would be the best way?
> Bugzilla? A google form? An email into the -devel list?
>

Whether it is a new BZ/RFE; a line item on a spreadsheet (via a form)
or, an email to the list - the incoming bits would need to be reviewed
and decided upon. A path which enables the Gluster community to
showcase in a public manner the received ideas and how they have
enabled features in the product would be the best thing to do.

The individual contributing the feature idea needs to know that
something was done with it and it wasn't a /dev/null


-- 
sankarshan mukhopadhyay

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

[Gluster-devel] GlusterFS 3.8 RC2 is coming soon

[Niels de Vos]

Hi,

just a heads up that I'm planning to tag glusterfs-3.8rc2 later today.
There are still some patches that are in need of reviews, please keep an
eye open for those with this link:

  http://review.gluster.org/#/q/status:open+project:glusterfs+branch:release-3.8

In addition to more patches that want to get included in 3.8 GA, we are
still waiting for more details in the release-notes. Please have a look
there and try to resolve some of the TODO items:

  https://public.pad.fsfe.org/p/glusterfs-3.8-release-notes

My plan is to mark all bugs that are still open, but should have been
fixed with this release as ON_QA and fixed_in_version=glusterfs-3.8rc2.
This sends a heads-up to the users that reported the bugs, and an
request for testing will be done on the users list as well.

Urgent issues that ABSOLUTELY need fixing before GA need to have a bug
with "glusterfs-3.8.0" in the "blocks" field. Those bugs will then be
attached to the tracker and should be listed here:

  
https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-3.8.0&maxdepth=2&hide_resolved=1

Thanks,
Niels


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Meeting minutes: Gluster Community Bug Triage

[Saravanakumar Arumugam]

Hi,

Please find the meeting minutes and summary:


 Minutes:

 Minutes: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-05-24/gluster_bug_triage.2016-05-24-12.00.html
 Minutes (text): 
https://meetbot.fedoraproject.org/gluster-meeting/2016-05-24/gluster_bug_triage.2016-05-24-12.00.txt
 Log: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-05-24/gluster_bug_triage.2016-05-24-12.00.log.html



 Meeting summary:

1. *Roll call* (Saravanakmr
   
,
   12:01:10)
2. *msvbhat will look into lalatenduM's automated Coverity setup in
   Jenkins which need assistance from an admin with more permissions*
   (Saravanakmr
   
,
   12:04:57)
1. /ACTION/: msvbhat will look into lalatenduM's automated Coverity
   setup in Jenkins which need assistance from an admin with more
   permissions (Saravanakmr
   
,
   12:06:06)

3. *ndevos need to decide on how to provide/use debug builds*
   (Saravanakmr
   
,
   12:06:18)
1. /ACTION/: ndevos need to decide on how to provide/use debug
   builds (Saravanakmr
   
,
   12:07:10)

4. *Manikandan and gem to followup with kshlm to get access to
   gluster-infra* (Saravanakmr
   
,
   12:08:34)
1. /ACTION/: Manikandan and gem to followup with kshlm to get
   access to gluster-infra (Saravanakmr
   
,
   12:09:25)

5. *ndevos to propose some test-cases for minimal libgfapi test*
   (Saravanakmr
   
,
   12:09:42)
1. /ACTION/: ndevos to propose some test-cases for minimal libgfapi
   test (Saravanakmr
   
,
   12:09:51)

6. *Group Triage* (Saravanakmr
   
,
   12:10:08)
1. you can fine the bugs to triage here in
   https://public.pad.fsfe.org/p/gluster-bugs-to-triage
   (Saravanakmr
   
,
   12:10:15)

7. *Open Floor* (Saravanakmr
   
,
   12:34:49)



Meeting ended at 12:37:02 UTC (full logs 
). 




 Action items

1. msvbhat will look into lalatenduM's automated Coverity setup in
   Jenkins which need assistance from an admin with more permissions
2. ndevos need to decide on how to provide/use debug builds
3. Manikandan and gem to followup with kshlm to get access to gluster-infra
4. ndevos to propose some test-cases for minimal libgfapi test


 Action items, by person

1. ndevos
1. ndevos need to decide on how to provide/use debug builds
2. ndevos to propose some test-cases for minimal libgfapi test
2. *UNASSIGNED*
1. msvbhat will look into lalatenduM's automated Coverity setup in
   Jenkins which need assistance from an admin with more permissions
2. Manikandan and gem to followup with kshlm to get access to
   gluster-infra


 People present (lines said)

1. Saravanakmr (31)
2. jiffin (3)
3. kkeithley (3)
4. zodbot (3)
5. hgowtham (3)
6. skoduri (1)
7. ndevos (1)

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

[Gluster-devel] Weekly Community Meeting - 18/May/2016

[Raghavendra Talur]

The meeting minutes for this weeks meeting are available at

Minutes:
https://meetbot.fedoraproject.org/gluster-meeting/2016-05-18/weekly_community_meeting_18may2016.2016-05-18-12.06.html
Minutes (text):
https://meetbot-raw.fedoraproject.org/gluster-meeting/2016-05-18/weekly_community_meeting_18may2016.2016-05-18-12.06.txt
Log:
https://meetbot.fedoraproject.org/gluster-meeting/2016-05-18/weekly_community_meeting_18may2016.2016-05-18-12.06.log.html

Next weeks meeting will be held at the same time.

Thanks,
Raghavendra Talur




Meeting summary
---
* Rollcall  (rastar, 12:07:08)

* Next weeks meeting host  (rastar, 12:09:28)

* kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla,
  github  (rastar, 12:10:55)
  * ACTION: kshlm/csim/nigelb to set up faux/pseudo user email for
gerrit, bugzilla, github  (rastar, 12:13:19)

* amye to check on some blog posts being distorted on blog.gluster.org,
  josferna's post in particular  (rastar, 12:13:34)
  * ACTION: aravinda/amye to check on some blog posts being distorted on
blog.gluster.org, josferna's post in particular  (rastar, 12:15:09)

* pranithk1 sends out a summary of release requirements, with some ideas
  (rastar, 12:15:27)
  * ACTION: hagarth to announce release strategy after getting inputs
from amye  (rastar, 12:21:50)

* kshlm to check with reported of 3.6 leaks on backport need  (rastar,
  12:22:37)
  * ACTION: kshlm to check with reported of 3.6 leaks on backport need
(rastar, 12:23:12)

* GlusterFS 3.7  (rastar, 12:23:38)

* GlusterFS 3.6  (rastar, 12:33:06)

* GlusterFS 3.5  (rastar, 12:37:50)

* GlusterFS 3.8  (rastar, 12:39:15)
  * LINK:
http://thread.gmane.org/gmane.comp.file-systems.gluster.maintainers/727
(ndevos, 12:40:11)
  * FYI (reminder) we don't (can't) ship in EPEL because RHS/RHGS
client-side pkgs are in RHEL.  We took a decision to not provide
el[567] 3.8 pkgs on download.gluster.org because they will be in the
CentOS Storage SIG  (kkeithley, 12:46:23)

* GlusterFS 4.0  (rastar, 12:49:04)

* NFS Ganesha and Gluster updates  (rastar, 12:52:53)

* Samba and Gluster  (rastar, 13:00:22)

* open floor  (rastar, 13:08:26)
  * HELP: packagers for lio/tcmu-runner with libgfapi wanted to get the
packages in the CentOS Storage SIG  (ndevos, 13:11:04)
  * IDEA: thought for the day: devs should occasionally do a build on a
32-bit system. It's a good way to catch log/printf format string
mistakes  (kkeithley, 13:11:41)
  * LINK: https://www.gluster.org/events/   (ndevos, 13:14:50)
  * ACTION: Saravanakmr to add documentation on how to add blogs
(rastar, 13:17:44)

Meeting ended at 13:25:03 UTC.




Action Items

* kshlm/csim/nigelb to set up faux/pseudo user email for gerrit,
  bugzilla, github
* aravinda/amye to check on some blog posts being distorted on
  blog.gluster.org, josferna's post in particular
* hagarth to announce release strategy after getting inputs from amye
* kshlm to check with reported of 3.6 leaks on backport need
* Saravanakmr to add documentation on how to add blogs




Action Items, by person
---
* amye
  * aravinda/amye to check on some blog posts being distorted on
blog.gluster.org, josferna's post in particular
  * hagarth to announce release strategy after getting inputs from amye
* hagarth
  * hagarth to announce release strategy after getting inputs from amye
* Saravanakmr
  * Saravanakmr to add documentation on how to add blogs
* **UNASSIGNED**
  * kshlm/csim/nigelb to set up faux/pseudo user email for gerrit,
bugzilla, github
  * kshlm to check with reported of 3.6 leaks on backport need




People Present (lines said)
---
* rastar (92)
* ndevos (65)
* kkeithley (38)
* hagarth (36)
* post-factum (35)
* ira (15)
* Saravanakmr (10)
* amye (6)
* jdarcy (5)
* obnox_ (3)
* zodbot (3)
* anoopcs (1)
* misc (1)
* atinm (1)
* obnox (1)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel