Fix for the issue #1398578 (https://bugs.launchpad.net/juniperopenstack/+bug/1398578). The fix is in setting the transaction isolation level from the default REPEATABLE-READ to READ-COMMITTED for innodb. This will essentially improve the locking of tables with indexes. With READ-COMMITTED, the entire table is not locked while there are existing transations on the table. Threads can update rows in the table and lock is released after statement completes. In addition the nova.conf on the compute has the rpc_response_time set to 120 sec. Tested the configuration in project ganges setup and did not see the issue after this fix

Change-Id: Icd355bbed255e43ac28bf54bfa5638707a925625
Merge "Fix for the issue #1398578 (https://bugs.launchpad.net/juniperopenstack/+bug/1398578). The fix is in setting the transaction isolation level from the default REPEATABLE-READ to READ-COMMITTED for innodb. This will essentially improve the locking of tables with indexes. With READ-COMMITTED, the entire table is not locked while there are existing transations on the table. Threads can update rows in the table and lock is released after statement completes. In addition the nova.conf on the compute has the rpc_response_time set to 120 sec. Tested the configuration in project ganges setup and did not see the issue after this fix" into R2.0