Re: [Hawkular-dev] 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&gt; > Para: "Discussions around Hawkular development" < hawkular-dev(a)lists.jboss.org&gt; > 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&gt; > > To: Discussions around Hawkular development < hawkular-dev(a)lists.jboss.org&gt; > > 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