Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: <CAKLH8EaGhW=b1KXCCfRYuu9Snb5+2SXNHatOBzsNnZ0XQhzsAw@mail.gmail.com>
References: <CAD97ioc1KU-sruOhaj96cG-6UGVKTp9vtJU1dYm0RC-hW0+oeA@mail.gmail.com>
 <CAC2panoHB59wKjjZ37bV+FRUNmEhi3mw6hZjOai4ti+t5JY3gg@mail.gmail.com>
 <CAC2panoQmip5_pk+_0eUSq4y6DEsfNc3eLCGY7kYWKO5nY007Q@mail.gmail.com>
 <CAAt5S3YHGc=a69iYHi8Si=YTwCqAunwU406=0dtMhBsCxEeTXg@mail.gmail.com>
 <CAC2panqLw5Bx=TG2LjZ7Amm7t2ot3HL1j-YZ5CYdLKVk_g-g8A@mail.gmail.com>
 <CADMzvUqLGemWeFkZWAL97R8CUjiTxqc2ZJdmiDsA6LtvPpJ8BA@mail.gmail.com>
 <CAC2panrKCVOEgwPBH4rrqsYtv3chMjWDODPTjOtBYWgm2iX0WA@mail.gmail.com>
 <CA01076C-3DE1-43E1-A495-2EFAF4407D39@gmail.com> <CAD97ioes1oTB4z3KBs7Q6drJ1W9=d1UOSRg+9Jd3doHRzc=E1Q@mail.gmail.com>
 <CAAt5S3Y7-6N8w2wZrgy8NFu5wnsb9MxLtM6rVjC1pZYQktVCPQ@mail.gmail.com>
 <CAAt5S3af3ddBG6vyPQkZ0TySUNzBT1EVbfB6R0w1Di+6JLNdpQ@mail.gmail.com> <CAKLH8EaGhW=b1KXCCfRYuu9Snb5+2SXNHatOBzsNnZ0XQhzsAw@mail.gmail.com>
From: Wei ZHOU <ustcweizhou@gmail.com>
Date: Tue, 21 Feb 2017 08:15:01 +0100
Message-ID: <CAAt5S3aFsB1aVRzvPODAj_UfevCgmRfAxMkNsXxzEbxfL7Jp9w@mail.gmail.com>
Subject: Re: [QUESTION] Upgrade path to JDK8
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a113eba287a85cd054905239d
archived-at: Tue, 21 Feb 2017 07:15:26 -0000

--001a113eba287a85cd054905239d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Marco,

Good point. Is there any issue if we compile code with jdk8 but run it on
jdk7 (systemvm) ?

-Wei

2017-02-21 7:43 GMT+01:00 Marc-Aur=C3=A8le Brothier <marco@exoscale.ch>:

> There's a list of compatibility issues between Java 7 & Java 8 here
> http://www.oracle.com/technetwork/java/javase/8-
> compatibility-guide-2156366.
> html
>
> The main problem I would see in two system communicating while running
> different Java version is the way they handle serialization and
> de-serialization of objects which had been a problem in the past between
> some Java versions. AFAIK we're using JSON for that now, so if the code
> already compiles with Java8, it should not be a problem.
>
> On Mon, Feb 20, 2017 at 10:36 PM, Wei ZHOU <ustcweizhou@gmail.com> wrote:
>
> > We tested 4.7.1+systemd patches as well, it also works fine.
> >
> > -Wei
> >
> > 2017-02-20 22:34 GMT+01:00 Wei ZHOU <ustcweizhou@gmail.com>:
> >
> > > @Will and @Syed, I build the packages of 4.9.2+systemd patches on
> ubuntu
> > > 16.04 (openjdk 8).
> > > Then install the packages to management server and kvm hosts (all are
> > > ubuntu 16.04 with openjdk8).
> > > The systemvm template is 4.6 with openjdk7.
> > >
> > > cpvm and ssvm work fine.
> > >
> > > As there is no java process in VR, so I did not check, VR should not =
be
> > > impacted.
> > >
> > > -Wei
> > >
> > > 2017-02-20 22:16 GMT+01:00 Pierre-Luc Dion <pdion@cloudops.com>:
> > >
> > >> That's quite interesting Chiradeep!
> > >>
> > >> so I could do something like this I guest:
> > >>
> > >> mvn clean install
> > >>
> > >> and then this one to build the systemvm.iso:
> > >> mvn -Psystemvm -source 1.7 -target 1.7 install
> > >>
> > >>
> > >> I'll give it a try! but for now, I'm worried about existing VR, they
> > must
> > >> continue to work while running on jdk7.  newer VPC would be ok to ru=
n
> > with
> > >> jdk8.  but we need to make sure while upgrading the management-serve=
r
> we
> > >> are not in the obligation to upgrade VR's.
> > >>
> > >> For sure it is required for strongswan + JDK8 to ugprade the VR, but=
 a
