Re:Re: next major release

[Haijiao]

Agree, unless we bring in architecture changes and/or significant improvments, 
we should still stay on the 4.1x 


Personally,  i think these features may make ACS really qualified to 5.0


- VR enhancement,  e.g. Vyos
- API 2.0
- Fully redundant VPC  ( it's broken in current version)
- Redesigned UI
- NoVNC console
- Fully redundant VPC
- VM clone
- Create VM in batch


Regards,


在2017年07月10 18时58分, "Rohit Yadav"写道:

It should be 4.11.0.0. Unless we're breaking APIs, I'm not in favour of 5.0.0.0.


- Rohit


From: Rajani Karuturi 
Sent: 10 July 2017 10:39:37
To: dev@cloudstack.apache.org
Subject: next major release

should it be 4.11.0.0 or 5.0.0.0?

~Rajani
http://cloudplatform.accelerite.com/

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
 

Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

[Rohit Yadav]

Hi Sean,


Thanks for sharing.


- Rohit


From: Sean Lair 
Sent: 11 July 2017 03:41:17
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: RE: [DISCUSS] CloudStack 4.9.3.0 (LTS)

Here are three issues we ran into in 4.9.2.0.  We have been running all of 
these fixes for several months without issues.  The code changes are all very 
easy/small, but had a big impact for us.

I'd respectfully suggest they go into 4.9.3.0:

https://github.com/apache/cloudstack/pull/2041 (VR related jobs scheduled and 
run twice on mgmt servers)
https://github.com/apache/cloudstack/pull/2040 (Bug in monitoring of S2S VPNs - 
also exists in 4.10)
https://github.com/apache/cloudstack/pull/1966 (IPSEC VPNs do not work after 
vRouter reboot)

Thanks
Sean

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
Sent: Friday, July 7, 2017 1:14 AM
To: dev@cloudstack.apache.org
Cc: us...@cloudstack.apache.org
Subject: [DISCUSS] CloudStack 4.9.3.0 (LTS)

All,


With 4.10.0.0 voted, I would like to start some initial discussion around the 
next minor LTS release 4.9.3.0. At the moment I don't have a timeline, plans or 
dates to share but I would like to engage with the community to gather list of 
issues, commits, PRs that we should consider for the next LTS release 4.9.3.0.


To reduce our test and QA scope, we don't want to consider changes that are new 
feature, or enhancements but strictly blockers/critical/major bugfixes and 
security related fixes, and we can consider reverting any already 
committed/merged PR(s) on 4.9 branch (committed since 4.9.2.0).


Please go through list of commits since 4.9.2.0 (you can also run, git log 
4.9.2.0..4.9) and let us know if there is any change we should consider 
reverting:

https://github.com/apache/cloudstack/commits/4.9


I started backporting some 
fixes on the 4.9 branch, please go through the following PR and raise 
objections on changes/commits that we should not backport or revert:

https://github.com/apache/cloudstack/pull/2052


Lastly, please also share any PRs that we should consider reviewing+merging on 
4.9 branch for the 4.9.3.0 release effort.


- Rohit

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Rohit Yadav]

PL - yes Trillian has tested with CentOS6 + JDK8 with 4.10.0.0/master+.

JRE/JDK8 are available in additional repositories on CentOS6 so at least for 
4.10.0.0 (already votes, to be announced) we cannot deprecate it. However, we 
can discuss that for 4.11.0.0 and onwards. However, I think unless we're 
breaking major compatibilities such as API, upgrades etc. we should not call 
the next release 5.x.


- Rohit


From: Pierre-Luc Dion 
Sent: 10 July 2017 18:51:33
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10

In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
to provide some instruction on how to install it, and is there anyone that
tested 4.10 packages on CentOS6 ?

Cheers,

On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus 
wrote:

> I would suggest that this would justify a 5.0 release.. might be a good
> time to get in any other major changes
>
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> Sent: 09 July 2017 13:46
> To: dev@cloudstack.apache.org
> Subject: [DISCUSS] drop support for CentOS6 with 4.10
>
> Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> management-server and usage ?
>
> all the Upgrade path tests I've made was by creating new management server
> on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> install well on centos7 and I'm not away somebody test them on centos6.
>
> Should we call a vote on this?  I'm writing the upgrade part of the
> release notes and I would focus on centos7 only. we should also update our
> Quick Install Guide...
>
>
> Thanks,
>
> PL
>

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Will Stevens]

Pierre-Luc is asking because he has been the only person contributing to
the upgrade documentation released with the new releases since around 4.4.

Rohit, would you be able to contribute an upgrade path for CentOS6
installations in the documentation for the 4.10 release?

On Jul 11, 2017 5:59 AM, "Rohit Yadav"  wrote:

