Re: 4.9 api docs went missing

[Özhan Rüzgar Karaman]

its working again, thanks Rohit

On Fri, Jan 6, 2017 at 9:58 AM, Rohit Yadav 
wrote:

> I've fixed it now, please recheck.
>
>
> Regards.
>
> 
> From: ?zhan R?zgar Karaman 
> Sent: 04 January 2017 17:59:10
> To: dev@cloudstack.apache.org
> Subject: Re: 4.9 api docs went missing
>
> Hi;
> I think they are setting up the api page for new CloudStack release, its
> not accessible till this Monday.
>
> Thanks
> ?zhan
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> On Wed, Jan 4, 2017 at 12:42 PM, Linas ?ilinskas  > wrote:
>
> Hello.
>
> Not sure if intentional, but 4.9 api docs at
> https://cloudstack.apache.org/api.html are missing now.
>
> It seems the page got reverted to a previous version.
>
> Linas ?ilinskas
> Head of Development
> [cid:part1.9B217719.D668B006@host1plus.com]
> website facebook com/Host1Plus> twitter linkedin<
> https://www.linkedin.com/company/digital-energy-technologies-ltd.>
>
> Host1Plus is a division of Digital Energy Technologies Ltd.
>
> 26 York Street, London W1U 6PZ, United Kingdom
>
>
>
>

Re:[RESULT][VOTE] Apache Cloudstack 4.9.2.0 (RC2)

[Haijiao]

I am not a developer, but thanks you all for this another great achievement !


Understand how hard to get all the things sorted out.  Just thinking we 
probably need 1-2 assistants to support RM going forward, share the workload 
like documentation, release notes,  PR tracking...


These comparatively less techinical work can be separated and shared which may 
ensure RM to focus on core part of release.


Again, thanks and congratulations !






在2017年01月06 13时03分, "Rohit Yadav"写道:

Hi all,



After 72 hours, the vote for CloudStack 4.9.2.0 *passes* with

4 PMC + 0 non-PMC votes.



+1 (PMC / binding)

4 person (Wido, Bruno, Rajani, Rohit)



+1 (non binding)

none


0

none



-1

none



Thanks to everyone participating.



I will now prepare the release announcement to go out after 24 hours to
give the mirrors time to catch up.

Regards.

Re: 4.9 api docs went missing

[Rohit Yadav]

I've fixed it now, please recheck.


Regards.


From: ?zhan R?zgar Karaman 
Sent: 04 January 2017 17:59:10
To: dev@cloudstack.apache.org
Subject: Re: 4.9 api docs went missing

Hi;
I think they are setting up the api page for new CloudStack release, its not 
accessible till this Monday.

Thanks
?zhan


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

On Wed, Jan 4, 2017 at 12:42 PM, Linas ?ilinskas 
> wrote:

Hello.

Not sure if intentional, but 4.9 api docs at 
https://cloudstack.apache.org/api.html are missing now.

It seems the page got reverted to a previous version.

Linas ?ilinskas
Head of Development
[cid:part1.9B217719.D668B006@host1plus.com]
website facebook 
twitter 
linkedin

Host1Plus is a division of Digital Energy Technologies Ltd.

26 York Street, London W1U 6PZ, United Kingdom

[RESULT][VOTE] Apache Cloudstack 4.9.2.0 (RC2)

[Rohit Yadav]

Hi all,



After 72 hours, the vote for CloudStack 4.9.2.0 *passes* with

4 PMC + 0 non-PMC votes.



+1 (PMC / binding)

4 person (Wido, Bruno, Rajani, Rohit)



+1 (non binding)

none


0

none



-1

none



Thanks to everyone participating.



I will now prepare the release announcement to go out after 24 hours to
give the mirrors time to catch up.

Regards.

[GitHub] cloudstack pull request #1892: CLOUDSTACK-9731: Hardcoded label appears on t...

[sureshanaparti]

GitHub user sureshanaparti opened a pull request:

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

CLOUDSTACK-9731: Hardcoded label appears on the Add zone wizard

Hardcoded label (label.remove.this.physical.network) appears on the Add 
zone wizard

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9731

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1892.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1892






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1891: CLOUDSTACK-9730: [VMware] Unable to add a hos...

[sureshanaparti]

GitHub user sureshanaparti opened a pull request:

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

CLOUDSTACK-9730: [VMware] Unable to add a host with space in its name to 
existing VMware cluster

