platform
Use the Gson adapters to serialize/deserialize the NatRules
Switch the NiciraNvpApi to a single gson Object with the proper adapters
Fix missing order setting for static nat rules and portforwarding rules
Return an error when a port range is passed in a portforwarding rule
The serializer is not required
Fix a bug where an ip address could be released even if it was still in
use for SourceNat
Throw a json parse exception when the type is unknown to the adapter
Missing default constructor fails the agent manager reloading the XCP
resource on reboot of management server. This is fixed by using the
default constructor as do other Xen resources and include a new resource
ala XenServers for XCP1.6.
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit 806aeb990d)
Conflicts:
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XcpServerResource.java
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
The debian package cloudstack-awsapi is being built empty. This patch
adds the required files to the package and a symlink for webapps/awsapi so the awsapi can
be found by tomcat, without change in configuration.
This fixes a null pointer if selected pool on which to deploy is unable
to be looked up via id. Used the same coding style found in the original
code (large if/else block).
If this is accepted, I'll fix master too. This patch doesn't apply
cleanly, but the code is very similar.
Testing:
Fixed broken system, tested against devcloud to ensure that it didn't
break a stock/fresh install (advanced zone with 3 storage pools).
Restarted VMs to ensure that the planner still functioned that way as
well.
Signed-off-by: Chip Childers <chip.childers@gmail.com>
an IP. This seems to be possible if expunge fails at some point after freeing
an IP, on subsequent expunge tries the IP is freed already and gets null pointer
when looking for account id.
BUG-ID: CLOUDSTACK-2279
Bugfix-for: 4.1,4.2
Signed-off-by: Marcus Sorensen <marcus@betterservers.com> 1367251304 -0600
pass back null if we fail to connect to agent or stop the vm, rather
than something that looks like success to the stopVirtualMachine api
command.
Testing:
Applied to 4.1 branch, attempted to stop VM with KVM agent disconnected,
finally saw it fail. The logs also showed why, which is good:
2013-04-25 17:37:09,933 ERROR [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-1:job-44) Unable to stop vm, agent unavailable:
com.cloud.exception.AgentUnavailableException: Resource [Host:1] is
unreachable: Host 1: Host with specified id is not in the right state:
Disconnected
Started the KVM agent, and stopping succeeded.
Signed-off-by: Chip Childers <chip.childers@gmail.com>
In the applicationContext .xml , the context of the 'UserConcentratedPodPlanner' needs to include the list of allocators.
This will ensure that when this component is loaded by Spring, the allocators gets initialized.
Chip Childers
Hugo Trippaers
Wido den Hollander
Prasanna Santhanam
Wido den Hollander
Emerson Pinter
Wei Zhou
Kishan Kavala
Chiradeep Vittal
Marcus Sorensen
Brian Federle
Gavin Lee
Chip Childers
Milamber
Edison Su
Hiroaki KAWAI
Sebastien Goasguen
Sheng Yang
Kelven Yang
Marcus Sorensen
Edison Su
Prachi Damle