Re: [Gluster-devel] Release 4.0: Making it happen!

2018-01-22 Thread Raghavendra G 
https://github.com/gluster/glusterfs/issues/397

The patch has been in discussion for quite some time. Thanks to efforts
from Amar, its good to be merged. I've proposed it for 4.0 for now. If the
branching is done or if you feel its not fit for 4.0 branch, please feel
free to change the milestone to appropriate version (maybe 4.1?)

On Fri, Jan 19, 2018 at 9:30 AM, Jiffin Tony Thottan 
wrote:

>
>
> On Wednesday 17 January 2018 04:55 PM, Jiffin Tony Thottan wrote:
>
>>
>>
>> On Tuesday 16 January 2018 08:57 PM, Shyam Ranganathan wrote:
>>
>>> On 01/10/2018 01:14 PM, Shyam Ranganathan wrote:
>>>
 Hi,

 4.0 branching date is slated on the 16th of Jan 2018 and release is
 slated for the end of Feb (28th), 2018.

>>> This is today! So read on...
>>>
>>> Short update: I am going to wait a couple more days before branching, to
>>> settle release content and exceptions. Branching is hence on Jan, 18th
>>> (Thursday).
>>>
>>> We are at the phase when we need to ensure our release scope is correct
 and *must* release features are landing. Towards this we need the
 following information for all contributors.

 1) Features that are making it to the release by branching date

 - There are currently 35 open github issues marked as 4.0 milestone [1]
 - Need contributors to look at this list and let us know which will meet
 the branching date

>>> Other than the protocol changes (from Amar), I did not receive any
>>> requests for features that are making it to the release. I have compiled
>>> a list of features based on patches in gerrit that are open, to check
>>> what features are viable to make it to 4.0. This can be found here [3].
>>>
>>> NOTE: All features, other than the ones in [3] are being moved out of
>>> the 4.0 milestone.
>>>
>>> - Need contributors to let us know which may slip and hence needs a
 backport exception to 4.0 branch (post branching).
 - Need milestone corrections on features that are not making it to the
 4.0 release

>>> I need the following contributors to respond and state if the feature in
>>> [3] should still be tracked against 4.0 and how much time is possibly
>>> needed to make it happen.
>>>
>>> - Poornima, Amar, Jiffin, Du, Susant, Sanoj, Vijay
>>>
>>
>> Hi,
>>
>> The two gfapi[1,2] related changes have ack from poornima and Niels
>> mentioned that he will do the review by EOD.
>>
>> [1] https://review.gluster.org/#/c/18784/
>> [2] https://review.gluster.org/#/c/18785/
>>
>>
>>
> Niels has few comments on above patch. I need to have one week
> extension(26th Jan 2018)
> --
> Jiffin
>
>
> Regards,
>> Jiffin
>>
>>
>>> NOTE: Slips are accepted if they fall 1-1.5 weeks post branching, not
 post that, and called out before branching!

 2) Reviews needing priority

 - There could be features that are up for review, and considering we
 have about 6-7 days before branching, we need a list of these commits,
 that you want review attention on.
 - This will be added to this [2] dashboard, easing contributor access to
 top priority reviews before branching

>>> As of now, I am adding a few from the list in [3] for further review
>>> attention as I see things evolving, more will be added as the point
>>> above is answered by the respective contributors.
>>>
>>> 3) Review help!

 - This link [2] contains reviews that need attention, as they are
 targeted for 4.0. Request maintainers and contributors to pay close
 attention to this list on a daily basis and help out with reviews.

 Thanks,
 Shyam

 [1] github issues marked for 4.0:
 https://github.com/gluster/glusterfs/milestone/3

 [2] Review focus for features planned to land in 4.0:
 https://review.gluster.org/#/q/owner:srangana%2540redhat.com+is:starred

>>> [3] Release 4.0 features with pending code reviews:
>>> http://bit.ly/2rbjcl8
>>>
>>> ___
 Gluster-devel mailing list
 Gluster-devel@gluster.org
 http://lists.gluster.org/mailman/listinfo/gluster-devel

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



-- 
Raghavendra G
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 4.0: Making it happen!

2018-01-18 Thread Jiffin Tony Thottan 



On Wednesday 17 January 2018 04:55 PM, Jiffin Tony Thottan wrote:



On Tuesday 16 January 2018 08:57 PM, Shyam Ranganathan wrote:

On 01/10/2018 01:14 PM, Shyam Ranganathan wrote:

Hi,