Issue: Unable to add a host with space in its name to existing VMware 
cluster

Root Cause: Previously cluster url from API used to be inserted into DB 
after validation of inventory url. White spaces in url would be encoded as '+' 
during creation of URI object which are being inserted into database. Further 
references of the cluster's data center name would see '+' symbols instead of 
white space which is incorrect.

Fix: Skip update of encoded cluster url path in cluster_details table while 
adding host to existing cluster.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9730

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1891.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1891


commit 9b5b3aa30a04589be843c66dd8173a2b94a92d4d
Author: Suresh Kumar Anaparti 
Date:   2017-01-05T23:12:14Z

CLOUDSTACK-9730: [VMware] Unable to add a host with space in its name to 
Cluster

Skip update of encoded cluster url path in cluster_details table while 
adding host to existing cluster.
Previously cluster url from API used to be inserted into DB after 
validation of inventory url. White spaces in url would be encoded as '+' during 
creation of URI object which are being inserted into database. Further 
references of the cluster's data center name would see '+' symbols instead of 
white space which is incorrect.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Moving for JDK8, this time for real!

[Erik Weber]

Yes, I understood that your proposal didn't change the debian version, I
suggested that it should do, since when we do update the debian version we
have to test everything over again anyway.

That said, I won't oppose your proposal, I'm +1 of upgrading to jdk 1.8

-- 
Erik


tor. 5. jan. 2017 kl. 15.46 skrev Rohit Yadav :

