Re: [Gluster-devel] Setting up dev environment

[Milind Changire]

If you are a Gluster contributor then you'll need to have a GitHub Account
with your Public SSH Key uploaded at GitHub to use the ssh transport.

If you are not a Gluster contributor, then you might just want to use the
https transport instead of the ssh transport to clone the glusterfs repo
off git.gluster.org.


On Sat, Jan 20, 2018 at 7:47 AM, Ram Ankireddypalle 
wrote:

> Hi,
>
>   I am trying to set  a dev environment and send out the code that I
> worked on out for review.
>
>   I tried setting up a build environment using doc @
> http://docs.gluster.org/en/latest/Developer-guide/Development-Workflow/
>
>
>
>  I am seeing the following error.
>
>
>
>  git clone ssh://ram-ankireddypa...@git.gluster.org/glusterfs.git
> glusterfs
>
>  Cloning into 'glusterfs'...
>
>  ssh: connect to host git.gluster.org port 22: Connection timed out
>
>
>
> Please suggest what could be the issue here.
>
>
>
> Thanks and Regards,
>
> Ram
>
>
> ***Legal Disclaimer***
> "This communication may contain confidential and privileged material for
> the
> sole use of the intended recipient. Any unauthorized review, use or
> distribution
> by others is strictly prohibited. If you have received the message by
> mistake,
> please advise the sender by reply email and delete the message. Thank you."
> **
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



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

[Gluster-devel] Setting up dev environment

[Ram Ankireddypalle]

Hi,
  I am trying to set  a dev environment and send out the code that I worked 
on out for review.
  I tried setting up a build environment using doc @ 
http://docs.gluster.org/en/latest/Developer-guide/Development-Workflow/

 I am seeing the following error.

 git clone ssh://ram-ankireddypa...@git.gluster.org/glusterfs.git glusterfs
 Cloning into 'glusterfs'...
 ssh: connect to host git.gluster.org port 22: Connection timed out

Please suggest what could be the issue here.

Thanks and Regards,
Ram

***Legal Disclaimer***
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by mistake,
please advise the sender by reply email and delete the message. Thank you."
**
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

[Shyam Ranganathan]

On 01/18/2018 01:23 PM, Shyam Ranganathan wrote:
> On 01/02/2018 11:08 AM, Shyam Ranganathan wrote:
>> Hi,
>>
>> As release 3.13.1 is announced, here is are the needed details for 3.13.2
>>
>> Release date: 19th Jan, 2018 (20th is a Saturday)
> 
> Heads up, this is tomorrow.

So, the patches are merged and the release notes are done [1], but there
is a backlog in the centos6 regression queue, so I am not sure if I can
get this out of the system tonight (as I will not get the regression
score for the release notes patch).

I will check the regression status tomorrow morning and then tag the
release.

Shyam

[1] Release notes: https://review.gluster.org/#/c/19255/
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

[Shyam Ranganathan]

On 01/18/2018 07:56 PM, Ravishankar N wrote:
>>> 1. There is one patch https://review.gluster.org/#/c/19218/ which
>>> introduces full locks for afr writevs. We're introducing this as a
>>> GD_OP_VERSION_3_13_2 option. Please wait for it to be merged on 3.13
>>> branch today. Karthik, please back port the patch.
>> Do we need this behind an option, if existing behavior causes split
>> brains?
> Yes this is for split-brain prevention. Arbiter volumes already take
> full locks but not normal replica volumes. This is for normal replica
> volumes. See Pranith's comment in
> https://review.gluster.org/#/c/19218/1/xlators/mgmt/glusterd/src/glusterd-volume-set.c@1557

Ack, so the option is a NO_DOC and needs to be set when things need to
be reverted to the older behavior (and at that point we need to move the
cluster opversion as well).
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

[Shyam Ranganathan]

On 01/19/2018 03:18 AM, Pranith Kumar Karampuri wrote:
> > 2. I'm also backporting https://review.gluster.org/#/c/18571/
> . Please
> > consider merging it too today if it is ready.
> 
> 
> Let's take this one in 3.13.3, I think we need to test a few more cases
> that I missed
> at the time of review.

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

[Gluster-devel] Coverity covscan for 2018-01-19-9eefff09 (master branch)

[staticanalysis]

GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-01-19-9eefff09
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

[Pranith Kumar Karampuri]

On Fri, Jan 19, 2018 at 6:19 AM, Shyam Ranganathan 
wrote:

> On 01/18/2018 07:34 PM, Ravishankar N wrote:
> >
> >
> > On 01/18/2018 11:53 PM, Shyam Ranganathan wrote:
> >> On 01/02/2018 11:08 AM, Shyam Ranganathan wrote:
> >>> Hi,
> >>>
> >>> As release 3.13.1 is announced, here is are the needed details for
> >>> 3.13.2
> >>>
> >>> Release date: 19th Jan, 2018 (20th is a Saturday)
> >> Heads up, this is tomorrow.
> >>
> >>> Tracker bug for blockers:
> >>> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.13.2
> >> The one blocker bug has had its patch merged, so I am assuming there are
> >> no more that should block this release.
> >>
> >> As usual, shout out in case something needs attention.
> >
> > Hi Shyam,
> >
> > 1. There is one patch https://review.gluster.org/#/c/19218/ which
> > introduces full locks for afr writevs. We're introducing this as a
> > GD_OP_VERSION_3_13_2 option. Please wait for it to be merged on 3.13
> > branch today. Karthik, please back port the patch.
>
> Do we need this behind an option, if existing behavior causes split
> brains? Or is the option being added for workloads that do not have
> multiple clients or clients writing to non-overlapping regions (and thus
> need not suffer a penalty in performance maybe? But they should not
> anyway as a single client and AFR eager locks should ensure this is done
> only once for the lifetime of the file being accesses, right?)
>
> Basically I would like to keep options out it possible in backports, as
> that changes the gluster op-version and involves other upgrade steps to
> be sure users can use this option etc. Which means more reading and
> execution of upgrade steps for our users. Hence the concern!
>
> >
> > 2. I'm also backporting https://review.gluster.org/#/c/18571/. Please
> > consider merging it too today if it is ready.
>

Let's take this one in 3.13.3, I think we need to test a few more cases
that I missed
at the time of review.


>
> This should be fine.
>
> >
> > We will attach the relevant BZs to the tracker bug.
> >
> > Thanks
> > Ravi
> >>
> >>> Shyam
> >>> ___
> >>> 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
> >
>



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