4.0 branching date is slated on the 16th of Jan 2018 and release is
slated for the end of Feb (28th), 2018.

This is today! So read on...

Short update: I am going to wait a couple more days before branching, to
settle release content and exceptions. Branching is hence on Jan, 18th
(Thursday).


We are at the phase when we need to ensure our release scope is correct
and *must* release features are landing. Towards this we need the
following information for all contributors.

1) Features that are making it to the release by branching date

- There are currently 35 open github issues marked as 4.0 milestone [1]
- Need contributors to look at this list and let us know which will 
meet

the branching date

Other than the protocol changes (from Amar), I did not receive any
requests for features that are making it to the release. I have compiled
a list of features based on patches in gerrit that are open, to check
what features are viable to make it to 4.0. This can be found here [3].

NOTE: All features, other than the ones in [3] are being moved out of
the 4.0 milestone.


- Need contributors to let us know which may slip and hence needs a
backport exception to 4.0 branch (post branching).
- Need milestone corrections on features that are not making it to the
4.0 release

I need the following contributors to respond and state if the feature in
[3] should still be tracked against 4.0 and how much time is possibly
needed to make it happen.

- Poornima, Amar, Jiffin, Du, Susant, Sanoj, Vijay


Hi,

The two gfapi[1,2] related changes have ack from poornima and Niels 
mentioned that he will do the review by EOD.


[1] https://review.gluster.org/#/c/18784/
[2] https://review.gluster.org/#/c/18785/




Niels has few comments on above patch. I need to have one week 
extension(26th Jan 2018)

--
Jiffin


Regards,
Jiffin




NOTE: Slips are accepted if they fall 1-1.5 weeks post branching, not
post that, and called out before branching!

2) Reviews needing priority

- There could be features that are up for review, and considering we
have about 6-7 days before branching, we need a list of these commits,
that you want review attention on.
- This will be added to this [2] dashboard, easing contributor 
access to

top priority reviews before branching

As of now, I am adding a few from the list in [3] for further review
attention as I see things evolving, more will be added as the point
above is answered by the respective contributors.


3) Review help!

- This link [2] contains reviews that need attention, as they are
targeted for 4.0. Request maintainers and contributors to pay close
attention to this list on a daily basis and help out with reviews.

Thanks,
Shyam

[1] github issues marked for 4.0:
https://github.com/gluster/glusterfs/milestone/3

[2] Review focus for features planned to land in 4.0:
https://review.gluster.org/#/q/owner:srangana%2540redhat.com+is:starred
[3] Release 4.0 features with pending code reviews: 
http://bit.ly/2rbjcl8



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


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


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


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

Re: [Gluster-devel] Release 4.0: Making it happen!

2018-01-17 Thread Susant Palai 
Hi,
   I would request some extension.  Targetting for the 27th weekend.

Thanks,
Susant

On Tue, Jan 16, 2018 at 8:57 PM, Shyam Ranganathan 
wrote:

> On 01/10/2018 01:14 PM, Shyam Ranganathan wrote:
> > Hi,
> >
> > 4.0 branching date is slated on the 16th of Jan 2018 and release is
> > slated for the end of Feb (28th), 2018.
>
> This is today! So read on...
>
> Short update: I am going to wait a couple more days before branching, to
> settle release content and exceptions. Branching is hence on Jan, 18th
> (Thursday).
>
> >
> > We are at the phase when we need to ensure our release scope is correct
> > and *must* release features are landing. Towards this we need the
> > following information for all contributors.
> >
> > 1) Features that are making it to the release by branching date
> >
> > - There are currently 35 open github issues marked as 4.0 milestone [1]
> > - Need contributors to look at this list and let us know which will meet
> > the branching date
>
> Other than the protocol changes (from Amar), I did not receive any
> requests for features that are making it to the release. I have compiled
> a list of features based on patches in gerrit that are open, to check
> what features are viable to make it to 4.0. This can be found here [3].
>
> NOTE: All features, other than the ones in [3] are being moved out of
> the 4.0 milestone.
>
> > - Need contributors to let us know which may slip and hence needs a
> > backport exception to 4.0 branch (post branching).
> > - Need milestone corrections on features that are not making it to the
> > 4.0 release
>
> I need the following contributors to respond and state if the feature in
> [3] should still be tracked against 4.0 and how much time is possibly
> needed to make it happen.
>
> - Poornima, Amar, Jiffin, Du, Susant, Sanoj, Vijay
>
> >
> > NOTE: Slips are accepted if they fall 1-1.5 weeks post branching, not
> > post that, and called out before branching!
> >
> > 2) Reviews needing priority
> >
> > - There could be features that are up for review, and considering we
> > have about 6-7 days before branching, we need a list of these commits,
> > that you want review attention on.
> > - This will be added to this [2] dashboard, easing contributor access to
> > top priority reviews before branching
>
> As of now, I am adding a few from the list in [3] for further review
> attention as I see things evolving, more will be added as the point
> above is answered by the respective contributors.
>
> >
> > 3) Review help!
> >
> > - This link [2] contains reviews that need attention, as they are
> > targeted for 4.0. Request maintainers and contributors to pay close
> > attention to this list on a daily basis and help out with reviews.
> >
> > Thanks,
> > Shyam
> >
> > [1] github issues marked for 4.0:
> > https://github.com/gluster/glusterfs/milestone/3
> >
> > [2] Review focus for features planned to land in 4.0:
> > https://review.gluster.org/#/q/owner:srangana%2540redhat.com+is:starred
>
> [3] Release 4.0 features with pending code reviews: http://bit.ly/2rbjcl8
>
> >
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-devel
> >
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 4.0: Making it happen!

