Re: S2S VPN to AWS problems

2017-12-01 Thread Nux!
Thanks! Manually modifying the VR kind of sucks ... hopefully this will be improved in the future. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Srinivas Gandikota" > To: "dev"

Re: Clean up old and obsolete branches

2017-12-01 Thread Khosrow Moossavi
@Daan That's a good point, I'll try to update the list to CLOUDSTACK- wherever applicable. But the majority of branches are 4.1.x to 4.6.x, which might be able to be cleaned up easily. - I feel we might be able to delete everything 4.1.x, 4.2.x, 4.3.x, 4.4.x, 4.5.x, 4.6.x (almost blindly). - the

Re: [PROPOSE] RM for 4.11

2017-12-01 Thread Rohit Yadav
Thanks everyone for your support (and statues :) ). I look forward to working with everyone for the next best CloudStack release. Regards. From: Simon Weller Sent: Friday, December 1, 2017 1:12:21 AM To: dev@cloudstack.apache.org

Re: Clean up old and obsolete branches

2017-12-01 Thread Daan Hoogland
also I think we can tolerate collective work on our repo. Not everything has to go on forks. On Fri, Dec 1, 2017 at 11:04 AM, Daan Hoogland wrote: > Rafael, I don't think that works. the versions in the pom.xml files are > updated to non snapshot versions on per release

Re: Clean up old and obsolete branches

2017-12-01 Thread Daan Hoogland
Rafael, I don't think that works. the versions in the pom.xml files are updated to non snapshot versions on per release mini branches. I like the principle but be carefull not to remove the GA branches. On Fri, Dec 1, 2017 at 10:41 AM, Rafael Weingärtner < rafaelweingart...@gmail.com> wrote: >

Re: Clean up old and obsolete branches

2017-12-01 Thread Rafael Weingärtner
Thanks for the initiative and the hard worki Khosrow! In my opinion, we should only maintain the master and major release branches. Then, for minor versions, we can keep track of them using tags. There is no need to have things such as GA-4.4.1, GA-4.4.2, and so forth. Instead, we should keep

Re: Issue with Opensaml and Self-Signed Certificates

2017-12-01 Thread Harika Punna
Rohit, I have debugged already and found that the password for keystore is null, though I have provided the password in properties file, which is the cause for the issue. I will try with any publicly available SAML providers. Thanks, Harika. On 30/11/17, 3:17 PM, "Rohit Yadav"