Jeromy, There is all sorts of things that might be the problem, can you make
your plugin a PR so we can look at it?
daan.hoogl...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands
@shapeblue
From: Jeromy Grimmett
2017-02-21 10:24:41,455 WARN [c.c.n.v.VpcManagerImpl]
(API-Job-Executor-1:ctx-35f691c4 job-84610 ctx-b97ae09e) (logid:8ad82f23)
Failed to start vpc [VPC [49-isp] due to
com.cloud.utils.exception.CloudRuntimeException: Unable to serialize: Job
is cancelled as it has been blocking others for too
We have been writing a plugin for ACS and have put our code into the plugins
directory according to the documentation here:
http://docs.cloudstack.apache.org/en/latest/plugins.html
The plugin does not show up after refreshing the UI or even after restarting
the cloud-management service.
Any
Importantly, if you're in a multi-hypervisor setup, you need to account for
what'll happen when all clusters of a hypervisor type go down. In your
case, if the KVM cluster goes down and you've pinned the systems VMs to the
KVM cluster, then CloudStack won't be able to restart them on either
[UPDATE]
According to this method
"com.cloud.resource.ResourceManagerImpl.getAvailableHypervisor(long)", if
you do not configure the “system.vm.default.hypervisor” parameter, the
hypervisor selected for system VMs is random (among the ones available).
On Mon, Feb 20, 2017 at 11:37 AM, Rafael
Hi Engelmann,
I still quite not understand your problem yet. I see that you have three
different clusters; one KVM, One XenServer 6.5 and one 7.0. You want to use
the KVM as the hypervisor to host your system VMs, right?
Have you configured the parameter “system.vm.default.hypervisor”?
On Mon,
Hi Rafael,
We do use the following setup (Test environment currently):
ACS 4.9.2
1x Xenserver 6.5 Cluster (3 nodes)
1x Xenserver 7.0 Cluster (1 node)
1x Ubuntu 16.04 KVM Cluster (3 nodes)
Networking = Advanced Zone VPC and Virtual Router
I noticed the error Message was just informational an
