Petr, thanks, There is also a collection of modules located in our extensions repository: https://github.com/apache/ignite-extensions
@Saikat Maitra <saikat.mai...@gmail.com> is migrating all our existing integrations to that repository and, once this is done, the extensions will be released to Maven separately. Is it reasonable to expand the scope of the IEP-52 and contemplate on how to install those extensions? - Denis On Thu, Aug 27, 2020 at 3:40 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Petr, > > The proposal makes sense to me - thanks for starting the discussion. > Current installation and upgrade procedures involve a lot of manual steps > and quite error-prone, we need to automate and simplify them as much as > possible. > > I believe we eventually should end up with a unified command-line tool > (ignitectl?) that will incorporate all the operations (enable/disable > modules, start/stop, configuration updates, activation, baseline, etc.). > This IEP is a step in this direction. > > Looking forward to testing a prototype :) > > -Val > > On Thu, Aug 27, 2020 at 2:17 AM Petr Ivanov <mr.wei...@gmail.com> wrote: > > > Hi, Igniters! > > > > > > For Apache Ignite 3.0 I would like to propose vision of enhanced delivery > > and upgrade processes [1]. > > The key idea is to make main binary as slim as possible (delivering every > > optional component by demand only) while providing way to run each new > > version seamlessly without much of the efforts migrating data and > > configuration between upgrades. > > > > I plan to create prototype based on current release of Apache Ignite > > (2.8.1 or 2.9.0 if it will be released soon) later in September. > > > > > > > > [1] > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158873958 > > > > >