2018-01-17 Thread Jiffin Tony Thottan 



On Tuesday 16 January 2018 08:57 PM, Shyam Ranganathan wrote:

On 01/10/2018 01:14 PM, Shyam Ranganathan wrote:

Hi,

4.0 branching date is slated on the 16th of Jan 2018 and release is
slated for the end of Feb (28th), 2018.

This is today! So read on...

Short update: I am going to wait a couple more days before branching, to
settle release content and exceptions. Branching is hence on Jan, 18th
(Thursday).


We are at the phase when we need to ensure our release scope is correct
and *must* release features are landing. Towards this we need the
following information for all contributors.

1) Features that are making it to the release by branching date

- There are currently 35 open github issues marked as 4.0 milestone [1]
- Need contributors to look at this list and let us know which will meet
the branching date

Other than the protocol changes (from Amar), I did not receive any
requests for features that are making it to the release. I have compiled
a list of features based on patches in gerrit that are open, to check
what features are viable to make it to 4.0. This can be found here [3].

NOTE: All features, other than the ones in [3] are being moved out of
the 4.0 milestone.


- Need contributors to let us know which may slip and hence needs a
backport exception to 4.0 branch (post branching).
- Need milestone corrections on features that are not making it to the
4.0 release

I need the following contributors to respond and state if the feature in
[3] should still be tracked against 4.0 and how much time is possibly
needed to make it happen.

- Poornima, Amar, Jiffin, Du, Susant, Sanoj, Vijay


Hi,

The two gfapi[1,2] related changes have ack from poornima and Niels 
mentioned that he will do the review by EOD.


[1] https://review.gluster.org/#/c/18784/
[2] https://review.gluster.org/#/c/18785/

Regards,
Jiffin




NOTE: Slips are accepted if they fall 1-1.5 weeks post branching, not
post that, and called out before branching!

2) Reviews needing priority

- There could be features that are up for review, and considering we
have about 6-7 days before branching, we need a list of these commits,
that you want review attention on.
- This will be added to this [2] dashboard, easing contributor access to
top priority reviews before branching

As of now, I am adding a few from the list in [3] for further review
attention as I see things evolving, more will be added as the point
above is answered by the respective contributors.


3) Review help!

- This link [2] contains reviews that need attention, as they are
targeted for 4.0. Request maintainers and contributors to pay close
attention to this list on a daily basis and help out with reviews.

Thanks,
Shyam

[1] github issues marked for 4.0:
https://github.com/gluster/glusterfs/milestone/3

[2] Review focus for features planned to land in 4.0:
https://review.gluster.org/#/q/owner:srangana%2540redhat.com+is:starred

[3] Release 4.0 features with pending code reviews: http://bit.ly/2rbjcl8


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


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


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

Re: [Gluster-devel] Release 4.0: Making it happen!

2018-01-16 Thread Shyam Ranganathan 
On 01/10/2018 01:14 PM, Shyam Ranganathan wrote:
> Hi,
> 
> 4.0 branching date is slated on the 16th of Jan 2018 and release is
> slated for the end of Feb (28th), 2018.

This is today! So read on...

Short update: I am going to wait a couple more days before branching, to
settle release content and exceptions. Branching is hence on Jan, 18th
(Thursday).

