https://build.gluster.org/job/rackspace-regression-2GB-triggered/14782/consoleFull
says
Going to copy log tarball for processing on http://elk.cloud.gluster.org/
scp:
/srv/jenkins-logs/upload/jenkins-rackspace-regression-2GB-triggered-14782.tgz:
No space left on device
Build step 'Execute
On Thu, Oct 08, 2015 at 03:37:07PM +0530, Milind Changire wrote:
> https://build.gluster.org/job/rackspace-regression-2GB-triggered/14782/consoleFull
>
> says
>
> Going to copy log tarball for processing on http://elk.cloud.gluster.org/
> scp:
>
Hi,
On checking yesterday's gluster meeting AIs and (later) reading the
minutes, for DHT2 here is what I gather and propose to do for $SUBJECT.
Feel free to add/negate any plans.
(This can also be discussed at [2])
---
1)
First of all my apologies for not going through the meeting blog before
sending my thoughts on how we plan to maintain GlusterD 2.0 [1].
This approach seems fine to me as long as we don't touch any existing
xlators. How do we handle cases where other xlators get impacted by
certain changes. Are