> PL - yes Trillian has tested with CentOS6 + JDK8 with 4.10.0.0/master+.
>
> JRE/JDK8 are available in additional repositories on CentOS6 so at least
> for 4.10.0.0 (already votes, to be announced) we cannot deprecate it.
> However, we can discuss that for 4.11.0.0 and onwards. However, I think
> unless we're breaking major compatibilities such as API, upgrades etc. we
> should not call the next release 5.x.
>
>
> - Rohit
>
> 
> From: Pierre-Luc Dion 
> Sent: 10 July 2017 18:51:33
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10
>
> In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
> to provide some instruction on how to install it, and is there anyone that
> tested 4.10 packages on CentOS6 ?
>
> Cheers,
>
> On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus 
> wrote:
>
> > I would suggest that this would justify a 5.0 release.. might be a good
> > time to get in any other major changes
> >
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> > Sent: 09 July 2017 13:46
> > To: dev@cloudstack.apache.org
> > Subject: [DISCUSS] drop support for CentOS6 with 4.10
> >
> > Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> > management-server and usage ?
> >
> > all the Upgrade path tests I've made was by creating new management
> server
> > on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> > install well on centos7 and I'm not away somebody test them on centos6.
> >
> > Should we call a vote on this?  I'm writing the upgrade part of the
> > release notes and I would focus on centos7 only. we should also update
> our
> > Quick Install Guide...
> >
> >
> > Thanks,
> >
> > PL
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Travis failing on PRs

[Rohit Yadav]

All,


Please see:

https://blog.travis-ci.com/2017-06-19-trusty-updates-2017-Q2


OracleJDK7 is no 
longer supported by Travis, switching to oraclejdk7 yields error.

Please help review and merge before 4.10 branch is cut and master is opened 
(officially) for accepting new PRs:

https://github.com/apache/cloudstack/pull/2172



- Rohit

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Rohit Yadav]

Will, I'll be on holidays next week and have tight schedules this month. I'll 
ping Paul if he has bandwidth to contribute them.


- Rohit


From: Will Stevens 
Sent: 11 July 2017 16:41:41
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10

Pierre-Luc is asking because he has been the only person contributing to
the upgrade documentation released with the new releases since around 4.4.

Rohit, would you be able to contribute an upgrade path for CentOS6
installations in the documentation for the 4.10 release?

On Jul 11, 2017 5:59 AM, "Rohit Yadav"  wrote:

> PL - yes Trillian has tested with CentOS6 + JDK8 with 4.10.0.0/master+.
>
> JRE/JDK8 are available in additional repositories on CentOS6 so at least
> for 4.10.0.0 (already votes, to be announced) we cannot deprecate it.
> However, we can discuss that for 4.11.0.0 and onwards. However, I think
> unless we're breaking major compatibilities such as API, upgrades etc. we
> should not call the next release 5.x.
>
>
> - Rohit
>
> 
> From: Pierre-Luc Dion 
> Sent: 10 July 2017 18:51:33
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10
>
> In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
> to provide some instruction on how to install it, and is there anyone that
> tested 4.10 packages on CentOS6 ?
>
> Cheers,
>
> On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus 
> wrote:
>
> > I would suggest that this would justify a 5.0 release.. might be a good
> > time to get in any other major changes
> >
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> > Sent: 09 July 2017 13:46
> > To: dev@cloudstack.apache.org
> > Subject: [DISCUSS] drop support for CentOS6 with 4.10
> >
> > Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> > management-server and usage ?
> >
> > all the Upgrade path tests I've made was by creating new management
> server
> > on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> > install well on centos7 and I'm not away somebody test them on centos6.
> >
> > Should we call a vote on this?  I'm writing the upgrade part of the
> > release notes and I would focus on centos7 only. we should also update
> our
> > Quick Install Guide...
> >
> >
> > Thanks,
> >
> > PL
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [DISCUSS] drop support for CentOS6 with 4.10

[Will Stevens]

Can you link the appropriate config files so we can review the
configuration?  Thanks...



On Jul 11, 2017 8:05 AM, "Rohit Yadav"  wrote:

Will, I'll be on holidays next week and have tight schedules this month.
I'll ping Paul if he has bandwidth to contribute them.


- Rohit


From: Will Stevens 
Sent: 11 July 2017 16:41:41
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10

Pierre-Luc is asking because he has been the only person contributing to
the upgrade documentation released with the new releases since around 4.4.

Rohit, would you be able to contribute an upgrade path for CentOS6
installations in the documentation for the 4.10 release?

On Jul 11, 2017 5:59 AM, "Rohit Yadav"  wrote:

> PL - yes Trillian has tested with CentOS6 + JDK8 with 4.10.0.0/master+.
>
> JRE/JDK8 are available in additional repositories on CentOS6 so at least
> for 4.10.0.0 (already votes, to be announced) we cannot deprecate it.
> However, we can discuss that for 4.11.0.0 and onwards. However, I think
> unless we're breaking major compatibilities such as API, upgrades etc. we
> should not call the next release 5.x.
>
>
> - Rohit
>
> 
> From: Pierre-Luc Dion 
> Sent: 10 July 2017 18:51:33
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] drop support for CentOS6 with 4.10
>
> In this case, if we say 4.10.0.0 can be install on centos6 it mean we need
> to provide some instruction on how to install it, and is there anyone that
> tested 4.10 packages on CentOS6 ?
>
> Cheers,
>
> On Mon, Jul 10, 2017 at 3:03 AM, Paul Angus 
> wrote:
>
> > I would suggest that this would justify a 5.0 release.. might be a good
> > time to get in any other major changes
> >
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pdion...@apache.org]
> > Sent: 09 July 2017 13:46
> > To: dev@cloudstack.apache.org
> > Subject: [DISCUSS] drop support for CentOS6 with 4.10
> >
> > Since 4.10 require JDK8, should we drop support for CentOS 6 as OS for
> > management-server and usage ?
> >
> > all the Upgrade path tests I've made was by creating new management
> server
> > on CentOS 7 that have updated tomcat and openJDK 8.  our packages (RPMs)
> > install well on centos7 and I'm not away somebody test them on centos6.
> >
> > Should we call a vote on this?  I'm writing the upgrade part of the
> > release notes and I would focus on centos7 only. we should also update
> our
> > Quick Install Guide...
> >
> >
> > Thanks,
> >
> > PL
> >
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

