[DISCUSSION] Ignite WebConsole Deprecation

[dmagda]

Igniters,

I would like to hear your opinion on what we should do with Ignite
WebConsole.

To my knowledge, we don't have active maintainers of the component, and a
list of issues is piling up [1]. Users even report that the docker images
have not been updated for more than a year [2].

Personally, I share the opinion of those who believe the community needs to
provide and support all the essential tooling (metrics and tracing API,
command-line tool) while the UI tools are not our business. There is a
myriad of UI tools Ignite can be monitored and traced with. Users already
have plenty of choices.

What are your thoughts? Probably, some of you want to become maintainers of
the component. Otherwise, we should let the tool go.

[1]
https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
[2] https://issues.apache.org/jira/browse/IGNITE-12923

-
Denis

[Saikat Maitra]

Hello Denis,

I am thinking if we should move web-console to a separate repo like
ignite-web-console. In my opinion the tech stack we have in web-console
like npm, nodejs and Mondodb etc are little different and can be hosted as
a separate project in a git repo.

I had used web-console for streamers project and found it helpful in
creating table schema and execute sql queries and also to do cache lookup.

https://github.com/samaitra/streamers

If we continue to find that usage of ignite-web-console is limited then we
can plan moving ignite-web-console in Apache Attic

https://attic.apache.org/

Please let me know your thoughts.

Regards,
Saikat



On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]> wrote:

> Igniters,
>
> I would like to hear your opinion on what we should do with Ignite
> WebConsole.
>
> To my knowledge, we don't have active maintainers of the component, and a
> list of issues is piling up [1]. Users even report that the docker images
> have not been updated for more than a year [2].
>
> Personally, I share the opinion of those who believe the community needs to
> provide and support all the essential tooling (metrics and tracing API,
> command-line tool) while the UI tools are not our business. There is a
> myriad of UI tools Ignite can be monitored and traced with. Users already
> have plenty of choices.
>
> What are your thoughts? Probably, some of you want to become maintainers of
> the component. Otherwise, we should let the tool go.
>
> [1]
>
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> [2] https://issues.apache.org/jira/browse/IGNITE-12923
>
> -
> Denis
>

[Nikolay Izhikov-2]

Hello.

+1 to remove any graphical utilities from the Ignite core.
I think we should maintain and support only cmd, JMX, and other «core» tools.

We shouldn't waste our resources on supporting pretty looking UI tools.

> 2 мая 2020 г., в 04:05, Saikat Maitra <[hidden email]> написал(а):
>
> Hello Denis,
>
> I am thinking if we should move web-console to a separate repo like
> ignite-web-console. In my opinion the tech stack we have in web-console
> like npm, nodejs and Mondodb etc are little different and can be hosted as
> a separate project in a git repo.
>
> I had used web-console for streamers project and found it helpful in
> creating table schema and execute sql queries and also to do cache lookup.
>
> https://github.com/samaitra/streamers
>
> If we continue to find that usage of ignite-web-console is limited then we
> can plan moving ignite-web-console in Apache Attic
>
> https://attic.apache.org/
>
> Please let me know your thoughts.
>
> Regards,
> Saikat
>
>
>
> On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]> wrote:
>
>> Igniters,
>>
>> I would like to hear your opinion on what we should do with Ignite
>> WebConsole.
>>
>> To my knowledge, we don't have active maintainers of the component, and a
>> list of issues is piling up [1]. Users even report that the docker images
>> have not been updated for more than a year [2].
>>
>> Personally, I share the opinion of those who believe the community needs to
>> provide and support all the essential tooling (metrics and tracing API,
>> command-line tool) while the UI tools are not our business. There is a
>> myriad of UI tools Ignite can be monitored and traced with. Users already
>> have plenty of choices.
>>
>> What are your thoughts? Probably, some of you want to become maintainers of
>> the component. Otherwise, we should let the tool go.
>>
>> [1]
>>
>> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
>> [2] https://issues.apache.org/jira/browse/IGNITE-12923
>>
>> -
>> Denis
>>

[slava.koptilin]

Hello,

+1 to remove this component or move it to a separate repository if someone
wants to maintain it.
In case the web console provides useful features, we should consider how to
add them to our command-line utilities, if possible.

Thanks,
Slava.

ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov <[hidden email]>:

> Hello.
>
> +1 to remove any graphical utilities from the Ignite core.
> I think we should maintain and support only cmd, JMX, and other «core»
> tools.
>
> We shouldn't waste our resources on supporting pretty looking UI tools.
>
>
> > 2 мая 2020 г., в 04:05, Saikat Maitra <[hidden email]>
> написал(а):
> >
> > Hello Denis,
> >
> > I am thinking if we should move web-console to a separate repo like
> > ignite-web-console. In my opinion the tech stack we have in web-console
> > like npm, nodejs and Mondodb etc are little different and can be hosted
> as
> > a separate project in a git repo.
> >
> > I had used web-console for streamers project and found it helpful in
> > creating table schema and execute sql queries and also to do cache
> lookup.
> >
> > https://github.com/samaitra/streamers
> >
> > If we continue to find that usage of ignite-web-console is limited then
> we
> > can plan moving ignite-web-console in Apache Attic
> >
> > https://attic.apache.org/
> >
> > Please let me know your thoughts.
> >
> > Regards,
> > Saikat
> >
> >
> >
> > On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]> wrote:
> >
> >> Igniters,
> >>
> >> I would like to hear your opinion on what we should do with Ignite
> >> WebConsole.
> >>
> >> To my knowledge, we don't have active maintainers of the component, and
> a
> >> list of issues is piling up [1]. Users even report that the docker
> images
> >> have not been updated for more than a year [2].
> >>
> >> Personally, I share the opinion of those who believe the community
> needs to
> >> provide and support all the essential tooling (metrics and tracing API,
> >> command-line tool) while the UI tools are not our business. There is a
> >> myriad of UI tools Ignite can be monitored and traced with. Users
> already
> >> have plenty of choices.
> >>
> >> What are your thoughts? Probably, some of you want to become
> maintainers of
> >> the component. Otherwise, we should let the tool go.
> >>
> >> [1]
> >>
> >>
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> >> [2] https://issues.apache.org/jira/browse/IGNITE-12923
> >>
> >> -
> >> Denis
> >>
>
>

[dmagda]

Folks,

Personally, I like the idea of Apache Attic [1] suggested by Saikat. We are
not discontinuing Ignite WebConsole because it became useless like it was
with Hadoop Accelerator. The tool has good capabilities such as the
configuration wizard, and the only problem is that we no longer want to
support or maintain this technology (while it has the right to exist).

Is anybody interested in figuring out with the ASF-mates if Ignite
WebConsole can be accepted to Attic? The Attic's guidelines talk about an
ASF project as a whole and not about individual components.

[1] https://attic.apache.org

-
Denis


On Wed, May 6, 2020 at 7:20 AM Вячеслав Коптилин <[hidden email]>
wrote:

> Hello,
>
> +1 to remove this component or move it to a separate repository if someone
> wants to maintain it.
> In case the web console provides useful features, we should consider how to
> add them to our command-line utilities, if possible.
>
> Thanks,
> Slava.
>
> ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov <[hidden email]>:
>
> > Hello.
> >
> > +1 to remove any graphical utilities from the Ignite core.
> > I think we should maintain and support only cmd, JMX, and other «core»
> > tools.
> >
> > We shouldn't waste our resources on supporting pretty looking UI tools.
> >
> >
> > > 2 мая 2020 г., в 04:05, Saikat Maitra <[hidden email]>
> > написал(а):
> > >
> > > Hello Denis,
> > >
> > > I am thinking if we should move web-console to a separate repo like
> > > ignite-web-console. In my opinion the tech stack we have in web-console
> > > like npm, nodejs and Mondodb etc are little different and can be hosted
> > as
> > > a separate project in a git repo.
> > >
> > > I had used web-console for streamers project and found it helpful in
> > > creating table schema and execute sql queries and also to do cache
> > lookup.
> > >
> > > https://github.com/samaitra/streamers
> > >
> > > If we continue to find that usage of ignite-web-console is limited then
> > we
> > > can plan moving ignite-web-console in Apache Attic
> > >
> > > https://attic.apache.org/
> > >
> > > Please let me know your thoughts.
> > >
> > > Regards,
> > > Saikat
> > >
> > >
> > >
> > > On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]> wrote:
> > >
> > >> Igniters,
> > >>
> > >> I would like to hear your opinion on what we should do with Ignite
> > >> WebConsole.
> > >>
> > >> To my knowledge, we don't have active maintainers of the component,
> and
> > a
> > >> list of issues is piling up [1]. Users even report that the docker
> > images
> > >> have not been updated for more than a year [2].
> > >>
> > >> Personally, I share the opinion of those who believe the community
> > needs to
> > >> provide and support all the essential tooling (metrics and tracing
> API,
> > >> command-line tool) while the UI tools are not our business. There is a
> > >> myriad of UI tools Ignite can be monitored and traced with. Users
> > already
> > >> have plenty of choices.
> > >>
> > >> What are your thoughts? Probably, some of you want to become
> > maintainers of
> > >> the component. Otherwise, we should let the tool go.
> > >>
> > >> [1]
> > >>
> > >>
> >
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> > >> [2] https://issues.apache.org/jira/browse/IGNITE-12923
> > >>
> > >> -
> > >> Denis
> > >>
> >
> >
>