> 
> We are at the phase when we need to ensure our release scope is correct
> and *must* release features are landing. Towards this we need the
> following information for all contributors.
> 
> 1) Features that are making it to the release by branching date
> 
> - There are currently 35 open github issues marked as 4.0 milestone [1]
> - Need contributors to look at this list and let us know which will meet
> the branching date

Other than the protocol changes (from Amar), I did not receive any
requests for features that are making it to the release. I have compiled
a list of features based on patches in gerrit that are open, to check
what features are viable to make it to 4.0. This can be found here [3].

NOTE: All features, other than the ones in [3] are being moved out of
the 4.0 milestone.

> - Need contributors to let us know which may slip and hence needs a
> backport exception to 4.0 branch (post branching).
> - Need milestone corrections on features that are not making it to the
> 4.0 release

I need the following contributors to respond and state if the feature in
[3] should still be tracked against 4.0 and how much time is possibly
needed to make it happen.

- Poornima, Amar, Jiffin, Du, Susant, Sanoj, Vijay

> 
> NOTE: Slips are accepted if they fall 1-1.5 weeks post branching, not
> post that, and called out before branching!
> 
> 2) Reviews needing priority
> 
> - There could be features that are up for review, and considering we
> have about 6-7 days before branching, we need a list of these commits,
> that you want review attention on.
> - This will be added to this [2] dashboard, easing contributor access to
> top priority reviews before branching

As of now, I am adding a few from the list in [3] for further review
attention as I see things evolving, more will be added as the point
above is answered by the respective contributors.

> 
> 3) Review help!
> 
> - This link [2] contains reviews that need attention, as they are
> targeted for 4.0. Request maintainers and contributors to pay close
> attention to this list on a daily basis and help out with reviews.
> 
> Thanks,
> Shyam
> 
> [1] github issues marked for 4.0:
> https://github.com/gluster/glusterfs/milestone/3
> 
> [2] Review focus for features planned to land in 4.0:
> https://review.gluster.org/#/q/owner:srangana%2540redhat.com+is:starred

[3] Release 4.0 features with pending code reviews: http://bit.ly/2rbjcl8

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

Re: [Gluster-devel] Release 4.0: Making it happen! (Protocol changes and wireshark)

2018-01-12 Thread Niels de Vos 
On Wed, Jan 10, 2018 at 03:36:55PM -0500, Shyam Ranganathan wrote:
> Hi,
> 
> As we are introducing a new protocol version, the existing gluster
> wireshark plugin [1] needs to be updated.
> 
> Further this needs to get released to wireshark users in some fashion,
> which looks like a need to follow wireshark roadmap [2] (not sure if
> this can be part of a maintenance release, which would possibly be based
> on the quantum of changes etc.).
> 
> This need not happen with 4.0 branching, but at least has to be
> completed before 4.0 release.
> 
> @neils once the protocol changes are complete, would this be possible to
> complete by you in the next 6 odd weeks by the release (end of Feb)? Or,
> if we need volunteers, please give a shout out here.

Adding the new bits to the Wireshark dissector is pretty straight
forward. Once the protocol changes have been done, it would be good to
have a few .pcap files captured that can be used for developing and
testing the changes. This can even be done in steps, as soon as one
chunk of the protocol is finalized, a patch to upstream Wireshark can be
sent already. We can improve it incrementally that way, also making it
easier for multiple contributors to work on it.

I can probably do some of the initial work, but would like assistance
from others with testing and possibly improving certain parts. If
someone can provide tcpdumps with updated protocol changes, that would
be most welcome! Capture the dumps like this:

  # tcpdump -i any -w /var/tmp/gluster-40-${proto_change}.pcap -s 0 tcp and not 
port 22
  ... exercise the protocol bit that changed, include connection setup
  ... press CTRL+C once done
  # gzip /var/tmp/gluster-40-${proto_change}.pcap
  ... Wireshark can read .pcap.gz without manual decompressing

Attach the .pcap.gz to the GitHub issue for the protocol change and
email gluster-devel@ once it is available so that a developer can start
working on the Wireshark change.

Thanks,
Niels


> 
> Shyam
> 
> [1] Gluster wireshark plugin:
> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=tree;f=epan/dissectors;h=8c8303285a204bdff3b8b80e2811dcd9b7ab6fe0;hb=HEAD
> 
> [2] Wireshark roadmap: https://wiki.wireshark.org/Development/Roadmap
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Release 4.0: Making it happen! (Protocol changes and wireshark)

