alena 41e5e38fef bug 9336: securityGroups can be used by other securityGroups in the same domain only; no cross domain SG authentication ... status 9336: resolved fixed Following changes were made: * deleteSecurityGroup/authorizeSecurityGroupIngress - removed account/domainId parameters as SG is uniquely identified by id now * removed account_name field from securityGroup DB table; removed allowed_security_group/allowed_sec_grp_acct from security_ingress_rule. These values were used for api response generation only for performance purposes; added caching on API level to improve performance * Added missing security checks for securityGroups/ingressRules		2011-04-22 11:35:29 -07:00
..
bindir	Additions made to the script inorder to avoid VM login using "saved_password" string	2011-03-09 15:54:18 -08:00
db	bug 9336: securityGroups can be used by other securityGroups in the same domain only; no cross domain SG authentication	2011-04-22 11:35:29 -07:00
.project	Branch 2.1.refactor committed	2010-08-11 09:13:42 -07:00