Re: Roadmap Apache Storm 3.x

[Alexandre Vermeerbergen]

Hello Julien,

Sorry for asking so late, but one detail puzzles my in this
discussion: according to semantic versioning, the change of major
version number is meant to introduce changes breaking compatibility.

Unless I have missed something, I do not see any changes that would
break compatibility from current Storm 2.x.y versions to this future
Storm 3.0.0 version.

Did I miss something?

Kind regards,
Alexandre

Le jeu. 7 déc. 2023 à 15:19, Bipin Prasad
 a écrit :
>
> I agree on the need to fix logviewer functionality so that it works in a 
> Kubernetes deployment (eg AWS EKS or GKE).
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Thursday, December 7, 2023, 4:26 AM, Richard Zowalla  
> wrote:
>
> It might be possible to build an abstraction layer + java 21-based
> module, so ppl can decide (for ex by configuration) to switch to it or
> not. If you do not activley decide to use it, it won't be a difference
> to how it is currently working. Might need some carefully thinking and
> some eyes on other projects.
>
> Am Donnerstag, dem 07.12.2023 um 13:24 +0100 schrieb Alexandre
> Vermeerbergen:
> > Agreed for leaving fiber projet aside from 3.x
> >
> > Re-logviewer : how about my idea to use storm-ui's app server and
> > write some kind of proxy servlet to make all traffic related to logs
> > retrieval going to storm UI ?
> >
> > Le jeu. 7 déc. 2023 à 13:06, Julien Nioche
> >  a écrit :
> > >
> > > Thanks Alexandre,
> > >
> > > I haven't looked nor know anything about fibers but it sounds
> > > promising.
> > > Forcing Java 21 would be problematic I think.
> > > Given that it is a fundamental change, maybe this could live in a
> > > separate
> > > branch until thoroughly tested and Java 21 is the norm. What do you
> > > think?
> > >
> > > Re-logviewer: it is something that has been bugging people for a
> > > while and
> > > that a lot of us would like to see fixed I think. Sadly, I don't
> > > have a
> > > clue on how to do it.
> > >
> > > Julien
> > >
> > > On Thu, 7 Dec 2023 at 11:01, Alexandre Vermeerbergen <
> > > avermeerber...@gmail.com> wrote:
> > >
> > > > Hello Julien,
> > > >
> > > > Excellent initiative indeed !
> > > >
> > > > I am very fond of "Find a way of having the Logviewer work in
> > > > Docker"
> > > > topic, because I think it's similar to a shorter time need which
> > > > I
> > > > have when deploying AWS EC2 with a VPN to avoid exposure of
> > > > "internal
> > > > VMs" : in this case, the public FQDN of Supervisor VMs is not
> > > > usable
> > > > for logviewer, so i'm trying to figure out a way to do some
> > > > proxying
> > > > through Nimbus/Nimbus UI process... it's only brainstorming at
> > > > the
> > > > moment.
> > > >
> > > > I also have recently  launched the idea to use Java fibers and
> > > > got a
> > > > positive feedback from Bipin, but I have no idea on whether it
> > > > could
> > > > be affordable for 3.x. One problem being is that unless we un-
> > > > support
> > > > Storm on Java < 21, we can't just build everything using JDK21 to
> > > > get
> > > > access to fibers API...
> > > >
> > > > That were my 2 cents...
> > > >
> > > > Alexandre
> > > >
> > > >
> > > >
> > > > Le jeu. 7 déc. 2023 à 10:43, Julien Nioche
> > > >  a écrit :
> > > > >
> > > > > Hi,
> > > > >
> > > > > Now that Storm is active again and we are getting regular
> > > > > releases,
> > > > should
> > > > > we try to come up with a roadmap for the Storm 3.x?
> > > > >
> > > > > Here are a few things that come to mind
> > > > >
> > > > >- Finish the migration from Clojure to Java (it is still
> > > > > used in the
> > > > >tests I think)
> > > > >- Find a way of having the Logviewer work in Docker
> > > > >
> > > > >- Publish the Docker images ourselves
> > > > >- UI Refresh (at least the libs) - suggested by R. Zowalla
> > > > >- Fix Maven build  - suggested by R. Zowalla
> > > > >
> > > > > Anything else? Who would like to get involved? Where would be a
> > > > > good
> > > > place
> > > > > to formalise a roadmap? JIRA? GitHub projects
> > > > > ?
> > > > >
> > > > > Best regards
> > > > >
> > > > > --
> > > > > *Julien Nioche *
> > > > >
> > > > >
> > > > > digitalpebble.com 
> > > >
> > >
> > >
> > > --
> > > *Julien Nioche *
> > >
> > >
> > > digitalpebble.com 
>
>
>
>