[Ilya Kasnacheev]

Hello!

I think we should move it to a separate repository, but not Attic.

I can see the scenario where there would be recurrence of interest to this
tool and somebody may step in to update it.

Regards,
--
Ilya Kasnacheev


ср, 6 мая 2020 г. в 22:20, Denis Magda <[hidden email]>:

> Folks,
>
> Personally, I like the idea of Apache Attic [1] suggested by Saikat. We are
> not discontinuing Ignite WebConsole because it became useless like it was
> with Hadoop Accelerator. The tool has good capabilities such as the
> configuration wizard, and the only problem is that we no longer want to
> support or maintain this technology (while it has the right to exist).
>
> Is anybody interested in figuring out with the ASF-mates if Ignite
> WebConsole can be accepted to Attic? The Attic's guidelines talk about an
> ASF project as a whole and not about individual components.
>
> [1] https://attic.apache.org
>
> -
> Denis
>
>
> On Wed, May 6, 2020 at 7:20 AM Вячеслав Коптилин <[hidden email]
> >
> wrote:
>
> > Hello,
> >
> > +1 to remove this component or move it to a separate repository if
> someone
> > wants to maintain it.
> > In case the web console provides useful features, we should consider how
> to
> > add them to our command-line utilities, if possible.
> >
> > Thanks,
> > Slava.
> >
> > ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov <[hidden email]>:
> >
> > > Hello.
> > >
> > > +1 to remove any graphical utilities from the Ignite core.
> > > I think we should maintain and support only cmd, JMX, and other «core»
> > > tools.
> > >
> > > We shouldn't waste our resources on supporting pretty looking UI tools.
> > >
> > >
> > > > 2 мая 2020 г., в 04:05, Saikat Maitra <[hidden email]>
> > > написал(а):
> > > >
> > > > Hello Denis,
> > > >
> > > > I am thinking if we should move web-console to a separate repo like
> > > > ignite-web-console. In my opinion the tech stack we have in
> web-console
> > > > like npm, nodejs and Mondodb etc are little different and can be
> hosted
> > > as
> > > > a separate project in a git repo.
> > > >
> > > > I had used web-console for streamers project and found it helpful in
> > > > creating table schema and execute sql queries and also to do cache
> > > lookup.
> > > >
> > > > https://github.com/samaitra/streamers
> > > >
> > > > If we continue to find that usage of ignite-web-console is limited
> then
> > > we
> > > > can plan moving ignite-web-console in Apache Attic
> > > >
> > > > https://attic.apache.org/
> > > >
> > > > Please let me know your thoughts.
> > > >
> > > > Regards,
> > > > Saikat
> > > >
> > > >
> > > >
> > > > On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]>
> wrote:
> > > >
> > > >> Igniters,
> > > >>
> > > >> I would like to hear your opinion on what we should do with Ignite
> > > >> WebConsole.
> > > >>
> > > >> To my knowledge, we don't have active maintainers of the component,
> > and
> > > a
> > > >> list of issues is piling up [1]. Users even report that the docker
> > > images
> > > >> have not been updated for more than a year [2].
> > > >>
> > > >> Personally, I share the opinion of those who believe the community
> > > needs to
> > > >> provide and support all the essential tooling (metrics and tracing
> > API,
> > > >> command-line tool) while the UI tools are not our business. There
> is a
> > > >> myriad of UI tools Ignite can be monitored and traced with. Users
> > > already
> > > >> have plenty of choices.
> > > >>
> > > >> What are your thoughts? Probably, some of you want to become
> > > maintainers of
> > > >> the component. Otherwise, we should let the tool go.
> > > >>
> > > >> [1]
> > > >>
> > > >>
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> > > >> [2] https://issues.apache.org/jira/browse/IGNITE-12923
> > > >>
> > > >> -
> > > >> Denis
> > > >>
> > >
> > >
> >
>

