[GitHub] [storm] bipinprasad merged pull request #3540: [STORM-3916] Add Round Robin Scheduling strategy with optional node limit
bipinprasad merged PR #3540: URL: https://github.com/apache/storm/pull/3540 -- 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: [DISCUSS] Call for PMC Members and Contributors
Agree with Bipin Prasad, since it seems that we're close to a Storm 2.5.0 candidate release... Le mar. 20 juin 2023 à 17:38, Bipin Prasad a écrit : > > I would urge PMC Chair to give us some guidance on this. > > > Sent from Yahoo Mail for iPhone > > > On Tuesday, June 20, 2023, 8:32 AM, 6harat > wrote: > > Hey, > > Just wanted to follow-up on the thread initiated by Richard, if there were > any updates from the PMC circle that can be shared with the wider audience. > Also, curious about if we have any previous roadmap available for the > further evolution of the project. (I checked on JIRA but wasn't able to > find one) > > I would be interested to help contribute to the project in any way possible > out of my personal capacity. (Have used Storm in the enterprise environment > for many years) > I would suggest if the PMC circle can syncup over google meet / zoom along > with interested new folks and help decide the way forward. Please let us > know your thoughts on the same. > > Regards > 6harat > > On Mon, Jun 19, 2023 at 12:37 PM Richard Zowalla wrote: > > > Don't want to come across as an annoying user, but have we made any > > progress in this area yet? Everyone who has expressed interest > > (usually) doesn't have read access to private@, so no one knows what > > the current status is regarding the continuation of the project by > > expanding the committer / pmc circle. CC'ing private@, so we can > > hopefully get an update. > > > > I am asking because I read about the intention to cut a storm 2.5.0 > > release and I am wondering, if we get the necessary votes in a timely > > manner. > > > > Gruß > > Richard > > > > Am Montag, dem 12.06.2023 um 12:06 +0200 schrieb Alexandre > > Vermeerbergen: > > > +1 > > > > > > Le lun. 12 juin 2023 à 11:57, Richard Zowalla a > > > écrit : > > > > > > > > Some weeks passed, any updates? > > > > > > > > Gruß > > > > Richard > > > > > > > > Am Donnerstag, dem 11.05.2023 um 19:16 -0400 schrieb P. Taylor > > > > Goetz: > > > > > Thanks for the reminder Richard, > > > > > > > > > > In response, I’ve bumped the PMC-private discussion around adding > > > > > new > > > > > members interested in contributing. > > > > > > > > > > - Taylor > > > > > > > > > > > On May 11, 2023, at 8:39 AM, Richard Zowalla > > > > > > wrote: > > > > > > > > > > > > Hello, > > > > > > > > > > > > I know we are all busy with our day jobs, but is there any > > > > > > news? > > > > > > > > > > > > We had some activity after a move to the attic was proposed. In > > > > > > the > > > > > > process, a few people volunteered to help with the project. > > > > > > > > > > > > A few weeks later, IMHO we are back to where we were before the > > > > > > proposal. Mails are going nowhere and I've heard of a few > > > > > > people > > > > > > planning to just fork Storm to get an updated version into > > > > > > production. > > > > > > > > > > > > If we want to prevent that and Storm should really be put into > > > > > > maintenance mode, then we should urgently take care of > > > > > > expanding > > > > > > the PMC/Committers circle, so that we are able to put out > > > > > > timely > > > > > > releases again and the work regarding maintenance is > > > > > > distributed on > > > > > > more than just 2 shoulders. > > > > > > > > > > > > Don't take it as a rant, it's just my opinion as someone who > > > > > > runs a > > > > > > Storm Cluster in production and would love to help the project > > > > > > to > > > > > > sustain. > > > > > > > > > > > > Gruß > > > > > > Richard > > > > > > > > > > > > On 2023/05/02 12:58:00 Richard Zowalla wrote: > > > > > > > Any updates? :-) > > > > > > > > > > > > > > Think Storm would benefit from a new release soon... > > > > > > > > > > > > > > Am Mittwoch, dem 22.02.2023 um 18:02 -0500 schrieb P. Taylor > > > > > > > Goetz: > > > > > > > > Quick update: > > > > > > > > > > > > > > > > The ASF Board voted to accept both our report and the > > > > > > > > resolution to > > > > > > > > change PMC Chair. Board feedback on our report was > > > > > > > > positive. > > > > > > > > > > > > > > > > The next step is to expand the the PMC/Committers group. > > > > > > > > Official > > > > > > > > votes will necessarily be private, but I see no reason > > > > > > > > nominations > > > > > > > > can’t be public. > > > > > > > > > > > > > > > > So lets open a thread to talk about adding new contributors > > > > > > > > to > > > > > > > > the > > > > > > > > PMC. Feel free to: > > > > > > > > > > > > > > > > 1. Volunteer to support the project as a PMC > > > > > > > > Member/Committer.. > > > > > > > > 2. Nominate someone become PMC/Committer > > > > > > > > > > > > > > > > I have a few candidates in mind, and will follow up > > > > > > > > accordingly. > > > > > > > > Votes for new members will be private, but successful votes > > > > > > > > for > > > > > > > > new > > > > > > > > members will be announced on the public lists. > > > > > > > > > > > > > > > > One important way to
Re: [PR Review] Support for declaring WorkerHook in Flux topology definitions
Hey, Just an update on the Apache JIRA account. I was able to get the access with help from us...@infra.apache.org. Requesting existing maintainers to please add me to the relevant user group for being able to get the JIRA assigned to myself going forward. (I have create ticket and comment permission only) Also, thanks a lot @bipin for approving the github workflow. (It would be great if I could please get the access as well. I want to trigger it for other PRs too) Since the workflow tests have passed and relevant test cases were also added, could someone please help review the PR. Also, please let me know the process to back-port this feature to the 1.x branch. Majorly my question is around if we can release new features under that branch or are we restricting new releases on that branch strictly for security fixes only. If there is no issue in back-porting some features on demand, I will submit a separate PR for 1.x branch which contains relevant changes for WorkerHook. On Sun, Jun 18, 2023 at 3:34 PM 6harat wrote: > Hey, > > I submitted a PR for review yesterday and am looking for some help from > existing contributors regarding the below: > > 1. new JIRA ticket for the feature (and if someone can also approve my > JIRA account creation request if they are one of the approvers) > 2. trigger the github workflow: https://github.com/apache/storm/pull/3546 > (I already ran the test locally on my machine) > 3. provide PR review comments > > (attached the related mail from users mailing list) > > Regards > 6harat > -- 6harat solr enthusiast [not affiliated to core dev team]
Re: [DISCUSS] Call for PMC Members and Contributors
I would urge PMC Chair to give us some guidance on this. Sent from Yahoo Mail for iPhone On Tuesday, June 20, 2023, 8:32 AM, 6harat wrote: Hey, Just wanted to follow-up on the thread initiated by Richard, if there were any updates from the PMC circle that can be shared with the wider audience. Also, curious about if we have any previous roadmap available for the further evolution of the project. (I checked on JIRA but wasn't able to find one) I would be interested to help contribute to the project in any way possible out of my personal capacity. (Have used Storm in the enterprise environment for many years) I would suggest if the PMC circle can syncup over google meet / zoom along with interested new folks and help decide the way forward. Please let us know your thoughts on the same. Regards 6harat On Mon, Jun 19, 2023 at 12:37 PM Richard Zowalla wrote: > Don't want to come across as an annoying user, but have we made any > progress in this area yet? Everyone who has expressed interest > (usually) doesn't have read access to private@, so no one knows what > the current status is regarding the continuation of the project by > expanding the committer / pmc circle. CC'ing private@, so we can > hopefully get an update. > > I am asking because I read about the intention to cut a storm 2.5.0 > release and I am wondering, if we get the necessary votes in a timely > manner. > > Gruß > Richard > > Am Montag, dem 12.06.2023 um 12:06 +0200 schrieb Alexandre > Vermeerbergen: > > +1 > > > > Le lun. 12 juin 2023 à 11:57, Richard Zowalla a > > écrit : > > > > > > Some weeks passed, any updates? > > > > > > Gruß > > > Richard > > > > > > Am Donnerstag, dem 11.05.2023 um 19:16 -0400 schrieb P. Taylor > > > Goetz: > > > > Thanks for the reminder Richard, > > > > > > > > In response, I’ve bumped the PMC-private discussion around adding > > > > new > > > > members interested in contributing. > > > > > > > > - Taylor > > > > > > > > > On May 11, 2023, at 8:39 AM, Richard Zowalla > > > > > wrote: > > > > > > > > > > Hello, > > > > > > > > > > I know we are all busy with our day jobs, but is there any > > > > > news? > > > > > > > > > > We had some activity after a move to the attic was proposed. In > > > > > the > > > > > process, a few people volunteered to help with the project. > > > > > > > > > > A few weeks later, IMHO we are back to where we were before the > > > > > proposal. Mails are going nowhere and I've heard of a few > > > > > people > > > > > planning to just fork Storm to get an updated version into > > > > > production. > > > > > > > > > > If we want to prevent that and Storm should really be put into > > > > > maintenance mode, then we should urgently take care of > > > > > expanding > > > > > the PMC/Committers circle, so that we are able to put out > > > > > timely > > > > > releases again and the work regarding maintenance is > > > > > distributed on > > > > > more than just 2 shoulders. > > > > > > > > > > Don't take it as a rant, it's just my opinion as someone who > > > > > runs a > > > > > Storm Cluster in production and would love to help the project > > > > > to > > > > > sustain. > > > > > > > > > > Gruß > > > > > Richard > > > > > > > > > > On 2023/05/02 12:58:00 Richard Zowalla wrote: > > > > > > Any updates? :-) > > > > > > > > > > > > Think Storm would benefit from a new release soon... > > > > > > > > > > > > Am Mittwoch, dem 22.02.2023 um 18:02 -0500 schrieb P. Taylor > > > > > > Goetz: > > > > > > > Quick update: > > > > > > > > > > > > > > The ASF Board voted to accept both our report and the > > > > > > > resolution to > > > > > > > change PMC Chair. Board feedback on our report was > > > > > > > positive. > > > > > > > > > > > > > > The next step is to expand the the PMC/Committers group. > > > > > > > Official > > > > > > > votes will necessarily be private, but I see no reason > > > > > > > nominations > > > > > > > can’t be public. > > > > > > > > > > > > > > So lets open a thread to talk about adding new contributors > > > > > > > to > > > > > > > the > > > > > > > PMC. Feel free to: > > > > > > > > > > > > > > 1. Volunteer to support the project as a PMC > > > > > > > Member/Committer.. > > > > > > > 2. Nominate someone become PMC/Committer > > > > > > > > > > > > > > I have a few candidates in mind, and will follow up > > > > > > > accordingly. > > > > > > > Votes for new members will be private, but successful votes > > > > > > > for > > > > > > > new > > > > > > > members will be announced on the public lists. > > > > > > > > > > > > > > One important way to contribute is to volunteer as a > > > > > > > release > > > > > > > manager > > > > > > > for any given release, even if we release infrequently > > > > > > > (e.g. > > > > > > > only in > > > > > > > response to a serious bug or security issue. I don’t have > > > > > > > the > > > > > > > bandwidth to act in that role, though I will commit to > > > > > > > support > > > > > > > voting > > > > > > > on releases,
Re: [DISCUSS] Call for PMC Members and Contributors
Hey, Just wanted to follow-up on the thread initiated by Richard, if there were any updates from the PMC circle that can be shared with the wider audience. Also, curious about if we have any previous roadmap available for the further evolution of the project. (I checked on JIRA but wasn't able to find one) I would be interested to help contribute to the project in any way possible out of my personal capacity. (Have used Storm in the enterprise environment for many years) I would suggest if the PMC circle can syncup over google meet / zoom along with interested new folks and help decide the way forward. Please let us know your thoughts on the same. Regards 6harat On Mon, Jun 19, 2023 at 12:37 PM Richard Zowalla wrote: > Don't want to come across as an annoying user, but have we made any > progress in this area yet? Everyone who has expressed interest > (usually) doesn't have read access to private@, so no one knows what > the current status is regarding the continuation of the project by > expanding the committer / pmc circle. CC'ing private@, so we can > hopefully get an update. > > I am asking because I read about the intention to cut a storm 2.5.0 > release and I am wondering, if we get the necessary votes in a timely > manner. > > Gruß > Richard > > Am Montag, dem 12.06.2023 um 12:06 +0200 schrieb Alexandre > Vermeerbergen: > > +1 > > > > Le lun. 12 juin 2023 à 11:57, Richard Zowalla a > > écrit : > > > > > > Some weeks passed, any updates? > > > > > > Gruß > > > Richard > > > > > > Am Donnerstag, dem 11.05.2023 um 19:16 -0400 schrieb P. Taylor > > > Goetz: > > > > Thanks for the reminder Richard, > > > > > > > > In response, I’ve bumped the PMC-private discussion around adding > > > > new > > > > members interested in contributing. > > > > > > > > - Taylor > > > > > > > > > On May 11, 2023, at 8:39 AM, Richard Zowalla > > > > > wrote: > > > > > > > > > > Hello, > > > > > > > > > > I know we are all busy with our day jobs, but is there any > > > > > news? > > > > > > > > > > We had some activity after a move to the attic was proposed. In > > > > > the > > > > > process, a few people volunteered to help with the project. > > > > > > > > > > A few weeks later, IMHO we are back to where we were before the > > > > > proposal. Mails are going nowhere and I've heard of a few > > > > > people > > > > > planning to just fork Storm to get an updated version into > > > > > production. > > > > > > > > > > If we want to prevent that and Storm should really be put into > > > > > maintenance mode, then we should urgently take care of > > > > > expanding > > > > > the PMC/Committers circle, so that we are able to put out > > > > > timely > > > > > releases again and the work regarding maintenance is > > > > > distributed on > > > > > more than just 2 shoulders. > > > > > > > > > > Don't take it as a rant, it's just my opinion as someone who > > > > > runs a > > > > > Storm Cluster in production and would love to help the project > > > > > to > > > > > sustain. > > > > > > > > > > Gruß > > > > > Richard > > > > > > > > > > On 2023/05/02 12:58:00 Richard Zowalla wrote: > > > > > > Any updates? :-) > > > > > > > > > > > > Think Storm would benefit from a new release soon... > > > > > > > > > > > > Am Mittwoch, dem 22.02.2023 um 18:02 -0500 schrieb P. Taylor > > > > > > Goetz: > > > > > > > Quick update: > > > > > > > > > > > > > > The ASF Board voted to accept both our report and the > > > > > > > resolution to > > > > > > > change PMC Chair. Board feedback on our report was > > > > > > > positive. > > > > > > > > > > > > > > The next step is to expand the the PMC/Committers group. > > > > > > > Official > > > > > > > votes will necessarily be private, but I see no reason > > > > > > > nominations > > > > > > > can’t be public. > > > > > > > > > > > > > > So lets open a thread to talk about adding new contributors > > > > > > > to > > > > > > > the > > > > > > > PMC. Feel free to: > > > > > > > > > > > > > > 1. Volunteer to support the project as a PMC > > > > > > > Member/Committer.. > > > > > > > 2. Nominate someone become PMC/Committer > > > > > > > > > > > > > > I have a few candidates in mind, and will follow up > > > > > > > accordingly. > > > > > > > Votes for new members will be private, but successful votes > > > > > > > for > > > > > > > new > > > > > > > members will be announced on the public lists. > > > > > > > > > > > > > > One important way to contribute is to volunteer as a > > > > > > > release > > > > > > > manager > > > > > > > for any given release, even if we release infrequently > > > > > > > (e.g. > > > > > > > only in > > > > > > > response to a serious bug or security issue. I don’t have > > > > > > > the > > > > > > > bandwidth to act in that role, though I will commit to > > > > > > > support > > > > > > > voting > > > > > > > on releases, etc. Ideally we would want at least two folks > > > > > > > ready to > > > > > > > step into that role, but we can get by with one if > > > > > > >
[GitHub] [storm] 6harat commented on pull request #3547: [STORM-3925] Allow user resources (in WorkerTopologyContext) to be set by Worker Hooks
6harat commented on PR #3547: URL: https://github.com/apache/storm/pull/3547#issuecomment-1599002790 Pending tasks: 1. Add feature tests 2. Update documentation / comments -- 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