RE: [NOTICE] Meeting with Accelerite Leadership

[Giles Sirett]

Ilya, all
Good initiative- thanks to you & John for taking the lead on it and thanks 
to the  Accelrite folks for some of the offers that theyr'e making here


Only a couple questions from me: the concept of the proposed call sounds like a 
general effort/alignment thing - almost like a project scrum  - am I correct ? 
I think this is a really good idea (you may want to ping Wido because he was 
trying to arrange something similar a while ago)

If so, then how do 2-10 progress ? They are a wide ranging set of initiatives 
(and personally  I think most of them are really good initiatives)  - I think 
lumping them all together would be overwhelming . They’ve each got their merits 
and would each require different people to drive forward. 

Kind regards
Giles

giles.sir...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: ilya musayev [mailto:ilya.mailing.li...@gmail.com] 
Sent: 11 July 2017 03:20
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [NOTICE] Meeting with Accelerite Leadership

Dear CloudStackers,

Last week, Johh Kinsella and myself were suppose to meet with Accelerite 
leadership team. Unfortunately John could not make it - so i was alone.

We discussed ways we can improve community collaboration and leverage 
Accelerite"s resources to align and drive larger community agenda including 
extendes roadmap.

Many topics have been mentioned, below is the summary of our discussion. I will 
list things in the order i see being important.


---
1) Proposal was made to have a quarterly call (or more often as needed) with 
all interested parties to discuss:
Upcoming Features you are working on developing (to avoid collision and 
maintain the roadmap)
Blockers that are impacting release and adoption
Other topics

The length of the call would be 90 minutes. Each party will get a fair 
amount of time. The agenda will be collated and presented prior to the call 
with a link to FS on Confluence and time allotted for each topic.

Minutes will be taken and posted on dev list. If there are issues and or 
suggestions, we will note it down in few sentences, identify interested parties 
and have them do a "post" discussion on the mailing list.

The proposed date and time  - Thursday August 17th 9AM PT



--
2) Accelerite is considering funding a position for a person who will be 
working within community - as community manager. Help organize and facilitate 
discussions, make sure Confluence and JIRA are up to date, help new users with 
answering basic questions or finding right individual to assist with solution. 
While funded by Accelerite - it must be clear that the person is working 
with/for Apache CloudStack project.


3) Marketing was mentioned, i suggested we do more press releases - and 
possibly make use of interns

4) OpenStack VS CloudStack (unbiased technology comparison), there is a common 
question - we need to come up something that can help justify Apache CloudStack 
to clients leadership

5) Cinder integration with Cloudstack was mentioned - but no solid plans yet.

6) Creating Appliances of CloudStack - that are ready to be consumed and user 
can spin nested VMs to try CloudStack effortlessly

7) CoudStack Template Repository (plugin)- there is a code written for it by 
Citrix and resides on ASF git - but for some reason it was dropped or never 
completed. If we can give user a rich marketplace of appliances to consume - we 
will certainly get a good edge. This can improve the adoption.

8) MeetUps - we need to re-kickstart this initiative within SF Bay Area and 
stream it to other locations/meetups.

9) Demo environment of CloudStack.  David mentioned Citrix donated gear is in 
one of ASF locations - but sitting idle. I proposed we make use of it and let 
new CloudStack explorers try it out - without the hassle of deploying it.

10) If we can get CloudStack into EPEL fedora and ubuntu upstream repositories 
- it will help with adoption as well.

Please let me know if you would be interested in item #1, which is quarterly 
meeting. The proposed time is 9am PST, August 17th.

I will help setting up the first few initial calls and be a moderator.

Looking forward to your comments

Regards
ilya

[DISCUSS] upgrade to 4.11

[Daan Hoogland]

Devs,

I am busy creating the skeleton upgrade code for our next version (working name 
4.11). Are we still supporting all direct upgrades from 2.x onward or should we 
only assume upgrade paths from 4.y onwards?

Tnx,

daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [DISCUSS] upgrade to 4.11

[Will Stevens]

Not sure I have an answer for that.  Are you creating a PR to this set of
documentation or where are you working?
https://github.com/apache/cloudstack-docs-rn/tree/master/source/upgrade

*Will Stevens*
CTO



On Tue, Jul 11, 2017 at 9:15 AM, Daan Hoogland 
wrote:

> Devs,
>
> I am busy creating the skeleton upgrade code for our next version (working
> name 4.11). Are we still supporting all direct upgrades from 2.x onward or
> should we only assume upgrade paths from 4.y onwards?
>
> Tnx,
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] upgrade to 4.11

[Daan Hoogland]

No I am creating the upgrade code for the next version. (schema-41000to41100 
and upgrade java class)

On 11/07/17 15:29, "williamstev...@gmail.com on behalf of Will Stevens" 
 wrote:

Not sure I have an answer for that.  Are you creating a PR to this set of
documentation or where are you working?
https://github.com/apache/cloudstack-docs-rn/tree/master/source/upgrade

*Will Stevens*
CTO



On Tue, Jul 11, 2017 at 9:15 AM, Daan Hoogland 
wrote:

> Devs,
>
> I am busy creating the skeleton upgrade code for our next version (working
> name 4.11). Are we still supporting all direct upgrades from 2.x onward or
> should we only assume upgrade paths from 4.y onwards?
>
> Tnx,
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: [DISCUSS] upgrade to 4.11

[Will Stevens]

Oh ok.  DB upgrade, not a new skeleton for the upgrade path between version
(hypervisors, etc...).

My bad.  :)

*Will Stevens*
CTO



On Tue, Jul 11, 2017 at 9:41 AM, Daan Hoogland 
wrote:

> No I am creating the upgrade code for the next version.
> (schema-41000to41100 and upgrade java class)
>
> On 11/07/17 15:29, "williamstev...@gmail.com on behalf of Will Stevens" <
> williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
>
> Not sure I have an answer for that.  Are you creating a PR to this set
> of
> documentation or where are you working?
> https://github.com/apache/cloudstack-docs-rn/tree/
> master/source/upgrade
>
> *Will Stevens*
> CTO
>
> 
>
> On Tue, Jul 11, 2017 at 9:15 AM, Daan Hoogland <
> daan.hoogl...@shapeblue.com>
> wrote:
>
> > Devs,
> >
> > I am busy creating the skeleton upgrade code for our next version
> (working
> > name 4.11). Are we still supporting all direct upgrades from 2.x
> onward or
> > should we only assume upgrade paths from 4.y onwards?
> >
> > Tnx,
> >
> > daan.hoogl...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>
>
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: [DISCUSS] upgrade to 4.11

[Daan Hoogland]

of which the heart is full, the mouth spilled ... (free from ancient
dutch saying ;)

On Tue, Jul 11, 2017 at 3:56 PM, Will Stevens  wrote:
> Oh ok.  DB upgrade, not a new skeleton for the upgrade path between version
> (hypervisors, etc...).
>
> My bad.  :)
>
> *Will Stevens*
> CTO
>
> 
>
> On Tue, Jul 11, 2017 at 9:41 AM, Daan Hoogland 
> wrote:
>
>> No I am creating the upgrade code for the next version.
>> (schema-41000to41100 and upgrade java class)
>>
>> On 11/07/17 15:29, "williamstev...@gmail.com on behalf of Will Stevens" <
>> williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
>>
>> Not sure I have an answer for that.  Are you creating a PR to this set
>> of
>> documentation or where are you working?
>> https://github.com/apache/cloudstack-docs-rn/tree/
>> master/source/upgrade
>>
>> *Will Stevens*
>> CTO
>>
>> 
>>
>> On Tue, Jul 11, 2017 at 9:15 AM, Daan Hoogland <
>> daan.hoogl...@shapeblue.com>
>> wrote:
>>
>> > Devs,
>> >
>> > I am busy creating the skeleton upgrade code for our next version
>> (working
>> > name 4.11). Are we still supporting all direct upgrades from 2.x
>> onward or
>> > should we only assume upgrade paths from 4.y onwards?
>> >
>> > Tnx,
>> >
>> > daan.hoogl...@shapeblue.com
>> > www.shapeblue.com
>> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> > @shapeblue
>> >
>> >
>> >
>> >
>>
>>
>>
>> daan.hoogl...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>>



-- 
Daan

Re: next major release

[Wido den Hollander]

I would say 4.11

5.0 should have major changes (like mentioned), API changes or other big 
things. It should have 'killer features'. New GUI, New API, etc. That kind of 
things.

Wido

> Op 10 juli 2017 om 7:09 schreef Rajani Karuturi :
> 
> 
> should it be 4.11.0.0 or 5.0.0.0?
> 
> ~Rajani
> http://cloudplatform.accelerite.com/

Re: [DISCUSS] CloudStack 4.9.3.0 (LTS)

[Wido den Hollander]

Hi,

I would suggest: https://github.com/apache/cloudstack/pull/2131

Serious issue with Ubuntu 16.04 and statistics gathering on KVM.

Wido

