You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Rohit Yadav <ro...@shapeblue.com> on 2017/01/05 12:11:17 UTC

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

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.yadav@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


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

Posted by Rohit Yadav <ro...@shapeblue.com>.
Thank you all, the PR has been merged now.


As a note, developers please setup Jenv in your environment and make sure to install/setup both JDK7 and JDK8 to help you work on master and 4.9/previous branches:

http://www.jenv.be/


No additional build changes are required.


For deploying and testing CloudStack from master, a new systemvmtemplate will be required. Please see for urls:

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.10/upgrade/upgrade-4.9.html#update-system-vm-templates


Regards.

________________________________
From: Rohit Yadav <ro...@shapeblue.com>
Sent: 10 January 2017 12:08:24
To: dev
Subject: Re: [DISCUSS] Moving for JDK8, this time for real!

All,


Thank you for your feedback.


We've no outstanding objections to the PR, at the time of the 4.10 release we'll document the new requirements around JRE1.8 and new systemvmtemplate in our installation/upgrade notes.


I'll proceed with the merge later this week.


Regards.

________________________________
From: Erik Weber <te...@gmail.com>
Sent: 06 January 2017 02:50:36
To: dev
Subject: Re: [DISCUSS] Moving for JDK8, this time for real!

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 <ro...@shapeblue.com>:

> 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 <te...@gmail.com>
>
> Sent: 05 January 2017 18:25:38
>
> To: dev
>
> Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
>
>
>
>
>
> rohit.yadav@shapeblue.com
>
> www.shapeblue.com<http://www.shapeblue.com>
>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>
> @shapeblue
>
>
>
>
>
>
>
> On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav <ro...@shapeblue.com>
> 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
>
>

rohit.yadav@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




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


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

Posted by Rohit Yadav <ro...@shapeblue.com>.
All,


Thank you for your feedback.


We've no outstanding objections to the PR, at the time of the 4.10 release we'll document the new requirements around JRE1.8 and new systemvmtemplate in our installation/upgrade notes.


I'll proceed with the merge later this week.


Regards.

________________________________
From: Erik Weber <te...@gmail.com>
Sent: 06 January 2017 02:50:36
To: dev
Subject: Re: [DISCUSS] Moving for JDK8, this time for real!

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 <ro...@shapeblue.com>:

> 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 <te...@gmail.com>
>
> Sent: 05 January 2017 18:25:38
>
> To: dev
>
> Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
>
>
>
>
>
> rohit.yadav@shapeblue.com
>
> www.shapeblue.com<http://www.shapeblue.com>
>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>
> @shapeblue
>
>
>
>
>
>
>
> On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav <ro...@shapeblue.com>
> 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
>
>

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


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

Posted by Erik Weber <te...@gmail.com>.
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 <ro...@shapeblue.com>:

> 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 <te...@gmail.com>
>
> Sent: 05 January 2017 18:25:38
>
> To: dev
>
> Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
>
>
>
>
>
> rohit.yadav@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 <ro...@shapeblue.com>
> 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!

Posted by Wido den Hollander <wi...@widodh.nl>.
> Op 5 januari 2017 om 16:06 schreef Will Stevens <ws...@cloudops.com>:
> 
> 
> 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
> 
> <https://goo.gl/NYZ8KK>
> 
> On Thu, Jan 5, 2017 at 9:45 AM, Rohit Yadav <ro...@shapeblue.com>
> 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 <te...@gmail.com>
> > Sent: 05 January 2017 18:25:38
> > To: dev
> > Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
> >
> >
> > rohit.yadav@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 <ro...@shapeblue.com>
> > 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!

Posted by Will Stevens <ws...@cloudops.com>.
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

<https://goo.gl/NYZ8KK>

On Thu, Jan 5, 2017 at 9:45 AM, Rohit Yadav <ro...@shapeblue.com>
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 <te...@gmail.com>
> Sent: 05 January 2017 18:25:38
> To: dev
> Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
>
>
> rohit.yadav@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 <ro...@shapeblue.com>
> 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!

Posted by Rohit Yadav <ro...@shapeblue.com>.
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 <te...@gmail.com>
Sent: 05 January 2017 18:25:38
To: dev
Subject: Re: [DISCUSS] Moving for JDK8, this time for real!


rohit.yadav@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 <ro...@shapeblue.com> 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!

Posted by Erik Weber <te...@gmail.com>.
On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav <ro...@shapeblue.com> 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