cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus <shadow...@gmail.com>
Subject Re: [DISCUSS] Move to JDK 11 (LTS) after 4.13
Date Tue, 18 Jun 2019 17:03:44 GMT
+1 for upgrading after 4.13.

I looked into this recently, and determined that actually for open source
users there's not a lot of benefit going to JDK 11, as OpenJDK 8 would be
supported until 2023, and switching to 11 only gets us to 2024.

https://access.redhat.com/articles/1299013

I realize some are using Oracle-supported packages, though. It may also
vary based on distribution.

On Tue, Jun 18, 2019 at 3:54 AM Rohit Yadav <rohit.yadav@shapeblue.com>
wrote:

> Thanks for your comment Daan.
>
>
> I think I would personally like to avoid any changes to 4.13 at this
> point. I don't think using jdk8 is an issue for now, but in 6-months like
> (let's say for 4.14) we should fix that and move to the latest jdk 11 lts.
> Also, moving master/4.13 to jdk11 would mean creating a new
> systemvmtemplate, but we don't have anything to require a new
> systemvmtemplate the master/4.13 can use the 4.11.3.0 systemvmtemplate.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> ________________________________
> From: Daan Hoogland <daan.hoogland@gmail.com>
> Sent: Tuesday, June 18, 2019 2:56:09 PM
> To: dev
> Subject: Re: [DISCUSS] Move to JDK 11 (LTS) after 4.13
>
> Is 4.13 already in freeze? I'd say let's update before the freeze, if we
> still can.
>
> On Mon, Jun 17, 2019 at 2:25 PM Rohit Yadav <rohit.yadav@shapeblue.com>
> wrote:
>
> > All,
> >
> >
> > JDK 8 (lts) has already reached EOL and we're dependent on
> > distro/maintainers and the next available LTS jdk is JDK 11.
> >
> >
> > Here's the proposal:
> >
> >
> > - Use JDK8 for building 4.13 and let users decide if they want to run/use
> > JDK8 (jre) or JDK 11 (jre) for cloudstack management/usage/agent
> services,
> > the systemvm will still have JDK 8 jre
> >
> >
> > - After 4.13 master is unfrozen, we fix the pom.xml to enforce that JDK
> 11
> > is used to build master
> >
> >
> > - New systemvmtemplate is created using the next/upcoming Debian 10 (
> > https://lists.debian.org/debian-devel-announce/2019/06/msg00003.html)
> > release and use latest/stable kernel (in Debian 10) and use JDK 11
> >
> >
> > - Experimental proposal: with 4.14+debian 10 based systemvmtemplate we do
> > not bundle JRE within the systemvmtemplate but using jlink (
> > https://docs.oracle.com/javase/9/tools/jlink.htm) create a systemvm.iso
> > that has a lightweight JRE embeded for use with the ssvm/cpvm agent. The
> > systemvmtemplate has about 100-200 MBs consumed due to the JRE
> installation
> > which is only necessary to run cpvm/ssvm agent but adds dead
> > weight/storage-size for VRs. If the jlink embedded jre concept works, it
> > will also work in our favour and reduce security impact, i.e. in case of
> a
> > future java related security issue we can simply create a new release
> (with
> > latest systemvm.iso and embedded jre) without requiring us to release a
> new
> > systemvmtemplate.
> >
> >
> > Thoughts, ideas, questions?
> >
> >
> > Regards,
> >
> > Rohit Yadav
> >
> > Software Architect, ShapeBlue
> >
> > https://www.shapeblue.com
> >
> > rohit.yadav@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>
> --
> Daan
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message