[Hawkular-dev] Hawkular.org

Tue Jul 5 11:31:18 EDT 2016

On Tue, Jul 5, 2016 at 9:14 AM, Thomas Heute <theute at redhat.com> wrote:

>
>
> On Tue, Jul 5, 2016 at 4:10 PM, Stefan Negrea <snegrea at redhat.com> wrote:
>
>>
>> On Tue, Jul 5, 2016 at 3:19 AM, Thomas Heute <theute at redhat.com> wrote:
>>
>>>
>>>
>>> On Thu, Jun 16, 2016 at 6:11 PM, Stefan Negrea <snegrea at redhat.com>
>>> wrote:
>>>
>>>> I really like this last revision because the content is sectioned along
>>>> the way we deliver to users. So when a user navigates the website, the
>>>> content is always related to what they can directly download and use and
>>>> not mixed together.
>>>>
>>>> I have 3 small proposals:
>>>> 1) Hawkular and Overview can be combined into one Hawkular Overview or
>>>> Hawkular (which has the overview of the projects).
>>>>
>>>
>>> This is more an issue with the representation in the mindmap I think.
>>> Hawkular is really the homepage: http://www.hawkular.org/index.html and
>>> I think we can remove the link since the link on the logo does the same
>>> thing and it's quite a UXD standard.
>>> Overview is a more detailed page:
>>> http://www.hawkular.org/docs/overview.html a user should find it's way
>>> among the various projects.
>>>
>>
>> As long as we do not have two top menu entries, one for Hawkular and one
>> for Overview, then the proposal makes sense.
>>
>>
>>>
>>>
>>>> 2) The Grafana plugin should be moved under Metrics because is for
>>>> Metrics and only Metrics.
>>>>
>>>
>>> The Grafana plugins works with Metrics and Services
>>>
>>
>> But it is a Metrics specific integration, no other services will ever
>> integrate with Grafana.
>>
>
> It is not Hawkular Metrics specific if it works for Hawkular Services.
>
>
That is where we will confuse everybody about the integration. Hawkular
Services has a lot services/stuff bundled. Grafana is only relevant and
works for Metrics, not Alerts, not Inventory. It does not integrate with
the other services for anything. Thinking from the perspective of a new
user, if I see the Grafana integration mentioned in the context of Hawkular
Services, then immediately I would assume that it integrates with all the
services. The context confuses everything ...

Thomas
>
>
>
>
>>
>>
>>>
>>>
>>>> 3) Hawkular Server should be renamed Hawkular Services because that the
>>>> official project name.
>>>>
>>>
>>> OTOH I would not want a totally separate structure for Hawkular Services
>>> *and* Hawkular Community, as they are very much the same except for some
>>> installation process (have to install C* separately or not) and maybe for
>>> additional parts in Community. The idea was to combined both into a single
>>> concept of server.
>>>
>>
>> Agree here, what I suggested is that Hawkular Community is just a
>> subsection in the Hawkular Services; and not two different sections. That
>> will give more visibility to the concept of Hawkular Services rather than
>> promote the unused name of Hawkular Server .
>>
>>
>>
>>
>>> Thomas
>>>
>>>
>>>>
>>>>
>>>> Thank you,
>>>> Stefan Negrea
>>>>
>>>> Software Engineer
>>>>
>>>> On Wed, Jun 15, 2016 at 1:18 PM, Thomas Heute <theute at redhat.com>
>>>> wrote:
>>>>
>>>>> Sorry, I meant to sent the PNG file... here it is
>>>>>
>>>>> On Wed, Jun 15, 2016 at 8:08 PM, Thomas Heute <theute at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Based on that suggestion, here is another proposal.
>>>>>>
>>>>>> Rectangle means a page
>>>>>> Underline is more likely a section on a page
>>>>>> Green arrows mean links (To Travis, to gitbook.io...)
>>>>>>
>>>>>> Let me know what you think of that updated section
>>>>>>
>>>>>> Thomas
>>>>>>
>>>>>> On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea <snegrea at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I do not see the idea proposed yet, but why not structure the
>>>>>>> website around major projects? We have Hawkular community, Hawkular
>>>>>>> Services, Hawkular Metrics, and APM. Projects like Inventory or the clients
>>>>>>> would fall under Hawkular Services umbrella. So rather than designing a
>>>>>>> generic structure with everything make individual sub-sites and then apply
>>>>>>> the structure you proposed.
>>>>>>>
>>>>>>> The current website was designed when the direction of the community
>>>>>>> was different so a re-org along the previous structure is not sufficient.
>>>>>>>
>>>>>>> Thank you,
>>>>>>> Stefan Negrea
>>>>>>>
>>>>>>> On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman <
>>>>>>> miburman at redhat.com> wrote:
>>>>>>>
>>>>>>>> Currently Heapster stores in internal memory few minutes of data
>>>>>>>> and allows queries that request this data (through its REST-interface). The
>>>>>>>> consume part will just request the data from the HWKMETRICS instead.
>>>>>>>>
>>>>>>>>   -  Micke
>>>>>>>>
>>>>>>>> ----- Original Message -----
>>>>>>>> From: "Thomas Heute" <theute at redhat.com>
>>>>>>>> To: "Discussions around Hawkular development" <
>>>>>>>> hawkular-dev at lists.jboss.org>
>>>>>>>> Sent: Tuesday, June 14, 2016 4:09:40 PM
>>>>>>>> Subject: Re: [Hawkular-dev] Hawkular.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman <
>>>>>>>> miburman at redhat.com > wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Consumers is terrible word for any client, as they both consume as
>>>>>>>> well as produce the data.
>>>>>>>>
>>>>>>>> Well that was actually reflecting the current state, we have
>>>>>>>> "things" that feed data to the server and "things" that consume data from
>>>>>>>> the server. The client libraries provide an API to feed and consume.
>>>>>>>>
>>>>>>>>
>>>>>>>> For example for Heapster, we currently produce the data, however at
>>>>>>>> the moment I'm creating a change that will consume the data from HWKMETRICS.
>>>>>>>>
>>>>>>>> Why does it consume data now ?
>>>>>>>>
>>>>>>>> Thomas
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Integration / clients is far more used and known word, while
>>>>>>>> consumer/producer is something more specific and implies a design pattern.
>>>>>>>>
>>>>>>>> - Micke
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>
>>>
>>
>> _______________________________________________
>> 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/20160705/e4b0cfcb/attachment.html 