[Hawkular-dev] Hawkular.org

[Thomas Heute]

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.

I'm fine leaving the 3 top level projects, and it should definitely not
grow.

Note that I didn't expose Alerts there to not add confusion even though it
can run on its own.

Thomas

On Thu, Jul 7, 2016 at 12:25 PM, Gary Brown <gbrown at redhat.com> wrote:

> Hi Thomas
>
> 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.
>
> Apologies if already discussed, but just wanted to clarify the purpose of
> having Metrics as separate distribution on the community project website.
>
> 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.
>
> 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?
>
> Regards
> Gary
>
>
> ----- Original Message -----
> > Thanks for the comments, I'm really looking more for feedback on the
> > organization of the content, all the content is taken from the existing.
> >
> > For the 3rd point, the current website has 2 very similar pages (I only
> > conserved one here as it was a quick shot, but the 2 needs to be merged)
> > http://www.hawkular.org/community/index.html
> > http://www.hawkular.org/community/join.html
> >
> >
> > On Thu, Jul 7, 2016 at 11:37 AM, Alissa Bonas < abonas at redhat.com >
> wrote:
> >
> >
> >
> > Couple of suggestions:
> >
> > 1. In the "Hawkular features" section in homepage make the icons
> clickable.
> > right now the only way to get more info is to click the "more" part.
> > 2. Top level menu font color is a really pale grey so everything looks
> > disabled.
> > 3. Community-Connect leads to page named "Join". Perhaps it would more
> clear
> > to make the link and the page name the same (and I would call it "Get
> > involved" anyway)
> >
> >
> >
> >
> > On Thu, Jul 7, 2016 at 11:58 AM, Thomas Heute < theute at redhat.com >
> wrote:
> >
> >
> >
> > So here is a very rough idea of how it would look like:
> > http://209.132.178.114:10188/
> >
> > Content need to be adapted, new pages to be created, but hopefully you
> get
> > the idea
> >
> > On Tue, Jul 5, 2016 at 8:27 PM, John Sanda < jsanda at redhat.com > wrote:
> >
> >
> >
> >
> >
> >
> >
> > On Jul 5, 2016, at 10:21 AM, Thomas Segismont < tsegismo at redhat.com >
> wrote:
> >
> >
> >
> > Le 05/07/2016 à 16:05, Stefan Negrea a écrit :
> >
> >
> > On Tue, Jul 5, 2016 at 8:03 AM, Thomas Segismont < tsegismo at redhat.com
> > < mailto:tsegismo at redhat.com >> wrote:
> >
> >
> >
> > Le 05/07/2016 à 14:59, Heiko W.Rupp a écrit :
> >
> >
> >
> >
> > 2) The Grafana plugin should be moved under Metrics because is for
> Metrics
> >
> >
> > and only Metrics.
> > If this is true - can we make it work with H-services as well?
> >
> >
> > The Grafana plugin works with all active flavors of Metrics: standalone,
> > Openshift-Metrics and Hawkular-Services.
> >
> > I'm not sure what Stefan meant.
> >
> >
> > The Grafana plugins works with Metrics deployed on all distributions
> > however, the plugin itself can only be used with the Metrics project,
> > there are no projects (such as Alerts, or Inventory) that will ever
> > integrate with it. That is why I think it should be under the Metrics
> > project and not in another place. The integration itself is very
> > specific to just Metrics, not the entire Hawkular Services.
> >
> > I see what you meant now. But we can't presume anything about other
> > services roadmaps. For example, the datasource plugin annotation feature
> > could be implemented with requests to an event service.
> >
> > Anyway, since it should be able to connect to Metrics in different
> > environments (H-Services, OS-Metrics and standalone), I err on the side
> > of promoting it as a top level project.
> >
> >
> > I think a top-level project makes the most sense.
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> >
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> >
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> >
> >
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160707/cece485f/attachment.html