On Tue, May 13, 2014 at 4:20 PM, Justin Clift jus...@gluster.org wrote:
On 13/05/2014, at 11:43 AM, Vijay Bellur wrote:
Hi All,
Me and Kaushal have effected the following changes on regression.sh in
build.gluster.org:
1. If a regression run results in a core and all tests pass, that
Avati that's awesome! I didn't know that the meta xlator could do that
already.
On Sat, May 17, 2014 at 9:30 AM, Anand Avati av...@gluster.org wrote:
KP, Vipul,
It will be awesome to get io-stats like instrumentation on the client
side. Here are some further thoughts on how to implement
It should be possible. I'll check and do the change.
~kaushal
On Thu, May 22, 2014 at 8:14 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
- Original Message -
From: Pranith Kumar Karampuri pkara...@redhat.com
To: Justin Clift jus...@gluster.org
Cc: Gluster Devel
, Kaushal M kshlms...@gmail.com wrote:
It should be possible. I'll check and do the change.
~kaushal
On Thu, May 22, 2014 at 8:14 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
- Original Message -
From: Pranith Kumar Karampuri pkara...@redhat.com
To: Justin Clift jus
the 'rebalance
status' command for a reason. But I currently cannot recall the reason, and
if cannot come with it soon, I wouldn't mind changing the test to avoid
rebalance status.
~kaushal
On Thu, May 22, 2014 at 5:22 PM, Justin Clift jus...@gluster.org wrote:
On 22/05/2014, at 12:32 PM, Kaushal M
I've changed the smoke.sh script to archive the logs on failures. The
archives will be saved into /d/logs/smoke and will be available for
download from [1].
I've also moved to location of the regression log archives from
/d/logs to /d/logs/regression. These will now be available for
download at
Turns out this change isn't working as I had thought it would. Vijay
helped me identify the problem and I've done another change.
Hopefully, it works now.
~kaushal
On Fri, May 23, 2014 at 2:35 PM, Kaushal M kshlms...@gmail.com wrote:
I've changed the smoke.sh script to archive the logs
On Fri, May 23, 2014 at 6:02 PM, Justin Clift jus...@gluster.org wrote:
Hi Pranith,
You don't have an account on build.gluster.org yet do you?
It's where the current (not my stuff) regression tests are run.
This is the script presently used to build the regression
tests:
$ more
This is surprising. There hasn't been any change that could cause this
kind of behaviour AFAICT.
Normally, the peer from which the probes were performed would be shown
using IPs on the other nodes. But if a reverse probe with hostnames
should fix this too.
Could you share more information on
Hi everyone,
As everyone hopefully knows by now, improving the peer identification
mechanism within Glusterd is one of the features being targeted for
glusterfs-3.6. [0]
I had proposed this a while back, but had not been able to do much
work related to this till now. Varun (CCd) and I have been
This sounds perfect.
On Thu, Jul 10, 2014 at 2:15 PM, Niels de Vos nde...@redhat.com wrote:
On Wed, Jul 09, 2014 at 09:33:01PM +0100, Justin Clift wrote:
That v3.5qa2 tag name on master is annoying, due to the RPM
naming it causes when building on master.
Did we figure out a solution?
My patch for improving peer identification [1] needs to get in. It's
functionally complete and can be merged right now. But KP has some
minor comments. I'll update it tonight, and it should be good for
merge by the morning,
~kaushal
[1] https://review.gluster.org/8238
On Mon, Jul 14, 2014 at
What do you mean by 'option-framework'? Is it the xlator options table
that we have in each xlator? Or the glusterd volume set framework
(which requires the xlator options tables to function anyway)?
On Tue, Jul 15, 2014 at 4:39 PM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
hi,
I'll take up documenting the options framework. I'd like take up graph
and dict, if Jeff doesn't mind.
Also, I think we should be aiming to document the complete API
provided by these components instead of just the data structure. That
would be more helpful to everyone IMO.
~kaushal
On Wed, Jul
I don't understand your confusion, but maybe these docs need to be reworded.
What both of these want to say is that for a patch to be merged into
glusterfs, it needs to be associated with a bug-id. This association
is done by adding a 'BUG: id' line in the commit message. If you
haven't manually
that it's lifecycle can be tracked correctly. So
bug just means bugzilla entry. You have bug bugs, enhancement
bugs, feature request bugs and so on.
tl;dr: bug == bugzilla entry.
On Thu, Jul 17, 2014 at 8:58 PM, Anders Blomdell
anders.blomd...@control.lth.se wrote:
On 2014-07-17 15:44, Kaushal
On Fri, Jul 18, 2014 at 11:11 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 07/17/2014 07:25 PM, Kaushal M wrote:
I came across mediawiki's developer documentation and guides when
browsing. These docs felt really good to me, and easy to approach.
I feel that we should take
On Fri, Jul 18, 2014 at 11:39 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 07/18/2014 11:22 AM, Kaushal M wrote:
On Fri, Jul 18, 2014 at 11:11 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 07/17/2014 07:25 PM, Kaushal M wrote:
I came across mediawiki's developer
The clear you have at top (the one for clear-stats) is for 'top
clear'. Below there is a section with GF_CLI_INFO_CLEAR, which handles
'profile info clear'.
~kaushal
On Tue, Jul 22, 2014 at 11:50 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 07/22/2014 11:43 AM, Kaushal M wrote
Joe,
BTW, Vipul (in CC) is also looking to quantify the impact of enabling
io-stats counters permanently.
It'd be great if you both could help each other out.
~kaushal
On Tue, Jul 22, 2014 at 12:54 PM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 07/22/2014 12:07 PM, Kaushal M wrote
Hey everyone,
While I was writing the documentation for the options framework, I
thought up of a way to better organize the code documentation we are
creating now. I've posted a patch for review that implements this
organization. [1]
Copying the description from the patch I've posted for review,
Hi all,
Currently we name tests associated with a bug with just the bug-id as
'bug-XXX.t'. This naming doesn't provide any context directly, and
someone looking at just the name wouldn't know what it does.
I suggest that we use slightly more descriptive names to the tests.
Lets name the
I'll do that, if someone could point me to it. Is it on the community
wiki or in doc/ directory in the source?
~kaushal
On Wed, Aug 27, 2014 at 1:12 PM, Niels de Vos nde...@redhat.com wrote:
On Wed, Aug 27, 2014 at 12:21:56PM +0530, Kaushal M wrote:
Hi all,
Currently we name tests associated
All,
Since I've had no objections to this idea, I'm going to update the
documentation with this.
Jeff, Could you explain what you meant by 'arranged into
subdirectories'? I didn't understand what you meant by that.
~kaushal
On Wed, Aug 27, 2014 at 5:07 PM, Jeff Darcy jda...@redhat.com wrote:
GlusterD performs the following functions as the management daemon for
GlusterFS:
- Peer membership management
- Maintains consistency of configuration data across nodes (distributed
configuration store)
- Distributed command execution (orchestration)
- Service management (manage GlusterFS
I was away on a small vacation last week, so I haven't been able to
reply to this thread till now.
There has been quite some discussion while I was away. This kind of
discussion was exactly what we wanted.
I've read through the thread, and I'd like to summarize what I feel is
the general feeling
I keep getting this warning(or maybe not) for checkpatch.pl itself
when I run rfc.sh.
`Useless use of greediness modifier '+' in regex; marked by -- HERE
in m/(^\+.*) {8,8}+ -- HERE \t/ at ./extras/checkpatch.pl line 2131.`
Anyone else seeing this?
~kaushal
On Mon, Sep 22, 2014 at 7:00 PM,
I'm using Perl 5.20.1. I was wondering how no one caught a mistake in
the checker.
~kaushal
On Mon, Sep 22, 2014 at 11:22 PM, Harshavardhana
har...@harshavardhana.net wrote:
On Mon, Sep 22, 2014 at 6:58 AM, Kaushal M kshlms...@gmail.com wrote:
I keep getting this warning(or maybe
IIRC, the regression test suite was changed a little recently, which
leads to tests failing to run when called directly using prove.
Can you run the test from within the GlusterFS src directory using
'./run-tests.sh test'? The run-tests.sh script now does some
environmental setup before running
'replace-brick commit force' is still going to be available. It's just
that data-migration for replace-brick is going to be removed. So
'replace-brick (start|stop)' are going to be deprecated.
To replace a brick in a replica set, you'll need to do a
'replace-brick commit force'. Self-healing will
Hey Jeff,
I'm trying to understand how the SSL support in socket-transport
works. I'm having a little trouble understanding it though.
Do you have any document describing how it works? Even user
documentation on how to use the feature will help.
~kaushal
Cool. Thanks Vijay.
On Thu, Nov 13, 2014 at 3:17 PM, Vijay Bellur vbel...@redhat.com wrote:
On 11/13/2014 03:11 PM, Kaushal M wrote:
Hey Jeff,
I'm trying to understand how the SSL support in socket-transport
works. I'm having a little trouble understanding it though.
Do you have any
In that case, I should send a note as the op-version has been bumped
for the master branch.
Please take note,
The operating-version for the master branch has been bumped to
'30700', which is aligned with the next release of GlusterFS, 3.7.
~kaushal
On Thu, Dec 18, 2014 at 12:49 PM, Lalatendu
As a part of our ongoing effort to improve the reliability and robustness
of GlusterD we are also targeting concurrency related issues, and this
proposal is with regard to the mentioned issue.
The Big-lock
GlusterD was originally designed as a single threaded application which
could
Hi list,
Applying as an organization for GSOC requires us to prepare a publicly
accessible list of project ideas.
Anyone within the community who has an idea for projects, and are willing
to mentor students, please add the idea at [1]. (Add them even if you
can't/won't mentor as well). There is
Thanks Niels. I've added links on each page to the other for now. We can
consolidate this when we find time.
On Wed, Feb 4, 2015 at 2:06 PM, Niels de Vos nde...@redhat.com wrote:
On Wed, Feb 04, 2015 at 01:04:55PM +0530, Kaushal M wrote:
Hi list,
Applying as an organization for GSOC
:10:36AM +0530, Kaushal M wrote:
Thanks for this information Kaleb.
I'll check the changes I've done till now with the older versions of the
libraries. I think I'm going to need at least the 0.8.* release of
liburcu,
as some new apis were introduced in it, which I'm using. I'll post
The local implementation is working well for liburcu-0.7. I'll be
continuing with this approach as it is going to cover most of the systems
we target. We can decide how we'll handle Debian Wheezy and Ubuntu Precise
later.
~kaushal
On Mon, Feb 2, 2015 at 3:00 PM, Kaushal M kshlms...@gmail.com
as there is at least
one shared lock in the hot path, the hard work gone into all the previous
shared lock fixes remain latent. However the end result is well worth all
the efforts.
Thanks
On Thu, Jan 29, 2015, 03:35 Kaushal M kshlms...@gmail.com wrote:
Hi all,
I had started a thread
Vijay is correct. We only increment the operating version when we add new
features that wouldn't be available in a previous version. Ideally in a Z
release (when following a X.Y.Z versioning scheme) we wouldn't be releasing
any new features, so the operation version wouldn't change between two Z
You are right. Failing just a GETSPEC would still allow client to connect
to the volume directly when by using a volfile. We can prevent this by also
setting 'auth.reject *' on the volume. The username/password based
authentication has higher priority than auth.reject or auth.allow, so all
the
+1 for Thursday (anytime).
-1 for Friday.
On Wed, Feb 11, 2015 at 7:22 PM, Niels de Vos nde...@redhat.com wrote:
On Mon, Feb 09, 2015 at 05:34:04PM -0500, Jeff Darcy wrote:
The inaugural GlusterFS 4.0 meeting on Friday was a great success.
Thanks to all who attended. Minutes are here:
--
From: Joe Julian j...@julianfamily.org
To: Kaushal M kshlms...@gmail.com; David F. Robinson
david.robin...@corvidtec.com
Cc: Gluster Users gluster-us...@gluster.org; Gluster Devel
gluster-devel@gluster.org
Sent: 1/27/2015 12:48:49 AM
Subject: Re: [Gluster-devel] [Gluster-users] v3.6.2
I think you get a connection refused if there are no servers running as
well.
On Tue, Jan 27, 2015 at 11:18 AM, Joe Julian j...@julianfamily.org wrote:
If that was true, wouldn't it not Connection refused because the kernel
nfs is listening?
On January 26, 2015 9:43:34 PM PST, Kaushal M
Hi all,
As it happens every year, the processes for GSOC begin in February,
starting with the organization registration, which runs this year from
February 9th to 20th. Rest of the timeline can be viewed at [1].
Last year we participated in GSOC under the Fedora organization, we hadn't
registered
Hi all,
I had started a thread previously on the efforts we are undertaking to
improve thread synchronization in GlusterD [1]. I had mentioned that we
will be using RCU for synchronization and the userspace RCU library
(liburcu) [2] for implementation.
I am now in a almost in a position to submit
tl;dr: Add a 'LEXLIB=' flag to your configure command, ie. `./configure
LEXLIB=`
This is problem with flex-2.5.38 and above. From this version, flex
generates a shared library in its default build (libfl.so). This shared
object doesn't actually contain any exported symbols (AFAIK).
to vote against doing this. I recommend contacting
the liburcu maintainers in Fedora/EPEL and see if you can't convince them
to update to the newest version.
Regards,
--
Kaleb
/30/2015 12:09 PM, Deepak Shetty wrote:
On Thu, Jan 29, 2015 at 5:05 PM, Kaushal M kshlms...@gmail.com
The Unify xlator is the predecessor of the DHT xlator and it has long been
deprecated in favour of DHT. I think it was removed from the source in
release 3.4.
If you still want to look at it for reference, you can checkout the
release-3.3 branch or view it online at [1].
~kaushal
[1]:
IMHO, doing hardening and security should be left the individual
distributions and the package maintainers. Generally, each distribution has
it's own policies with regards to hardening and security. We as an upstream
project cannot decide on what a distribution should do. But we should be
ready to
On Tue, Mar 31, 2015 at 12:49 PM, Niels de Vos nde...@redhat.com wrote:
On Tue, Mar 31, 2015 at 12:14:29PM +0530, Vijay Bellur wrote:
On 03/28/2015 02:08 PM, Emmanuel Dreyfus wrote:
Pranith Kumar Karampuri pkara...@redhat.com wrote:
Emmanuel,
What can we do to make it vote
Openstack uses Zuul [1], which manages this kinds of issues. Maybe we
can explore it.
This was brought up sometime before by Prashant Pai (I don't remember
if it was on IRC or here).
~kaushal
[1] http://ci.openstack.org/zuul/
___
Gluster-devel mailing
Hi everyone.
I'm disappointed to announce that our application to be a mentoring
organization for GSoC-2015 has been rejected. Google has accepted 137
organizations [1] this year (down from 190 last year) and couldn't find
place to accommodate us.
The main reason behind the rejection was the
I forgot to mention this earlier. Anyone who has any patch on review that
involves GlusterD, will need to rebase their patch. Sorry for the
inconvenience.
~kaushal
On Wed, Mar 4, 2015 at 1:20 PM, Kaushal M kshlms...@gmail.com wrote:
Review http://review.gluster.org/9624 just got merged
Hi list,
The review http://review.gluster.org/9605 got merged yesterday. This patch
introduces a build requirement on liburcu, which is needed for the changes
planned for GlusterD. liburcu = 0.7 is required to build GlusterD.
I'm listing the package names for some common distros, just to help
I should have caught this during the review. I've been on the lookout
for this kind of breakage in all GlusterD changes, but this slipped
through somehow. Apologies.
I don't think we need to revert KP's change. I'll test Vijay's fix and
do any further changes required to stop the failures, ASAP.
On Thu, Apr 2, 2015 at 10:14 AM, Kaushal M kshlms...@gmail.com wrote:
I should have caught this during the review. I've been on the lookout
for this kind of breakage in all GlusterD changes, but this slipped
through somehow. Apologies.
I don't think we need to revert KP's change. I'll test
Also, everyone please rebase your patches so that they get the fix and
regression can be triggered on them again.
~kaushal
On Thu, Apr 2, 2015 at 3:42 PM, Vijay Bellur vbel...@redhat.com wrote:
On 04/02/2015 01:28 PM, Niels de Vos wrote:
Hi,
it seems that there is a major breakage in the
Anyone know how to create a direct link to a CID? I can't seem to figure it out.
~kaushal
On Fri, Apr 24, 2015 at 11:19 AM, Kaushal M kshlms...@gmail.com wrote:
I'll look at those over the weekend.
Cheers.
On Thu, Apr 23, 2015 at 11:11 PM, Niels de Vos nde...@redhat.com wrote:
On Thu, Apr
I'll look at those over the weekend.
Cheers.
On Thu, Apr 23, 2015 at 11:11 PM, Niels de Vos nde...@redhat.com wrote:
On Thu, Apr 23, 2015 at 07:10:23PM +0530, Kaushal M wrote:
Gerrit has a configuration option to enable automatic creating links
from regex matches in commit-messages, comments
Posted changes for review,
https://review.gluster.org/10425
https://review.gluster.org/10426
~kaushal
On Tue, Apr 28, 2015 at 6:34 PM, Kaushal M kshlms...@gmail.com wrote:
After a long discussion (not really), we've concluded that a 64-bit
uint is really overkill for how we are using
?)
+ Justin
On 28 Apr 2015, at 12:45, Kaushal M kshlms...@gmail.com wrote:
Found the problem. The NetBSD slaves are running a 32-bit kernel and
userspace.
```
nbslave7a# uname -p
i386
```
Because of this CAA_BITS_PER_LONG is set to 32 and the case for size 8
isn't compiled
After a long discussion (not really), we've concluded that a 64-bit
uint is really overkill for how we are using the generation number,
and I'll change it to a 32-bit uint. I'll send a change to do this
right away.
The generation number we use is not permanent, it is valid only within
a GlusterD
I seem to have found the issue.
The uatomic_add_return function is defined in urcu/uatomic.h as
```
/* uatomic_add_return */
static inline __attribute__((always_inline))
unsigned long __uatomic_add_return(void *addr, unsigned long val,
int len)
{
switch
.
~Atin
Niels
On 04/29/2015 11:56 AM, Kaushal M wrote:
If we were to run without `-N`, in daemon mode, yum wouldn't know when
glusterd actually finished the upgrade process. Yum would consider the
parent process returning to be the end.
On Wed, Apr 29, 2015 at 9:17 PM, Raghavendra Talur
Linking to CIDs and Change-Ids should also be enabled now.
~kaushal
On Sat, Apr 25, 2015 at 3:41 PM, Kaushal M kshlms...@gmail.com wrote:
Anyone know how to create a direct link to a CID? I can't seem to figure it
out.
~kaushal
On Fri, Apr 24, 2015 at 11:19 AM, Kaushal M kshlms
If we were to run without `-N`, in daemon mode, yum wouldn't know when
glusterd actually finished the upgrade process. Yum would consider the
parent process returning to be the end.
On Wed, Apr 29, 2015 at 9:17 PM, Raghavendra Talur rta...@redhat.com wrote:
Hi,
As part of the yum upgrade
I don't think the post is correct style for a wiki (I may be
influenced by Wikipedias guidelines) as is, but can be added after
some changes.
On Fri, May 8, 2015 at 2:57 AM, Justin Clift jus...@gluster.org wrote:
On 7 May 2015, at 16:53, Kaushal M kshlms...@gmail.com wrote:
Forgot the link. :D
Forgot the link. :D
[1]: https://kshlm.in/network-encryption-in-glusterfs/
On Thu, May 7, 2015 at 8:51 PM, Kaushal M kshlms...@gmail.com wrote:
I've written a how-to for setting up network encryption on GlusterFS at [1].
This was something that was requested as setting up network encryption
Smoke tests aren't being reported back. This is a known issue.
Successful regression runs don't get reported back sometimes due to
the network issues we have. If you have such regression jobs, inform
any person with root access on build.gluster.org. They can manually
run the ssh command which
Modularising GlusterD is something we plan to do. As of now, it's
just that a plan. We don't yet have a design to achieve it yet.
What Atin mentioned and what you've mentioned seem to be the same at a
high level. The core of GlusterD will be a co-ordinating engine, which
defines an interface for
I've written a how-to for setting up network encryption on GlusterFS at [1].
This was something that was requested as setting up network encryption
is not really easy.
I've tried to cover all possible cases.
Please read through, and let me know of any changes,improvements needed.
Thanks,
Kaushal
Hey Kotresh,
This is a known issue. We are evaluating some possible solutions. The
failure is because of changes introduced by
https://review.gluster.org/10147 .
The GlusterD rpcsvc uses the synctask framework to provide multi
threading. GlusterD uses synclock_t provided by the synctask
at 07:52:49PM +0530, Kaushal M wrote:
Because this GlusterD didn't die
Um, that is something I have been seeing on netbsd-6: killing glusterd does
not cause it to exit, you have to kill -9. On netbsd-7 it is fine.
The question is therefore: why does it catch SIGTERM?
--
Emmanuel Dreyfus
m
I finally started testing this today after getting my NetBSD VMs setup
correctly.
I ran the test on a NetBSD-6.1.5 VM with NetBSD-7 kernel, and on a NetBSD-7 vm.
On the NetBSD-6 VM the test failed always, where as it didn't fail on
the NetBSD-7 VM.
The tests 11 and 14 failed always because of a
I'm looking at this currently. But I'm having a slightly hard time
getting Gluster running on Netbsd. I have a netbsd-6.1.5 installation,
but cannot get extended attributes to work and volume creation keeps
failing. This is preventing me from checking the issue.
Manu, if you help with this? In
On Wed, Apr 15, 2015 at 1:20 PM, Emmanuel Dreyfus m...@netbsd.org wrote:
On Wed, Apr 15, 2015 at 12:58:32PM +0530, Kaushal M wrote:
I'm looking at this currently. But I'm having a slightly hard time
getting Gluster running on Netbsd. I have a netbsd-6.1.5 installation,
but cannot get extended
On Wed, Apr 15, 2015 at 3:16 PM, Emmanuel Dreyfus m...@netbsd.org wrote:
On Wed, Apr 15, 2015 at 02:39:05PM +0530, Kaushal M wrote:
Doesn't work on 6.1.5. I'm still getting 'Not supported'. Do I need
NetBSD-7 for this to work?
I think I see the problem now: in netbsd-6 branch the relevant
The glusterfs package contains the CTR xlator, which requires libgfdb.
We have 2 choices now. We could either,
1. Move the CTR xlator into the glusterfs-server package. This makes
sense because CTR is a server side only xlator, and has no reason to
be in the glusterfs package.
or,
2. Move libgfdb
, Kaushal M kshlms...@gmail.com wrote:
The six netbsd slaves were hung on jobs for over 15h each. I've
disabled the netbsd-regression project so that I can kill the hung vms
and restart them. I'll re-enable the project once the vms have been
restarted.
~kaushal
On Thu, Jun 18, 2015 at 1:50 AM, Niels de Vos nde...@redhat.com wrote:
On Mon, Jun 15, 2015 at 04:19:14PM +0530, Kaushal M wrote:
Hi all,
...
I propose that we move back to the old model of starting regression
runs only once the maintainers are ready to merge. But instead of the
maintainers
Just triggered a run [1]. It should complete in about an hour. I'll
merge once complete.
[1]
http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/7191/console
On Mon, Jun 22, 2015 at 9:51 AM, Ravishankar N ravishan...@redhat.com wrote:
Hi Kaushal,
Could you please merge the
One other design characteristic I can think of is to have GlusterD-2.0
be able to make best use of Nodes based on the Node topology, not sure
if this is covered by any other feature below ?
IOW, admin should be able to provide a hierarchy of how nodes are
provisioned
(rack, site, zone,
nbslave7{2,4,5,h} had hung mounts, which lead to hung regression jobs.
I've rebooted these vms and retriggered the hung tests.
~kaushal
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
The hang we observe is not something specific to Gluster. I've
observed this kind of hangs when a filesystem which is in use goes
offline.
For example I've accidently shutdown machines which were being used
for mounting nfs, which lead to the client systems hanging completely
and required a hard
Hi all,
The recent rush of reviews being sent due to the release of 3.7 was a
cause of frustration for many of us because of the regression tests
(gerrit troubles themselves are another thing).
W.R.T regression 3 main sources of frustration were,
1. Spurious test failures
2. Long wait times
3.
I'll try temprorarily block merges, so that the repo cannot be changed
even more.
~kaushal
On Fri, Jun 12, 2015 at 11:11 AM, Kaushal M kshlms...@gmail.com wrote:
The review.gluster.org git repository for glusterfs seems to be corrupted.
The gerrit log is complaining about some missing git
Humble has blocked submit/merge access on the glusterfs project for
now. We'll re-enable it once we've fixed the problems.
On Fri, Jun 12, 2015 at 11:23 AM, Kaushal M kshlms...@gmail.com wrote:
I'll try temprorarily block merges, so that the repo cannot be changed
even more.
~kaushal
On Fri
Forwarding Humble's mail about opening merges, as it appears people
haven't recieved it.
On Fri, Jun 12, 2015 at 11:34 AM, Humble Chirammal hchir...@redhat.com wrote:
- Kaushal M kshlms...@gmail.com wrote:
| Humble has blocked submit/merge access on the glusterfs project for
| now
The review.gluster.org git repository for glusterfs seems to be corrupted.
The gerrit log is complaining about some missing git objects, which is
not allow git pulls to happen.
I'll be investigating the problem and keep updating here.
~kaushal
___
On Thu, Jun 18, 2015 at 1:17 AM, Niels de Vos nde...@redhat.com wrote:
On Wed, Jun 17, 2015 at 04:26:13PM +0530, Raghavendra Talur wrote:
Hi,
MSV Bhat and I had presented in Gluster Design Summit some ideas about
improving our testing infrastructure.
Here is the link to the slides:
On Thu, Jun 18, 2015 at 10:26 AM, Kotresh Hiremath Ravishankar
khire...@redhat.com wrote:
Hi All,
Another thing to be considered is every patch automatically triggers
regressions.
It is very unlikely that, the very Patch Set 1 submitted would be a merge
candidate.
There would be some or
to complete in the future,
nightly full regression runs would be nice to have.
--
regards
Aravinda
On 06/15/2015 06:49 AM, Kaushal M wrote:
Hi all,
The recent rush of reviews being sent due to the release of 3.7 was a
cause of frustration for many of us because of the regression tests
(gerrit
cloud.gluster.org is served by Rackspace Cloud DNS. AFAICT, there is
no readily available option to do zone transfers from it. We might
have to contact the Rackspace support to find out if they can do it as
a special request.
On Wed, Jun 17, 2015 at 11:50 AM, Emmanuel Dreyfus m...@netbsd.org
Just moving Gerrit and Jenkins out of iWeb should help a lot.
On Wed, Jun 17, 2015 at 4:28 PM, Justin Clift jus...@gluster.org wrote:
On 17 Jun 2015, at 10:53, Michael Scherer msche...@redhat.com wrote:
Le mercredi 17 juin 2015 à 11:48 +0200, Michael Scherer a écrit :
Le mercredi 17 juin 2015
nbslave7{d..f} were the entries created by Vijay last week, which were
resolving to nbslave71; there were no actual vms on rackspace. I had
disabled nbslave71 at that point in time to reboot it, but I think I
forgot to re-enable it.
~kaushal
On Wed, Jun 17, 2015 at 7:21 PM, Emmanuel Dreyfus
Would restarting jenkins once help? It might help it pick up the newly
added entries to the hosts file.
On Wed, Jun 17, 2015 at 8:30 PM, Emmanuel Dreyfus m...@netbsd.org wrote:
On Wed, Jun 17, 2015 at 02:57:28PM +, Emmanuel Dreyfus wrote:
I re-enabled it and it went online, but it does not
:
- Kaushal M kshlms...@gmail.com wrote:
| Humble has blocked submit/merge access on the glusterfs project for
| now. We'll re-enable it once we've fixed the problems.
I have reverted the access permission and looks like gerrit is back now.
Thanks Vijay++ and Kaushal++.
So, for the sake
A change would get a +2 from a maintainer only once the maintainer
believes that the patch is ready to be accepted. To be at this level
of confidence, the change would have been reviewed thoroughly, and
such a generally wouldn't fail regression (excluding spurious
failures). If there was something
Hey Luis,
You just announced this right when we were about to make public our
plans for Manila integration w.r.t GlusterD-2.0.
We are about to kickstart GlusterD-2.0, and the first piece we wanted
to implement was a method to create volumes intelligently. This is
pretty much what heketi is
1 - 100 of 430 matches
Mail list logo