[Dmitry Pavlov]

Hi Igniters,

Only whole project may go to the attic. Main reason of moving project to
the attic is inactive community and less than 3 PMC members voting for new
release.
So attic is more about waiting for new community to resurrect project, and
less about codebase.

I suggest us, as always, create new repo and state that development of the
module was discontinued, for now.

Additionally, discontinuation is essential and really major community-wide
decision, it requires formal vote to be run after this discussion. I'm sure
if we build consensus in advance, here in the discussion, vote would be
just formality, but it is still needed.

Sincerely,
Dmitriy Pavlov


чт, 7 мая 2020 г. в 12:34, Ilya Kasnacheev <[hidden email]>:

> Hello!
>
> I think we should move it to a separate repository, but not Attic.
>
> I can see the scenario where there would be recurrence of interest to this
> tool and somebody may step in to update it.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 6 мая 2020 г. в 22:20, Denis Magda <[hidden email]>:
>
> > Folks,
> >
> > Personally, I like the idea of Apache Attic [1] suggested by Saikat. We
> are
> > not discontinuing Ignite WebConsole because it became useless like it was
> > with Hadoop Accelerator. The tool has good capabilities such as the
> > configuration wizard, and the only problem is that we no longer want to
> > support or maintain this technology (while it has the right to exist).
> >
> > Is anybody interested in figuring out with the ASF-mates if Ignite
> > WebConsole can be accepted to Attic? The Attic's guidelines talk about an
> > ASF project as a whole and not about individual components.
> >
> > [1] https://attic.apache.org
> >
> > -
> > Denis
> >
> >
> > On Wed, May 6, 2020 at 7:20 AM Вячеслав Коптилин <
> [hidden email]
> > >
> > wrote:
> >
> > > Hello,
> > >
> > > +1 to remove this component or move it to a separate repository if
> > someone
> > > wants to maintain it.
> > > In case the web console provides useful features, we should consider
> how
> > to
> > > add them to our command-line utilities, if possible.
> > >
> > > Thanks,
> > > Slava.
> > >
> > > ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov <[hidden email]>:
> > >
> > > > Hello.
> > > >
> > > > +1 to remove any graphical utilities from the Ignite core.
> > > > I think we should maintain and support only cmd, JMX, and other
> «core»
> > > > tools.
> > > >
> > > > We shouldn't waste our resources on supporting pretty looking UI
> tools.
> > > >
> > > >
> > > > > 2 мая 2020 г., в 04:05, Saikat Maitra <[hidden email]>
> > > > написал(а):
> > > > >
> > > > > Hello Denis,
> > > > >
> > > > > I am thinking if we should move web-console to a separate repo like
> > > > > ignite-web-console. In my opinion the tech stack we have in
> > web-console
> > > > > like npm, nodejs and Mondodb etc are little different and can be
> > hosted
> > > > as
> > > > > a separate project in a git repo.
> > > > >
> > > > > I had used web-console for streamers project and found it helpful
> in
> > > > > creating table schema and execute sql queries and also to do cache
> > > > lookup.
> > > > >
> > > > > https://github.com/samaitra/streamers
> > > > >
> > > > > If we continue to find that usage of ignite-web-console is limited
> > then
> > > > we
> > > > > can plan moving ignite-web-console in Apache Attic
> > > > >
> > > > > https://attic.apache.org/
> > > > >
> > > > > Please let me know your thoughts.
> > > > >
> > > > > Regards,
> > > > > Saikat
> > > > >
> > > > >
> > > > >
> > > > > On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]>
> > wrote:
> > > > >
> > > > >> Igniters,
> > > > >>
> > > > >> I would like to hear your opinion on what we should do with Ignite
> > > > >> WebConsole.
> > > > >>
> > > > >> To my knowledge, we don't have active maintainers of the
> component,
> > > and
> > > > a
> > > > >> list of issues is piling up [1]. Users even report that the docker
> > > > images
> > > > >> have not been updated for more than a year [2].
> > > > >>
> > > > >> Personally, I share the opinion of those who believe the community
> > > > needs to
> > > > >> provide and support all the essential tooling (metrics and tracing
> > > API,
> > > > >> command-line tool) while the UI tools are not our business. There
> > is a
> > > > >> myriad of UI tools Ignite can be monitored and traced with. Users
> > > > already
> > > > >> have plenty of choices.
> > > > >>
> > > > >> What are your thoughts? Probably, some of you want to become
> > > > maintainers of
> > > > >> the component. Otherwise, we should let the tool go.
> > > > >>
> > > > >> [1]
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-12923
> > > > >>
> > > > >> -
> > > > >> Denis
> > > > >>
> > > >
> > > >
> > >
> >
>