> Op 11 juli 2017 om 11:49 schreef Rohit Yadav :
> 
> 
> Hi Sean,
> 
> 
> Thanks for sharing.
> 
> 
> - Rohit
> 
> 
> From: Sean Lair 
> Sent: 11 July 2017 03:41:17
> To: dev@cloudstack.apache.org
> Cc: us...@cloudstack.apache.org
> Subject: RE: [DISCUSS] CloudStack 4.9.3.0 (LTS)
> 
> Here are three issues we ran into in 4.9.2.0.  We have been running all of 
> these fixes for several months without issues.  The code changes are all very 
> easy/small, but had a big impact for us.
> 
> I'd respectfully suggest they go into 4.9.3.0:
> 
> https://github.com/apache/cloudstack/pull/2041 (VR related jobs scheduled and 
> run twice on mgmt servers)
> https://github.com/apache/cloudstack/pull/2040 (Bug in monitoring of S2S VPNs 
> - also exists in 4.10)
> https://github.com/apache/cloudstack/pull/1966 (IPSEC VPNs do not work after 
> vRouter reboot)
> 
> Thanks
> Sean
> 
> rohit.ya...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>   
>  
> 
> 
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Friday, July 7, 2017 1:14 AM
> To: dev@cloudstack.apache.org
> Cc: us...@cloudstack.apache.org
> Subject: [DISCUSS] CloudStack 4.9.3.0 (LTS)
> 
> All,
> 
> 
> With 4.10.0.0 voted, I would like to start some initial discussion around the 
> next minor LTS release 4.9.3.0. At the moment I don't have a timeline, plans 
> or dates to share but I would like to engage with the community to gather 
> list of issues, commits, PRs that we should consider for the next LTS release 
> 4.9.3.0.
> 
> 
> To reduce our test and QA scope, we don't want to consider changes that are 
> new feature, or enhancements but strictly blockers/critical/major bugfixes 
> and security related fixes, and we can consider reverting any already 
> committed/merged PR(s) on 4.9 branch (committed since 4.9.2.0).
> 
> 
> Please go through list of commits since 4.9.2.0 (you can also run, git log 
> 4.9.2.0..4.9) and let us know if there is any change we should consider 
> reverting:
> 
> https://github.com/apache/cloudstack/commits/4.9
> 
> 
> I started backporting some 
> fixes on the 4.9 branch, please go through the following PR and raise 
> objections on changes/commits that we should not backport or revert:
> 
> https://github.com/apache/cloudstack/pull/2052
> 
> 
> Lastly, please also share any PRs that we should consider reviewing+merging 
> on 4.9 branch for the 4.9.3.0 release effort.
> 
> 
> - Rohit
> 
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> 
> 
>

RE: [NOTICE] Meeting with Accelerite Leadership

[Wido den Hollander]

> Op 11 juli 2017 om 15:06 schreef Giles Sirett :
> 
> 
> Ilya, all
> Good initiative- thanks to you & John for taking the lead on it and 
> thanks to the  Accelrite folks for some of the offers that theyr'e making here
> 

Indeed! Sounds very good.

> 
> Only a couple questions from me: the concept of the proposed call sounds like 
> a general effort/alignment thing - almost like a project scrum  - am I 
> correct ? I think this is a really good idea (you may want to ping Wido 
> because he was trying to arrange something similar a while ago)
> 

Yes, I did. Still seems like a good idea and this will probably broaden the 
support for it.

> If so, then how do 2-10 progress ? They are a wide ranging set of initiatives 
> (and personally  I think most of them are really good initiatives)  - I think 
> lumping them all together would be overwhelming . They’ve each got their 
> merits and would each require different people to drive forward. 
> 
> Kind regards
> Giles
> 
> giles.sir...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>   
>  
> 
> 
> -Original Message-
> From: ilya musayev [mailto:ilya.mailing.li...@gmail.com] 
> Sent: 11 July 2017 03:20
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: [NOTICE] Meeting with Accelerite Leadership
> 
> Dear CloudStackers,
> 
> Last week, Johh Kinsella and myself were suppose to meet with Accelerite 
> leadership team. Unfortunately John could not make it - so i was alone.
> 
> We discussed ways we can improve community collaboration and leverage 
> Accelerite"s resources to align and drive larger community agenda including 
> extendes roadmap.
> 
> Many topics have been mentioned, below is the summary of our discussion. I 
> will list things in the order i see being important.
> 
> 
> ---
> 1) Proposal was made to have a quarterly call (or more often as needed) with 
> all interested parties to discuss:
> Upcoming Features you are working on developing (to avoid collision 
> and maintain the roadmap)
> Blockers that are impacting release and adoption
> Other topics
> 
> The length of the call would be 90 minutes. Each party will get a 
> fair amount of time. The agenda will be collated and presented prior to the 
> call with a link to FS on Confluence and time allotted for each topic.
> 
> Minutes will be taken and posted on dev list. If there are issues and or 
> suggestions, we will note it down in few sentences, identify interested 
> parties and have them do a "post" discussion on the mailing list.
> 
> The proposed date and time  - Thursday August 17th 9AM PT
> 
> 
> 
> --
> 2) Accelerite is considering funding a position for a person who will be 
> working within community - as community manager. Help organize and facilitate 
> discussions, make sure Confluence and JIRA are up to date, help new users 
> with answering basic questions or finding right individual to assist with 
> solution. While funded by Accelerite - it must be clear that the person is 
> working with/for Apache CloudStack project.
> 
> 
> 3) Marketing was mentioned, i suggested we do more press releases - and 
> possibly make use of interns
> 
> 4) OpenStack VS CloudStack (unbiased technology comparison), there is a 
> common question - we need to come up something that can help justify Apache 
> CloudStack to clients leadership
> 
> 5) Cinder integration with Cloudstack was mentioned - but no solid plans yet.
> 
> 6) Creating Appliances of CloudStack - that are ready to be consumed and user 
> can spin nested VMs to try CloudStack effortlessly
> 
> 7) CoudStack Template Repository (plugin)- there is a code written for it by 
> Citrix and resides on ASF git - but for some reason it was dropped or never 
> completed. If we can give user a rich marketplace of appliances to consume - 
> we will certainly get a good edge. This can improve the adoption.
> 
> 8) MeetUps - we need to re-kickstart this initiative within SF Bay Area and 
> stream it to other locations/meetups.
> 
> 9) Demo environment of CloudStack.  David mentioned Citrix donated gear is in 
> one of ASF locations - but sitting idle. I proposed we make use of it and let 
> new CloudStack explorers try it out - without the hassle of deploying it.
> 
> 10) If we can get CloudStack into EPEL fedora and ubuntu upstream 
> repositories - it will help with adoption as well.
> 
> Please let me know if you would be interested in item #1, which is quarterly 
> meeting. The proposed time is 9am PST, August 17th.
> 
> I will help setting up the first few initial calls and be a moderator.
> 
> Looking forward to your comments
> 
> Regards
> ilya

