On Wed, 16 Mar 2016 13:23:31 +1300
Mark Kirkwood wrote:
> So integrating swift-recon into regular monitoring/alerting
> (collectd/nagios or whatever) is one approach (mind you most folk
> already monitor disk usage data... and there is nothing overly special
> about ensuring you don't run of s
On 16/03/16 00:51, Peter Brouwer wrote:
Ah, good info. Followup question, assume worse case ( just to emphasis
the situation) , one copy ( replication = 1 ) , disk approaching its max
capacity.
How can you monitor this situation, i.e. to avoid the disk full scenario
and
if the disk is full, what
On 16/03/16 00:09, Peter Brouwer wrote:
See https://ask.openstack.org/en/question/6766/what-is-a-swift-partition/
Yep, misunderstood you - see comments email after that one!
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/open
On 15/03/2016 10:29, Mark Kirkwood wrote:
On 15/03/16 22:21, Peter Brouwer wrote:
PArtitions is used in the swift context, i.e. the partitions scheme the
ring-builder uses. I'm assuming a whole physical disk is used, i.e.
filesystem created on a disk using the whole physical disk.
So the ring
On 15/03/2016 09:51, Mark Kirkwood wrote:
On 15/03/16 22:21, Peter Brouwer wrote:
On 10/03/2016 05:14, Mark Kirkwood wrote:
Hmm, I'm confused by the phrase 'partitions that point to the same
disk':
PArtitions is used in the swift context, i.e. the partitions scheme the
ring-builder uses.
On 15/03/16 22:21, Peter Brouwer wrote:
PArtitions is used in the swift context, i.e. the partitions scheme the
ring-builder uses. I'm assuming a whole physical disk is used, i.e.
filesystem created on a disk using the whole physical disk.
So the ring structure provides a reference to a swift par
On 15/03/16 22:21, Peter Brouwer wrote:
On 10/03/2016 05:14, Mark Kirkwood wrote:
Hmm, I'm confused by the phrase 'partitions that point to the same disk':
PArtitions is used in the swift context, i.e. the partitions scheme the
ring-builder uses.
I'm sorry but that does not make sense. The
Hi Mark,
On 10/03/2016 05:14, Mark Kirkwood wrote:
On 10/03/16 00:03, Peter Brouwer wrote:
Indeed, I should have been a bit more clear with my question.
What is swifts behavior of a situation in which a disk where a swift
partition points to runs out of space? There can be a number of swift
On 10/03/16 00:03, Peter Brouwer wrote:
Indeed, I should have been a bit more clear with my question.
What is swifts behavior of a situation in which a disk where a swift
partition points to runs out of space? There can be a number of swift
partitions that point to the same disk, does each par
On 08/03/2016 02:26, Mark Kirkwood wrote:
On 06/03/16 21:15, Peter Brouwer wrote:
Interesting info.
Two followup questions,
Can the ring builder cope with a disk that is dynamic in size, like
an nfs share from a storage array in which an nfs share shares
capacity from a pool, i.e. If an othe
On 06/03/16 21:15, Peter Brouwer wrote:
Interesting info.
Two followup questions,
Can the ring builder cope with a disk that is dynamic in size, like an nfs
share from a storage array in which an nfs share shares capacity from a pool,
i.e. If an other share in that pool takes up space the nfs s
Regards, Peter
> On 5 Mar 2016, at 02:52, John Dickinson wrote:
>
>
>
>> On 3 Mar 2016, at 13:32, Mark Kirkwood wrote:
>>
>>> On 03/03/16 03:57, Peter Brouwer wrote:
>>> Hello
>>>
>>> I am trying to find some information on the relationship of the ring
>>> (builder) structure of swift and
On 3 Mar 2016, at 13:32, Mark Kirkwood wrote:
> On 03/03/16 03:57, Peter Brouwer wrote:
>> Hello
>>
>> I am trying to find some information on the relationship of the ring
>> (builder) structure of swift and the size of disks used, i.e. how is
>> capacity of a disk managed.
>> I've seen many doc
On 03/03/16 03:57, Peter Brouwer wrote:
> Hello
>
> I am trying to find some information on the relationship of the ring
> (builder) structure of swift and the size of disks used, i.e. how is
> capacity of a disk managed.
> I've seen many docs/blogs explaining the ring and partitions but I have
>
14 matches
Mail list logo