[DISCUSS] 4.11.1.0 release

2018-04-20 Thread Rohit Yadav
All, I would like to kick a discussion around the next 4.11 LTS minor/bugfix release - 4.11.1.0. Many of us have tried to discuss, triage and fix issues that you've reported both on users and dev MLs. It is possible that some of those discussions have not met a conclusion/solution yet. There

Re: [DISCUSS] Why we MARK packets?

2018-04-20 Thread Rohit Yadav
Thanks Jayapal. I don't have any comparative study yet, but I'll explore this in future if we can get away without marking (mangling) packets which is generally an expensive task. - Rohit From: Jayapal Uradi Sent: Thursday, A

[ASK][PARTICIPATE] Test new cloudmonkey v6.0.0-alpha1

2018-04-20 Thread Rohit Yadav
All, The go-based port is functionally complete! I would like to invite interested users to help test it. You can build yourself the binaries from here: github.com/apache/cloudstack-cloudmonkey Alternatively, you can test using pre-built binaries from here: https://lab.yadav.cloud/testing/

RE: Re: starting the management service(ACS4.10)

2018-04-20 Thread 丸子良太 / MARUKO,RYOTA
Dear Ivan, Initially I tried to build on ACS4.11 with KVM. I could not find the manual, so I could not build it. ex) 1) In the case of ipv6 disable on CentOS7 with ACS4.11, the management service cannot start. 2) Even if I can start the service, I cannot add the KVM hosts. Because of it, I bu

RE: starting the management service(ACS4.10)

2018-04-20 Thread 丸子良太 / MARUKO,RYOTA
Dear Dag, Thank you for your advice. Starting the service is quicker than before. Regards, Ryota Maruko > -Original Message- > From: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com] > Sent: Thursday, April 19, 2018 6:24 PM > To: users@cloudstack.apache.org > Subject: Re: starting the ma

Re: Upgrade from ACS 4.9.3 to 4.11.0

2018-04-20 Thread Andrei Mikhailovsky
Hello everyone, Further into the investigation, the problem was pinned down to those rules. All the traffic from internal IP on the static NATed connection were forced to go to the outside interface (eth1), by setting the mark 0x1 and then using the matching # ip rule to direct it. #iptables -