alena f6a79c603f bug 11036: resource count update is refactored ... status 11036: resolved fixed 1) Use row locks instead of global lock when update resource_count table. When update resource_count for account, make sure that we lock account+all related domains 2) Insert resource_count records for account/domain at the moment when account/domain is created. 3) As a part of DB upgrade, insert missing resource_count records for all non-removed accounts/domains Conflicts: core/src/com/cloud/alert/AlertManager.java server/test/com/cloud/agent/MockAgentManagerImpl.java		2011-09-13 10:47:36 -07:00
..
DatabaseConfig.java	bug 11036: resource count update is refactored	2011-09-13 10:47:36 -07:00
IPRangeConfig.java	Store ip address as String instead of Long in user_ip_address and port_forwarding_rules tables	2011-02-09 19:35:03 -08:00
PodZoneConfig.java	Save vnet range in data_center table when do deploy from server-setup.xml in Dev environment	2011-02-08 19:18:52 -08:00