[ANNOUNCE] New Apache Ignite PMC member: Igor Sapego
Hello Ignite Community, The Project Management Committee (PMC) for Apache Ignite has invited Igor Sapego to join the PMC as a new member and we are pleased to announce that he has accepted. Igor is an active Community member for a long time. He made a worthless contribution in Ignite C++ development and continues to do it today. Moreover he drives thin clients development for other programming languages. Additionally, always helpful on users mailing list. Wrote blog posts and spoke publicly about Ignite. Being a PMC member enables assistance with the management and to guide the direction of the project. Please join me in congratulating Igor! Best regards, Ivan Pavlukhin on behalf of Apache Ignite PMC
Re: IGNITE-12361 Migrate Flume module to ignite-extensions
Hi Alexey, As discussed I have updated the wiki with agreed solution. Independent Integrations: https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations Discussion Links: https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-DiscussionLinks Tickets: https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-Tickets Please let me know if I can share more information. Regards, Saikat On Fri, Jan 17, 2020 at 9:16 PM Saikat Maitra wrote: > Hello Alexey, > > Thank you for your email. > > 1. Yes, we discussed in dev list and agreed on creating a new repository > for hosting our Ignite integrations. Please find the discussion thread > below. I will update the wiki page as well and share updates. > > > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html > > 2. I was hoping to complete migration of the following modules before we > go ahead with release. I am tracking the jira story here > https://issues.apache.org/jira/browse/IGNITE-12355 > >- Flink >- Twitter >- Storm >- ZeroMQ >- RocketMQ >- Flume >- MQTT >- Camel >- JMS > > 3. The dependencies for modules are pointing to latest snapshot of ignite > project and if there are changes in ignite master branch then related > affected Ignite extensions module also need to be modified. We will verify > all the extensions for upcoming release but release only the one that are > impacted. We will plan to avoid publishing any extension unless there are > changes. Here is the discussion thread on release process: > > > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-dependencies-and-release-process-for-Ignite-Extensions-td44478.html > > 4. Sounds good, we can maintain a compatibility matrix to ensure we can > share Ignite Core and related Ignite Extensions. I have seen something > similar in Apache Beam and we can also create a similar wiki page to > maintain Ignite Core and Ignite Extensions dependencies > > https://beam.apache.org/documentation/runners/capability-matrix/ > > Regards, > Saikat > > > > On Fri, Jan 17, 2020 at 6:27 AM Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > >> Saikat, >> >> Code-wise the PR looks ok because it basically moves the module to another >> repo. I have some infrastructure/process questions though before we merge >> the PRs >> * I see that there are some objections from Alexey Zinoviev [1] on >> whether >> the streaming modules should be placed in extensions or in a separate >> streaming project. Sorry if I missed the corresponding discussion on the >> dev-list. If there is one, we need to edit the IEP page, if not, I think >> we >> should come to a consensus before making this change >> * When are we planning to release the extensions? Are we going to release >> them one-by-one incrementally or do we want to release them in one batch? >> * Now that the release lifecycle of Ignite and extensions is split, we >> need to understand how this is going to be tested. Will we run a candidate >> Ignite build against already released extensions? What if we make changes >> to both Ignite and an extension? Is it even allowed, or do we need to wait >> for an Ignite release before making any changes in an extension? >> * I think there should be some sort of compatibility matrix now that >> releases of Ignite and extensions are separated >> >> I would not delete the extension from Ignite codebase until we agree on >> the >> points above. >> >> Would you mind taking care of the discussion about it and formalizing it >> on >> the wiki? >> >> чт, 16 янв. 2020 г. в 06:27, Saikat Maitra : >> >> > Hi Denis, Alexey >> > >> > Thank you so much for your email. I really appreciate it. >> > >> > Regards, >> > Saikat >> > >> > On Wed, Jan 15, 2020 at 4:11 AM Alexey Goncharuk < >> > alexey.goncha...@gmail.com> >> > wrote: >> > >> > > Saikat, >> > > >> > > Thanks for working on this! I'll do my best to take a look at it this >> > week. >> > > >> > > --AG >> > > >> > > пн, 13 янв. 2020 г. в 21:37, Denis Magda : >> > > >> > > > Alex Goncharuk, Nikolay Izhikov, >> > > > >> > > > Could you possibly check the changes or suggest any other >> > > > committer/contributor for that? >> > > > >> > > > - >> > > > Denis >> > > > >> > > > >> > > > On Sun, Jan 12, 2020 at 9:31 AM Saikat Maitra < >> saikat.mai...@gmail.com >> > > >> > > > wrote: >> > > > >> > > >> Hello, >> > > >> >> > > >> These PRs are part of Modularization effort >> > > >> >> > > >> >> > > >> > >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations >> > > >> >> > > >> If the changes looks good, I can go ahead and merge the changes. >> > > >> >> > > >> Regards, >> > > >> Saikat >> > > >> >> > > >> On Sun, Jan 5, 2020 at 1:08
Task to implement: IGNITE-12581
Hi everyone. How do you think, can I start this task: https://issues.apache.org/jira/projects/IGNITE/issues/IGNITE-12581 ? It looks useful and seems good for a newbie to begin researching the code and test techniques.
Re: AWS EBS Discovery: Contributor Wanted
Hi all! I do believe being able to execute some AWS integration tests on demand would be of value, especially for reviewers who cannot have an AWS stack created on demand. More than happy to help on that. Kind regards *Emmanouil Gkatziouras* https://egkatzioura.com/ | https://www.linkedin.com/in/gkatziourasemmanouil/ https://github.com/gkatzioura On Fri, 24 Jan 2020 at 15:15, Sergey Chugunov wrote: > Hello Emmanouil, > > It would be great if we have at least basic integration tests in real AWS > environment. Even though they may require more work to keep them green (I > mean here AWS quotas and additional configuration/reconfiguration efforts) > it worth it because these tests can also be useful as an examples. > > As the same time as IpFinder is such a basic component I don't think we > need to include them in constantly triggered suites like Run All but to > trigger them manually before/right after merging them to master branch or > when developing something in related code. > > What do you think? > > -- > Thank you, > Sergey Chugunov. > > On Thu, Jan 23, 2020 at 5:32 PM Emmanouil Gkatziouras < > gkatzio...@gmail.com> > wrote: > > > Hi all! > > > > Yes It seems possible to get some free quota for integration tests on AWS > > [1] however most probably they are not gonna last forever. > > > > [1] > > > > > https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/ > > > > King Regards > > *Emmanouil Gkatziouras* > > https://egkatzioura.com/ | > > https://www.linkedin.com/in/gkatziourasemmanouil/ > > https://github.com/gkatzioura > > > > > > On Wed, 22 Jan 2020 at 16:48, Denis Magda wrote: > > > > > Hi Emmanouil, > > > > > > Thanks for preparing a pull-request for Application Load Balancer: > > > https://issues.apache.org/jira/browse/IGNITE-8617 > > > > > > Igniters, who is willing to step in as a primary reviewer? > > > > > > As for automated testing on AWS, are you aware of any sponsorship > program > > > of AWS for open source projects of our kind? It will be ideal to have > > real > > > testing on AWS but someone needs to pay. > > > > > > - > > > Denis > > > > > > > > > On Sun, Jan 19, 2020 at 6:45 AM Emmanouil Gkatziouras < > > > gkatzio...@gmail.com> > > > wrote: > > > > > > > Hi all! > > > > > > > > I have spinned up an Application Load Balancer and an autoscaling > group > > > on > > > > AWS and the Ignite discovery using TcpDiscoveryAlbIpFinder works as > > > > expected. > > > > > > > >- On startup nodes discover each other. > > > >- On ec2 node down, connection is lost and the cluster decreases. > > > >- On an extra node addition the cluster size increases > > > > > > > > This contribution is essential since the Previous ELB based discovery > > > uses > > > > the Classic Load Balancer which is still available however > > > > AWS advices users to use the Application one. [1] > > > > While my pull request gets reviewed I will also have a look at > > > > the IGNITE-12398 [2] issue which has to do with the S3 discovery. > > > > Another idea would also be to implement a `TCP Load Balancer based` > > > > discovery. > > > > > > > > In order to test this issue and future ones I implemented some > > terraform > > > > scripts (which I shall use for other issues too) [3]. > > > > If some automated e2e testing on AWS is being considered they might > be > > of > > > > value. > > > > I can help on implementing those tests by provisioning the > > infrastructure > > > > in an automated way and validate the discovery. > > > > > > > > [1] > > > > > > > > > > > > > > https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/migrate-to-application-load-balancer.html > > > > [2] https://issues.apache.org/jira/browse/IGNITE-12398 > > > > [3] https://github.com/gkatzioura/ignite-aws-deploy > > > > > > > > Kind regards, > > > > *Emmanouil Gkatziouras* > > > > https://egkatzioura.com/ | > > > > https://www.linkedin.com/in/gkatziourasemmanouil/ > > > > https://github.com/gkatzioura > > > > > > > > > > > > On Tue, 14 Jan 2020 at 22:22, Denis Magda wrote: > > > > > > > > > Hi Emmanouil, > > > > > > > > > > Agree, let's check that the IP finder functions normally in the > cloud > > > > > environment and the mock tests can be used for regular testing on > > Team > > > > > City. That's the way we tested other environment-specific IP > finders > > > > > including the Kubernetes one. > > > > > > > > > > Let us know once the IP finder is tested on AWS and then we can > > proceed > > > > > with the review. > > > > > > > > > > - > > > > > Denis > > > > > > > > > > > > > > > On Tue, Jan 14, 2020 at 2:47 AM Emmanouil Gkatziouras < > > > > > gkatzio...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi all! > > > > > > > > > > > > With regards to the `Node Discovery Using AWS Application ELB` > > issue > > > > [1] > > > > > > I made this pull request to fix the merge conflicts [2]. > > > > > > Will also check if the concerns described on the mailing list > topic > > > > > >