> Erik,
>
>
>
>
>
> The PR I've proposed does not change the base Debian distro, it's still
> Debian 7 (wheezy) and not Jessie. I would like to avoid making too many
> changes in the same PR, especially moving to Jessie which won't be straight
> forward as it would introduce several changes, major package version
> changes, systemd usage etc.
>
>
>
>
>
> What I'm proposing is simple -- moving to jdk8 for building CloudStack
> (this works flawlessly now), and using jre-8 on systemvm template.
>
>
>
>
>
> Regards.
>
>
>
> 
>
> From: Erik Weber 
>
> Sent: 05 January 2017 18:25:38
>
> To: dev
>
> Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
>
>
>
>
>
> rohit.ya...@shapeblue.com
>
> www.shapeblue.com
>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>
> @shapeblue
>
>
>
>
>
>
>
> On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav 
> wrote:
>
> > All,
>
> >
>
> >
>
> > I've been working on moving our codebase and runtime-environment to Java
> 8, and since this is a much needed big change I want your feedback and
> blessings on:
>
> >
>
> > https://github.com/apache/cloudstack/pull/1888
>
> >
>
> >
>
> > In order for this to work, I had to make changes in our veewee-based
> systemvmtemplate build scripts to install a third party opensource
> openjdk-8-jre distribution (xulu-8 is a openjdk-8 distribution from Azul,
> please review and advise wrt their terms of usage here:
> http://www.azul.com/products/zulu/zulu-terms-of-use/), since
>
> >
>
> > Debian 7 (wheezy) repositories don't have openjdk-8-jre and installing
> openjdk-8-jre from testing/sid updates several system packages such as libc
> that I wanted to avoid. Accepting this change on master/4.10 would require
> us to have a new systemvmtemplate for 4.10+ releases.
>
> >
>
> >
>
> > With these changes, I've ran smoke tests across KVM, VMware and
> XenServer in the following PR and all of the tests are passing (ignoring
> known intermittent failures in vpc/rvr related tests).
>
> >
>
> >
>
> > Thoughts, feedback?
>
>
>
> Wheezy has roughly 1 year left (until May 2018) before it is EOL.
>
> Since 4.10 is not LTS and the fact that both Java8 and Debian Jessie
>
> could have hard to find issues I would suggest that you update the
>
> systemvm now, and work through bugs and quirks throught the 4.10.x
>
> version.
>
> I believe there are other changes, like strongswan, as well that could
>
> make 4.10 a potentially unstable version?
>
>
>
> --
>
> Erik
>
>

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[mike-tutkowski]

Github user mike-tutkowski commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
I walked through the diffs and they LGTM. I did not actually run the code, 
however, because I'm in the middle of another CloudStack project and I don't 
have the resources available at the time being.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Looks good now @rhtyd 

LGTM for the code


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Moving for JDK8, this time for real!

[Wido den Hollander]

> Op 5 januari 2017 om 16:06 schreef Will Stevens :
> 
> 
> I agree with Rohit about not making too many changes at once.  I know we
> both agree that we should be going to Jessie, but let's do it in phases.
> Going to Java 8 is a big enough step for right now, lets stabilize that and
> then we can look at updating the system vm template after.
> 

Ack on that. Keep this PR lean and clean. Change the SSVM afterwards.

Wido

> *Will STEVENS*
> Lead Developer
> 
> 
> 
> On Thu, Jan 5, 2017 at 9:45 AM, Rohit Yadav 
> wrote:
> 
> > Erik,
> >
> >
> > The PR I've proposed does not change the base Debian distro, it's still
> > Debian 7 (wheezy) and not Jessie. I would like to avoid making too many
> > changes in the same PR, especially moving to Jessie which won't be straight
> > forward as it would introduce several changes, major package version
> > changes, systemd usage etc.
> >
> >
> > What I'm proposing is simple -- moving to jdk8 for building CloudStack
> > (this works flawlessly now), and using jre-8 on systemvm template.
> >
> >
> > Regards.
> >
> > 
> > From: Erik Weber 
> > Sent: 05 January 2017 18:25:38
> > To: dev
> > Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
> >
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> > On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav 
> > wrote:
> > > All,
> > >
> > >
> > > I've been working on moving our codebase and runtime-environment to Java
> > 8, and since this is a much needed big change I want your feedback and
> > blessings on:
> > >
> > > https://github.com/apache/cloudstack/pull/1888
> > >
> > >
> > > In order for this to work, I had to make changes in our veewee-based
> > systemvmtemplate build scripts to install a third party opensource
> > openjdk-8-jre distribution (xulu-8 is a openjdk-8 distribution from Azul,
> > please review and advise wrt their terms of usage here:
> > http://www.azul.com/products/zulu/zulu-terms-of-use/), since
> > >
> > > Debian 7 (wheezy) repositories don't have openjdk-8-jre and installing
> > openjdk-8-jre from testing/sid updates several system packages such as libc
> > that I wanted to avoid. Accepting this change on master/4.10 would require
> > us to have a new systemvmtemplate for 4.10+ releases.
> > >
> > >
> > > With these changes, I've ran smoke tests across KVM, VMware and
> > XenServer in the following PR and all of the tests are passing (ignoring
> > known intermittent failures in vpc/rvr related tests).
> > >
> > >
> > > Thoughts, feedback?
> >
> > Wheezy has roughly 1 year left (until May 2018) before it is EOL.
> > Since 4.10 is not LTS and the fact that both Java8 and Debian Jessie
> > could have hard to find issues I would suggest that you update the
> > systemvm now, and work through bugs and quirks throught the 4.10.x
> > version.
> > I believe there are other changes, like strongswan, as well that could
> > make 4.10 a potentially unstable version?
> >
> > --
> > Erik
> >

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Overall the changes look good to me. But can you explain why for example 
you changed the dhcp package name? It doesn't seem related to Java 8.

 All in favor of this switch, just checking why it's in there.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Thanks @wido I've reverted and updated the PR now, you can refresh to see 
the updated changes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
@rhtyd Understood, no problem, just trying to keep the changes in this PR 
clean. All changes should be Java 8 related.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Thanks @wido I'll rever that line, though the dhcp-3 is a virtual package 
that actually install isc-dhcp-client, see 
https://packages.debian.org/wheezy/dhcp3-client


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
All, for transparency this comment has the build log of the new 
systemvmtemplate attached:

[systemvm-buildlog.txt](https://github.com/apache/cloudstack/files/687704/systemvm-buildlog.txt)

The systemvmtemplates for 4.10 (Debian7 based with openjdk-8/zulu-8): 
http://packages.shapeblue.com/systemvmtemplate/custom/4.10-jre8

Notes for above systemvmtemplate:
- Newer openssl/openssh-server updates, along with other security updates
- OpenJDK-8 (zulu-8 distribution as wheezy don't have jre-8 packages yet)
- Bigger /var/log partition
- No major change wrt any other package such as apache2, openswan etc.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Moving for JDK8, this time for real!

[Will Stevens]

I agree with Rohit about not making too many changes at once.  I know we
both agree that we should be going to Jessie, but let's do it in phases.
Going to Java 8 is a big enough step for right now, lets stabilize that and
then we can look at updating the system vm template after.

*Will STEVENS*
Lead Developer



On Thu, Jan 5, 2017 at 9:45 AM, Rohit Yadav 
wrote:

> Erik,
>
>
> The PR I've proposed does not change the base Debian distro, it's still
> Debian 7 (wheezy) and not Jessie. I would like to avoid making too many
> changes in the same PR, especially moving to Jessie which won't be straight
> forward as it would introduce several changes, major package version
> changes, systemd usage etc.
>
>
> What I'm proposing is simple -- moving to jdk8 for building CloudStack
> (this works flawlessly now), and using jre-8 on systemvm template.
>
>
> Regards.
>
> 
> From: Erik Weber 
> Sent: 05 January 2017 18:25:38
> To: dev
> Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav 
> wrote:
> > All,
> >
> >
> > I've been working on moving our codebase and runtime-environment to Java
> 8, and since this is a much needed big change I want your feedback and
> blessings on:
> >
> > https://github.com/apache/cloudstack/pull/1888
> >
> >
> > In order for this to work, I had to make changes in our veewee-based
> systemvmtemplate build scripts to install a third party opensource
> openjdk-8-jre distribution (xulu-8 is a openjdk-8 distribution from Azul,
> please review and advise wrt their terms of usage here:
> http://www.azul.com/products/zulu/zulu-terms-of-use/), since
> >
> > Debian 7 (wheezy) repositories don't have openjdk-8-jre and installing
> openjdk-8-jre from testing/sid updates several system packages such as libc
> that I wanted to avoid. Accepting this change on master/4.10 would require
> us to have a new systemvmtemplate for 4.10+ releases.
> >
> >
> > With these changes, I've ran smoke tests across KVM, VMware and
> XenServer in the following PR and all of the tests are passing (ignoring
> known intermittent failures in vpc/rvr related tests).
> >
> >
> > Thoughts, feedback?
>
> Wheezy has roughly 1 year left (until May 2018) before it is EOL.
> Since 4.10 is not LTS and the fact that both Java8 and Debian Jessie
> could have hard to find issues I would suggest that you update the
> systemvm now, and work through bugs and quirks throught the 4.10.x
> version.
> I believe there are other changes, like strongswan, as well that could
> make 4.10 a potentially unstable version?
>
> --
> Erik
>

Re: [DISCUSS] Moving for JDK8, this time for real!

[Rohit Yadav]

Erik,


The PR I've proposed does not change the base Debian distro, it's still Debian 
7 (wheezy) and not Jessie. I would like to avoid making too many changes in the 
same PR, especially moving to Jessie which won't be straight forward as it 
would introduce several changes, major package version changes, systemd usage 
etc.


What I'm proposing is simple -- moving to jdk8 for building CloudStack (this 
works flawlessly now), and using jre-8 on systemvm template.


Regards.


From: Erik Weber 
Sent: 05 January 2017 18:25:38
To: dev
Subject: Re: [DISCUSS] Moving for JDK8, this time for real!


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

On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav  wrote:
> All,
>
>
> I've been working on moving our codebase and runtime-environment to Java 8, 
> and since this is a much needed big change I want your feedback and blessings 
> on:
>
> https://github.com/apache/cloudstack/pull/1888
>
>
> In order for this to work, I had to make changes in our veewee-based 
> systemvmtemplate build scripts to install a third party opensource 
> openjdk-8-jre distribution (xulu-8 is a openjdk-8 distribution from Azul, 
> please review and advise wrt their terms of usage here: 
> http://www.azul.com/products/zulu/zulu-terms-of-use/), since
>
> Debian 7 (wheezy) repositories don't have openjdk-8-jre and installing 
> openjdk-8-jre from testing/sid updates several system packages such as libc 
> that I wanted to avoid. Accepting this change on master/4.10 would require us 
> to have a new systemvmtemplate for 4.10+ releases.
>
>
> With these changes, I've ran smoke tests across KVM, VMware and XenServer in 
> the following PR and all of the tests are passing (ignoring known 
> intermittent failures in vpc/rvr related tests).
>
>
> Thoughts, feedback?

Wheezy has roughly 1 year left (until May 2018) before it is EOL.
Since 4.10 is not LTS and the fact that both Java8 and Debian Jessie
could have hard to find issues I would suggest that you update the
systemvm now, and work through bugs and quirks throught the 4.10.x
version.
I believe there are other changes, like strongswan, as well that could
make 4.10 a potentially unstable version?

--
Erik

Re: [GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[Sergey Levitskiy]

Code review LGTM

Re: [DISCUSS] Moving for JDK8, this time for real!

[Erik Weber]

On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav  wrote:
> All,
>
>
> I've been working on moving our codebase and runtime-environment to Java 8, 
> and since this is a much needed big change I want your feedback and blessings 
> on:
>
> https://github.com/apache/cloudstack/pull/1888
>
>
> In order for this to work, I had to make changes in our veewee-based 
> systemvmtemplate build scripts to install a third party opensource 
> openjdk-8-jre distribution (xulu-8 is a openjdk-8 distribution from Azul, 
> please review and advise wrt their terms of usage here: 
> http://www.azul.com/products/zulu/zulu-terms-of-use/), since
>
> Debian 7 (wheezy) repositories don't have openjdk-8-jre and installing 
> openjdk-8-jre from testing/sid updates several system packages such as libc 
> that I wanted to avoid. Accepting this change on master/4.10 would require us 
> to have a new systemvmtemplate for 4.10+ releases.
>
>
> With these changes, I've ran smoke tests across KVM, VMware and XenServer in 
> the following PR and all of the tests are passing (ignoring known 
> intermittent failures in vpc/rvr related tests).
>
>
> Thoughts, feedback?

Wheezy has roughly 1 year left (until May 2018) before it is EOL.
Since 4.10 is not LTS and the fact that both Java8 and Debian Jessie
could have hard to find issues I would suggest that you update the
systemvm now, and work through bugs and quirks throught the 4.10.x
version.
I believe there are other changes, like strongswan, as well that could
make 4.10 a potentially unstable version?

-- 
Erik

[DISCUSS] Moving for JDK8, this time for real!

[Rohit Yadav]

All,


I've been working on moving our codebase and runtime-environment to Java 8, and 
since this is a much needed big change I want your feedback and blessings on:

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


In order for this to work, I had to make changes in our veewee-based 
systemvmtemplate build scripts to install a third party opensource 
openjdk-8-jre distribution (xulu-8 is a openjdk-8 distribution from Azul, 
please review and advise wrt their terms of usage here: 
http://www.azul.com/products/zulu/zulu-terms-of-use/), since

Debian 7 (wheezy) repositories don't have openjdk-8-jre and installing 
openjdk-8-jre from testing/sid updates several system packages such as libc 
that I wanted to avoid. Accepting this change on master/4.10 would require us 
to have a new systemvmtemplate for 4.10+ releases.


With these changes, I've ran smoke tests across KVM, VMware and XenServer in 
the following PR and all of the tests are passing (ignoring known intermittent 
failures in vpc/rvr related tests).


Thoughts, feedback?


Regards.

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

[GitHub] cloudstack pull request #1890: FIX issue on preshared key if we disable/enab...

[ustcweizhou]

GitHub user ustcweizhou opened a pull request:

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

FIX issue on preshared key if we disable/enable remote access vpn

Way to reproduce the issue
(1) enable remote access vpn
root@r-8349-VM:~# cat /etc/ipsec.d/ipsec.any.secrets
: PSK "mVSx5KDXCPYX7X5DGb2W8yNW"

(2) disable/enable vpn
root@r-8349-VM:~# cat /etc/ipsec.d/ipsec.any.secrets
: PSK "mVSx5KDXCPYX7X5DGb2W8yNW"
: PSK "HeV3dHZpZXt4chhfvhx8D83C"

Expected configuration:
root@r-8349-VM:~# cat /etc/ipsec.d/ipsec.any.secrets
: PSK "HeV3dHZpZXt4chhfvhx8D83C"

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ustcweizhou/cloudstack vpn-preshared-key-issue

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1890.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1890


commit 16c2cd0244e65238fa1aa7fe85fe2636a2298a7c
Author: Wei Zhou 
Date:   2017-01-05T11:14:13Z

FIX issue on preshared key if we disable/enable remote access vpn

Way to reproduce the issue
(1) enable remote access vpn
root@r-8349-VM:~# cat /etc/ipsec.d/ipsec.any.secrets
: PSK "mVSx5KDXCPYX7X5DGb2W8yNW"

(2) disable/enable vpn
root@r-8349-VM:~# cat /etc/ipsec.d/ipsec.any.secrets
: PSK "mVSx5KDXCPYX7X5DGb2W8yNW"
: PSK "HeV3dHZpZXt4chhfvhx8D83C"

Expected configuration:
root@r-8349-VM:~# cat /etc/ipsec.d/ipsec.any.secrets
: PSK "HeV3dHZpZXt4chhfvhx8D83C"




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1812: CLOUDSTACK-9650: Allow starting VMs regardless of cp...

[koushik-das]

Github user koushik-das commented on the issue:

https://github.com/apache/cloudstack/pull/1812
  
Looks like this is ready for merge. None of the test failures are related 
to this PR.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
code LGTM. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1847: CLOUDSTACK-9691: Fixed unhandeled excetion in list s...

[sateesh-chodapuneedi]

Github user sateesh-chodapuneedi commented on the issue:

https://github.com/apache/cloudstack/pull/1847
  
@karuturi Seems this is ready for merge, with code LGTMs and based on test 
results published by @cloudmonger ?
The 4 test failures seems not relevant to this patch  with code changes in 
API layer.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1847: CLOUDSTACK-9691: Fixed unhandeled excetion in list s...

[cloudmonger]

Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1847
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 204
 Hypervisor xenserver
 NetworkType Advanced
 Passed=101
 Failed=3
 Skipped=7

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**
* test_routers_network_ops.py

 * test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failing since 3 
runs

 * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failing since 
3 runs

 * test_03_RVR_Network_check_router_state Failing since 3 runs


**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Trillian test result (tid-770)
Environment: xenserver-65sp1 (x2), Advanced Networking with Mgmt server 6
Total time taken: 45108 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1888-t770-xenserver-65sp1.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py
Test completed. 47 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_05_rvpc_multi_tiers | `Failure` | 524.67 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | `Failure` | 1346.28 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | `Failure` | 580.45 
| test_vpc_redundant.py
test_04_rvpc_privategw_static_routes | `Failure` | 739.70 | 
test_privategw_acl.py
test_01_vpc_site2site_vpn | Success | 301.98 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 166.76 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 549.39 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 400.91 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 689.38 | test_vpc_router_nics.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 870.51 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 1093.42 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 15.72 | test_volumes.py
test_08_resize_volume | Success | 96.00 | test_volumes.py
test_07_resize_fail | Success | 101.19 | test_volumes.py
test_06_download_detached_volume | Success | 30.43 | test_volumes.py
test_05_detach_volume | Success | 100.32 | test_volumes.py
test_04_delete_attached_volume | Success | 10.23 | test_volumes.py
test_03_download_attached_volume | Success | 15.33 | test_volumes.py
test_02_attach_volume | Success | 10.75 | test_volumes.py
test_01_create_volume | Success | 392.41 | test_volumes.py
test_03_delete_vm_snapshots | Success | 280.27 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 224.50 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 100.85 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 313.33 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.85 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.16 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 136.59 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.09 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 5.12 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 10.18 | test_vm_life_cycle.py
test_02_start_vm | Success | 20.25 | test_vm_life_cycle.py
test_01_stop_vm | Success | 30.35 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 131.12 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 5.21 | test_templates.py
test_03_delete_template | Success | 5.13 | test_templates.py
test_02_edit_template | Success | 90.11 | test_templates.py
test_01_create_template | Success | 80.73 | test_templates.py
test_10_destroy_cpvm | Success | 226.98 | test_ssvm.py
test_09_destroy_ssvm | Success | 203.97 | test_ssvm.py
test_08_reboot_cpvm | Success | 141.54 | test_ssvm.py
test_07_reboot_ssvm | Success | 154.11 | test_ssvm.py
test_06_stop_cpvm | Success | 166.74 | test_ssvm.py
test_05_stop_ssvm | Success | 174.41 | test_ssvm.py
test_04_cpvm_internals | Success | 1.14 | test_ssvm.py
test_03_ssvm_internals | Success | 3.55 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.12 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py
test_01_snapshot_root_disk | Success | 21.67 | test_snapshots.py
test_04_change_offering_small | Success | 129.16 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.18 | test_service_offerings.py
test_01_create_service_offering | Success | 0.12 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.12 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.18 | test_secondary_storage.py
test_01_scale_vm | Success | 5.19 | 

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[abhinandanprateek]

Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
lgtm on code review @rhtyd 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---