Cao Shufeng 48790b66aa Log node uuid rather than id when acquiring node lock ...

When attempting to get lock of a node, we get such log:
    "Attempting to get exclusive lock on node 2 (for
     port update)"
However, when reserving and releasing the same node lock,
we get such log:
    "Node 7c3c747d-6315-4db8-8fa5-8e55cf2bcc34 successfully
     reserved for port update (took 0.02 seconds)"
    "Successfully released exclusive lock for port update
     on node 7c3c747d-6315-4db8-8fa5-8e55cf2bcc34 (lock
     was held 0.04 sec)"

Sometimes, we log node_id but in other places, we log
node_uuid. It will become a challenge for trouble shooting
with such inconsistent log.

With this change we always log node_uuid when acquiring node
lock.

Change-Id: Icac16d490d654c73cc99e5d2a9a7c682adbc2802
Closes-bug: #1602490

2016-08-19 07:34:15 -04:00

..

__init__.py

Remove copyright from empty files

2014-01-07 21:05:01 +08:00

base_manager.py

Deprecate putting periodic tasks on a driver object

2016-08-09 13:59:50 +02:00

manager.py

Adding InfiniBand Support

2016-08-14 09:14:34 +03:00

rpcapi.py

Introduce new driver call and RPC for heartbeat

2016-06-27 15:26:10 +02:00

task_manager.py

Log node uuid rather than id when acquiring node lock

2016-08-19 07:34:15 -04:00

utils.py

Merge "Follow-up to Active Node Creation"

2016-06-17 18:10:57 +00:00