2018-01-10 Thread Shyam Ranganathan 
Hi,

As we are introducing a new protocol version, the existing gluster
wireshark plugin [1] needs to be updated.

Further this needs to get released to wireshark users in some fashion,
which looks like a need to follow wireshark roadmap [2] (not sure if
this can be part of a maintenance release, which would possibly be based
on the quantum of changes etc.).

This need not happen with 4.0 branching, but at least has to be
completed before 4.0 release.

@neils once the protocol changes are complete, would this be possible to
complete by you in the next 6 odd weeks by the release (end of Feb)? Or,
if we need volunteers, please give a shout out here.

Shyam

[1] Gluster wireshark plugin:
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=tree;f=epan/dissectors;h=8c8303285a204bdff3b8b80e2811dcd9b7ab6fe0;hb=HEAD

[2] Wireshark roadmap: https://wiki.wireshark.org/Development/Roadmap

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

[Gluster-devel] Release 4.0: Making it happen! (GlusterD2)

2018-01-10 Thread Shyam Ranganathan 
Hi, (GD2 team, packaging team, please read)

Here are some things we need to settle so that we can ship/release GD2
along with Gluster 4.0 release (considering this is a separate
repository as of now).

1) Generating release package (read as RPM for now) to go with Gluster
4.0 release

Proposal:
  - GD2 makes github releases, as in [1]

  - GD2 Releases (tagging etc.) are made in tandem to Gluster releases
- So, when an beta1/RC0 is tagged for gluster release, this will
receive a coordinated release (if required) from the GD2 team
- GD2 team will receive *at-least* a 24h notice on a tentative
Gluster tagging date/time, to aid the GD2 team to prepare the required
release tarball in github

  - Post a gluster tag being created, and the subsequent release job is
run for gluster 4.0, the packaging team will be notified about which GD2
tag to pick up for packaging, with this gluster release
- IOW, a response to the Jenkins generated packaging job, with the
GD2 version/tag/release to pick up

  - GD2 will be packaged as a sub-package of the glusterfs package, and
hence will have appropriate changes to the glusterfs spec file (or other
variants of packaging as needed), to generate one more package (RPM) to
post in the respective download location

  - The GD2 package version would be the same as the release version
that GD2 makes (it will not be the gluster package version, at least for
now)

  - For now, none of the gluster RPMs would be dependent on the GD2 RPM
in the downloads, so any user wanting to use GD2 would have to install
the package specifically and then proceed as needed

  - (thought/concern) Jenkins smoke job (or other jobs) that builds RPMs
will not build GD2 (as the source is not available) and will continue as
is (which means there is enough spec file magic here that we can specify
during release packaging to additionally build GD2)

2) Generate a quick start or user guide, to aid using GD2 with 4.0

@Kaushal if this is generated earlier (say with beta builds of 4.0
itself) we could get help from the community to test drive the same and
provide feedback to improve the guide for users by the release (as
discussed in the maintainers meeting).

Thanks,
Shyam

[1] github GD2 releases: https://github.com/gluster/glusterd2/releases
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Release 4.0: Making it happen!

2018-01-10 Thread Shyam Ranganathan 
Hi,

4.0 branching date is slated on the 16th of Jan 2018 and release is
slated for the end of Feb (28th), 2018.

We are at the phase when we need to ensure our release scope is correct
and *must* release features are landing. Towards this we need the
following information for all contributors.

1) Features that are making it to the release by branching date

- There are currently 35 open github issues marked as 4.0 milestone [1]
- Need contributors to look at this list and let us know which will meet
the branching date
- Need contributors to let us know which may slip and hence needs a
backport exception to 4.0 branch (post branching).
- Need milestone corrections on features that are not making it to the
4.0 release

NOTE: Slips are accepted if they fall 1-1.5 weeks post branching, not
post that, and called out before branching!

2) Reviews needing priority

- There could be features that are up for review, and considering we
have about 6-7 days before branching, we need a list of these commits,
that you want review attention on.
- This will be added to this [2] dashboard, easing contributor access to
top priority reviews before branching

3) Review help!

- This link [2] contains reviews that need attention, as they are
targeted for 4.0. Request maintainers and contributors to pay close
attention to this list on a daily basis and help out with reviews.

Thanks,
Shyam

[1] github issues marked for 4.0:
https://github.com/gluster/glusterfs/milestone/3

[2] Review focus for features planned to land in 4.0:
https://review.gluster.org/#/q/owner:srangana%2540redhat.com+is:starred

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