<div dir="ltr">+1<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Thank you,<br>Stefan Negrea<br><br>Software Engineer<br></div></div></div>
<br><div class="gmail_quote">On Mon, May 9, 2016 at 5:54 AM, Lucas Ponce <span dir="ltr"><<a href="mailto:lponce@redhat.com" target="_blank">lponce@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">"Hawkular-aio" stands for "Hawkular All In One" ?<br>
<br>
I prefer to not use acronyms, those are harder to identify (sometimes).<br>
<br>
I propose:<br>
<br>
1) Hawkular<br>
2) Hawkular Services<br>
3) Hawkular Metrics<br>
<br>
<br>
<br>
----- Mensaje original -----<br>
> De: "Heiko W.Rupp" <<a href="mailto:hrupp@redhat.com">hrupp@redhat.com</a>><br>
> Para: "Discussions around Hawkular development" <<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
> Enviados: Lunes, 9 de Mayo 2016 12:35:28<br>
> Asunto: [Hawkular-dev] Fwd: Composition of the community distribution / Naming<br>
<div class="HOEnZb"><div class="h5">><br>
> Ping<br>
> Silence means acceptance :-) (Especially for the naming)<br>
><br>
> > From: Heiko W.Rupp <<a href="mailto:hrupp@redhat.com">hrupp@redhat.com</a>><br>
> > To: Discussions around Hawkular development <<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>><br>
> > Subject: [Hawkular-dev] Composition of the community distribution / Naming<br>
> > Date: Wed, 04 May 2016 16:05:00 +0200<br>
> ><br>
> > Now that the votes has been cast, it is clear that there is a desire to<br>
> > still have<br>
> > a community distribution.<br>
> ><br>
> > Looking at the comments also make it clear that the scope needs to<br>
> > refined.<br>
> > Especially in the light that it was not communicated well enough before<br>
> > that e.g.<br>
> > the app-server tab in the UI will go away.<br>
> > Discussion areas can be found below.<br>
> ><br>
> > Another question is the naming.<br>
> > In <a href="http://www.hawkular.org/blog/2016/04/28/new-packaging.html" rel="noreferrer" target="_blank">http://www.hawkular.org/blog/2016/04/28/new-packaging.html</a><br>
> > we referenced 3 'distributions'<br>
> > 1) Hawkular community release<br>
> > which includes<br>
> > 2) Hawkular core services<br>
> > which includes<br>
> > 3) Hawkular-metrics<br>
> ><br>
> > I propose to to rename 1) and 2) going forward to<br>
> ><br>
> > 1new) Hawkular-aio distribution<br>
> > 2new) Hawkular<br>
> ><br>
> ><br>
> ><br>
> > Technical areas for discussion in the community-release (Hawkular-aio)<br>
> > are:<br>
> ><br>
> > * Url handling / pinger / avail-creator<br>
> ><br>
> > Probably not needed going forward<br>
> ><br>
> > * UI/ Alert Center<br>
> ><br>
> > Needed in a generic way - i.e. allow to see fired alerts/events and to<br>
> > define<br>
> > generic triggers. For the display it will be enough to iterate over the<br>
> > Event/Alert<br>
> > object returned from the REST-api and to display the key/value pairs.<br>
> ><br>
> > * UI/ Explorer<br>
> ><br>
> > This needs to stay and we need to fix some smaller bugs to allow<br>
> > for inventory browsing and display of metric charts<br>
> ><br>
> > * Accounts / Multi-tenancy<br>
> ><br>
> > I still see this as a great value and unique selling point, but also see<br>
> > the effort<br>
> > of maintaining this (and the issues we have with KC and hostnames).<br>
> > It may be good to also remove this<br>
> ><br>
> ><br>
> > * Embedded Cassandra<br>
> ><br>
> > I think this needs to be present in the community-distribution<br>
> ><br>
> > * UI/Agent installer<br>
> ><br>
> > Not sure if this is still needed or if we would just put the<br>
> > agent+installer<br>
> > into a directory of the zip for the users to take the installer from<br>
> > there.<br>
> ><br>
> > * Default user<br>
> ><br>
> > The Hawkular-aio download should feature a default user jdoe/password<br>
> > which is also set in the embedded agent.<br>
> > _______________________________________________<br>
> > hawkular-dev mailing list<br>
> > <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
> _______________________________________________<br>
> hawkular-dev mailing list<br>
> <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
><br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
</div></div></blockquote></div><br></div>