Re: [VOTE] Apache Cloudstack 4.11.0.0 (LTS)

Thanks all for your participation towards 4.11.0.0 RC1. We've managed to discover and fix about 10 blocker fixes, I'll close RC1 voting now and cut RC2 shortly. - Rohit From: Frank Maximus Sent: Wednesday, January 24, 2018 2

[VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

Hi All, I've created a 4.11.0.0 release (RC2), with the following artifacts up for testing and a vote: Git Branch and Commit SH: https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.0.0-RC20180126T1313 Commit: 5dada1f7ed5fb6a8ee261c763f744583e586f8bf Source release (

Re: New L2 nework types are not shared

Jean-Francois, The issue raised is a valid bug in the new feature but not a blocker so it was not included in RC2, the shared bugfix PR will be targeted for 4.11.1.0 release. - Rohit From: Jean-Francois Nadeau Sent: Thursday

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

Hi all, I’ve done upgrade testing on the following platform matrix: OS and Hypervisor \ ACS Version 4.5 → 4.11 4.6 → 4.11 4.9 → 4.11 M: CentOS6 H: CentOS 6 ✔ M: CentOS6 H: XS65sp1 ✔ M: CentOS6 H: VMware 5.5u3 ✔ M: CentOS7 H: CentOS 7 ✔ M: CentOS7 H: XS7

Enhance package.sh script

Hi community I fixed and enhanced package.sh script in PR #2433 [1]. It's based on 4.11 branch and since it's only touches packaging script, it should be safe to be included in 4.11.0.0 and/or 4.11.1.0. The idea was to be able to "brand" the final package name to distinguish the custom built pack

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

I won't be able to test sooner than Monday guys. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Boris Stoyanov" > To: "dev" > Cc: "users" > Sent: Friday, 26 January, 2018 17:48:24 > Subject: Re: [VOTE] Apache Cloudstack 4.11.0.0 LT

System VMs and bridge connections

Can someone tell me where I am going wrong or if this is possible (apologies for the long post) I have configured the management server as per installation instructions with just an interface in the management network using subnet 172.16.7.0/27 I then configured a host with 3 separate NICs