> > >>  existing VR should remain usable for port forwarding, vm creation a=
nd
> > >> such...
> > >>
> > >> I'll post my finding...
> > >>
> > >> Thanks !
> > >>
> > >>
> > >>
> > >> On Mon, Feb 20, 2017 at 3:59 PM, Chiradeep Vittal <
> chiradeepv@gmail.com
> > >
> > >> wrote:
> > >>
> > >> > You can build the system vm with  -source 1.7 -target 1.7
> > >> > Also unless you are using Java8 features (lambda) the classfiles
> > >> produced
> > >> > by javac 8 should work in a 1.7 JVM
> > >> >
> > >> > Sent from my iPhone
> > >> >
> > >> > > On Feb 20, 2017, at 11:51 AM, Will Stevens <wstevens@cloudops.co=
m
> >
> > >> > wrote:
> > >> > >
> > >> > > yes, that is what I was expecting.  which is why I was asking
> about
> > >> Wei's
> > >> > > setup because he seems to have worked around that problem.  Or h=
e
> > has
> > >> a
> > >> > > custom SystemVM template running with both JDK7 and JDK8.
> > >> > >
> > >> > > *Will STEVENS*
> > >> > > Lead Developer
> > >> > >
> > >> > > <https://goo.gl/NYZ8KK>
> > >> > >
> > >> > >> On Mon, Feb 20, 2017 at 2:20 PM, Syed Ahmed <sahmed@cloudops.co=
m
> >
> > >> > wrote:
> > >> > >>
> > >> > >> The problem is that systemvm.iso is built with java 8 whereas
> java
> > on
> > >> > the
> > >> > >> VR is java 7
> > >> > >>> On Mon, Feb 20, 2017 at 13:20 Will Stevens <
> wstevens@cloudops.com
> > >
> > >> > wrote:
> > >> > >>>
> > >> > >>> Did it work after resetting a VPC or when blowing away the SSV=
M
> or
> > >> > >> CPVM?  I
> > >> > >>> would not expect the SSVM or the CPVM to come up if the
> management
> > >> > server
> > >> > >>> was built with JDK8 and the system vm template is only using
> JDK7.
> > >> Can
> > >> > >> you
> > >> > >>> confirm?=E2=80=8B
> > >> > >>>
> > >> > >>> *Will STEVENS*
> > >> > >>> Lead Developer
> > >> > >>>
> > >> > >>> <https://goo.gl/NYZ8KK>
> > >> > >>>
> > >> > >>>> On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU <
> ustcweizhou@gmail.com
> > >
> > >> > wrote:
> > >> > >>>>
> > >> > >>>> We've tested management server 4.7.1 with ubuntu 16.04/openjd=
k8
> > and
> > >> > >>>> systemvm 4.6 with debian7/openjdk7.
> > >> > >>>> The systemvms (ssvm, cpvm) work fine.
> > >> > >>>>
> > >> > >>>> I agree we need consider the openjdk upgrade in systemvm
> > template.
> > >> > >>>>
> > >> > >>>> -Wei
> > >> > >>>>
> > >> > >>>> 2017-02-20 18:15 GMT+01:00 Will Stevens <wstevens@cloudops.co=
m
> >:
> > >> > >>>>
> > >> > >>>>> Regarding my question. Is it because of the version of Java
> that
> > >> the
> > >> > >>>>> systemvm.iso is built on?
> > >> > >>>>>
> > >> > >>>>> On Feb 20, 2017 11:58 AM, "Will Stevens" <
> wstevens@cloudops.com
> > >
> > >> > >>> wrote:
> > >> > >>>>>
> > >> > >>>>>> A question that is hidden in here is:
> > >> > >>>>>> - Why does the JDK version on the management server have to
> > match
> > >> > >> the
> > >> > >>>> JDK
> > >> > >>>>>> version of the System VM?
> > >> > >>>>>>
> > >> > >>>>>> *Will STEVENS*
> > >> > >>>>>> Lead Developer
> > >> > >>>>>>
> > >> > >>>>>> <https://goo.gl/NYZ8KK>
> > >> > >>>>>>
> > >> > >>>>>> On Mon, Feb 20, 2017 at 11:50 AM, Pierre-Luc Dion <
> > >> > >>> pdion@cloudops.com>
> > >> > >>>>>> wrote:
> > >> > >>>>>>
> > >> > >>>>>>> Hi,
> > >> > >>>>>>>
> > >> > >>>>>>> In the context of deployment of CloudStack with VPCs,
> > >> > >>>>>>> What will happen to a cloud when upgrading to 4.10 that no=
w
> > use
> > >> > >>> jdk8?
> > >> > >>>>>>>
> > >> > >>>>>>> Does upgrading the management-server to 4.10 jdk8 and then
> > keep
> > >> > >> the
> > >> > >>>> old
> > >> > >>>>>>> VRs
> > >> > >>>>>>> run for a while that run on JDK7 will still work ?
> > >> > >>>>>>>
> > >> > >>>>>>> Because If we upgrade the management-server to jdk8, we ne=
ed
> > to
> > >> > >> keep
> > >> > >>>> VR
> > >> > >>>>> to
> > >> > >>>>>>> work until they get upgraded but we can't force an upgrade
> of
> > VR
> > >> > >>> just
> > >> > >>>>>>> because the management-server is now using JDK8.
> > >> > >>>>>>>
> > >> > >>>>>>> Thanks,
> > >> > >>>>>>>
> > >> > >>>>>>
> > >> > >>>>>>
> > >> > >>>>>
> > >> > >>>>
> > >> > >>>
> > >> > >>
> > >> >
> > >>
> > >
> > >
> >
>

--001a113eba287a85cd054905239d--