Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May

[Mohammed Rafi K C]

Hi Shyam,

Myself and Sunny are working on snapshot integration effort to gd2. So
we wanted to propose the feature for 4.1,

issue : https://github.com/gluster/glusterd2/issues/461

status : There are were two patch sets targeted, one is merged, one is
under review. One is under development.


Regards

Rafi KC



>
> On Wed, Mar 21, 2018 at 2:05 PM, Ravishankar N  > wrote:
>
>
>
> On 03/20/2018 07:07 PM, Shyam Ranganathan wrote:
>
> On 03/12/2018 09:37 PM, Shyam Ranganathan wrote:
>
> Hi,
>
> As we wind down on 4.0 activities (waiting on docs to hit
> the site, and
> packages to be available in CentOS repositories before
> announcing the
> release), it is time to start preparing for the 4.1 release.
>
> 4.1 is where we have GD2 fully functional and shipping
> with migration
> tools to aid Glusterd to GlusterD2 migrations.
>
> Other than the above, this is a call out for features that
> are in the
> works for 4.1. Please *post* the github issues to the
> *devel lists* that
> you would like as a part of 4.1, and also mention the
> current state of
> development.
>
> Thanks for those who responded. The github lane and milestones
> for the
> said features are updated, request those who mentioned issues
> being
> tracked for 4.1 check that these are reflected in the project
> lane [1].
>
> I have few requests as follows that if picked up would be a
> good thing
> to achieve by 4.1, volunteers welcome!
>
> - Issue #224: Improve SOS report plugin maintenance
>- https://github.com/gluster/glusterfs/issues/224
> 
>
> - Issue #259: Compilation warnings with gcc 7.x
>- https://github.com/gluster/glusterfs/issues/259
> 
>
> - Issue #411: Ensure python3 compatibility across code base
>- https://github.com/gluster/glusterfs/issues/411
> 
>
> - NFS Ganesha HA (storhaug)
>- Does this need an issue for Gluster releases to track?
> (maybe packaging)
>
> I will close the call for features by Monday 26th Mar, 2018.
> Post this,
> I would request that features that need to make it into 4.1 be
> raised as
> exceptions to the devel and maintainers list for evaluation.
>
>
> Hi Shyam,
>
> I want to add https://github.com/gluster/glusterfs/issues/363
>  also for 4.1. It
> is not a new feature but rather an enhancement to a volume option
> in AFR. I don't think it can qualify as a bug fix, so mentioning
> it here just in case it needs to be tracked too. The (only) patch
> is undergoing review cycles.
>
> Regards,
> Ravi
>
>
> Further, as we hit end of March, we would make it
> mandatory for features
> to have required spec and doc labels, before the code is
> merged, so
> factor in efforts for the same if not already done.
>
> Current 4.1 project release lane is empty! I cleaned it
> up, because I
> want to hear from all as to what content to add, than add
> things marked
> with the 4.1 milestone by default.
>
> [1] 4.1 Release lane:
> https://github.com/gluster/glusterfs/projects/1#column-1075416
> 
>
> Thanks,
> Shyam
> P.S: Also any volunteers to shadow/participate/run 4.1 as
> a release owner?
>
> Calling this out again!
>
> ___
> 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
> 
>
>
>
>
> -- 
> Thanks and Regards,
> Kotresh H R
>
>
> _

[Gluster-devel] Maintainer's meeting minutes (21st March, 2018)

[Amar Tumballi]

Meeting date: 03/07/2018 (March 3rd, 2018. 19:30IST, 14:00UTC, 09:00EST)
BJ Link

   - Bridge: https://bluejeans.com/205933580
   - Download: https://bluejeans.com/s/huECj

Attendance

   - Amar, Kaleb, PPai, Nithya, Sac, Deepshika, Shyam (joined late)

Agenda

   -

   AI from previous meeting:
   - Email on version numbers: [Done]
  - Email on 4.1 features: [Done]
  - Email on bugzilla automation etc: [Done]
   -

   Any more features required, wanted in 4.1?
   - Question to FB team: are you fine with features being merged? Any more
  pending features, bug fixes from FB branch?
  - Question to Red Hat: are the features fine?
  - Question to community: Is there any concerns?
  - GD2: Can we update the community about the proposal for 4.1
 - [PPai] we can send the github link to the project to community.
  -

   https://bugzilla.redhat.com/show_bug.cgi?id=1193929
   -

   If agreed for option change, what would be good version number next?
   - [Sac] Need more discipline to have calendar based releases
  - [ppai] http://semver.org is more practised
   -

   Round Table
   - [kaleb] fyi, I’m NOT making progress with debian packaging of gd2.
  I’ve been told that Marcus (a nfs-ganesha/ceph dev) has Debian pkging
  skillz. When he returns from the Ceph dev conf in China I’ll see if I can
  get some of his time. Also my appeals for help from debian packages and
  from Patrick Matthaie have gone unanswered. Debian packaging is already
  voodoo black magic; golang makes it even harder. ;-)
  - [amarts] auto tunable options is the future requirement for us.
  Everyone, please consider figuring out for your components work for it.
  - [shyam] I see a good response for features this time. Expectation
  is to meet what we promised. See github projects page for seeing whats
  agreed for 4.1




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

