<div dir="ltr">Hawkular Services should indeed be the default choice, we heard of multiple (potential) users of Hawkular Metrics asking about alerts and/or inventory support... Metrics is the fallback if one happen to only use metrics. At least the message of Hawkular Metrics is simple, it's a TSDB, period.<div><br></div><div>I'm fine leaving the 3 top level projects, and it should definitely not grow.<br><div><br></div><div>Note that I didn't expose Alerts there to not add confusion even though it can run on its own.</div><div><br></div><div>Thomas</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 7, 2016 at 12:25 PM, Gary Brown <span dir="ltr"><<a href="mailto:gbrown@redhat.com" target="_blank">gbrown@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Thomas<br>
<br>
Think it looks fine - as long as we are not going to be providing any more distributions (e.g. Metrics + Alerts) - otherwise it will be extending the top level menu.<br>
<br>
Apologies if already discussed, but just wanted to clarify the purpose of having Metrics as separate distribution on the community project website.<br>
<br>
I understand that Metrics is used as a standalone component within openshift, but wondering whether that means it should be publicly available as such on the hawkular website, encouraging other community users to use it as a separate component.<br>
<br>
Wondering whether for simplicity, it would be better to only provide hawkular-services distribution publicly, even if user only wants metrics, and then the Metrics build is just an internal packaging option provided to Openshift?<br>
<span class="im HOEnZb"><br>
Regards<br>
Gary<br>
<br>
<br>
----- Original Message -----<br>
</span><div class="HOEnZb"><div class="h5">> Thanks for the comments, I'm really looking more for feedback on the<br>
> organization of the content, all the content is taken from the existing.<br>
><br>
> For the 3rd point, the current website has 2 very similar pages (I only<br>
> conserved one here as it was a quick shot, but the 2 needs to be merged)<br>
> <a href="http://www.hawkular.org/community/index.html" rel="noreferrer" target="_blank">http://www.hawkular.org/community/index.html</a><br>
> <a href="http://www.hawkular.org/community/join.html" rel="noreferrer" target="_blank">http://www.hawkular.org/community/join.html</a><br>
><br>
><br>
> On Thu, Jul 7, 2016 at 11:37 AM, Alissa Bonas < <a href="mailto:abonas@redhat.com">abonas@redhat.com</a> > wrote:<br>
><br>
><br>
><br>
> Couple of suggestions:<br>
><br>
> 1. In the "Hawkular features" section in homepage make the icons clickable.<br>
> right now the only way to get more info is to click the "more" part.<br>
> 2. Top level menu font color is a really pale grey so everything looks<br>
> disabled.<br>
> 3. Community-Connect leads to page named "Join". Perhaps it would more clear<br>
> to make the link and the page name the same (and I would call it "Get<br>
> involved" anyway)<br>
><br>
><br>
><br>
><br>
> On Thu, Jul 7, 2016 at 11:58 AM, Thomas Heute < <a href="mailto:theute@redhat.com">theute@redhat.com</a> > wrote:<br>
><br>
><br>
><br>
> So here is a very rough idea of how it would look like:<br>
> <a href="http://209.132.178.114:10188/" rel="noreferrer" target="_blank">http://209.132.178.114:10188/</a><br>
><br>
> Content need to be adapted, new pages to be created, but hopefully you get<br>
> the idea<br>
><br>
> On Tue, Jul 5, 2016 at 8:27 PM, John Sanda < <a href="mailto:jsanda@redhat.com">jsanda@redhat.com</a> > wrote:<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Jul 5, 2016, at 10:21 AM, Thomas Segismont < <a href="mailto:tsegismo@redhat.com">tsegismo@redhat.com</a> > wrote:<br>
><br>
><br>
><br>
> Le 05/07/2016 à 16:05, Stefan Negrea a écrit :<br>
><br>
><br>
> On Tue, Jul 5, 2016 at 8:03 AM, Thomas Segismont < <a href="mailto:tsegismo@redhat.com">tsegismo@redhat.com</a><br>
> < mailto:<a href="mailto:tsegismo@redhat.com">tsegismo@redhat.com</a> >> wrote:<br>
><br>
><br>
><br>
> Le 05/07/2016 à 14:59, Heiko W.Rupp a écrit :<br>
><br>
><br>
><br>
><br>
> 2) The Grafana plugin should be moved under Metrics because is for Metrics<br>
><br>
><br>
> and only Metrics.<br>
> If this is true - can we make it work with H-services as well?<br>
><br>
><br>
> The Grafana plugin works with all active flavors of Metrics: standalone,<br>
> Openshift-Metrics and Hawkular-Services.<br>
><br>
> I'm not sure what Stefan meant.<br>
><br>
><br>
> The Grafana plugins works with Metrics deployed on all distributions<br>
> however, the plugin itself can only be used with the Metrics project,<br>
> there are no projects (such as Alerts, or Inventory) that will ever<br>
> integrate with it. That is why I think it should be under the Metrics<br>
> project and not in another place. The integration itself is very<br>
> specific to just Metrics, not the entire Hawkular Services.<br>
><br>
> I see what you meant now. But we can't presume anything about other<br>
> services roadmaps. For example, the datasource plugin annotation feature<br>
> could be implemented with requests to an event service.<br>
><br>
> Anyway, since it should be able to connect to Metrics in different<br>
> environments (H-Services, OS-Metrics and standalone), I err on the side<br>
> of promoting it as a top level project.<br>
><br>
><br>
> I think a top-level project makes the most sense.<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>
><br>
><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>
><br>
><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>
><br>
><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>
><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>
<br>
<br>
</div></div></blockquote></div><br></div>