I did try to dedicate a Pod to an account, however it whilst it meant other
accounts couldn't launch in the pod, it didn't force the target account to
have newly created vm's placed in that pod.
Cloudstack continued to use its regular placement algorithm, which we have
set to FirstFitPlanner, and
Hi,
I have had this issue a few times now with my management server. I have had a
couple unfortunate hw issues that have caused the machine to crash (have
replaced motherboard, backplane and network cards…. don’t ask). Upon restoring
the machine there is a new entry in the mshost table. Howev
Starting a VM instance will end in error if there is no host suitable for it.
We normally limit number of VM in an affinity group to be one less than the
number of hosts in the cluster.
Let’s say I have 5 instances for my app, and I have 5 hosts in my cluster. I
will only put 4 instances in
Now I think I understood what you want to do.
What about dedicating the pod directly, without using any changes at the
service offering (lets avoid mixing configs in this sea of possibilities we
have here), then you could limit the amount of resource the user can use by
the maximum amount of (CPU/
No. The template needs to be registered separately in each region (using
registerTemplate API).
On 05/10/16, 12:49 AM, "Ghaith Bannoura" wrote:
Hello All,
Is there any automated way to replicate templates between regions ?
Best Regards
Ghaith Bannoura
DIS