[dmagda]

Dmitry, thanks for the details.

Then I agree with the proposal of moving the tool to a separate repo and
officially discontinuing its support. The question is should we keep it in
the ASF repo or move to an independent GitHub repo and forget about it?


-
Denis


On Thu, May 7, 2020 at 4:53 AM Dmitriy Pavlov <[hidden email]> wrote:

> Hi Igniters,
>
> Only whole project may go to the attic. Main reason of moving project to
> the attic is inactive community and less than 3 PMC members voting for new
> release.
> So attic is more about waiting for new community to resurrect project, and
> less about codebase.
>
> I suggest us, as always, create new repo and state that development of the
> module was discontinued, for now.
>
> Additionally, discontinuation is essential and really major community-wide
> decision, it requires formal vote to be run after this discussion. I'm sure
> if we build consensus in advance, here in the discussion, vote would be
> just formality, but it is still needed.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> чт, 7 мая 2020 г. в 12:34, Ilya Kasnacheev <[hidden email]>:
>
> > Hello!
> >
> > I think we should move it to a separate repository, but not Attic.
> >
> > I can see the scenario where there would be recurrence of interest to
> this
> > tool and somebody may step in to update it.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > ср, 6 мая 2020 г. в 22:20, Denis Magda <[hidden email]>:
> >
> > > Folks,
> > >
> > > Personally, I like the idea of Apache Attic [1] suggested by Saikat. We
> > are
> > > not discontinuing Ignite WebConsole because it became useless like it
> was
> > > with Hadoop Accelerator. The tool has good capabilities such as the
> > > configuration wizard, and the only problem is that we no longer want to
> > > support or maintain this technology (while it has the right to exist).
> > >
> > > Is anybody interested in figuring out with the ASF-mates if Ignite
> > > WebConsole can be accepted to Attic? The Attic's guidelines talk about
> an
> > > ASF project as a whole and not about individual components.
> > >
> > > [1] https://attic.apache.org
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Wed, May 6, 2020 at 7:20 AM Вячеслав Коптилин <
> > [hidden email]
> > > >
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > +1 to remove this component or move it to a separate repository if
> > > someone
> > > > wants to maintain it.
> > > > In case the web console provides useful features, we should consider
> > how
> > > to
> > > > add them to our command-line utilities, if possible.
> > > >
> > > > Thanks,
> > > > Slava.
> > > >
> > > > ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov <[hidden email]>:
> > > >
> > > > > Hello.
> > > > >
> > > > > +1 to remove any graphical utilities from the Ignite core.
> > > > > I think we should maintain and support only cmd, JMX, and other
> > «core»
> > > > > tools.
> > > > >
> > > > > We shouldn't waste our resources on supporting pretty looking UI
> > tools.
> > > > >
> > > > >
> > > > > > 2 мая 2020 г., в 04:05, Saikat Maitra <[hidden email]>
> > > > > написал(а):
> > > > > >
> > > > > > Hello Denis,
> > > > > >
> > > > > > I am thinking if we should move web-console to a separate repo
> like
> > > > > > ignite-web-console. In my opinion the tech stack we have in
> > > web-console
> > > > > > like npm, nodejs and Mondodb etc are little different and can be
> > > hosted
> > > > > as
> > > > > > a separate project in a git repo.
> > > > > >
> > > > > > I had used web-console for streamers project and found it helpful
> > in
> > > > > > creating table schema and execute sql queries and also to do
> cache
> > > > > lookup.
> > > > > >
> > > > > > https://github.com/samaitra/streamers
> > > > > >
> > > > > > If we continue to find that usage of ignite-web-console is
> limited
> > > then
> > > > > we
> > > > > > can plan moving ignite-web-console in Apache Attic
> > > > > >
> > > > > > https://attic.apache.org/
> > > > > >
> > > > > > Please let me know your thoughts.
> > > > > >
> > > > > > Regards,
> > > > > > Saikat
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]>
> > > wrote:
> > > > > >
> > > > > >> Igniters,
> > > > > >>
> > > > > >> I would like to hear your opinion on what we should do with
> Ignite
> > > > > >> WebConsole.
> > > > > >>
> > > > > >> To my knowledge, we don't have active maintainers of the
> > component,
> > > > and
> > > > > a
> > > > > >> list of issues is piling up [1]. Users even report that the
> docker
> > > > > images
> > > > > >> have not been updated for more than a year [2].
> > > > > >>
> > > > > >> Personally, I share the opinion of those who believe the
> community
> > > > > needs to
> > > > > >> provide and support all the essential tooling (metrics and
> tracing
> > > > API,
> > > > > >> command-line tool) while the UI tools are not our business.
> There
> > > is a
> > > > > >> myriad of UI tools Ignite can be monitored and traced with.
> Users
> > > > > already
> > > > > >> have plenty of choices.
> > > > > >>
> > > > > >> What are your thoughts? Probably, some of you want to become
> > > > > maintainers of
> > > > > >> the component. Otherwise, we should let the tool go.
> > > > > >>
> > > > > >> [1]
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> > > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-12923
> > > > > >>
> > > > > >> -
> > > > > >> Denis
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