Re: Developer Guide - Current Setup Guide?

[Will Stevens]

So this is the guide I always used to follow.  I think it is very outdated
as well:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack

I feel like both of these guides are pretty limited because it does not
cover an integration with any hypervisor, so you may be able to build ACS,
but you won't be able to do any real dev since you won't be able to spin
new VMs or anything like that.

The latest thing I have done for putting together a setup similar to this,
is documented here: https://github.com/swill/apachecon2016

Here are the slides:
https://github.com/swill/apachecon2016/blob/master/slides.pdf

This is not ideal either, but if you are troubleshooting the installation
process, it may help shed some light on the topic.

Also, a good resource for the setup is here as well:
https://github.com/apache/cloudstack/blob/master/.travis.yml

Not sure any of this helps...



*Will Stevens*
CTO



On Mon, Jul 10, 2017 at 4:43 PM, Alex Hitchins 
wrote:

> Great - the setup guide I'm following is : https://cwiki.apache.org/
> confluence/display/CLOUDSTACK/Setting+up+CloudStack+
> Development+Environment+on+Linux
>
> I have got a pull request open for the git repo readme, however it's
> breaking the build (somehow!). That is this one :
> https://github.com/apache/cloudstack/pull/2170
>
>
>
>
> Alexander Hitchins
> 
> E: a...@alexhitchins.com
> W: alexhitchins.com
> M: 07788 423 969
> T: 01892 523 587
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 10 July 2017 21:30
> To: dev@cloudstack.apache.org
> Subject: RE: Developer Guide - Current Setup Guide?
>
> Perfect. I will review that set of docs after I finish the one I am
> working on and we will go from there.
>
> Can you link the doc you are referencing?
>
> On Jul 10, 2017 4:21 PM, "Alex Hitchins"  wrote:
>
> > Thanks Will, very kind of you.
> >
> > I will try and get as far along as I can and keep notes of things I
> > notice along the way.
> >
> > Alexander Hitchins
> > 
> > E: a...@alexhitchins.com
> > W: alexhitchins.com
> > M: 07788 423 969
> > T: 01892 523 587
> >
> > -Original Message-
> > From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> > Behalf Of Will Stevens
> > Sent: 10 July 2017 20:49
> > To: dev@cloudstack.apache.org
> > Subject: Re: Developer Guide - Current Setup Guide?
> >
> > Alex, I have been slowly started getting through some of the
> > documentation that is out of date and will be adding some PRs with
> > changes.  I have not looked at that specific guide yet, so I will have
> > to review that one to be any help.  I will see what I can do to help
> > this week.  You can ping me directly if you have specific questions
> > and I will try to help.  Or ask on https://apachecloudstack.slack.com/
> > and get more real time support from more of us.
> >
> > *Will Stevens*
> > CTO
> >
> > 
> >
> > On Mon, Jul 10, 2017 at 1:58 PM, Alex Hitchins 
> > wrote:
> >
> > > This sounds like it isn't needed currently, correct?
> > >
> > > I will see if I can locate my confluence credentials, sure I had
> > > these circa 2013!
> > >
> > > Do I assume the broader answer to my question is that this is the
> > > most up to date resource? I see another person ask noob question so
> > > wondered if I had missed something.
> > >
> > > If anyone with cloudstack chops has a spare 10 minutes to look over
> > > the current guide with me I'd be more than happy to work the changes
> > > back in to the wiki. I'll even hand over all rights to Apache.
> > >
> > > > On 10 Jul 2017, at 18:29, Ron Wheeler
> > > > 
> > > wrote:
> > > >
> > > > You may want to own the wiki content as well as the software.
> > > >
> > > > A company may want to quote the wiki or incorporate some of it
> > > > into
> > > their documentation without having to get the rights from each
> > > person who contributed to the page.
> > > >
> > > >
> > > > Even more complicated if someone posts a design or an enhancement
> > > > and
> > > then claims to own it and patent it.
> > > >
> > > > It is good practice to make sure that Apache owns it all (code,
> > > > docs,
> > > test cases, enhancements, patches)  and that you can use it all
> > > without legal problems under the Apache license.
> > > >
> > > >
> > > > Ron
> > > >
> > > >> On 10/07/2017 12:23 PM, Daan Hoogland wrote:
> > > >> Why do you say that Ron? You need one to become a committer. for
> > > >> the wiki we need to recognise you as a contributor. I think you
> > > >> need no more.
> > > >>
> > > >> On Mon, Jul 10, 2017 at 5:10 PM, Ron Wheeler
> > > >>  wrote:
> > > >>> Alex,
> > > >>> Do you have a CLA on file with Apache.
> > > >>> You should have one to contribute to the wiki.
> > > >>>
> > > >>> Ron
> > > >>>
> > >  On 10/07/2017 10:42 AM, Daan Hoogland wrote:
> > >  create your account on cwiki and we can give you access
> > > 
> > > 