[Gluster-devel] tendrl-release v1.6.2 (milestone-4 2018) is available

[Rohan Kanade]

The Tendrl team is happy to present tendrl-release v1.6.2 (milestone-4 2018)

Install docs:
https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.6.2-(install-guide)
Metrics: https://github.com/Tendrl/documentation/wiki/Metrics

Changelog:

Backend:
- Tendrl will now generate alerts with severity "critical" (this is a
threshold alert)
- Aggregate more gluster metric collection instead of per node
- Alert on new peer addition
- Multipath disk layout detection support

Details:
- https://github.com/Tendrl/commons/milestone/4
- https://github.com/Tendrl/node-agent/milestone/4
- https://github.com/Tendrl/gluster-integration/milestone/4
- https://github.com/Tendrl/monitoring-integration/milestone/4

### API
- Expand cluster via the API
- https://github.com/Tendrl/commons/milestone/4

### UI
- Trigger expand cluster via the UI
- https://github.com/Tendrl/ui/milestone/4



Next Release:
- Support gluster deployments with IP address based peers and/or FQDN based
peers
- Support packing/unpacking Tendrl objects
- Unmanage cluster per node
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Coverity covscan for 2018-03-22-5b46d556 (master branch)

[staticanalysis]

GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-22-5b46d556
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May

[Shyam Ranganathan]

On 03/21/2018 04:12 AM, Amar Tumballi wrote:
> Current 4.1 project release lane is empty! I cleaned it up, because I
> want to hear from all as to what content to add, than add things marked
> with the 4.1 milestone by default.
> 
> 
> I would like to see we have sane default values for most of the options,
> or have group options for many use-cases.

Amar, do we have an issue that lists the use-cases and hence the default
groups to be provided for the same?

> 
> Also want to propose that,  we include a release
> of http://github.com/gluster/gluster-health-report with 4.1, and make
> the project more usable.

In the theme of including sub-projects that we want to highlight, what
else should we tag a release for or highlight with 4.1?

@Aravinda, how do you envision releasing this with 4.1? IOW, what
interop tests and hence sanity can be ensured with 4.1 and how can we
tag a release that is sane against 4.1?

> 
> Also, we see that some of the patches from FB branch on namespace and
> throttling are in, so we would like to call that feature out as
> experimental by then.

I would assume we track this against
https://github.com/gluster/glusterfs/issues/408 would that be right?
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Release 4.0.2: Planned for the 20th of Apr, 2018

[Shyam Ranganathan]

Hi,

As release 4.0.1 is (to be) announced, here is are the needed details
for 4.0.2

Release date: 20th Apr, 2018
Tracker bug for blockers:
https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-4.0.2

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

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: LTM release targeted for end of May

[Amar Tumballi]

On Thu, Mar 22, 2018 at 11:34 PM, Shyam Ranganathan 
wrote:

> On 03/21/2018 04:12 AM, Amar Tumballi wrote:
> > Current 4.1 project release lane is empty! I cleaned it up, because I
> > want to hear from all as to what content to add, than add things
> marked
> > with the 4.1 milestone by default.
> >
> >
> > I would like to see we have sane default values for most of the options,
> > or have group options for many use-cases.
>
> Amar, do we have an issue that lists the use-cases and hence the default
> groups to be provided for the same?
>
>
Considering group options' task is more in glusterd2, the issue is @
https://github.com/gluster/glusterd2/issues/614 &
https://github.com/gluster/glusterd2/issues/454


> >
> > Also want to propose that,  we include a release
> > of http://github.com/gluster/gluster-health-report with 4.1, and make
> > the project more usable.
>
> In the theme of including sub-projects that we want to highlight, what
> else should we tag a release for or highlight with 4.1?
>
> @Aravinda, how do you envision releasing this with 4.1? IOW, what
> interop tests and hence sanity can be ensured with 4.1 and how can we
> tag a release that is sane against 4.1?
>
> >
> > Also, we see that some of the patches from FB branch on namespace and
> > throttling are in, so we would like to call that feature out as
> > experimental by then.
>
> I would assume we track this against
> https://github.com/gluster/glusterfs/issues/408 would that be right?
>

Yes, that is right. sorry for missing out the github issues in the first
email.

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