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 <rohit.ya...@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 <terbol...@gmail.com> > > 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 <rohit.ya...@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 > >
