Re: [Review] CloudMonkey v6.0.0 release announcement review request

2019-03-15 Thread Sally Khudairi
Thank you, Rohit --very comprehensive!

I'll review and forward any adjustments this weekend.

Kind regards,
Sally

- - -
Vice President Marketing & Publicity
Vice President Sponsor Relations
The Apache Software Foundation

Tel +1 617 921 8656 | s...@apache.org


On Thu, Mar 14, 2019, at 04:56, Rohit Yadav wrote:
> All,

> 

> Kindly review the release announcement for CloudMonkey v6.0.0, and also share 
> your quotes/comments that we can use in the release wrt cloudmonkey v6.0:

> 

> ### START ###

> 

> 

>  — The Apache Software Foundation (ASF), the 
> all-volunteer developers, stewards, and incubators of more than 350 Open 
> Source projects and initiatives, announced today Apache® CloudStack® 
> CloudMonkey v6.0, the latest version of the turnkey enterprise Cloud 
> orchestration platform's command line interface tool. 
> 
> Apache CloudStack is the proven, highly scalable, and easy-to-deploy IaaS 
> platform used for rapidly creating private, public, and hybrid Cloud 
> environments. Thousands of large-scale public Cloud providers and enterprise 
> organizations use Apache CloudStack to enable billions of dollars worth of 
> business transactions annually across their clouds.
> Apache CloudMonkey v6.0.0 is the latest major release since the previous 
> major 5.x release in September 2013. CloudMonkey v6.0.0 is a rewrite of the 
> original tool in Go programming language, and can be used both as an 
> interactive shell and as a command line tool that simplifies CloudStack 
> configuration and management.
> 
> Some of the new features and major changes include:
> 
>  * Rewrite in Go, ships as single binary for Linux, Mac, and Windows
>  * Drop-in replacement for legacy Python-based cloudmonkey
>  * About 5-20x faster than legacy Python-based cloudmonkey
>  * Interactive UX for parameter and arg completion and selection
>  * JSON is the default output format
>  * New `column` based output
>  * Enable debug mode using `set debug true` option, file-based logging removed
>  * Per server profile based API cache
>  * New syntax `arg=@/path/to/file` to pass the content of file as API 
> argument value similar to `curl`
>  * Improve help docs using `-h` argument
>  * Removed: XML output, coloured output, several `set` options
> 
> "This release is the work of over one year of effort and driven by the people 
> operating CloudStack clouds,” said Rohit Yadav, Apache CloudStack CloudMonkey 
> v6.0 author, and release manager. "I would like to thank the contributors 
> across all of these organizations for supporting this release, which reflects 
> both the user-driven nature of our community and the Apache CloudStack 
> project's commitment to continue to be the most stable, easily deployable, 
> scalable Open Source platform for IaaS. Along with ease of installation, 
> usage and availability of cross-platform dependency-free builds including 
> Windows builds, v6.0 brings many changes and optimizations such as more 
> interactive shell for parameter completion, faster API requests processing, 
> server profile specific API caching, improved API help docs and a new syntax 
> to pass content of files as API parameter argument." The background and story 
> of v6.0 effort was recently blogged here: 
> https://www.shapeblue.com/whats-coming-in-the-new-cloudmonkey-6-0/
> 
> 
> 
> 
> *Downloads and Documentation*
> **
> The official source code for CloudMonkey v6.0.0 can be downloaded from 
> http://cloudstack.apache.org/downloads.html. The community-maintained builds 
> are available at the project's Github release page at 
> https://github.com/apache/cloudstack-cloudmonkey/releases
> 
> CloudMonkey's usage is documented at 
> https://github.com/apache/cloudstack-cloudmonkey/wiki
> 
> *Availability and Oversight*
> **
> Apache CloudStack software is released under the Apache License v2.0 and is 
> overseen by a self-selected team of active contributors to the project. A 
> Project Management Committee (PMC) guides the Project's day-to-day 
> operations, including community development and product releases. For 
> downloads, documentation, and ways to become involved with Apache CloudStack, 
> visit http://cloudstack.apache.org/ and https://twitter.com/CloudStack
> 
> *About The Apache Software Foundation (ASF)*
> **
> Established in 1999, the all-volunteer Foundation oversees more than 350 
> leading Open Source projects, including Apache HTTP Server --the world's most 
> popular Web server software. Through the ASF's meritocratic process known as 
> "The Apache Way," more than 680 individual Members and 6,500 Committers 
> across six continents successfully collaborate to develop freely available 
> enterprise-grade software, benefiting millions of users worldwide: thousands 
> of software solutions are distributed under the Apache License; and the 
> community actively participates in ASF mailing lists, mentoring initiatives, 
> and ApacheCon, the Foundation's official user conference, trainings, and 
> expo. 

