Hello All
We found in the process of use, when the vcpu in service_offering is a multiple
of 6, vm cpu socket =vcpu/6, when vcpu is a multiple of 4, vm cpu socket=vcpu/4
Excuse me, why do we design this way?
In my application scenario, there are restrictions on cpu socket, so I want to
lock t
Hello All
I started VM HA through the calculation scheme.
However, at work, it is sometimes necessary to "temporarily" shut down the HA
for testing.
My current practice is to directly modify cloud.ha_enabled=0;
Is there any hidden danger in this operation?
-Jerry
Hi Li,
if that works for you, then that's all you need. You can always revert the
change back AND test that it works fine (i.e. stop VM and see if ACS will
start it again)
If you have a need to just occasionally stop the VM from inside the OS -
then, assuming you doing some manual work (i.e not a
rhtyd commented on issue #29: Implement autogenerated actions forms with
key-remapping
URL:
https://github.com/apache/cloudstack-primate/issues/29#issuecomment-557952280
Fixed in e82f401d83a6d37c44d4310b35e4ec2b6d6e8278
config: action args remapping framework
This
rhtyd closed issue #29: Implement autogenerated actions forms with key-remapping
URL: https://github.com/apache/cloudstack-primate/issues/29
This is an automated message from the Apache Git Service.
To respond to the message,
Thank you Andrija
I have another problem with VM HA.
Our scenario is KVM + ACS 4.11.2;
When we found that the guest OS had a blue screen during the test, the VM did
not detect that the VM failed and triggered HA. Is this normal?
-邮件原件-
发件人: Andrija Panic
发送时间: 2019年11月25日 2:10
收件人: d
