IMHO it's something desirable, because in case of emergency, it's better to
migrate a VM to a host that does not follow the anti affinity group, rather
than leaving the VM on a host that must be shutdown for example and loosing
the VM. It's up to the admin to make this transgression during the shor
Can you open a jira issue on this?
Simon Weller/ENA
(615) 312-6068
-Original Message-
From: Yiping Zhang [yzh...@marketo.com]
Received: Tuesday, 08 Nov 2016, 8:03PM
To: users@cloudstack.apache.org [users@cloudstack.apache.org]
Subject: API migrateVirtualMachine does not respect affinity g
Hi,
It seems that the API migrateVirtualMachine does not respect instance’s
affinity group assignment. Is this intentional?
To reproduce:
Assigning two VM instances running on different hosts, say v1 running on h1 and
v2 running on h2, to the same affinity group. In GUI, it won’t let you mig
Hi Kurt,
Is your secondary storage on a separate NFS server?
Have you added the secondary storage mount to CloudStack Management?
If so, have you tried mounting your secondary storage on a different server to
make sure the permissions are set correctly?
- Si
___
Forwarded Message
Subject:Templates are not showing
Date: Tue, 8 Nov 2016 20:09:17 +0530
From: Kurt K
To: users@cloudstack.apache.org
Hi There,
We have started to build our own cloud platform on our organization. Our
deployment is like a small scale arch.
Hi Glenn, thanks for suggestion. I am able to add the host now.
On Tue, Nov 8, 2016 at 4:20 PM, Glenn Wagner
wrote:
> Hi,
>
> What Hyopervisor are you using KVM?
>
> Just check that you can connect the agent back to the management server.
> Check your firewall rules on the host, also check that
Hi,
What Hyopervisor are you using KVM?
Just check that you can connect the agent back to the management server.
Check your firewall rules on the host, also check that the agent is setup
correctly in the agent.properties the host setting is not localhost , but the
IP of the management server (E
