Re: KVM HostHA

2018-03-15 Thread Jon Marshall
Hi Parth Can I just ask a few questions - 1) how many compute nodes do you have 2) are you running basic or advanced networking 3) how have you setup your NICs ie. on each compute node I have 3 separate NICs, one for management, one for the VMs and one for storage (NFS). So far I have no

Re: Cloudstack installation on Ubuntu Xenial

2018-03-15 Thread Rohit Yadav
Hi Daniel, After you added the Ubuntu hosts, does it have cloud.jks at /etc/cloudstack/agent? Can you confirm any errors seen during addition of KVM host to the Ubuntu based management server? The log: 2018-03-12 20:44:03,787 WARN [utils.nio.Link] (main:null) (logid:) Failed to load keysto

Re: Change VPC CIDR - and some Mailing List issues

2018-03-15 Thread Rafael Weingärtner
Can people review this PR https://github.com/apache/cloudstack-www/pull/43. It has to do with the mailing list search mechanism On Wed, Mar 7, 2018 at 11:30 AM, Andrija Panic wrote: > root@r-5015-VM:~# grep -ir "10.128.0.0/18" /etc/ ### this is VPC CIDR > > /etc/iptables/router_rules.v4:-A INPUT

Re: KVM HostHA

2018-03-15 Thread Parth Patel
Hi Jon, I have to admit that I have a beginner/mediocre understanding of cloudstack overall (especially the host HA feature). But what works for me should work for everyone. So, to answer your questions: 1) how many compute nodes do you have > I have tested using three agents as when using only

Re: KVM HostHA

2018-03-15 Thread Jon Marshall
Hi Parth Thanks for that. I am a beginner too when it comes to this. Am currently rebuilding so will update this thread when I have retested Jon From: Parth Patel Sent: 15 March 2018 14:37 To: [email protected] Subject: Re: KVM HostHA Hi Jon,

Re: Cloudstack installation on Ubuntu Xenial

2018-03-15 Thread Daniel Coric
Hello Rohit, I'm glad you've noticed the thread. Thank you for clearance. It is definitely reproducible with the 4.11.0.0 and Ubuntu Xenial (16.4.04) - unfortunately I did't save any of the logs. In the process of adding the host, I couldn't authenticate with the "root" user (the default value