Don't lock all nodes when performing a gnt-backup task

[GoogleCodeExporter]

Hello.

I just ran into a somewhat annoying issue.

I'm writing a piece of script to backup ganeti instances to another server 
(which is a ganeti-node without the vm capabilities, only for backup).

I wished I could run a gnt-backup on every node simultaneously, and apparently, 
it's not the case.

I don't know if it's a lot of work or a lot of changes to be made. 

I'm using ganeti 2.11.2 on Debian 7.0 

Steps to reproduce the problem :
- run several "gnt-backup export" commands from the master node (each command 
backing up instance on different nodes)
- run "gnt-job list" and see some BACKUP_EXPORT jobs waiting even though there 
are no backup job running on the node.

I hope I was clear in writing this bug report.

Don't hesitate to ask if you need details.

Thanks.

Original issue reported on code.google.com by cyril.la...@gmail.com on 16 Jul 2014 at 1:04

[GoogleCodeExporter]

This has been a FIXME in the code for a while. Prioritizing it to 2.13 to get 
it fixed anytime soon.

Original comment by hel...@google.com on 16 Jul 2014 at 1:37

• Changed state: Accepted
• Added labels: Milestone-Release2.13, Priority-High, Type-Defect

[GoogleCodeExporter]

Ganeti currently checks all nodes to find possibly existing previous backups of 
the instance, which it wants to remove once a new backup has successfully been 
created. To keep the functionality the same, we'd have to play around with the 
locks, so fixing this is rather tough.

Original comment by r...@google.com on 10 Jun 2015 at 1:46

• Added labels: Component-storage, Milestone-Unplanned, Priority-Low, Type-Enhancement
• Removed labels: Milestone-Release2.13, Priority-High, Type-Defect