Re: Any plan for 4.11 LTS extension ?

2019-03-15 Thread Ron Wheeler

That is written from the point of view of a developer.

From someone who has no desire to ever see the code, let alone change 
it, EOL has a big impact.
In a normal project, in the period prior to EOL, the developers commit 
to fixing bugs and issuing security notices with resolutions.


Cloudstack will have a hard time gaining traction outside the companies 
that develop it, if EOL has no meaning.


I worry that the lack of control over the roadmap and the apparent lack 
of commitment to EOL means that, as good as Cloudstack may be, it is not 
a system for production use unless the user is prepared to take on the 
long-term maintenance at a moments notice and live with uncertainty 
about future viability.


A bit harsh but the conversation about EOL is disturbing.

Ron

On 3/15/19 11:04 AM, Giles Sirett wrote:

Yes - I see your point
I think the thing to bear in mind here is that there is no *formal* EOL for an ACS 
version or branch - its open source - EOL effectively  means that people have lost the 
interest in maintaining that branch.   If people see a demand for more releases on a 
branch in order to maintain that branch  longer- then I'd think it unlikely that anybody 
here is going to say "no"


  maybe the wording in the wiki is misleading



Kind regards
Giles

giles.sir...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
   
  



-Original Message-
From: Jean-Francois Nadeau 
Sent: 15 March 2019 12:49
To: dev@cloudstack.apache.org
Cc: Riepl, Gregor (SWISS TXT) 
Subject: Re: Any plan for 4.11 LTS extension ?

I can only agree with Haijiao,  that 4.11 deserves a longer time span.
Because many bugs are found naturally between the .0 and .1 of the next LTS 
release with it's adoption.

For us 4.11 could only be adopted with 4.11.2.0 after several bugs needed
to get resolved.   So if 4.11's support stops in July then it's time span
was only 6 months from our perspective.

-jfn

On Fri, Mar 15, 2019 at 5:34 AM Wido den Hollander  wrote:



On 3/15/19 10:20 AM, Riepl, Gregor (SWISS TXT) wrote:

Hi Giles,


I would *expect*  4.13.0 (LTS) to be released in Q2, which  will
supersede the 4.11 branch as the current LTS branch

Are you confident that this schedule can be kept?
4.12 is still in RC right now, and I don't think it's a good idea to
rush another major release in just 3 months...


4.11.3 will be released first with some bugfixes to keep 4.11 a proper
release.

4.12 needs to go out now so that we can test and prepare for 4.13. I'm
confident we can have a stable and proper 4.13 release as long as we
don't keep the window open for too long.

The major problem is having the master branch open for a long time,
features going in and people not testing it sufficiently.

By having a relatively short period between 4.12 and 4.13 we can catch
most bugs and stabilize for a proper LTS.

Wido



RE: Any plan for 4.11 LTS extension ?

2019-03-15 Thread Giles Sirett
Yes - I see your point
I think the thing to bear in mind here is that there is no *formal* EOL for an 
ACS version or branch - its open source - EOL effectively  means that people 
have lost the interest in maintaining that branch.   If people see a demand for 
more releases on a branch in order to maintain that branch  longer- then I'd 
think it unlikely that anybody here is going to say "no"


 maybe the wording in the wiki is misleading 



Kind regards
Giles

giles.sir...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-Original Message-
From: Jean-Francois Nadeau  
Sent: 15 March 2019 12:49
To: dev@cloudstack.apache.org
Cc: Riepl, Gregor (SWISS TXT) 
Subject: Re: Any plan for 4.11 LTS extension ?

I can only agree with Haijiao,  that 4.11 deserves a longer time span.
Because many bugs are found naturally between the .0 and .1 of the next LTS 
release with it's adoption.

For us 4.11 could only be adopted with 4.11.2.0 after several bugs needed
to get resolved.   So if 4.11's support stops in July then it's time span
was only 6 months from our perspective.

-jfn

On Fri, Mar 15, 2019 at 5:34 AM Wido den Hollander  wrote:

