RE: Re: Move Azure, AWS, GCE to the ignite-extensions

Thank you it will very help us > Hello Stephen, > > I'm planning to release the extensions soon. Tests are OK, however, > some TC Suites still need to be configured. > > On Wed, 26 Jan 2022 at 21:07, Stephen Darlington > wrote: > > > > Do we know what happened with this thread? I just saw a

Re: Move Azure, AWS, GCE to the ignite-extensions

Hello Stephen, I'm planning to release the extensions soon. Tests are OK, however, some TC Suites still need to be configured. On Wed, 26 Jan 2022 at 21:07, Stephen Darlington wrote: > > Do we know what happened with this thread? I just saw a question in the user > list asking about where the

Re: Move Azure, AWS, GCE to the ignite-extensions

Do we know what happened with this thread? I just saw a question in the user list asking about where the ignite-aws-ext module is now that Ignite 2.12 is out. Regards, Stephen > On 24 Nov 2021, at 11:11, Maxim Muzafarov wrote: > > Petr, > > There is only the GCE suite left to be configured.

Re: Move Azure, AWS, GCE to the ignite-extensions

Petr, There is only the GCE suite left to be configured. I've created an issue [1] to do this. Please, take a look. [1] https://issues.apache.org/jira/browse/IGNITE-15981 On Wed, 24 Nov 2021 at 12:00, Petr Ivanov wrote: > > Hi, Maksim. > > > Can you file a ticket about recreating test suites

Re: Move Azure, AWS, GCE to the ignite-extensions

Hi, Maksim. Can you file a ticket about recreating test suites for extensions, please? I will attend to it in nearest time. > On 23 Nov 2021, at 17:14, Maxim Muzafarov wrote: > > Hello Petr, > > Can you assist me with configuring the GCE [1] suite on the TC > Extensions project? Currently,

Re: Move Azure, AWS, GCE to the ignite-extensions

Hello Petr, Can you assist me with configuring the GCE [1] suite on the TC Extensions project? Currently, I have an issue with moving environment variables from the old GCE suite [2] to the new one. I need to create the following envs: - env.test.gce.account.id - env.test.gce.p12.path -

Re: Move Azure, AWS, GCE to the ignite-extensions

Folks, I've moved the azure, gce, aws modules to the ignite-extensions project. https://issues.apache.org/jira/browse/IGNITE-15541 Building the modules in the ignite-extension project will prepare an appropriate release zip file containing all the necessary dependencies: - ignite-aws-ext.zip -

Re: Move Azure, AWS, GCE to the ignite-extensions

Okay, I phrased that badly. I mean an extra platform-specific ZIP file that I used to augment the generic Ignite ZIP file. So, to run on Azure I’d download ignite.zip + azure.zip. Extending ignite.sh would also be great, kind of like what’s happening with Ignite 3 as far as I can tell. What

Re: Move Azure, AWS, GCE to the ignite-extensions

Our self-contained zip file currently is over 400Mb and continues to grow. Even considering that internet speeds has grown too, it is nonsense to force user to download such an archive where 90% are useless for most cases. Also we can: — pack all extensions in single binary with latests

Re: Move Azure, AWS, GCE to the ignite-extensions

Having extensions in Maven Central makes perfect sense for tools that need to be built and integrated with other code, Spring integrations for example. That’s not the case for extensions that are required just to run Ignite. A self-contained zip file for each platform would work. > On 13 Oct

Re: Move Azure, AWS, GCE to the ignite-extensions

Nikolay, All extensions will be available at the maven central for download. Previously extensions have a dependent version on the ignite core, so each time the Ignite was released it made sense to include all the extensions into the uber-zip file. Each extension has its own release version now,

Re: Move Azure, AWS, GCE to the ignite-extensions

Maxim. > Currently, they are copied from the optional > directory of the ignite binary package but would be copied from an > appropriate ignite extension binary package. But how, the user will download this binary package? Right now, all the user need is Ignite distributive. > 13 окт. 2021 г.,

Re: Move Azure, AWS, GCE to the ignite-extensions

Stephen, I guess the required classes of IP-finders should be in the classpath (libs directory). Currently, they are copied from the optional directory of the ignite binary package but would be copied from an appropriate ignite extension binary package. Probably I'm missing something but almost

Re: Move Azure, AWS, GCE to the ignite-extensions

I understand the motivation from a development point of view, but how will this work for end users? Currently, the documentation talks about extensions only in terms of importing maven dependencies (download.cgi ). If I’m trying to start a

Re: Move Azure, AWS, GCE to the ignite-extensions

+1 Those parts still very optional nowadays. > On 20 Sep 2021, at 15:29, Maxim Muzafarov wrote: > > Folks, > > > I've created an issue [1] to move all cloud-based IP-finders to the > ignite-extensions. The motivation is the same as with migration of > Spring Data integration - to remove

Re: Move Azure, AWS, GCE to the ignite-extensions

+1 to migrate and include to the Ignite 2.12 scope пн, 20 сент. 2021 г. в 17:09, Denis Magda : > > Perfect, thanks, Maxim! > > - > Denis > > > On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov wrote: > > > Folks, > > > > > > I've created an issue [1] to move all cloud-based IP-finders to the > >

Re: Move Azure, AWS, GCE to the ignite-extensions

Perfect, thanks, Maxim! - Denis On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov wrote: > Folks, > > > I've created an issue [1] to move all cloud-based IP-finders to the > ignite-extensions. The motivation is the same as with migration of > Spring Data integration - to remove integration

Move Azure, AWS, GCE to the ignite-extensions

Folks, I've created an issue [1] to move all cloud-based IP-finders to the ignite-extensions. The motivation is the same as with migration of Spring Data integration - to remove integration dependency of the release cycle on Ignite releases. [1]