Re: [PR] STORM-4009 - Regenerate using thrift 0.18.1 (storm)

[via GitHub]

rzo1 merged PR #3608:
URL: https://github.com/apache/storm/pull/3608


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Roadmap Apache Storm 3.x

[Bipin Prasad]

I agree on the need to fix logviewer functionality so that it works in a 
Kubernetes deployment (eg AWS EKS or GKE).


Sent from Yahoo Mail for iPhone


On Thursday, December 7, 2023, 4:26 AM, Richard Zowalla  
wrote:

It might be possible to build an abstraction layer + java 21-based
module, so ppl can decide (for ex by configuration) to switch to it or
not. If you do not activley decide to use it, it won't be a difference
to how it is currently working. Might need some carefully thinking and
some eyes on other projects. 

Am Donnerstag, dem 07.12.2023 um 13:24 +0100 schrieb Alexandre
Vermeerbergen:
> Agreed for leaving fiber projet aside from 3.x
> 
> Re-logviewer : how about my idea to use storm-ui's app server and
> write some kind of proxy servlet to make all traffic related to logs
> retrieval going to storm UI ?
> 
> Le jeu. 7 déc. 2023 à 13:06, Julien Nioche
>  a écrit :
> > 
> > Thanks Alexandre,
> > 
> > I haven't looked nor know anything about fibers but it sounds
> > promising.
> > Forcing Java 21 would be problematic I think.
> > Given that it is a fundamental change, maybe this could live in a
> > separate
> > branch until thoroughly tested and Java 21 is the norm. What do you
> > think?
> > 
> > Re-logviewer: it is something that has been bugging people for a
> > while and
> > that a lot of us would like to see fixed I think. Sadly, I don't
> > have a
> > clue on how to do it.
> > 
> > Julien
> > 
> > On Thu, 7 Dec 2023 at 11:01, Alexandre Vermeerbergen <
> > avermeerber...@gmail.com> wrote:
> > 
> > > Hello Julien,
> > > 
> > > Excellent initiative indeed !
> > > 
> > > I am very fond of "Find a way of having the Logviewer work in
> > > Docker"
> > > topic, because I think it's similar to a shorter time need which
> > > I
> > > have when deploying AWS EC2 with a VPN to avoid exposure of
> > > "internal
> > > VMs" : in this case, the public FQDN of Supervisor VMs is not
> > > usable
> > > for logviewer, so i'm trying to figure out a way to do some
> > > proxying
> > > through Nimbus/Nimbus UI process... it's only brainstorming at
> > > the
> > > moment.
> > > 
> > > I also have recently  launched the idea to use Java fibers and
> > > got a
> > > positive feedback from Bipin, but I have no idea on whether it
> > > could
> > > be affordable for 3.x. One problem being is that unless we un-
> > > support
> > > Storm on Java < 21, we can't just build everything using JDK21 to
> > > get
> > > access to fibers API...
> > > 
> > > That were my 2 cents...
> > > 
> > > Alexandre
> > > 
> > > 
> > > 
> > > Le jeu. 7 déc. 2023 à 10:43, Julien Nioche
> > >  a écrit :
> > > > 
> > > > Hi,
> > > > 
> > > > Now that Storm is active again and we are getting regular
> > > > releases,
> > > should
> > > > we try to come up with a roadmap for the Storm 3.x?
> > > > 
> > > > Here are a few things that come to mind
> > > > 
> > > >    - Finish the migration from Clojure to Java (it is still
> > > > used in the
> > > >    tests I think)
> > > >    - Find a way of having the Logviewer work in Docker
> > > >    
> > > >    - Publish the Docker images ourselves
> > > >    - UI Refresh (at least the libs) - suggested by R. Zowalla
> > > >    - Fix Maven build  - suggested by R. Zowalla
> > > > 
> > > > Anything else? Who would like to get involved? Where would be a
> > > > good
> > > place
> > > > to formalise a roadmap? JIRA? GitHub projects
> > > > ?
> > > > 
> > > > Best regards
> > > > 
> > > > --
> > > > *Julien Nioche *
> > > > 
> > > > 
> > > > digitalpebble.com 
> > > 
> > 
> > 
> > --
> > *Julien Nioche *
> > 
> > 
> > digitalpebble.com 