[Saikat Maitra]

Hi,

I am thinking we can create a new repo under ASF and move the web-console
module. We can name the repo may be like ignite-web-console or
ignite-tools. The reason for suggesting ASF repo is since the web-console
already has Apache 2.0 license we can continue to maintain same license.
Also keeping it under ASF may encourage new contribution.

We can consider adding a badge as OSS Lifecycle Maintenance similar to as
mentioned in Netflix Hystrix repo.

https://github.com/Netflix/Hystrix

Warm regards,
Saikat





On Fri, May 8, 2020 at 4:53 PM Denis Magda <[hidden email]> wrote:

> Dmitry, thanks for the details.
>
> Then I agree with the proposal of moving the tool to a separate repo and
> officially discontinuing its support. The question is should we keep it in
> the ASF repo or move to an independent GitHub repo and forget about it?
>
>
> -
> Denis
>
>
> On Thu, May 7, 2020 at 4:53 AM Dmitriy Pavlov <[hidden email]> wrote:
>
> > Hi Igniters,
> >
> > Only whole project may go to the attic. Main reason of moving project to
> > the attic is inactive community and less than 3 PMC members voting for
> new
> > release.
> > So attic is more about waiting for new community to resurrect project,
> and
> > less about codebase.
> >
> > I suggest us, as always, create new repo and state that development of
> the
> > module was discontinued, for now.
> >
> > Additionally, discontinuation is essential and really major
> community-wide
> > decision, it requires formal vote to be run after this discussion. I'm
> sure
> > if we build consensus in advance, here in the discussion, vote would be
> > just formality, but it is still needed.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> >
> > чт, 7 мая 2020 г. в 12:34, Ilya Kasnacheev <[hidden email]>:
> >
> > > Hello!
> > >
> > > I think we should move it to a separate repository, but not Attic.
> > >
> > > I can see the scenario where there would be recurrence of interest to
> > this
> > > tool and somebody may step in to update it.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > ср, 6 мая 2020 г. в 22:20, Denis Magda <[hidden email]>:
> > >
> > > > Folks,
> > > >
> > > > Personally, I like the idea of Apache Attic [1] suggested by Saikat.
> We
> > > are
> > > > not discontinuing Ignite WebConsole because it became useless like it
> > was
> > > > with Hadoop Accelerator. The tool has good capabilities such as the
> > > > configuration wizard, and the only problem is that we no longer want
> to
> > > > support or maintain this technology (while it has the right to
> exist).
> > > >
> > > > Is anybody interested in figuring out with the ASF-mates if Ignite
> > > > WebConsole can be accepted to Attic? The Attic's guidelines talk
> about
> > an
> > > > ASF project as a whole and not about individual components.
> > > >
> > > > [1] https://attic.apache.org
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Wed, May 6, 2020 at 7:20 AM Вячеслав Коптилин <
> > > [hidden email]
> > > > >
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > +1 to remove this component or move it to a separate repository if
> > > > someone
> > > > > wants to maintain it.
> > > > > In case the web console provides useful features, we should
> consider
> > > how
> > > > to
> > > > > add them to our command-line utilities, if possible.
> > > > >
> > > > > Thanks,
> > > > > Slava.
> > > > >
> > > > > ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov <[hidden email]>:
> > > > >
> > > > > > Hello.
> > > > > >
> > > > > > +1 to remove any graphical utilities from the Ignite core.
> > > > > > I think we should maintain and support only cmd, JMX, and other
> > > «core»
> > > > > > tools.
> > > > > >
> > > > > > We shouldn't waste our resources on supporting pretty looking UI
> > > tools.
> > > > > >
> > > > > >
> > > > > > > 2 мая 2020 г., в 04:05, Saikat Maitra <[hidden email]
> >
> > > > > > написал(а):
> > > > > > >
> > > > > > > Hello Denis,
> > > > > > >
> > > > > > > I am thinking if we should move web-console to a separate repo
> > like
> > > > > > > ignite-web-console. In my opinion the tech stack we have in
> > > > web-console
> > > > > > > like npm, nodejs and Mondodb etc are little different and can
> be
> > > > hosted
> > > > > > as
> > > > > > > a separate project in a git repo.
> > > > > > >
> > > > > > > I had used web-console for streamers project and found it
> helpful
> > > in
> > > > > > > creating table schema and execute sql queries and also to do
> > cache
> > > > > > lookup.
> > > > > > >
> > > > > > > https://github.com/samaitra/streamers
> > > > > > >
> > > > > > > If we continue to find that usage of ignite-web-console is
> > limited
> > > > then
> > > > > > we
> > > > > > > can plan moving ignite-web-console in Apache Attic
> > > > > > >
> > > > > > > https://attic.apache.org/
> > > > > > >
> > > > > > > Please let me know your thoughts.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Saikat
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Fri, May 1, 2020 at 12:43 PM Denis Magda <[hidden email]
> >
> > > > wrote:
> > > > > > >
> > > > > > >> Igniters,
> > > > > > >>
> > > > > > >> I would like to hear your opinion on what we should do with
> > Ignite
> > > > > > >> WebConsole.
> > > > > > >>
> > > > > > >> To my knowledge, we don't have active maintainers of the
> > > component,
> > > > > and
> > > > > > a
> > > > > > >> list of issues is piling up [1]. Users even report that the
> > docker
> > > > > > images
> > > > > > >> have not been updated for more than a year [2].
> > > > > > >>
> > > > > > >> Personally, I share the opinion of those who believe the
> > community
> > > > > > needs to
> > > > > > >> provide and support all the essential tooling (metrics and
> > tracing
> > > > > API,
> > > > > > >> command-line tool) while the UI tools are not our business.
> > There
> > > > is a
> > > > > > >> myriad of UI tools Ignite can be monitored and traced with.
> > Users
> > > > > > already
> > > > > > >> have plenty of choices.
> > > > > > >>
> > > > > > >> What are your thoughts? Probably, some of you want to become
> > > > > > maintainers of
> > > > > > >> the component. Otherwise, we should let the tool go.
> > > > > > >>
> > > > > > >> [1]
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/IGNITE-12923?jql=project%20%3D%20IGNITE%20AND%20text%20~%20%22web%20console%22%20AND%20status%20%3D%20Open%20and%20type%20%3D%20Bug%20ORDER%20BY%20createdDate%20
> > > > > > >> [2] https://issues.apache.org/jira/browse/IGNITE-12923
> > > > > > >>
> > > > > > >> -
> > > > > > >> Denis
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>