9:05 a.m.
Now that the votes has been cast, it is clear that there is a desire to
still have
a community distribution.
Looking at the comments also make it clear that the scope needs to
refined.
Especially in the light that it was not communicated well enough before
that e.g.
the app-server tab in the UI will go away.
Discussion areas can be found below.
Another question is the naming.
In http://www.hawkular.org/blog/2016/04/28/new-packaging.html
we referenced 3 'distributions'
1) Hawkular community release
which includes
2) Hawkular core services
which includes
3) Hawkular-metrics
I propose to to rename 1) and 2) going forward to
1new) Hawkular-aio distribution
2new) Hawkular
Technical areas for discussion in the community-release (Hawkular-aio)
are:
* Url handling / pinger / avail-creator
Probably not needed going forward
* UI/ Alert Center
Needed in a generic way - i.e. allow to see fired alerts/events and to
define
generic triggers. For the display it will be enough to iterate over the
Event/Alert
object returned from the REST-api and to display the key/value pairs.
* UI/ Explorer
This needs to stay and we need to fix some smaller bugs to allow
for inventory browsing and display of metric charts
* Accounts / Multi-tenancy
I still see this as a great value and unique selling point, but also see
the effort
of maintaining this (and the issues we have with KC and hostnames).
It may be good to also remove this
* Embedded Cassandra
I think this needs to be present in the community-distribution
* UI/Agent installer
Not sure if this is still needed or if we would just put the
agent+installer
into a directory of the zip for the users to take the installer from
there.
* Default user
The Hawkular-aio download should feature a default user jdoe/password
which is also set in the embedded agent.
5:35 a.m.
New subject: Fwd: Composition of the community distribution / Naming
Ping
Silence means acceptance :-) (Especially for the naming)
From: Heiko W.Rupp <hrupp(a)redhat.com>
To: Discussions around Hawkular development <hawkular-dev(a)lists.jboss.org>
Subject: [Hawkular-dev] Composition of the community distribution / Naming
Date: Wed, 04 May 2016 16:05:00 +0200
Now that the votes has been cast, it is clear that there is a desire to
still have
a community distribution.
Looking at the comments also make it clear that the scope needs to
refined.
Especially in the light that it was not communicated well enough before
that e.g.
the app-server tab in the UI will go away.
Discussion areas can be found below.
Another question is the naming.
In http://www.hawkular.org/blog/2016/04/28/new-packaging.html
we referenced 3 'distributions'
1) Hawkular community release
which includes
2) Hawkular core services
which includes
3) Hawkular-metrics
I propose to to rename 1) and 2) going forward to
1new) Hawkular-aio distribution
2new) Hawkular
Technical areas for discussion in the community-release (Hawkular-aio)
are:
* Url handling / pinger / avail-creator
Probably not needed going forward
* UI/ Alert Center
Needed in a generic way - i.e. allow to see fired alerts/events and to
define
generic triggers. For the display it will be enough to iterate over the
Event/Alert
object returned from the REST-api and to display the key/value pairs.
* UI/ Explorer
This needs to stay and we need to fix some smaller bugs to allow
for inventory browsing and display of metric charts
* Accounts / Multi-tenancy
I still see this as a great value and unique selling point, but also see
the effort
of maintaining this (and the issues we have with KC and hostnames).
It may be good to also remove this
* Embedded Cassandra
I think this needs to be present in the community-distribution
* UI/Agent installer
Not sure if this is still needed or if we would just put the
agent+installer
into a directory of the zip for the users to take the installer from
there.
* Default user
The Hawkular-aio download should feature a default user jdoe/password
which is also set in the embedded agent.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
5:49 a.m.
New subject: Fwd: Composition of the community distribution / Naming
What about:
1) Hawkular - the community (all in one) distribution, and
2) Hawkular-server - the server only, which may be of interest to community as a server
only install, but also as foundation for MiQ integration.
Regards
Gary
----- Original Message -----
Ping
Silence means acceptance :-) (Especially for the naming)
> From: Heiko W.Rupp <hrupp(a)redhat.com>
> To: Discussions around Hawkular development <hawkular-dev(a)lists.jboss.org>
> Subject: [Hawkular-dev] Composition of the community distribution / Naming
> Date: Wed, 04 May 2016 16:05:00 +0200
>
> Now that the votes has been cast, it is clear that there is a desire to
> still have
> a community distribution.
>
> Looking at the comments also make it clear that the scope needs to
> refined.
> Especially in the light that it was not communicated well enough before
> that e.g.
> the app-server tab in the UI will go away.
> Discussion areas can be found below.
>
> Another question is the naming.
> In http://www.hawkular.org/blog/2016/04/28/new-packaging.html
> we referenced 3 'distributions'
> 1) Hawkular community release
> which includes
> 2) Hawkular core services
> which includes
> 3) Hawkular-metrics
>
> I propose to to rename 1) and 2) going forward to
>
> 1new) Hawkular-aio distribution
> 2new) Hawkular
>
>
>
> Technical areas for discussion in the community-release (Hawkular-aio)
> are:
>
> * Url handling / pinger / avail-creator
>
> Probably not needed going forward
>
> * UI/ Alert Center
>
> Needed in a generic way - i.e. allow to see fired alerts/events and to
> define
> generic triggers. For the display it will be enough to iterate over the
> Event/Alert
> object returned from the REST-api and to display the key/value pairs.
>
> * UI/ Explorer
>
> This needs to stay and we need to fix some smaller bugs to allow
> for inventory browsing and display of metric charts
>
> * Accounts / Multi-tenancy
>
> I still see this as a great value and unique selling point, but also see
> the effort
> of maintaining this (and the issues we have with KC and hostnames).
> It may be good to also remove this
>
>
> * Embedded Cassandra
>
> I think this needs to be present in the community-distribution
>
> * UI/Agent installer
>
> Not sure if this is still needed or if we would just put the
> agent+installer
> into a directory of the zip for the users to take the installer from
> there.
>
> * Default user
>
> The Hawkular-aio download should feature a default user jdoe/password
> which is also set in the embedded agent.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
5:54 a.m.
New subject: Fwd: Composition of the community distribution / Naming
"Hawkular-aio" stands for "Hawkular All In One" ?
I prefer to not use acronyms, those are harder to identify (sometimes).
I propose:
1) Hawkular
2) Hawkular Services
3) Hawkular Metrics
----- Mensaje original -----
De: "Heiko W.Rupp" <hrupp(a)redhat.com>
Para: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Enviados: Lunes, 9 de Mayo 2016 12:35:28
Asunto: [Hawkular-dev] Fwd: Composition of the community distribution / Naming
Ping
Silence means acceptance :-) (Especially for the naming)
> From: Heiko W.Rupp <hrupp(a)redhat.com>
> To: Discussions around Hawkular development <hawkular-dev(a)lists.jboss.org>
> Subject: [Hawkular-dev] Composition of the community distribution / Naming
> Date: Wed, 04 May 2016 16:05:00 +0200
>
> Now that the votes has been cast, it is clear that there is a desire to
> still have
> a community distribution.
>
> Looking at the comments also make it clear that the scope needs to
> refined.
> Especially in the light that it was not communicated well enough before
> that e.g.
> the app-server tab in the UI will go away.
> Discussion areas can be found below.
>
> Another question is the naming.
> In http://www.hawkular.org/blog/2016/04/28/new-packaging.html
> we referenced 3 'distributions'
> 1) Hawkular community release
> which includes
> 2) Hawkular core services
> which includes
> 3) Hawkular-metrics
>
> I propose to to rename 1) and 2) going forward to
>
> 1new) Hawkular-aio distribution
> 2new) Hawkular
>
>
>
> Technical areas for discussion in the community-release (Hawkular-aio)
> are:
>
> * Url handling / pinger / avail-creator
>
> Probably not needed going forward
>
> * UI/ Alert Center
>
> Needed in a generic way - i.e. allow to see fired alerts/events and to
> define
> generic triggers. For the display it will be enough to iterate over the
> Event/Alert
> object returned from the REST-api and to display the key/value pairs.
>
> * UI/ Explorer
>
> This needs to stay and we need to fix some smaller bugs to allow
> for inventory browsing and display of metric charts
>
> * Accounts / Multi-tenancy
>
> I still see this as a great value and unique selling point, but also see
> the effort
> of maintaining this (and the issues we have with KC and hostnames).
> It may be good to also remove this
>
>
> * Embedded Cassandra
>
> I think this needs to be present in the community-distribution
>
> * UI/Agent installer
>
> Not sure if this is still needed or if we would just put the
> agent+installer
> into a directory of the zip for the users to take the installer from
> there.
>
> * Default user
>
> The Hawkular-aio download should feature a default user jdoe/password
> which is also set in the embedded agent.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
9:55 a.m.
New subject: Fwd: Composition of the community distribution / Naming
+1
2016-05-09 12:54 GMT+02:00 Lucas Ponce <lponce(a)redhat.com>:
"Hawkular-aio" stands for "Hawkular All In One"
?
I prefer to not use acronyms, those are harder to identify (sometimes).
I propose:
1) Hawkular
2) Hawkular Services
3) Hawkular Metrics
12:54 p.m.
New subject: Fwd: Composition of the community distribution / Naming
+1
Thank you,
Stefan Negrea
Software Engineer
On Mon, May 9, 2016 at 5:54 AM, Lucas Ponce <lponce(a)redhat.com> wrote:
"Hawkular-aio" stands for "Hawkular All In One"
?
I prefer to not use acronyms, those are harder to identify (sometimes).
I propose:
1) Hawkular
2) Hawkular Services
3) Hawkular Metrics
----- Mensaje original -----
> De: "Heiko W.Rupp" <hrupp(a)redhat.com>
> Para: "Discussions around Hawkular development" <
hawkular-dev(a)lists.jboss.org>
> Enviados: Lunes, 9 de Mayo 2016 12:35:28
> Asunto: [Hawkular-dev] Fwd: Composition of the community distribution /
Naming
>
> Ping
> Silence means acceptance :-) (Especially for the naming)
>
> > From: Heiko W.Rupp <hrupp(a)redhat.com>
> > To: Discussions around Hawkular development <
hawkular-dev(a)lists.jboss.org>
> > Subject: [Hawkular-dev] Composition of the community distribution /
Naming
> > Date: Wed, 04 May 2016 16:05:00 +0200
> >
> > Now that the votes has been cast, it is clear that there is a desire to
> > still have
> > a community distribution.
> >
> > Looking at the comments also make it clear that the scope needs to
> > refined.
> > Especially in the light that it was not communicated well enough before
> > that e.g.
> > the app-server tab in the UI will go away.
> > Discussion areas can be found below.
> >
> > Another question is the naming.
> > In http://www.hawkular.org/blog/2016/04/28/new-packaging.html
> > we referenced 3 'distributions'
> > 1) Hawkular community release
> > which includes
> > 2) Hawkular core services
> > which includes
> > 3) Hawkular-metrics
> >
> > I propose to to rename 1) and 2) going forward to
> >
> > 1new) Hawkular-aio distribution
> > 2new) Hawkular
> >
> >
> >
> > Technical areas for discussion in the community-release (Hawkular-aio)
> > are:
> >
> > * Url handling / pinger / avail-creator
> >
> > Probably not needed going forward
> >
> > * UI/ Alert Center
> >
> > Needed in a generic way - i.e. allow to see fired alerts/events and to
> > define
> > generic triggers. For the display it will be enough to iterate over the
> > Event/Alert
> > object returned from the REST-api and to display the key/value pairs.
> >
> > * UI/ Explorer
> >
> > This needs to stay and we need to fix some smaller bugs to allow
> > for inventory browsing and display of metric charts
> >
> > * Accounts / Multi-tenancy
> >
> > I still see this as a great value and unique selling point, but also
see
> > the effort
> > of maintaining this (and the issues we have with KC and hostnames).
> > It may be good to also remove this
> >
> >
> > * Embedded Cassandra
> >
> > I think this needs to be present in the community-distribution
> >
> > * UI/Agent installer
> >
> > Not sure if this is still needed or if we would just put the
> > agent+installer
> > into a directory of the zip for the users to take the installer from
> > there.
> >
> > * Default user
> >
> > The Hawkular-aio download should feature a default user jdoe/password
> > which is also set in the embedded agent.
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
9:19 a.m.
New subject: Fwd: Composition of the community distribution / Naming
There is a bit of confusion over what 'Hawkular' is. I constantly have to remind
people that we are using 'Hawkular Metrics' in OpenShift and not
'Hawkular' (but half of the time they continue to just call it 'Hawkular'
anyways).
This means I sometimes get questions (or even bugs) opened when people are trying to
access the main 'Hawkular' UI or to access the endpoints of other services (such
as Alerts) because they think that all of 'Hawkular' is in OpenShift somewhere.
I would prefer to use 'Hawkular' as the term for the technology umbrella, rather
than call one of those components 'Hawkular' directly. I think that would just
confuse things even more.
----- Original Message -----
From: "Stefan Negrea" <snegrea(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Monday, May 9, 2016 1:54:12 PM
Subject: Re: [Hawkular-dev] Fwd: Composition of the community distribution / Naming
+1
Thank you,
Stefan Negrea
Software Engineer
On Mon, May 9, 2016 at 5:54 AM, Lucas Ponce < lponce(a)redhat.com > wrote:
"Hawkular-aio" stands for "Hawkular All In One" ?
I prefer to not use acronyms, those are harder to identify (sometimes).
I propose:
1) Hawkular
2) Hawkular Services
3) Hawkular Metrics
----- Mensaje original -----
> De: "Heiko W.Rupp" < hrupp(a)redhat.com >
> Para: "Discussions around Hawkular development" <
> hawkular-dev(a)lists.jboss.org >
> Enviados: Lunes, 9 de Mayo 2016 12:35:28
> Asunto: [Hawkular-dev] Fwd: Composition of the community distribution /
> Naming
>
> Ping
> Silence means acceptance :-) (Especially for the naming)
>
> > From: Heiko W.Rupp < hrupp(a)redhat.com >
> > To: Discussions around Hawkular development <
> > hawkular-dev(a)lists.jboss.org >
> > Subject: [Hawkular-dev] Composition of the community distribution /
> > Naming
> > Date: Wed, 04 May 2016 16:05:00 +0200
> >
> > Now that the votes has been cast, it is clear that there is a desire to
> > still have
> > a community distribution.
> >
> > Looking at the comments also make it clear that the scope needs to
> > refined.
> > Especially in the light that it was not communicated well enough before
> > that e.g.
> > the app-server tab in the UI will go away.
> > Discussion areas can be found below.
> >
> > Another question is the naming.
> > In http://www.hawkular.org/blog/2016/04/28/new-packaging.html
> > we referenced 3 'distributions'
> > 1) Hawkular community release
> > which includes
> > 2) Hawkular core services
> > which includes
> > 3) Hawkular-metrics
> >
> > I propose to to rename 1) and 2) going forward to
> >
> > 1new) Hawkular-aio distribution
> > 2new) Hawkular
> >
> >
> >
> > Technical areas for discussion in the community-release (Hawkular-aio)
> > are:
> >
> > * Url handling / pinger / avail-creator
> >
> > Probably not needed going forward
> >
> > * UI/ Alert Center
> >
> > Needed in a generic way - i.e. allow to see fired alerts/events and to
> > define
> > generic triggers. For the display it will be enough to iterate over the
> > Event/Alert
> > object returned from the REST-api and to display the key/value pairs.
> >
> > * UI/ Explorer
> >
> > This needs to stay and we need to fix some smaller bugs to allow
> > for inventory browsing and display of metric charts
> >
> > * Accounts / Multi-tenancy
> >
> > I still see this as a great value and unique selling point, but also see
> > the effort
> > of maintaining this (and the issues we have with KC and hostnames).
> > It may be good to also remove this
> >
> >
> > * Embedded Cassandra
> >
> > I think this needs to be present in the community-distribution
> >
> > * UI/Agent installer
> >
> > Not sure if this is still needed or if we would just put the
> > agent+installer
> > into a directory of the zip for the users to take the installer from
> > there.
> >
> > * Default user
> >
> > The Hawkular-aio download should feature a default user jdoe/password
> > which is also set in the embedded agent.
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
5:09 a.m.
On 4 May 2016, at 16:05, Heiko W.Rupp wrote:
Technical areas for discussion in the community-release
(Hawkular-aio)
are:
* Url handling / pinger / avail-creator
Probably not needed going forward
Ok, will be removed.
See https://issues.jboss.org/browse/HAWKULAR-1077
* UI/ Alert Center
Needed in a generic way - i.e. allow to see fired alerts/events and to
define
generic triggers. For the display it will be enough to iterate over the
Event/Alert
object returned from the REST-api and to display the key/value pairs.
* UI/ Explorer
This needs to stay and we need to fix some smaller bugs to allow
for inventory browsing and display of metric charts
* Accounts / Multi-tenancy
I still see this as a great value and unique selling point, but also see
the effort
of maintaining this (and the issues we have with KC and hostnames).
It may be good to also remove this
This is addressed by the JAAS work that is going on and
the 'hawkular' default tenant. Juca sent email about that
some days ago.
* Embedded Cassandra
I think this needs to be present in the community-distribution
* UI/Agent installer
Not sure if this is still needed or if we would just put the
agent+installer
into a directory of the zip for the users to take the installer from
there.
Opinions? For hawkular-services, there is no UI, so there will be
no UI screen there. I think for the full/community distribution
just putting that in a directory of the downloaded .zip is enough.
* Default user
The Hawkular-aio download should feature a default user jdoe/password
which is also set in the embedded agent.
And also being prepopulated with the default tenant.
5:12 a.m.
And of course I forgot the elephant in the room:
removal of the app-server tab and its special knowledge.
On 13 May 2016, at 12:09, Heiko W.Rupp wrote:
On 4 May 2016, at 16:05, Heiko W.Rupp wrote:
> Technical areas for discussion in the community-release
> (Hawkular-aio)
> are:
>
> * Url handling / pinger / avail-creator
>
> Probably not needed going forward
Ok, will be removed.
See https://issues.jboss.org/browse/HAWKULAR-1077
> * UI/ Alert Center
>
> Needed in a generic way - i.e. allow to see fired alerts/events and
> to
> define
> generic triggers. For the display it will be enough to iterate over
> the
> Event/Alert
> object returned from the REST-api and to display the key/value pairs.
>
> * UI/ Explorer
>
> This needs to stay and we need to fix some smaller bugs to allow
> for inventory browsing and display of metric charts
>
> * Accounts / Multi-tenancy
>
> I still see this as a great value and unique selling point, but also
> see
> the effort
> of maintaining this (and the issues we have with KC and hostnames).
> It may be good to also remove this
This is addressed by the JAAS work that is going on and
the 'hawkular' default tenant. Juca sent email about that
some days ago.
> * Embedded Cassandra
>
> I think this needs to be present in the community-distribution
>
> * UI/Agent installer
>
> Not sure if this is still needed or if we would just put the
> agent+installer
> into a directory of the zip for the users to take the installer from
> there.
Opinions? For hawkular-services, there is no UI, so there will be
no UI screen there. I think for the full/community distribution
just putting that in a directory of the downloaded .zip is enough.
> * Default user
>
> The Hawkular-aio download should feature a default user jdoe/password
> which is also set in the embedded agent.
And also being prepopulated with the default tenant.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschäftsführer: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill
5:32 a.m.
On Fri, May 13, 2016 at 12:09 PM, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
On 4 May 2016, at 16:05, Heiko W.Rupp wrote:
> Technical areas for discussion in the community-release (Hawkular-aio)
> are:
>
> * Url handling / pinger / avail-creator
>
> Probably not needed going forward
Ok, will be removed.
See https://issues.jboss.org/browse/HAWKULAR-1077
> * UI/ Alert Center
>
> Needed in a generic way - i.e. allow to see fired alerts/events and to
> define
> generic triggers. For the display it will be enough to iterate over the
> Event/Alert
> object returned from the REST-api and to display the key/value pairs.
>
> * UI/ Explorer
>
> This needs to stay and we need to fix some smaller bugs to allow
> for inventory browsing and display of metric charts
>
> * Accounts / Multi-tenancy
>
> I still see this as a great value and unique selling point, but also see
> the effort
> of maintaining this (and the issues we have with KC and hostnames).
> It may be good to also remove this
This is addressed by the JAAS work that is going on and
the 'hawkular' default tenant. Juca sent email about that
some days ago.
> * Embedded Cassandra
>
> I think this needs to be present in the community-distribution
>
> * UI/Agent installer
>
> Not sure if this is still needed or if we would just put the
> agent+installer
> into a directory of the zip for the users to take the installer from
> there.
Opinions? For hawkular-services, there is no UI, so there will be
no UI screen there. I think for the full/community distribution
just putting that in a directory of the downloaded .zip is enough.
I'm not sure we need to put it there anyway, since this is MW specific
unlike everything else.
That said I guess it makes the release process easier ?
Thomas
> * Default user
>
> The Hawkular-aio download should feature a default user jdoe/password
> which is also set in the embedded agent.
And also being prepopulated with the default tenant.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3149
days inactive
3158
days old
10 comments
7 participants
participants (7)
-
Gary Brown -
Heiko W.Rupp -
Lucas Ponce -
Matt Wringe -
Stefan Negrea -
Thomas Heute -
Thomas Segismont