Open Stack

Hello all,

I'd also be very interested in anyone's knowledge or experience of this
topic, extending also to cinder-volume operation concurrency.

We see similar behaviour in that many cinder-volume conversion operations
started simultaneously can impact the cloud overall.

Thanks,
Paul


On Sat, 8 Jun 2019, 08:15 Cory Hawkless, <Cory at hawkless.id.au> wrote:

> I’m using Rocky and Cinders built in Ceph backup driver which is working
> ok but I’d like to limit each instance of the backup agent to X number of
> concurrent backups.
>
> For example, if I(Or a tenant) trigger a backup to run on 20 volumes, the
> cinder-0backuip agent promptly starts the process of backup up all 20
> volumes simultaneously and while this works ok it has the downside of over
> saturating links, causing high IO on the disks etc.
>
>
>
> Ideally I’d like to have each cinder-backup agent limited to running
> X(Perhaps 5) backups jobs at any one time and the remaining jobs will be
> ‘queued’ until an agent has less than X jobs remaining.
>
>
>
> Is this possible at all?
>
> Based on my understanding the Cinder scheduler services handles the
> allocation and distribution of the backup tasks, is that correct?
>
>
>
> Thanks in advance
>
> Cory
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190608/9c90487a/attachment.html>