5495f10bce
Revert "Reverting the range of commits that broke the build"
...
This reverts commit b59e3aaefc
2013-08-08 15:02:40 -07:00
b59e3aaefc
Reverting the range of commits that broke the build
...
This reverts commits 30c33415..f6a2c817bc
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
2013-08-08 14:46:56 +05:30
5287f4c9ec
Got everything running through testing
2013-08-07 16:41:06 -07:00
5161ded69c
Removed the configuration parameters from Config.java
2013-08-07 16:41:05 -07:00
49cd4fa380
Connected config gathering to CloudStack
2013-08-07 16:41:04 -07:00
942f282a6e
Moved config into it's own package
2013-08-07 16:41:02 -07:00
cf3bbb1fb1
Switched AgentManager to use ConfigDepot
2013-08-07 16:41:00 -07:00
e115ee4026
CLOUDSTACK-3535: still maintain stop agent wont trigger HA
2013-08-07 14:43:16 -07:00
5b0314fff9
CLOUDSTACK-3535: add kvminvestigator to investirage kvm host
...
Conflicts:
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
2013-08-07 11:44:19 -07:00
0b1f97d048
Added Configurable interface
2013-08-02 11:07:54 -07:00
1e1ee902a2
Moved over the new jobs framework from vmsync. This has not been integrated into the server package yet. Will do that next
2013-07-30 15:00:58 -07:00
1d4b22d6de
Removed AgentMonitor and moved it inside AgentManager
2013-07-29 19:13:32 -07:00
d0a3a69170
Unused code removal
2013-07-29 19:13:31 -07:00
46e644e134
Separate agentmanager from server code. Moved out ssvm. Remove methods that shouldn't be used
2013-07-29 19:13:31 -07:00
2dc3ede0a8
Remove a line to make it compile
2013-07-25 20:29:13 -07:00
111febc567
Fixed up the rest of the management server code that calls clustermanager
2013-07-25 19:57:45 -07:00
9aaa378b08
Moved ClusterManager into it's own package. Removed the agent load balancing code.
2013-07-25 19:00:26 -07:00
8295cb0ac2
CLOUDSTACK-3250: Add PvlanSetupCommand into maintenance mode allowed command list
...
Then the rule in the old host can be cleared.
2013-07-23 15:19:34 -07:00
db8b9ea53a
Remove CLOUDSTACK-3513 debugging messages.
2013-07-22 16:18:16 -07:00
1325014a03
Changed VirtualMachineProfile to be non-generic. From here on VirtualMachineManager will only manage vm instance. It doesn't understand the difference between different types of VMs. This makes the vmsync code to be generic across all vms.
2013-07-22 11:48:11 -07:00
e1c17bd853
CLOUDSTACK-3513: add debug message to diagnose copyIso issue on
...
automation setup where DownloadCommand is never sent.
2013-07-18 16:08:29 -07:00
11971b5a58
Bring over from vmsync changes in utils package. Simple changes. New files are not being used yet in master
2013-07-17 18:29:42 -07:00
11e1e585b1
UserContext switched to CallContext. Added generic storage mechanism for other code to carry information throughout a call. Made the calling User and Account a must have. Added an interface to carry entities in error. Fixed up the code. Part of the vmsync branch
2013-07-16 11:24:21 -07:00
aed49572c7
CLOUDSTACK-2918: In a scaled up environment, hosts fail to come up after Management server restart in clustered set up
...
Summary of changes in the fix
- Optimized host scan logic, now instead of iterating over each cluster host scan is done for a batch of clusters
- Made host scan task interval configurable
2013-07-10 12:13:24 +05:30
43ab9506ab
Moved HostAllocator and PodAllocator from server to api package, where they are supposed to be. In the process, I had to change the VO objects used by these two itnerfaces to interface equivalent. This makes sense because there's really no reasons why allocators require write access to the database. One of the files have been reformatted because it contained a bunch of tabs instead of spaces for indentation.
2013-07-03 17:48:53 -07:00
ec2bf09284
CLOUDSTACK-2794: Global parameter "router.template.id" should be removed The parameter was not in use. We use zone/global coonfigutaion parameters router.template.xenserver/vmware/hyperv/kvm/lxc to deploy router
...
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-06-26 15:56:40 +05:30
9aec9c605c
merge to master
2013-06-19 18:16:47 -07:00
0a4e65126f
CLOUDSTACK-3079: Use global var "ping.timeout" as a multiplier to ping.interval before announcing an agent has timed out. The multiplier used to be hardcoded to 3
2013-06-19 15:11:53 -07:00
f7c1b711ad
merge to master
2013-05-16 23:56:20 -07:00
a2eb7bab1e
CLOUDSTACK-2056: DeploymentPlanner choice via ServiceOffering
...
- Changes merged from planner_reserve branch
- Exposing deploymentplanner as an optional parameter while creating a service offering
- changes to DeploymentPlanningManagerImpl to make sure host reserve-release happens between conflicting planner usages.
2013-05-16 15:02:17 -07:00
3047929367
Merged
2013-05-10 16:21:43 -07:00
5b76e4914c
Remove sendToSecStorage methods from agentManager to use EndPoint
...
instead.
2013-04-24 16:21:41 -07:00
7543f314a7
Remove more VMTemplateHostDao references.
2013-04-23 17:12:21 -07:00
9c584b5500
Use EndPoint to send local/remote command, and hide agentMgr message
...
passing.
2013-04-22 13:21:28 -07:00
abf40435f3
refactor downloadlistener, sync system vm templates when adding a new image store
2013-04-21 22:46:02 -07:00
21ce3befc8
Storage motion for Xenserver changes: 1. Implemented Api findStoragePoolsForMigration. Added a new response objects to list storage pools available for migration. 2. Updated migrateVolume api for allowing migrating volumes of running vms. These changes are integrated into the latest storage refactoring changes. 3. Added the implementation for findHostsForMigration api. It lists the hosts to which an instance can be migrated, including hosts from within and across clusters to which an instance may be migrated with storage motion. The work of migrating a volume of a running vm is also done in copyAsync. 4. Updated the listHosts api for backward compatibility. 5. Added the implementation for migrateVirtualMachineWithVolume api. It migrates an instance with its volumes within a cluster and also across clusters. Also introduced a new XenServerStorageMotionStrategy for migrating volumes of a vm. When a vm is being migrated with its volumes, the vm is put in migrating state and a request is send to the volume manager to migrate the vm and its volumes. Volume manager calls into the volume service which forwards the request to data motion service after moving all the volumes to migrating state. Data motion service enumerates the strategies and the request reaches the XenServerStorageMotionStrategy. It calls in to the resource to complete the operation. 6. Resolved an issue where storage xenmotion of 2nd VM created from the same template to a host was failing with duplicate_vm exception. Made changes to remove the mac_seed key value pair from other_config when vms are created. This is was storage motion to fail. 7. Updated the db upgrade schema script. 8. Added the right permissions in commands.properties 9. Marvin tests for testing storage motion. Following scenarios are tested. 9.1. A virtual machine is migrated to another host. Its volumes are also migrated to another storage pool. 9.2. Just the volumes of a vm are migrated to another storage pool while the vm continues to run on the same host. 10. Unit tests for testing migration of a vm with its volumes.
...
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-04-19 11:36:42 +05:30
1b3994e180
Fix copyTemplateCmd.
2013-04-16 16:38:14 -07:00
f1259d50bd
Fix for _pingTimeout being 0 in AgentMonitor
...
With commit d79f1f6fdc
2013-04-04 14:23:42 +02:00
9a5bf78c3e
Better error handling for some corner cases
...
Make the exceptions more descriptive so admins can pinpoint the issue
easier.
2013-03-29 12:06:03 +01:00
409ec9c6b6
CLOUDSTACK-1426: We has strong implication that VO must implement an interface, otherwise EntityManagerImpl can't the vo
2013-03-07 18:25:57 -08:00
333dd810d2
CLOUDSTACK-1339: Using Sping interface injection pattern to avoid using CGLIB proxying mode. Spring with CGLIB proxying will concflict with CGLIB usage in CloudStack DB code, CloudStack CGLIB usage can cause Spring to lose tack of its proxied object and therefore creates a massive amount of objects in memory
2013-03-05 19:03:30 -05:00
23e54bb0f4
Cloudstack-711: Cpu and Ram Overcommit Ratio.
2013-02-22 17:31:06 +05:30
6823adb3ac
CLOUDSTACK-1367 NPE noticed in logs while AgentMonitor is monitoring the host ping interval
...
Added null check. If the host is not found, we dont ping anymore.
2013-02-21 17:40:08 -08:00
bd4661e467
CLOUDSTACK-1137: force reconnect to a disconnected host throws error.
2013-02-14 17:57:41 -08:00
296c20332d
Merge javelin into master
2013-02-01 14:40:45 -08:00
777147ce8a
CS-CLOUDSTACK-606:
...
The issue happens randomly when hosts in a cluster gets distributed across multiple MS. Host can get split in following scenarios:
a. Add host – MS on which add host is executed takes ownership of the host. So if 2 hosts belonging to same cluster are added from 2 different MS then cluster gets split
b. scanDirectAgentToLoad – This runs every 90 secs. and check if there are any hosts that needs to be reconnected. The current logic of host scan can also lead to a split
The idea is to fix (b) to ensure that hosts in a cluster are managed by same MS. For (a) only the entry in the database is going to be created except in case if the host getting added is first in the cluster (in this case agent creation happens at the same time) and then (b) will take care of connection and agent creation part. Since currently addHost only creates an entry in the db there is a small window where the host state will be shown as 'Alert' till the time (b) is scheduled and picks up the host to make a connection. The MS doing add host will immediately schedule a scan task and also send notification to peers to start the scan task.
2013-02-01 15:34:41 +05:30
176523254e
Improve component lifecycle management with system run-level concept
2013-01-30 15:21:02 -08:00
2c5859dbd4
Bring javelin back to the status of being able to start System VMs after another round of master branch merge
2013-01-18 19:15:32 -08:00
10d9c019a9
All merge conflicts resolved
2013-01-18 12:14:57 -08:00
e45a9f3aed
CLOUDSTACK-803: HA gets triggered even when the host investigator is unable to determine the state of the host HA won't be triggered in case the host investigator is not able to determine the state
...
Signed-off-by: Koushik Das <koushik.das@citrix.com>
Signed-off-by: Abhinandan Prateek <aprateek@apache.org>
2013-01-18 17:20:51 +05:30
Alex Huang
Prasanna Santhanam
Edison Su
Sheng Yang
Min Chen
Koushik Das
Alex Huang
Harikrishna Patnala
Alena Prokharchyk
Edison Su
Prachi Damle
Devdeep Singh
Hugo Trippaers
Kelven Yang
Bharat Kumar