Re: Roadmap Apache Storm 3.x

[Richard Zowalla]

It might be possible to build an abstraction layer + java 21-based
module, so ppl can decide (for ex by configuration) to switch to it or
not. If you do not activley decide to use it, it won't be a difference
to how it is currently working. Might need some carefully thinking and
some eyes on other projects. 

Am Donnerstag, dem 07.12.2023 um 13:24 +0100 schrieb Alexandre
Vermeerbergen:
> Agreed for leaving fiber projet aside from 3.x
> 
> Re-logviewer : how about my idea to use storm-ui's app server and
> write some kind of proxy servlet to make all traffic related to logs
> retrieval going to storm UI ?
> 
> Le jeu. 7 déc. 2023 à 13:06, Julien Nioche
>  a écrit :
> > 
> > Thanks Alexandre,
> > 
> > I haven't looked nor know anything about fibers but it sounds
> > promising.
> > Forcing Java 21 would be problematic I think.
> > Given that it is a fundamental change, maybe this could live in a
> > separate
> > branch until thoroughly tested and Java 21 is the norm. What do you
> > think?
> > 
> > Re-logviewer: it is something that has been bugging people for a
> > while and
> > that a lot of us would like to see fixed I think. Sadly, I don't
> > have a
> > clue on how to do it.
> > 
> > Julien
> > 
> > On Thu, 7 Dec 2023 at 11:01, Alexandre Vermeerbergen <
> > avermeerber...@gmail.com> wrote:
> > 
> > > Hello Julien,
> > > 
> > > Excellent initiative indeed !
> > > 
> > > I am very fond of "Find a way of having the Logviewer work in
> > > Docker"
> > > topic, because I think it's similar to a shorter time need which
> > > I
> > > have when deploying AWS EC2 with a VPN to avoid exposure of
> > > "internal
> > > VMs" : in this case, the public FQDN of Supervisor VMs is not
> > > usable
> > > for logviewer, so i'm trying to figure out a way to do some
> > > proxying
> > > through Nimbus/Nimbus UI process... it's only brainstorming at
> > > the
> > > moment.
> > > 
> > > I also have recently  launched the idea to use Java fibers and
> > > got a
> > > positive feedback from Bipin, but I have no idea on whether it
> > > could
> > > be affordable for 3.x. One problem being is that unless we un-
> > > support
> > > Storm on Java < 21, we can't just build everything using JDK21 to
> > > get
> > > access to fibers API...
> > > 
> > > That were my 2 cents...
> > > 
> > > Alexandre
> > > 
> > > 
> > > 
> > > Le jeu. 7 déc. 2023 à 10:43, Julien Nioche
> > >  a écrit :
> > > > 
> > > > Hi,
> > > > 
> > > > Now that Storm is active again and we are getting regular
> > > > releases,
> > > should
> > > > we try to come up with a roadmap for the Storm 3.x?
> > > > 
> > > > Here are a few things that come to mind
> > > > 
> > > >    - Finish the migration from Clojure to Java (it is still
> > > > used in the
> > > >    tests I think)
> > > >    - Find a way of having the Logviewer work in Docker
> > > >    
> > > >    - Publish the Docker images ourselves
> > > >    - UI Refresh (at least the libs) - suggested by R. Zowalla
> > > >    - Fix Maven build  - suggested by R. Zowalla
> > > > 
> > > > Anything else? Who would like to get involved? Where would be a
> > > > good
> > > place
> > > > to formalise a roadmap? JIRA? GitHub projects
> > > > ?
> > > > 
> > > > Best regards
> > > > 
> > > > --
> > > > *Julien Nioche *
> > > > 
> > > > 
> > > > digitalpebble.com 
> > > 
> > 
> > 
> > --
> > *Julien Nioche *
> > 
> > 
> > digitalpebble.com 

