290c799b2c
Bug 9273 : [Stress Test] 'Count' in resource_count table has negative values
...
pushing 2.2.4 changes in to master
2011-04-11 15:37:53 +05:30
598503f094
bug 9129:can't create vm if an instance limit is set at root domain
...
pushing 2.2.4 fixes
2011-04-08 13:25:51 +05:30
923f562aa8
Bug 6873: disable/enable mode for clusters (and pods and zones and hosts)
...
- Added a new flag 'allocation_state' to zone,pod,cluster and host
- The possible values for this flag are 'Enabled' or 'Disabled'
- When a new zone,pod,cluster or host is added, allocation_state is 'Disabled' by default.
- For existing zone,pod,cluster or host, the state is 'Enabled'.
- All Add/Update/List commands for each of zone,pod,cluster or host can now take a new parameter 'allocationstate'
- If 'allocation_state' is 'Disabled', Allocators skip that zone or pod or cluster or pod.
- For a root admin, ListZones lists all zones including the 'Disabled' zones. But for any other user, the 'Disabled' zones are not included in the response.
- For any usecase that creates/deploys/adds/registers a resource and takes in zone as parameter, now we check if the Zone is 'Disabled'. If yes then the operation cannot be performed by a user other than root-admin. Add volume, snapshot, templates are examples of this usecase.
- To enable the root admin to test a particular pod/cluster/host, deployVM command takes in 'host_id' parameter that can be passed in only by root admin.
If this parameter is passed in by the admin, allocators do not search for hosts and use that host only. StoragePools are searched in the cluster of that host.
If VM cannot be deployed to that host, allocators and deployVM fails without retrying
2011-03-23 22:15:35 -07:00
5129df106b
bug 8847: createUser api - "account" parameter is required now
...
status 8847: resolved fixed
2011-03-09 10:21:50 -08:00
db7a0ddb75
bug 8672: Added action events for User commands
...
status 8672: resolved fixed
2011-03-04 16:45:49 +05:30
a8e70cf9b4
bug 8763: Fixed account cleanup process - don't destroy networks when vm expunge failed
...
status 8763: resolved fixed
Conflicts:
server/src/com/cloud/user/AccountManagerImpl.java
2011-03-01 14:25:09 -08:00
65eaf27c5c
bug 8670, 8672: Added action events for account/user actions
...
status 8670: resolved fixed
2011-03-01 21:19:34 +05:30
62b3d548d6
bug 8753: never release public Ip address without ensuring that all corresponding resources (PF/StaticNat/Lb rules) are cleaned up.
...
Fixed couple of other problems along:
* when expunge PF/Static nat rules as a part of vmExpunge/IpRelease process, first mark all rules as Revoke, and then send commands to the backend. Group commands by Ip address.
Before we used to do Revoke/Send per rule basis.
* When release source nat rule, make sure that corresponding vpn (if exists) is being expunged.
2011-02-28 09:21:05 -08:00
65d22a7a15
Fixed exception logging in several places
2011-02-25 09:31:21 -08:00
970e0ab320
Removed unused imports
2011-02-24 19:47:25 -08:00
8eb665246e
bug 7935: Included hypervisor type to vm usage records
...
status 7935: resolved fixed
2011-02-24 20:08:12 +05:30
15f59e6f58
bug 8637: throw ResourceAllocationException when resource limit is exceeded.
...
status 8637: resolved fixed
2011-02-18 12:26:58 -08:00
7aa18d4fe2
bug 8600: cleaning up remote access vpns and users as part of delete account
...
status 8600: resolved fixed
2011-02-18 11:11:43 -08:00
96ef94eb37
ShutdownNetwork - added reservationContext parameter (contains account/callerUserId)
2011-02-17 16:13:28 -08:00
2275d8d833
bug 8452: introducing a state for domain; blocking creation of accounts/users whilst domain is in an inactive state
2011-02-17 15:17:45 -08:00
3d7c61bf8b
bug 8452: forcing vm stop whilst disabling account
...
status 8452: resolved fixed
2011-02-17 13:57:04 -08:00
ab6ea4d6ef
bug 8491: remove corresponding record from resource_limits table when limit is updated with -1 value
...
status 8491: resolved fixed
2011-02-08 19:08:35 -08:00
75e596bb80
bug 7952, 8363: Fixed usage events for Vm destroy and recover
...
status 7952, 8363: resolved fixed
2011-02-08 16:57:46 +05:30
e299402243
Perform security check for deleteNetwork inside the management server method instead of api command itself
2011-02-07 10:02:10 -08:00
0105c03a27
initial HA work
2011-02-04 11:51:14 -08:00
56f3343911
Added action events for VM, volume, Ip and snapshot actions
2011-02-04 19:59:41 +05:30
e9490bda55
bug 8359: fixed deleteDomainCommand - didn't work when domain had accounts assigned (incorrect method cleanupAccount was called instead of deleteAccount)
...
status 8359: resolved fixed
2011-02-03 10:38:53 -08:00
8ce576dde5
bug 8239: NPE while executing CreateSnapshotCmd
...
status 8239: resolved fixed
2011-02-02 13:12:34 -08:00
668fde991c
Don't default resource owner to System account when command is executed via 8096 and account or domainId are missing
2011-02-01 14:20:45 -08:00
447153f570
bug 8247: when we have vms in error state, we destoy their volumes. then, when we delete account with such vms, we should NOT try and destroy vols already destroyed.
...
status 8247: resolved fixed
2011-02-01 11:13:40 -08:00
620466d393
Network destroy: when release ip addresses assigned to the network, no need to send applyIpAssociations command to the network elements as they are already shutdown.
2011-01-28 10:09:20 -08:00
6304a92c23
bug 7881: fixed publicIpAllocation to an account.
...
status 7881: resolved fixed
Also fixed the issue with account delete when nonSourceNat ip addresses were not being released
2011-01-24 10:03:18 -08:00
af3373c4d6
Deleted global config parameter direct.network.no.default.route that is no longer in use.
2011-01-20 13:15:25 -08:00
a4cfe20db8
bug 7389: implemented listPortForwardingRules by ip/account/domainId. Also fixed broken pagination for this call
...
status 7389: resolved fixed
2011-01-20 11:35:40 -08:00
94ec7bf27a
bug 7842: events refactoring. Still wrok in progress
2011-01-20 21:49:50 +05:30
afcb202923
bug 7900: removing obsolete network domain param
...
status 7900: resolved fixed
2011-01-19 17:18:02 -08:00
632d3c67f1
bug 6689: release source nat ip address as a part of domR/dhcp destroy
...
status 6689: resolved fixed
Changes to destroyNetwork process. Here are the steps:
* shutdown network - shutdowns all network elements (domRs/Dhcps)
* delete network - destroy all network elements, cleanup network's resources (vlans, ip ranges), mark network with Destroyed state and set Removed field
2011-01-18 19:31:04 -08:00
2b66b8a924
bug 7929: remove security groups when account is deleted.
...
status 7929: resolved fixed
2011-01-13 15:40:29 -08:00
381717854c
Fixed NPE in deleteAccount - search for all accounts (instead of searching for active accounts only) when do deleteNetwork
2011-01-12 16:34:56 -08:00
916b516d13
bug 7878: Fixed Basic zone functionality - uservm/systemvm/domR start
...
status 7878: resolved fixed
2011-01-06 15:44:13 -08:00
0b7a15ab99
bug 7348: reapply PortForwardingRules (including 1-1 Nat), LB rules, Vpn as a part of domr Stop/Start
...
status 7348: resolved fixed
More fixes:
* Update user_statistics on each domR stop/reboot
* Reset dhcpData/userData as a part of domR stop/reboot
* More logging for domR commands
2011-01-03 23:00:05 -08:00
511c780e97
bug 7754: added userId and accountId for deleteUser event
...
status 7754: resolved fixed
2011-01-03 16:42:54 +05:30
dfecc1f448
Changed account state to be in lower case.
2010-12-30 09:57:59 -08:00
da4ed648ac
consolidated all of the vm destroy, cleanup and account cleanup.
2010-12-30 05:46:54 -08:00
544fa7ff1b
remote access vpn, user ip address changes
2010-12-29 09:32:54 -08:00
52478aaf73
bug 7699: set correct account_id/user_id for createUser events
...
status 7699: resolved fixed
2010-12-27 19:54:36 -08:00
e51dc79000
bug 7504: Events refactoring
...
status 7504: resolved fixed
2010-12-24 19:38:28 +05:30
53d3455cbe
bug 7504: Events refactoring
2010-12-24 12:58:32 +05:30
bb0e6a0ae3
bug 7504: Events refactoring
2010-12-24 12:58:32 +05:30
0ecb0118ec
renamed the domainrouter services
2010-12-21 03:56:01 -08:00
21bb9df292
Fixed accountCleanup to release all public ip addresses and delete the corresponding networks.
2010-12-20 20:20:09 -08:00
376d5da45d
bug 7106: fixing the account updating bug
...
status 7106: resolved fixed
2010-12-16 17:32:22 -08:00
5154ba1539
bug 6361: this is a good point to commit; 1st round of refactor is done, code is clean compiling and ms is deploying
2010-12-16 15:37:19 -08:00
6ae9e73c0b
bug 7466: adding a whole bunch of new apis for accounts and users; merging account locking and disabling into one; preventing account manipulation on user disabling; disabling user lock
2010-12-14 15:38:37 -08:00
d077b127aa
bug 7498: fixed search by keyword in listUserVm/listSystemVms/listRouters commands
...
status 7498: resolved fixed
2010-12-13 15:22:11 -08:00
Murali Reddy
prachi
alena
kishan
abhishek
Alex Huang
Chiradeep Vittal