Le jeudi 12 mai 2016 à 14:43 -0400, Jeff Darcy a écrit :
> > I also remember that Jeff Darcy posted on "we need to change a value in
> > lvm.conf (LVM allocation settings, mail from 6th of april), so anyone
> > has more information about that ? (or if someone can ping Jeff for me)
>
> Yes, I
On Fri, May 13, 2016 at 3:11 AM, Aravinda wrote:
> +1 from Geo-rep.
>
> Will explicit ack to be done in the mailing list?
>
Yes, sending out a note on gluster-devel would be appropriate. A
description of tests done etc. in the note would help us track and
improve quality
> > > There were concerns raised around this for the below reasons:
> > > 1. word-size and endianness
> > > 2. security issues
> > > 3. Backward compatibility issues i.e. old/new client and server
> > > combination.
> >
> > Can you please elaborate on the above 3 points? A bit more verbose
> >
Hi all,
This week's status:
-Fixed some review comments on the patch
-Working on re-factoring some parts of the feature
Plan for next week:
-Completing the re-factoring of the feature
Current work:
Patch: http://review.gluster.org/#/c/13429/
http://review.gluster.org/#/c/14222/
On Fri, May 13, 2016 at 06:44:58AM -0400, Raghavendra Gowdappa wrote:
>
>
> - Original Message -
> > From: "Poornima Gurusiddaiah"
> > To: "Gluster Devel" , "Niels de Vos"
> > , "Jeff Darcy"
> > ,
> In the recent past, have seen multiple instances where we needed to
> send some data along with the fop on wire. And we have been using the
> xdata for the same. Eg:
>
> 1. Add lease-id, transaction id to every fop.
The original purpose of xdata was to convey extra information without
having
- Original Message -
> From: "Poornima Gurusiddaiah"
> To: "Gluster Devel" , "Niels de Vos"
> , "Jeff Darcy"
> , "Raghavendra Talur" , "Rajesh Joseph"
> ,
Hi,
In the recent past, have seen multiple instances where we needed to send some
data along with the fop on wire. And we have been using the xdata for the same.
Eg:
1. Add lease-id, transaction id to every fop.
2. Send the xattrs to invalidate in xdata.
3. Send the share flags during open.
Hello all,
please review [1]
the above patch changes client insecure port ceiling from 65535 to 49151:
current port allocation to various processes (clumsy):
1023 - 1-> client ports range if bind secure is turned on
49151 - 1024 -> fall back to this, if in above case ports exhaust
+1 for "Proposed alternative 3 - One LTS every year and non LTS stable release
once in every 4 months" as it is more appropriate.
Regards,
Poornima
- Original Message -
> From: "Aravinda"
> To: "Kaushal M" , "Gluster Devel"
>
Hi,
Based on the discussion in last community meeting and previous discussions,
1. Too frequent releases are difficult to manage.(without dedicated
release manager)
2. Users wants to see features early for testing or POC.
3. Backporting patches to more than two release branches is pain
+1 from Geo-rep.
Will explicit ack to be done in the mailing list?
regards
Aravinda
On 05/10/2016 12:01 AM, Vijay Bellur wrote:
Hi All,
We are blocked on 3.7.12 owing to this proposal. Appreciate any
feedback on this!
Thanks,
Vijay
On Thu, Apr 28, 2016 at 11:58 PM, Vijay Bellur
On Fri, May 13, 2016 at 11:15 AM, Jiffin Tony Thottan
wrote:
> Hi all,
>
> There are around 20 features targeted for 3.8 release. All the gluster
> related
> code changes got merged by first week of May(rc-1 is not yet done). There
> is
> a long way to go with approximately
Refreshed the patch to fix glupy, systemd and mount.glusterfs files.
http://review.gluster.org/14315
regards
Aravinda
On 05/13/2016 10:25 AM, Kaushal M wrote:
On Fri, May 13, 2016 at 9:59 AM, Aravinda wrote:
Sent patch to fix glupy installation issue.
On 05/13/2016 11:39 AM, Milind Changire wrote:
> Job: https://build.gluster.org/job/smoke/27731/console
> Error: bin/mkdir: cannot create directory
> `/usr/lib/python2.6/site-packages/gluster': Permission denied
>
> Please advise.
> Do I just resubmit the job?
> Would restarting the VM be of
Job: https://build.gluster.org/job/smoke/27731/console
Error: bin/mkdir: cannot create directory
`/usr/lib/python2.6/site-packages/gluster': Permission denied
Please advise.
Do I just resubmit the job?
Would restarting the VM be of help here?
This is the second time the smoke test has failed
16 matches
Mail list logo