Re: Roadmap Apache Storm 3.x

[Alexandre Vermeerbergen]

Agreed for leaving fiber projet aside from 3.x

Re-logviewer : how about my idea to use storm-ui's app server and
write some kind of proxy servlet to make all traffic related to logs
retrieval going to storm UI ?

Le jeu. 7 déc. 2023 à 13:06, Julien Nioche
 a écrit :
>
> Thanks Alexandre,
>
> I haven't looked nor know anything about fibers but it sounds promising.
> Forcing Java 21 would be problematic I think.
> Given that it is a fundamental change, maybe this could live in a separate
> branch until thoroughly tested and Java 21 is the norm. What do you think?
>
> Re-logviewer: it is something that has been bugging people for a while and
> that a lot of us would like to see fixed I think. Sadly, I don't have a
> clue on how to do it.
>
> Julien
>
> On Thu, 7 Dec 2023 at 11:01, Alexandre Vermeerbergen <
> avermeerber...@gmail.com> wrote:
>
> > Hello Julien,
> >
> > Excellent initiative indeed !
> >
> > I am very fond of "Find a way of having the Logviewer work in Docker"
> > topic, because I think it's similar to a shorter time need which I
> > have when deploying AWS EC2 with a VPN to avoid exposure of "internal
> > VMs" : in this case, the public FQDN of Supervisor VMs is not usable
> > for logviewer, so i'm trying to figure out a way to do some proxying
> > through Nimbus/Nimbus UI process... it's only brainstorming at the
> > moment.
> >
> > I also have recently  launched the idea to use Java fibers and got a
> > positive feedback from Bipin, but I have no idea on whether it could
> > be affordable for 3.x. One problem being is that unless we un-support
> > Storm on Java < 21, we can't just build everything using JDK21 to get
> > access to fibers API...
> >
> > That were my 2 cents...
> >
> > Alexandre
> >
> >
> >
> > Le jeu. 7 déc. 2023 à 10:43, Julien Nioche
> >  a écrit :
> > >
> > > Hi,
> > >
> > > Now that Storm is active again and we are getting regular releases,
> > should
> > > we try to come up with a roadmap for the Storm 3.x?
> > >
> > > Here are a few things that come to mind
> > >
> > >- Finish the migration from Clojure to Java (it is still used in the
> > >tests I think)
> > >- Find a way of having the Logviewer work in Docker
> > >
> > >- Publish the Docker images ourselves
> > >- UI Refresh (at least the libs) - suggested by R. Zowalla
> > >- Fix Maven build  - suggested by R. Zowalla
> > >
> > > Anything else? Who would like to get involved? Where would be a good
> > place
> > > to formalise a roadmap? JIRA? GitHub projects
> > > ?
> > >
> > > Best regards
> > >
> > > --
> > > *Julien Nioche *
> > >
> > >
> > > digitalpebble.com 
> >
>
>
> --
> *Julien Nioche *
>
>
> digitalpebble.com 

Re: Roadmap Apache Storm 3.x

[Julien Nioche]

Thanks Alexandre,

I haven't looked nor know anything about fibers but it sounds promising.
Forcing Java 21 would be problematic I think.
Given that it is a fundamental change, maybe this could live in a separate
branch until thoroughly tested and Java 21 is the norm. What do you think?

Re-logviewer: it is something that has been bugging people for a while and
that a lot of us would like to see fixed I think. Sadly, I don't have a
clue on how to do it.

Julien

On Thu, 7 Dec 2023 at 11:01, Alexandre Vermeerbergen <
avermeerber...@gmail.com> wrote:

> Hello Julien,
>
> Excellent initiative indeed !
>
> I am very fond of "Find a way of having the Logviewer work in Docker"
> topic, because I think it's similar to a shorter time need which I
> have when deploying AWS EC2 with a VPN to avoid exposure of "internal
> VMs" : in this case, the public FQDN of Supervisor VMs is not usable
> for logviewer, so i'm trying to figure out a way to do some proxying
> through Nimbus/Nimbus UI process... it's only brainstorming at the
> moment.
>
> I also have recently  launched the idea to use Java fibers and got a
> positive feedback from Bipin, but I have no idea on whether it could
> be affordable for 3.x. One problem being is that unless we un-support
> Storm on Java < 21, we can't just build everything using JDK21 to get
> access to fibers API...
>
> That were my 2 cents...
>
> Alexandre
>
>
>
> Le jeu. 7 déc. 2023 à 10:43, Julien Nioche
>  a écrit :
> >
> > Hi,
> >
> > Now that Storm is active again and we are getting regular releases,
> should
> > we try to come up with a roadmap for the Storm 3.x?
> >
> > Here are a few things that come to mind
> >
> >- Finish the migration from Clojure to Java (it is still used in the
> >tests I think)
> >- Find a way of having the Logviewer work in Docker
> >
> >- Publish the Docker images ourselves
> >- UI Refresh (at least the libs) - suggested by R. Zowalla
> >- Fix Maven build  - suggested by R. Zowalla
> >
> > Anything else? Who would like to get involved? Where would be a good
> place
> > to formalise a roadmap? JIRA? GitHub projects
> > ?
> >
> > Best regards
> >
> > --
> > *Julien Nioche *
> >
> >
> > digitalpebble.com 
>


-- 
*Julien Nioche *


digitalpebble.com 

Re: Roadmap Apache Storm 3.x

[Alexandre Vermeerbergen]

Hello Julien,

Excellent initiative indeed !

I am very fond of "Find a way of having the Logviewer work in Docker"
topic, because I think it's similar to a shorter time need which I
have when deploying AWS EC2 with a VPN to avoid exposure of "internal
VMs" : in this case, the public FQDN of Supervisor VMs is not usable
for logviewer, so i'm trying to figure out a way to do some proxying
through Nimbus/Nimbus UI process... it's only brainstorming at the
moment.

I also have recently  launched the idea to use Java fibers and got a
positive feedback from Bipin, but I have no idea on whether it could
be affordable for 3.x. One problem being is that unless we un-support
Storm on Java < 21, we can't just build everything using JDK21 to get
access to fibers API...

That were my 2 cents...

Alexandre



Le jeu. 7 déc. 2023 à 10:43, Julien Nioche
 a écrit :
>
> Hi,
>
> Now that Storm is active again and we are getting regular releases, should
> we try to come up with a roadmap for the Storm 3.x?
>
> Here are a few things that come to mind
>
>- Finish the migration from Clojure to Java (it is still used in the
>tests I think)
>- Find a way of having the Logviewer work in Docker
>
>- Publish the Docker images ourselves
>- UI Refresh (at least the libs) - suggested by R. Zowalla
>- Fix Maven build  - suggested by R. Zowalla
>
> Anything else? Who would like to get involved? Where would be a good place
> to formalise a roadmap? JIRA? GitHub projects
> ?
>
> Best regards
>
> --
> *Julien Nioche *
>
>
> digitalpebble.com 

Roadmap Apache Storm 3.x

[Julien Nioche]

Hi,

Now that Storm is active again and we are getting regular releases, should
we try to come up with a roadmap for the Storm 3.x?

Here are a few things that come to mind

   - Finish the migration from Clojure to Java (it is still used in the
   tests I think)
   - Find a way of having the Logviewer work in Docker
   
   - Publish the Docker images ourselves
   - UI Refresh (at least the libs) - suggested by R. Zowalla
   - Fix Maven build  - suggested by R. Zowalla

Anything else? Who would like to get involved? Where would be a good place
to formalise a roadmap? JIRA? GitHub projects
?

Best regards

-- 
*Julien Nioche *


digitalpebble.com 

Re: [PR] STORM-4011 - Migrate Storm itself to use Commons Collections 4 (storm)

[via GitHub]

rzo1 merged PR #3610:
URL: https://github.com/apache/storm/pull/3610


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org