10:16 a.m.
Hello,
Is there any objection / potential problem if we upgrade from 1.0.0.Final to 1.1.0.Final
?
During investigation of a clustering issue, there are some fixes related that seems to be
packaged on 1.1.0.Final.
I am still working on this but I would want to know if upgrading the Wildfly version in
parent could have consensus.
Thanks,
Lucas
10:21 a.m.
On 7 Feb 2017, at 10:16, Lucas Ponce wrote:
Is there any objection / potential problem if we upgrade from
1.0.0.Final to 1.1.0.Final ?
Do we know if 10.1 is just a bug-fix release or would it
introduce new features, that we are then using?
During investigation of a clustering issue, there are some fixes
related that seems to be packaged on 1.1.0.Final.
If it is bugfixes only, I am all for updating.
10:28 a.m.
----- Mensaje original -----
De: "Heiko W.Rupp" <hrupp(a)redhat.com>
Para: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Enviados: Martes, 7 de Febrero 2017 10:21:36
Asunto: Re: [Hawkular-dev] Upgrade to Wildfly 1.1.0.Final
On 7 Feb 2017, at 10:16, Lucas Ponce wrote:
> Is there any objection / potential problem if we upgrade from
> 1.0.0.Final to 1.1.0.Final ?
Do we know if 10.1 is just a bug-fix release or would it
introduce new features, that we are then using?
There are some new features
http://wildfly.org/news/2016/08/19/WildFly10-1-Released/
> During investigation of a clustering issue, there are some
fixes
> related that seems to be packaged on 1.1.0.Final.
If it is bugfixes only, I am all for updating.
I am starting to test it locally, at least for Alerting, to see if it resolves issues I am
having.
But if there is some way to test other components it would be good to give it a try.
2:29 p.m.
I'll repost what I mentioned in December:
"I noticed that on Openshift we are running Hawkular Metrics on WildFly
10.1.0. It was upped from 10.0.0 several months ago due to a blocking
issue that had been fixed in EAP but not WF 10.0. I ran into a new
issue when trying to deploy Metrics master on OS Origin. It failed to
deploy on WF 10.1.0. I was able to solve the issue without a major
change but it called out the fact that we are building Hawkular against
WF 10.0.1 bom and running itests against 10.0.0 server.
Because OS is a primary target platform I'm wondering if we should bump
the parent pom deps to the 10.1.0 bom and server (as well as upping a
few related deps as well, like ISPN). As part of my investigation I did
this locally for parent pom, commons, alerting and metrics and did not
see any issues."
I think I have a branch somewhere that fixed whatever that deployment
issue is...
On 2/7/2017 4:28 AM, Lucas Ponce wrote:
----- Mensaje original -----
> De: "Heiko W.Rupp" <hrupp(a)redhat.com>
> Para: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
> Enviados: Martes, 7 de Febrero 2017 10:21:36
> Asunto: Re: [Hawkular-dev] Upgrade to Wildfly 1.1.0.Final
>
> On 7 Feb 2017, at 10:16, Lucas Ponce wrote:
>
>> Is there any objection / potential problem if we upgrade from
>> 1.0.0.Final to 1.1.0.Final ?
> Do we know if 10.1 is just a bug-fix release or would it
> introduce new features, that we are then using?
>
There are some new features
http://wildfly.org/news/2016/08/19/WildFly10-1-Released/
>> During investigation of a clustering issue, there are some fixes
>> related that seems to be packaged on 1.1.0.Final.
> If it is bugfixes only, I am all for updating.
I am starting to test it locally, at least for Alerting, to see if it resolves issues I
am having.
But if there is some way to test other components it would be good to give it a try.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
9:51 p.m.
----- Original Message -----
From: "Heiko W.Rupp" <hrupp(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, 7 February, 2017 4:21:36 AM
Subject: Re: [Hawkular-dev] Upgrade to Wildfly 1.1.0.Final
On 7 Feb 2017, at 10:16, Lucas Ponce wrote:
> Is there any objection / potential problem if we upgrade from
> 1.0.0.Final to 1.1.0.Final ?
Do we know if 10.1 is just a bug-fix release or would it
introduce new features, that we are then using?
With Wildfly there is no backporting to fix issues.
To make sure that we are running with the latest bug fixes and security updates, whenever
there is a new release of Wildfly we should be moving to that as soon as possible.
> During investigation of a clustering issue, there are some
fixes
> related that seems to be packaged on 1.1.0.Final.
If it is bugfixes only, I am all for updating.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
9:55 p.m.
To make sure that we are running with the latest bug fixes and
security
updates, whenever there is a new release of Wildfly we should be moving to
that as soon as possible.
The problem with that is, it may break us if run in older EAP versions (like EAP6).
But this may not be an issue with server-side components like metrics and alerts.
It is an issue with the wildfly agent, though.
11:33 p.m.
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, 7 February, 2017 3:55:44 PM
Subject: Re: [Hawkular-dev] Upgrade to Wildfly 1.1.0.Final
> To make sure that we are running with the latest bug fixes and security
> updates, whenever there is a new release of Wildfly we should be moving to
> that as soon as possible.
The problem with that is, it may break us if run in older EAP versions (like
EAP6).
If you are relying on an older version of Wildfly to behave the same way as EAP you are
going to be disappointed. They may share a common ancestor, but the longer that EAP is out
there the more out of sync it gets with Wildfly. EAP will have backported fixes and other
updates that the older Wildfly version its based on will never get.
They are similar but different enough that its probably a wise idea to be supporting them
separately. We have to do this with our metric images for OpenShift.
For the community version we should always be updating, even just to make sure we have the
latest security updates.
But this may not be an issue with server-side components like metrics
and
alerts.
It is an issue with the wildfly agent, though.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
2643
days inactive
2644
days old
6 comments
5 participants
participants (5)
-
Heiko W.Rupp -
Jay Shaughnessy -
John Mazzitelli -
Lucas Ponce -
Matt Wringe