Usage Server in Docker Simulator

[John McDonnell]

Hi,

I asked this back in April on the Users mailing list and the response
I got was that the usage server should be on by default in the docker
container.  I got sidetracked by other things and am coming back to
this issue.

Is it meant to be running by default? or is there something needed to
do to turn it on in the container?  (wasn't sure if this is a defect,
so thought I'd ask here.)


I use the container as a development tool(to avoid using a real life
system) to test the API out and usage collection is a major part of
what I use the API for.


Steps to reproduce:

(Have docker installed)
$ docker pull cloudstack/simulator
$ docker run --name cloudstack -d -p 8080:8080 cloudstack/simulator
$ docker exec -ti cloudstack python \
/root/tools/marvin/marvin/deployDataCenter.py -i /root/setup/dev/advanced.cfg

After a while login to the UI: localhost:8080/client (admin:password)

And usually, after a while, there will be a General Alert saying there
is no Usage Server running.  Even before this message, if I add an
instance, and attempt to collection usage with the API, I don't get
anything back.

Any help?

Re: Developer Guide - Current Setup Guide?

[Alex Hitchins]

Thanks Will, looks good.

My searching brought up many older guides, one was Ian Duffys blog. These look 
a better base to start from.

AH

> On 11 Jul 2017, at 22:06, Will Stevens  wrote:
> 
> So this is the guide I always used to follow.  I think it is very outdated
> as well:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack
> 
> I feel like both of these guides are pretty limited because it does not
> cover an integration with any hypervisor, so you may be able to build ACS,
> but you won't be able to do any real dev since you won't be able to spin
> new VMs or anything like that.
> 
> The latest thing I have done for putting together a setup similar to this,
> is documented here: https://github.com/swill/apachecon2016
> 
> Here are the slides:
> https://github.com/swill/apachecon2016/blob/master/slides.pdf
> 
> This is not ideal either, but if you are troubleshooting the installation
> process, it may help shed some light on the topic.
> 
> Also, a good resource for the setup is here as well:
> https://github.com/apache/cloudstack/blob/master/.travis.yml
> 
> Not sure any of this helps...
> 
> 
> 
> *Will Stevens*
> CTO
> 
> 
> 
> On Mon, Jul 10, 2017 at 4:43 PM, Alex Hitchins 
> wrote:
> 
>> Great - the setup guide I'm following is : https://cwiki.apache.org/
>> confluence/display/CLOUDSTACK/Setting+up+CloudStack+
>> Development+Environment+on+Linux
>> 
>> I have got a pull request open for the git repo readme, however it's
>> breaking the build (somehow!). That is this one :
>> https://github.com/apache/cloudstack/pull/2170
>> 
>> 
>> 
>> 
>> Alexander Hitchins
>> 
>> E: a...@alexhitchins.com
>> W: alexhitchins.com
>> M: 07788 423 969
>> T: 01892 523 587
>> 
>> -Original Message-
>> From: Will Stevens [mailto:williamstev...@gmail.com]
>> Sent: 10 July 2017 21:30
>> To: dev@cloudstack.apache.org
>> Subject: RE: Developer Guide - Current Setup Guide?
>> 
>> Perfect. I will review that set of docs after I finish the one I am
>> working on and we will go from there.
>> 
>> Can you link the doc you are referencing?
>> 
>>> On Jul 10, 2017 4:21 PM, "Alex Hitchins"  wrote:
>>> 
>>> Thanks Will, very kind of you.
>>> 
>>> I will try and get as far along as I can and keep notes of things I
>>> notice along the way.
>>> 
>>> Alexander Hitchins
>>> 
>>> E: a...@alexhitchins.com
>>> W: alexhitchins.com
>>> M: 07788 423 969
>>> T: 01892 523 587
>>> 
>>> -Original Message-
>>> From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
>>> Behalf Of Will Stevens
>>> Sent: 10 July 2017 20:49
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: Developer Guide - Current Setup Guide?
>>> 
>>> Alex, I have been slowly started getting through some of the
>>> documentation that is out of date and will be adding some PRs with
>>> changes.  I have not looked at that specific guide yet, so I will have
>>> to review that one to be any help.  I will see what I can do to help
>>> this week.  You can ping me directly if you have specific questions
>>> and I will try to help.  Or ask on https://apachecloudstack.slack.com/
>>> and get more real time support from more of us.
>>> 
>>> *Will Stevens*
>>> CTO
>>> 
>>> 
>>> 
>>> On Mon, Jul 10, 2017 at 1:58 PM, Alex Hitchins 
>>> wrote:
>>> 
 This sounds like it isn't needed currently, correct?
 
 I will see if I can locate my confluence credentials, sure I had
 these circa 2013!
 
 Do I assume the broader answer to my question is that this is the
 most up to date resource? I see another person ask noob question so
 wondered if I had missed something.
 
 If anyone with cloudstack chops has a spare 10 minutes to look over
 the current guide with me I'd be more than happy to work the changes
 back in to the wiki. I'll even hand over all rights to Apache.
 
> On 10 Jul 2017, at 18:29, Ron Wheeler
> 
 wrote:
> 
> You may want to own the wiki content as well as the software.
> 
> A company may want to quote the wiki or incorporate some of it
> into
 their documentation without having to get the rights from each
 person who contributed to the page.
> 
> 
> Even more complicated if someone posts a design or an enhancement
> and
 then claims to own it and patent it.
> 
> It is good practice to make sure that Apache owns it all (code,
> docs,
 test cases, enhancements, patches)  and that you can use it all
 without legal problems under the Apache license.
> 
> 
> Ron
> 
>> On 10/07/2017 12:23 PM, Daan Hoogland wrote:
>> Why do you say that Ron? You need one to become a committer. for
>> the wiki we need to recognise you as a contributor. I think you
>> need no more.
>> 
>> On Mon, Jul 10, 2017 at 5:10 PM, Ron Wheeler
>>  wrote:
>>> Alex,
>>> Do you have a CLA on file

[4.10] repos

[Pierre-Luc Dion]

Hi,

I've created new jenkins jobs [1] to create package for our release, The
jobs pushed rpm's but for systemvm, look like there is a wget job somewhere
that download systemvm template from jenkins from build of master branch,
I've created a set of systemvm templates that I would like to published on
download.cloudstack.org but they are most likely going to be overwritten,
could we disable that job ?

[1] https://builds.cloudstack.org/view/release/

PL

Re: [4.10] repos

[Daan Hoogland]

Monsieur,

The job should be altered to go into 4.11. lemme look.

On 12/07/17 02:06, "Pierre-Luc Dion"  wrote:

Hi,

I've created new jenkins jobs [1] to create package for our release, The
jobs pushed rpm's but for systemvm, look like there is a wget job somewhere
that download systemvm template from jenkins from build of master branch,
I've created a set of systemvm templates that I would like to published on
download.cloudstack.org but they are most likely going to be overwritten,
could we disable that job ?

[1] https://builds.cloudstack.org/view/release/

PL



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: Usage Server in Docker Simulator

[Erik Weber]

Are you running the usage server?

It is a different service and run independently of the mgmt server

-- 
Erik

ons. 12. jul. 2017 kl. 00.25 skrev John McDonnell :

> Hi,
>
> I asked this back in April on the Users mailing list and the response
> I got was that the usage server should be on by default in the docker
> container.  I got sidetracked by other things and am coming back to
> this issue.
>
> Is it meant to be running by default? or is there something needed to
> do to turn it on in the container?  (wasn't sure if this is a defect,
> so thought I'd ask here.)
>
>
> I use the container as a development tool(to avoid using a real life
> system) to test the API out and usage collection is a major part of
> what I use the API for.
>
>
> Steps to reproduce:
>
> (Have docker installed)
> $ docker pull cloudstack/simulator
> $ docker run --name cloudstack -d -p 8080:8080 cloudstack/simulator
> $ docker exec -ti cloudstack python \
> /root/tools/marvin/marvin/deployDataCenter.py -i
> /root/setup/dev/advanced.cfg
>
> After a while login to the UI: localhost:8080/client (admin:password)
>
> And usually, after a while, there will be a General Alert saying there
> is no Usage Server running.  Even before this message, if I add an
> instance, and attempt to collection usage with the API, I don't get
> anything back.
>
> Any help?
>

Re: next major release

[Rajani Karuturi]

I made the pom changes on master to 4.11.0.0-SNAPSHOT

4.10 branch is created

master and 4.10 can now accept changes once the upgrade paths are
in place.

Release notes and release announcement are the pending items now.

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On July 12, 2017 at 1:23 AM, Wido den Hollander (w...@widodh.nl)
wrote:

I would say 4.11

5.0 should have major changes (like mentioned), API changes or
other big things. It should have 'killer features'. New GUI, New
API, etc. That kind of things.

Wido

Op 10 juli 2017 om 7:09 schreef Rajani Karuturi
:

should it be 4.11.0.0 or 5.0.0.0?

~Rajani
http://cloudplatform.accelerite.com/