We tested 4.7.1+systemd patches as well, it also works fine.

-Wei

2017-02-20 22:34 GMT+01:00 Wei ZHOU <ustcweiz...@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 <pd...@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 run with
>> jdk8.  but we need to make sure while upgrading the management-server 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 and
>> such...
>>
>> I'll post my finding...
>>
>> Thanks !
>>
>>
>>
>> On Mon, Feb 20, 2017 at 3:59 PM, Chiradeep Vittal <chirade...@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 <wstev...@cloudops.com>
>> > 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 he 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 <sah...@cloudops.com>
>> > 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 <wstev...@cloudops.com>
>> > wrote:
>> > >>>
>> > >>> Did it work after resetting a VPC or when blowing away the SSVM 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?​
>> > >>>
>> > >>> *Will STEVENS*
>> > >>> Lead Developer
>> > >>>
>> > >>> <https://goo.gl/NYZ8KK>
>> > >>>
>> > >>>> On Mon, Feb 20, 2017 at 1:15 PM, Wei ZHOU <ustcweiz...@gmail.com>
>> > wrote:
>> > >>>>
>> > >>>> We've tested management server 4.7.1 with ubuntu 16.04/openjdk8 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 <wstev...@cloudops.com>:
>> > >>>>
>> > >>>>> 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" <wstev...@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 <
>> > >>> pd...@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 now 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 need 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,
>> > >>>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>
>> > >>>>
>> > >>>
>> > >>
>> >
>>
>
>

Reply via email to