>
>
> On 3/15/19 10:20 AM, Riepl, Gregor (SWISS TXT) wrote:
> > Hi Giles,
> >
> >> I would *expect*  4.13.0 (LTS) to be released in Q2, which  will 
> >> supersede the 4.11 branch as the current LTS branch
> >
> > Are you confident that this schedule can be kept?
> > 4.12 is still in RC right now, and I don't think it's a good idea to 
> > rush another major release in just 3 months...
> >
> 4.11.3 will be released first with some bugfixes to keep 4.11 a proper 
> release.
>
> 4.12 needs to go out now so that we can test and prepare for 4.13. I'm 
> confident we can have a stable and proper 4.13 release as long as we 
> don't keep the window open for too long.
>
> The major problem is having the master branch open for a long time, 
> features going in and people not testing it sufficiently.
>
> By having a relatively short period between 4.12 and 4.13 we can catch 
> most bugs and stabilize for a proper LTS.
>
> Wido
>


Re: [VOTE] Apache CloudStack 4.12.0.0 [RC5]

2019-03-15 Thread Gabriel Beims Bräscher
+1

Tested:
-- Environment
ACS management + DB: Ubuntu 16.04
Hypervisor: KVM hosts Ubuntu 16.04, XenServer 6.5
Primary Storage: KVM Local Filesystem, NFS, and Ceph
Secondary Storage: NFS
Network: Advanced Network

-- Tests
- build from source
- deploy system VMs
- create VR for the advanced network with Security Group enabled
- create user VMs
- test VM lifecycle (starting, running, stop, stopping, stopped, destroy,
expunging, expunged)
- add secondary IPv6 address to VM
- live migrate VM on local storage (Filesystem/KVM)
- upload, use, and remove template
- verify CloudStack usage service
- assert that Security Groups are being removed from the source host and
added on target host when migrating VMs (tested on XenServer and KVM)

Em sex, 15 de mar de 2019 às 06:25, Wido den Hollander 
escreveu:

> +1 (binding)
>
> Tested:
>
> - Building DEB packages
> - Run on Ubuntu 18.04
> - Tested live storage migration
> - Tested Advanced Networking with VXLAN
> - Tested IPv6 deployment in Advanced Networking
> - Tested destroy and re-create of Virtual Routers
>
> On 3/14/19 10:58 PM, Gabriel Beims Bräscher wrote:
> > Hi All,
> >
> > I've created a 4.12.0.0 release (RC5), with the following artifacts up
> for
> > a vote:
> > The changes since RC4 are listed at the end of this email.
> >
> > Git Branch: 4.12.0.0-RC20190314T1011
> > https://github.com/apache/cloudstack/tree/4.12.0.0-RC20190314T1011
> >
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.12.0.0-RC20190314T1011
> >
> > Commit: a137398bf106028d2fd5344d599fcd2b560d2944
> >
> https://github.com/apache/cloudstack/commit/a137398bf106028d2fd5344d599fcd2b560d2944
> >
> > Source release for 4.12.0.0-RC20190314T1011:
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.12.0.0/
> >
> > PGP release keys (signed using 25908455):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > The vote will be open for 3 business days (until 19th March).
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> indicate
> > "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Additional information:
> >
> > For users' convenience, packages are available in
> > http://cloudstack.apt-get.eu/
> > The 4.12.0.0 RC5 is available for the following distros:
> > - Ubuntu 14.04, 16.04, and 18.04:
> > http://cloudstack.apt-get.eu/ubuntu/dists/trusty/4.12/
> > http://cloudstack.apt-get.eu/ubuntu/dists/xenial/4.12/
> > http://cloudstack.apt-get.eu/ubuntu/dists/bionic/4.12/
> >
> > - CentOS6 and CentOS7:
> > http://cloudstack.apt-get.eu/centos/6/4.12/
> > http://cloudstack.apt-get.eu/centos/7/4.12/
> >
> > Please, use the template 4.11.2 (located in [1]) when testing the RC5.
> > The release notes [2] still need to be updated.
> >
> > Changes Since RC4:
> > Merged #3210 systemd: Fix -Dpid arg passing to systemd usage service [3]
> >
> > [1] http://download.cloudstack.org/systemvm/4.11/
> > [2]
> >
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html
> > [3] https://github.com/apache/cloudstack/pull/3210
> >
>


Re: Any plan for 4.11 LTS extension ?

2019-03-15 Thread Jean-Francois Nadeau
I can only agree with Haijiao,  that 4.11 deserves a longer time span.
Because many bugs are found naturally between the .0 and .1 of the next LTS
release with it's adoption.

For us 4.11 could only be adopted with 4.11.2.0 after several bugs needed
to get resolved.   So if 4.11's support stops in July then it's time span
was only 6 months from our perspective.

-jfn

On Fri, Mar 15, 2019 at 5:34 AM Wido den Hollander  wrote:

>
>
> On 3/15/19 10:20 AM, Riepl, Gregor (SWISS TXT) wrote:
> > Hi Giles,
> >
> >> I would *expect*  4.13.0 (LTS) to be released in Q2, which  will
> >> supersede the 4.11 branch as the current LTS branch
> >
> > Are you confident that this schedule can be kept?
> > 4.12 is still in RC right now, and I don't think it's a good idea to
> > rush another major release in just 3 months...
> >
> 4.11.3 will be released first with some bugfixes to keep 4.11 a proper
> release.
>
> 4.12 needs to go out now so that we can test and prepare for 4.13. I'm
> confident we can have a stable and proper 4.13 release as long as we
> don't keep the window open for too long.
>
> The major problem is having the master branch open for a long time,
> features going in and people not testing it sufficiently.
>
> By having a relatively short period between 4.12 and 4.13 we can catch
> most bugs and stabilize for a proper LTS.
>
> Wido
>


Re: Any plan for 4.11 LTS extension ?

2019-03-15 Thread Wido den Hollander



On 3/15/19 10:20 AM, Riepl, Gregor (SWISS TXT) wrote:
> Hi Giles,
> 
>> I would *expect*  4.13.0 (LTS) to be released in Q2, which  will
>> supersede the 4.11 branch as the current LTS branch
> 
> Are you confident that this schedule can be kept?
> 4.12 is still in RC right now, and I don't think it's a good idea to
> rush another major release in just 3 months...
> 
4.11.3 will be released first with some bugfixes to keep 4.11 a proper
release.

4.12 needs to go out now so that we can test and prepare for 4.13. I'm
confident we can have a stable and proper 4.13 release as long as we
don't keep the window open for too long.

The major problem is having the master branch open for a long time,
features going in and people not testing it sufficiently.

By having a relatively short period between 4.12 and 4.13 we can catch
most bugs and stabilize for a proper LTS.

Wido


Re: [VOTE] Apache CloudStack 4.12.0.0 [RC5]

2019-03-15 Thread Wido den Hollander
+1 (binding)

Tested:

- Building DEB packages
- Run on Ubuntu 18.04
- Tested live storage migration
- Tested Advanced Networking with VXLAN
- Tested IPv6 deployment in Advanced Networking
- Tested destroy and re-create of Virtual Routers

On 3/14/19 10:58 PM, Gabriel Beims Bräscher wrote:
> Hi All,
> 
> I've created a 4.12.0.0 release (RC5), with the following artifacts up for
> a vote:
> The changes since RC4 are listed at the end of this email.
> 
> Git Branch: 4.12.0.0-RC20190314T1011
> https://github.com/apache/cloudstack/tree/4.12.0.0-RC20190314T1011
> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.12.0.0-RC20190314T1011
> 
> Commit: a137398bf106028d2fd5344d599fcd2b560d2944
> https://github.com/apache/cloudstack/commit/a137398bf106028d2fd5344d599fcd2b560d2944
> 
> Source release for 4.12.0.0-RC20190314T1011:
> https://dist.apache.org/repos/dist/dev/cloudstack/4.12.0.0/
> 
> PGP release keys (signed using 25908455):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> The vote will be open for 3 business days (until 19th March).
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Additional information:
> 
> For users' convenience, packages are available in
> http://cloudstack.apt-get.eu/
> The 4.12.0.0 RC5 is available for the following distros:
> - Ubuntu 14.04, 16.04, and 18.04:
> http://cloudstack.apt-get.eu/ubuntu/dists/trusty/4.12/
> http://cloudstack.apt-get.eu/ubuntu/dists/xenial/4.12/
> http://cloudstack.apt-get.eu/ubuntu/dists/bionic/4.12/
> 
> - CentOS6 and CentOS7:
> http://cloudstack.apt-get.eu/centos/6/4.12/
> http://cloudstack.apt-get.eu/centos/7/4.12/
> 
> Please, use the template 4.11.2 (located in [1]) when testing the RC5.
> The release notes [2] still need to be updated.
> 
> Changes Since RC4:
> Merged #3210 systemd: Fix -Dpid arg passing to systemd usage service [3]
> 
> [1] http://download.cloudstack.org/systemvm/4.11/
> [2]
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html
> [3] https://github.com/apache/cloudstack/pull/3210
> 


Re: Any plan for 4.11 LTS extension ?

2019-03-15 Thread Riepl, Gregor (SWISS TXT)
Hi Giles,

> I would *expect*  4.13.0 (LTS) to be released in Q2, which  will
> supersede the 4.11 branch as the current LTS branch

Are you confident that this schedule can be kept?
4.12 is still in RC right now, and I don't think it's a good idea to
rush another major release in just 3 months...