CLOUDSTACK COLLABORATION CONFERENCE 2019 - LAS VEGAS

Hi Fellow CloudStack People. Hopefully you have all heard that *CCCNA2019* will be happening on September 9th-11th 2019 in *Las Vegas* in in conjunction with ApacheCon. And the CFP closes *13th May* If not, in summary CCC (CloudStack Collaboration Conference) is where we try to get together as

Re: Cloudstack-agent gets the local IP address exception

That sounds great Li, glad you solved the problem. On Tue, 23 Apr 2019 at 16:49, li jerry wrote: > Hi Andrija > > > > Your method is very good. I just tested agent. lb. When management > fails, the agent can complete switching in a very short time. > > > > > >

答复: Cloudstack-agent gets the local IP address exception

Hi Andrija Your method is very good. I just tested agent. lb. When management fails, the agent can complete switching in a very short time. 发件人: Andrija Panic 发送时间: Tuesday, April 23, 2019 10:22:47 PM 收件人: dev 抄送: us...@cloudstack.apache.org 主题: Re:

Re: Cloudstack-agent gets the local IP address exception

Hi Jerry, not a good idea, if you don't mind me saying that. Are you using 4.11 release ? If so you should use the internal LB logic that is now part of Agent on KVM side - please check this one: https://www.shapeblue.com/software-based-agent-lb-for-cloudstack/ Let me know if this works for

答复: 答复: Cloudstack-agent gets the local IP address exception

Hi Dag Sonstebo Because we only have three servers in total, we can't make one management node independently, so we can only downgrade and let them merge. 发件人: Dag Sonstebo 发送时间: 2019年4月23日 21:35 收件人:

Re: 答复: Cloudstack-agent gets the local IP address exception

Hi Li, Your configuration goes against best practice - you generally always keep management and hypervisors separate. To my knowledge there is nothing in the CloudStack KVM agent which will allow for the configuration you have in place, so you would have to deploy your own manual workarounds

答复: Cloudstack-agent gets the local IP address exception

HI Dag Sonstebo We deploy management and agent on the same host, with three such nodes. So we need to deploy keepalived on these three nodes, elect a VIP, and let all agents communicate with this VIP. 发件人: Dag Sonstebo 发送时间: 2019年4月23日 17:08 收件人:

Re: Latest Qemu KVM EV appears to be broken with ACS

All, I've found and fixed an edge/security case while testing it for CentOS6, the PR should not be compatible for all support KVM distros: https://github.com/apache/cloudstack/pull/3278 The issue was that the systemvm.iso file includes an authorized_keys file from our codebase and may

Re: Cross cluster cold migration failed in vmware

Hi Alireza You can create similar compute offering with host tags (of hosts in a cluster to start VM) and change the compute offering for the VM to the new one. - Suresh On Tue, Apr 23, 2019 at 2:49 PM Alireza Eskandari wrote: > Hi guys, > I face with a problem in old migration of VMs between

Cross cluster cold migration failed in vmware

Hi guys, I face with a problem in old migration of VMs between 2 cluster. If you stop a VM in 1st cluster, then you try to start it on a host in 2nd cluster, you will get "The specified key, name, or identifier already exists." error from VMWare. I have opened an issue in CloudStack github about

Re: Cloudstack-agent gets the local IP address exception

Li, Why do you run with this configuration? If this is for network resilience you would run a bond/team, not keepalived. Regards, Dag Sonstebo Cloud Architect ShapeBlue On 22/04/2019, 14:37, "li jerry" wrote: HI All my kvm host [ip:10.226.16.11] virtualized a