Get Ganeti cluster name from ssconf
Modify snf-ganeti-eventd in order to get the name of the Ganeti clusterfrom shared configuration files (ssconf) instead of performing a LUXI query.Performing a LUXI restricts eventd to run only on the master node.
Merge branch 'devel-0.11' into ui-0.11
Conflicts: snf-cyclades-app/synnefo/db/models.py snf-cyclades-app/synnefo/logic/backend.py snf-cyclades-app/synnefo/ui/static/snf/js/models.js
Change eventd and dispatcher AMQP retries
Set unlimited connection retries to AMQP hosts for snf-ganeti-eventd,since death of snf-ganeti-eventd results in loss of events.Also increase retries of snf-dispatcher.
Fix None timestamp in eventd messages
Send the job timestamp when an opcode does not have a timestamp.
Change process title to simplify 'ps' display
Use python-setproctitle to change the process title of the runningdaemon. Make it appear as a native executable to simplifyadministration. Only set executable name, because cannot set individualvalues for arguments.
Fix no-time in eventd messages
Ganeti opcodes may not have an end-timestamp when they go toan error state. In that case send the job end-timestamp.
Fix progress monitor client initialization
correct api use.
Fix AMQP bug in snf-progress-monitor
Comply with the new monitoring system of snf-image
For now only the image-copy-progress messages are processed
Get cluster name from Ganeti
Query Ganeti for getting the cluster name, instead of reading thessconf files.
View revisions
Also available in: Atom