7:08 p.m.
OK, folks, as much as I hate these "what should we name this thing?" threads, I
have to do it.
We are at the point where we are going to start going full-throttle on building out an
agent that can monitor things on Open Shift (and Heiko wants to be able to monitor things
outside of Open Shift - I'll let him chime in on what his use cases are to get a
better feel for what he's thinking)
We need a name ASAP so we can create a repository under the Hawkular github namespace and
put the code up there so people can start working on it. I would like to do this sooner
rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k" ==
kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in "Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift (back to
the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a group -
but I nominate Thomas H, Heiko R, and John D. as the committee to give the final
approval/tie-breaking authority :) It won't be me. I suck at coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you can enter your
submissions and vote for other submissions?
7:17 p.m.
‘kubehawk’, ‘kubular’ or ‘hawkshift’ seem obvious…
— Mike
On Oct 18, 2016, at 10:08 AM, John Mazzitelli <mazz(a)redhat.com>
wrote:
OK, folks, as much as I hate these "what should we name this thing?" threads, I
have to do it.
We are at the point where we are going to start going full-throttle on building out an
agent that can monitor things on Open Shift (and Heiko wants to be able to monitor things
outside of Open Shift - I'll let him chime in on what his use cases are to get a
better feel for what he's thinking)
We need a name ASAP so we can create a repository under the Hawkular github namespace and
put the code up there so people can start working on it. I would like to do this sooner
rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k"
== kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in "Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift (back to
the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a group -
but I nominate Thomas H, Heiko R, and John D. as the committee to give the final
approval/tie-breaking authority :) It won't be me. I suck at coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you can enter your
submissions and vote for other submissions?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
7:32 p.m.
Hawkster :)
On 10/18/2016 1:17 PM, mike thompson wrote:
‘kubehawk’, ‘kubular’ or ‘hawkshift’ seem obvious…
— Mike
> On Oct 18, 2016, at 10:08 AM, John Mazzitelli <mazz(a)redhat.com> wrote:
>
> OK, folks, as much as I hate these "what should we name this thing?"
threads, I have to do it.
>
> We are at the point where we are going to start going full-throttle on building out
an agent that can monitor things on Open Shift (and Heiko wants to be able to monitor
things outside of Open Shift - I'll let him chime in on what his use cases are to get
a better feel for what he's thinking)
>
> We need a name ASAP so we can create a repository under the Hawkular github namespace
and put the code up there so people can start working on it. I would like to do this
sooner rather than later - say, by Thursday???
>
> Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because
"k" == kubernetes.
>
> I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in "Go"
>
> I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift (back to
the ideas Heiko has for this thing).
>
> "GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
>
> I'm assuming we'll come up with a name and agree to it collectively as a
group - but I nominate Thomas H, Heiko R, and John D. as the committee to give the final
approval/tie-breaking authority :) It won't be me. I suck at coming up with names.
>
> --John Mazz
>
> P.S. Who knows how to setup one of those online polls/surveys where you can enter
your submissions and vote for other submissions?
> _______________________________________________
> 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
8:04 p.m.
On Oct 18, 2016, at 10:32 AM, Jay Shaughnessy
<jshaughn(a)redhat.com> wrote:
Hawkster :)
Mazz was too afraid to send this: ‘Mazzster’
On 10/18/2016 1:17 PM, mike thompson wrote:
> ‘kubehawk’, ‘kubular’ or ‘hawkshift’ seem obvious…
>
> — Mike
>
>
>> On Oct 18, 2016, at 10:08 AM, John Mazzitelli <mazz(a)redhat.com>
<mailto:mazz@redhat.com> wrote:
>>
>> OK, folks, as much as I hate these "what should we name this thing?"
threads, I have to do it.
>>
>> We are at the point where we are going to start going full-throttle on building
out an agent that can monitor things on Open Shift (and Heiko wants to be able to monitor
things outside of Open Shift - I'll let him chime in on what his use cases are to get
a better feel for what he's thinking)
>>
>> We need a name ASAP so we can create a repository under the Hawkular github
namespace and put the code up there so people can start working on it. I would like to do
this sooner rather than later - say, by Thursday???
>>
>> Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because
"k" == kubernetes.
>>
>> I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in "Go"
>>
>> I wasn't keen on relying on "kubernetes" as part of the name since
its really targeting Open Shift and even then doesn't have to run in Open Shift (back
to the ideas Heiko has for this thing).
>>
>> "GoHawk" doesn't seem to be a winner simply because what happens if
we implement other hawkular feeds in Golang?
>>
>> I'm assuming we'll come up with a name and agree to it collectively as a
group - but I nominate Thomas H, Heiko R, and John D. as the committee to give the final
approval/tie-breaking authority :) It won't be me. I suck at coming up with names.
>>
>> --John Mazz
>>
>> P.S. Who knows how to setup one of those online polls/surveys where you can enter
your submissions and vote for other submissions?
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
<https://lists.jboss.org/mailman/listinfo/hawkular-dev>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
<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
9:19 p.m.
How about naming the project Hawkular KMon?
Thank you,
Stefan Negrea
On Tue, Oct 18, 2016 at 1:04 PM, mike thompson <mithomps(a)redhat.com> wrote:
On Oct 18, 2016, at 10:32 AM, Jay Shaughnessy <jshaughn(a)redhat.com> wrote:
Hawkster :)
Mazz was too afraid to send this: ‘Mazzster’
On 10/18/2016 1:17 PM, mike thompson wrote:
‘kubehawk’, ‘kubular’ or ‘hawkshift’ seem obvious…
— Mike
On Oct 18, 2016, at 10:08 AM, John Mazzitelli <mazz(a)redhat.com>
<mazz(a)redhat.com> wrote:
OK, folks, as much as I hate these "what should we name this thing?" threads, I
have to do it.
We are at the point where we are going to start going full-throttle on building out an
agent that can monitor things on Open Shift (and Heiko wants to be able to monitor things
outside of Open Shift - I'll let him chime in on what his use cases are to get a
better feel for what he's thinking)
We need a name ASAP so we can create a repository under the Hawkular github namespace and
put the code up there so people can start working on it. I would like to do this sooner
rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k"
== kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in "Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift (back to
the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a group -
but I nominate Thomas H, Heiko R, and John D. as the committee to give the final
approval/tie-breaking authority :) It won't be me. I suck at coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you can enter your
submissions and vote for other submissions?
_______________________________________________
hawkular-dev mailing
listhawkular-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing
listhawkular-dev@lists.jboss.orghttps://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
9:38 p.m.
On Tue, Oct 18, 2016 at 2:04 PM, mike thompson <mithomps(a)redhat.com> wrote:
On Oct 18, 2016, at 10:32 AM, Jay Shaughnessy <jshaughn(a)redhat.com> wrote:
Hawkster :)
Mazz was too afraid to send this: ‘Mazzster’
I'm going to guess that one does not make it past the PC police.
On 10/18/2016 1:17 PM, mike thompson wrote:
‘kubehawk’, ‘kubular’ or ‘hawkshift’ seem obvious…
— Mike
On Oct 18, 2016, at 10:08 AM, John Mazzitelli <mazz(a)redhat.com>
<mazz(a)redhat.com> wrote:
OK, folks, as much as I hate these "what should we name this thing?" threads, I
have to do it.
We are at the point where we are going to start going full-throttle on building out an
agent that can monitor things on Open Shift (and Heiko wants to be able to monitor things
outside of Open Shift - I'll let him chime in on what his use cases are to get a
better feel for what he's thinking)
We need a name ASAP so we can create a repository under the Hawkular github namespace and
put the code up there so people can start working on it. I would like to do this sooner
rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k"
== kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in "Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift (back to
the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a group -
but I nominate Thomas H, Heiko R, and John D. as the committee to give the final
approval/tie-breaking authority :) It won't be me. I suck at coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you can enter your
submissions and vote for other submissions?
_______________________________________________
hawkular-dev mailing
listhawkular-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing
listhawkular-dev@lists.jboss.orghttps://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
9:41 p.m.
I actually like "hawkulark". Why have only one bird when you can have two.
I'm sure to repeatedly misspell it, but that's true of most things I type.
~jd
On Tue, Oct 18, 2016 at 1:08 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
OK, folks, as much as I hate these "what should we name this
thing?"
threads, I have to do it.
We are at the point where we are going to start going full-throttle on
building out an agent that can monitor things on Open Shift (and Heiko
wants to be able to monitor things outside of Open Shift - I'll let him
chime in on what his use cases are to get a better feel for what he's
thinking)
We need a name ASAP so we can create a repository under the Hawkular
github namespace and put the code up there so people can start working on
it. I would like to do this sooner rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k"
==
kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented
in "Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift
(back to the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a
group - but I nominate Thomas H, Heiko R, and John D. as the committee to
give the final approval/tie-breaking authority :) It won't be me. I suck at
coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you
can enter your submissions and vote for other submissions?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
10:30 p.m.
Here's what we got in alphabetical order - and I can't believe I'm typing some
of these :p
GoHawk
Hawkshift
Hawkster
Hawkulark
KMon
Kubehawk
Kubular
We need more. All of these smell. You people disappoint me :) Where's Thomas S ??? We
need him.
Who knows how to create one of those online surveys?
10:54 p.m.
I hate these polls websites, but whatever:
http://doodle.com/poll/4xky52qwzdszrpz4
I want this done by Thursday. If you want me to add something to the list let me know. I
can't find a way to tell doodle to let a user add their own option.
So go vote. You won't feel dirty pulling the lever for whatever you pick, unlike our
presidential choices.
9:20 a.m.
Personally I would vote for:
- Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent" and
reduce its scope to the embedded WF scenario (+ remote for domains). Small
in scope == easier to maintain, document, understand...
- Name this one "Hawkular Kubernetes Agent", or "Hawkular OpenShift
Agent" if it really depends on OpenShift (but I'm not sure why), because
the discovery is a key feature and I guess (will) use Kubernetes API.
I can understand this could be extended to other usecases that don't
involve WildFly or Kubernetes, but I'm afraid that we just make things more
complex/harder to understand while those 2 targets are key.
PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark
(and in theory requires legal implication)
Thomas
On Tue, Oct 18, 2016 at 7:08 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
OK, folks, as much as I hate these "what should we name this
thing?"
threads, I have to do it.
We are at the point where we are going to start going full-throttle on
building out an agent that can monitor things on Open Shift (and Heiko
wants to be able to monitor things outside of Open Shift - I'll let him
chime in on what his use cases are to get a better feel for what he's
thinking)
We need a name ASAP so we can create a repository under the Hawkular
github namespace and put the code up there so people can start working on
it. I would like to do this sooner rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k"
==
kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented
in "Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift
(back to the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a
group - but I nominate Thomas H, Heiko R, and John D. as the committee to
give the final approval/tie-breaking authority :) It won't be me. I suck at
coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you
can enter your submissions and vote for other submissions?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
9:39 a.m.
I would really hate to have:
- Hawkular Agent (is our current name for the Wildfly agent)
- Hawkulark or hawkster or hawkshift... for this Kuber/Openshift one
- hawkraf or karhawk if we ever build an embedded karaf agent
- hawkdroid andrhawk when someone contributes an Android monitoring agent
- ...
On Wed, Oct 19, 2016 at 9:20 AM, Thomas Heute <theute(a)redhat.com> wrote:
Personally I would vote for:
- Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent"
and reduce its scope to the embedded WF scenario (+ remote for domains).
Small in scope == easier to maintain, document, understand...
- Name this one "Hawkular Kubernetes Agent", or "Hawkular OpenShift
Agent" if it really depends on OpenShift (but I'm not sure why), because
the discovery is a key feature and I guess (will) use Kubernetes API.
I can understand this could be extended to other usecases that don't
involve WildFly or Kubernetes, but I'm afraid that we just make things more
complex/harder to understand while those 2 targets are key.
PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark
(and in theory requires legal implication)
Thomas
On Tue, Oct 18, 2016 at 7:08 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
> OK, folks, as much as I hate these "what should we name this thing?"
> threads, I have to do it.
>
> We are at the point where we are going to start going full-throttle on
> building out an agent that can monitor things on Open Shift (and Heiko
> wants to be able to monitor things outside of Open Shift - I'll let him
> chime in on what his use cases are to get a better feel for what he's
> thinking)
>
> We need a name ASAP so we can create a repository under the Hawkular
> github namespace and put the code up there so people can start working on
> it. I would like to do this sooner rather than later - say, by Thursday???
>
> Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because
"k" ==
> kubernetes.
>
> I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented
> in "Go"
>
> I wasn't keen on relying on "kubernetes" as part of the name since its
> really targeting Open Shift and even then doesn't have to run in Open Shift
> (back to the ideas Heiko has for this thing).
>
> "GoHawk" doesn't seem to be a winner simply because what happens if we
> implement other hawkular feeds in Golang?
>
> I'm assuming we'll come up with a name and agree to it collectively as a
> group - but I nominate Thomas H, Heiko R, and John D. as the committee to
> give the final approval/tie-breaking authority :) It won't be me. I suck at
> coming up with names.
>
> --John Mazz
>
> P.S. Who knows how to setup one of those online polls/surveys where you
> can enter your submissions and vote for other submissions?
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
9:58 a.m.
On 19 Oct 2016, at 9:20, Thomas Heute wrote:
Personally I would vote for:
- Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent" and
reduce its scope to the embedded WF scenario (+ remote for domains). Small
in scope == easier to maintain, document, understand...
- Name this one "Hawkular Kubernetes Agent", or "Hawkular OpenShift
Agent" if it really depends on OpenShift (but I'm not sure
+1
PS: I don't think we need yet another cryptic name as GoHawk /
Hawkulark
(and in theory requires legal implication)
The binary certainly needs one - but something like hawkagent
should be good enough here.
10:06 a.m.
Other cryptic names we won't use anyway: hawkenshift (sonority close to
openshift), variant: Hawk'n Shift
But +1 for the desperately serious "Hawkular Kubernetes/OpenShift Agent"
and renaming Hawkular Agent :)
On Wed, Oct 19, 2016 at 9:58 AM, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
On 19 Oct 2016, at 9:20, Thomas Heute wrote:
> Personally I would vote for:
> - Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent"
and
> reduce its scope to the embedded WF scenario (+ remote for domains).
Small
> in scope == easier to maintain, document, understand...
> - Name this one "Hawkular Kubernetes Agent", or "Hawkular
OpenShift
> Agent" if it really depends on OpenShift (but I'm not sure
+1
> PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark
> (and in theory requires legal implication)
The binary certainly needs one - but something like hawkagent
should be good enough here.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
2:12 p.m.
Yes, hawkster was meant as a joke with a nod to heapster, I am +1 to a
series of 'Hawkular * Agent' namings. Although, one more just for fun,
hawkfeed!
On 10/19/2016 4:06 AM, Joel Takvorian wrote:
Other cryptic names we won't use anyway: hawkenshift (sonority
close
to openshift), variant: Hawk'n Shift
But +1 for the desperately serious "Hawkular Kubernetes/OpenShift
Agent" and renaming Hawkular Agent :)
On Wed, Oct 19, 2016 at 9:58 AM, Heiko W.Rupp <hrupp(a)redhat.com
<mailto:hrupp@redhat.com>> wrote:
On 19 Oct 2016, at 9:20, Thomas Heute wrote:
> Personally I would vote for:
> - Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent" and
> reduce its scope to the embedded WF scenario (+ remote for
domains). Small
> in scope == easier to maintain, document, understand...
> - Name this one "Hawkular Kubernetes Agent", or "Hawkular
OpenShift
> Agent" if it really depends on OpenShift (but I'm not sure
+1
> PS: I don't think we need yet another cryptic name as GoHawk /
Hawkulark
> (and in theory requires legal implication)
The binary certainly needs one - but something like hawkagent
should be good enough here.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
<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
2:37 p.m.
Hello,
It's hard to come up with some name that fits well with the hawk and ocular
metaphor. I like what the ELK stack has, they have units called beats (it
evokes some periodicity to me and also it sounds like a bee). imho, "bee"
is the best name for a lightweight agent that collect metrics, but it
doesn't work for us.
What about having multiple agents called "ocular" or okular. Like OpenShift
Okular, WildFly Okular, ${you name it} Okular? Although, flying hawk w/
multiple oculars imply the pull architecture. Hawkular X Agent isn't bad,
but it's too long and too enterprisy, worse is only Red Hat Hawkular
OpenShift Agent :]
jk
On Wed, Oct 19, 2016 at 10:06 AM, Joel Takvorian <jtakvori(a)redhat.com>
wrote:
Other cryptic names we won't use anyway: hawkenshift (sonority
close to
openshift), variant: Hawk'n Shift
But +1 for the desperately serious "Hawkular Kubernetes/OpenShift Agent"
and renaming Hawkular Agent :)
On Wed, Oct 19, 2016 at 9:58 AM, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
> On 19 Oct 2016, at 9:20, Thomas Heute wrote:
>
> > Personally I would vote for:
> > - Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent"
> and
> > reduce its scope to the embedded WF scenario (+ remote for domains).
> Small
> > in scope == easier to maintain, document, understand...
> > - Name this one "Hawkular Kubernetes Agent", or "Hawkular
OpenShift
> > Agent" if it really depends on OpenShift (but I'm not sure
>
> +1
>
> > PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark
> > (and in theory requires legal implication)
>
> The binary certainly needs one - but something like hawkagent
> should be good enough here.
> _______________________________________________
> 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
3:24 p.m.
OK, so if we use Hawkular Kubernetes Agent then the gitrepo would be named:
hawkular/hawkular-kubernetes-agent
Yes?
----- Original Message -----
Personally I would vote for:
- Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent" and
reduce its scope to the embedded WF scenario (+ remote for domains). Small
in scope == easier to maintain, document, understand...
- Name this one "Hawkular Kubernetes Agent", or "Hawkular OpenShift
Agent" if it really depends on OpenShift (but I'm not sure why), because
the discovery is a key feature and I guess (will) use Kubernetes API.
I can understand this could be extended to other usecases that don't
involve WildFly or Kubernetes, but I'm afraid that we just make things more
complex/harder to understand while those 2 targets are key.
PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark
(and in theory requires legal implication)
Thomas
On Tue, Oct 18, 2016 at 7:08 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
> OK, folks, as much as I hate these "what should we name this thing?"
> threads, I have to do it.
>
> We are at the point where we are going to start going full-throttle on
> building out an agent that can monitor things on Open Shift (and Heiko
> wants to be able to monitor things outside of Open Shift - I'll let him
> chime in on what his use cases are to get a better feel for what he's
> thinking)
>
> We need a name ASAP so we can create a repository under the Hawkular
> github namespace and put the code up there so people can start working on
> it. I would like to do this sooner rather than later - say, by Thursday???
>
> Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because
"k" ==
> kubernetes.
>
> I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented
> in "Go"
>
> I wasn't keen on relying on "kubernetes" as part of the name since
its
> really targeting Open Shift and even then doesn't have to run in Open Shift
> (back to the ideas Heiko has for this thing).
>
> "GoHawk" doesn't seem to be a winner simply because what happens if
we
> implement other hawkular feeds in Golang?
>
> I'm assuming we'll come up with a name and agree to it collectively as a
> group - but I nominate Thomas H, Heiko R, and John D. as the committee to
> give the final approval/tie-breaking authority :) It won't be me. I suck at
> coming up with names.
>
> --John Mazz
>
> P.S. Who knows how to setup one of those online polls/surveys where you
> can enter your submissions and vote for other submissions?
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
3:28 p.m.
> Personally I would vote for:
> - Renaming the existing "Hawkular Agent" to "Hawkular WildFly
Agent" and
> reduce its scope to the embedded WF scenario (+ remote for domains). Small
> in scope == easier to maintain, document, understand...
For the record, that has been what I've been calling that agent for a while now.
"Hawkular WildFly Agent". The git repo isn't called that, but the internals
are - e.g. https://github.com/hawkular/hawkular-agent/tree/master/hawkular-wildfly-a...
The "hawkular-agent" repo was created and named as such with the naive thought
that all hawkular feeds/agents would go under that one big umbrella repo. But that ended
up being a stupid idea :)
3:39 p.m.
> OK, so if we use Hawkular Kubernetes Agent then the gitrepo
would be named:
>
> hawkular/hawkular-kubernetes-agent
Sounds good to me
And the executable name? The name we call it in code and in logging messages?
Based on what people are saying, I'm just going to call the executable
"hawkular-kubernetes-agent" and have for example
"hawkular-kubernetes-agent.go" and when logging needs to name it call it
"Hawkular Kubernetes Agent"
This is what I was getting at - I wasn't asking for the "product name" (we
can call it anything we want and it doesn't affect me at this point in time :) but
what are we to call it in the code, for logging messages, executable names, github repo,
etc. I'm fine with "hawkular-kubernetes-agent" and everything that entails
if that is what people want.
3:40 p.m.
+1 to the verbose naming, it's totally clear if we just do it that way.
On 10/19/2016 9:39 AM, John Mazzitelli wrote:
>> OK, so if we use Hawkular Kubernetes Agent then the gitrepo
would be named:
>>
>> hawkular/hawkular-kubernetes-agent
> Sounds good to me
And the executable name? The name we call it in code and in logging messages?
Based on what people are saying, I'm just going to call the executable
"hawkular-kubernetes-agent" and have for example
"hawkular-kubernetes-agent.go" and when logging needs to name it call it
"Hawkular Kubernetes Agent"
This is what I was getting at - I wasn't asking for the "product name" (we
can call it anything we want and it doesn't affect me at this point in time :) but
what are we to call it in the code, for logging messages, executable names, github repo,
etc. I'm fine with "hawkular-kubernetes-agent" and everything that entails
if that is what people want.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:51 p.m.
+1 on the format and hawkular/hawkular-wildfly-agent (renaming sucks but
we're still young enough to allow this)
But we still need to decide betwen Openshift vs Kubernetes.
On Wed, Oct 19, 2016 at 3:32 PM, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
On 19 Oct 2016, at 15:24, John Mazzitelli wrote:
> OK, so if we use Hawkular Kubernetes Agent then the gitrepo would be
named:
>
> hawkular/hawkular-kubernetes-agent
Sounds good to me
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:55 p.m.
So assume Hawkular Metrics is running "somewhere", is the agent itself
dependent on OpenShift or Kubernetes ?
On Wed, Oct 19, 2016 at 3:51 PM, Thomas Heute <theute(a)redhat.com> wrote:
+1 on the format and hawkular/hawkular-wildfly-agent (renaming sucks
but
we're still young enough to allow this)
But we still need to decide betwen Openshift vs Kubernetes.
On Wed, Oct 19, 2016 at 3:32 PM, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
> On 19 Oct 2016, at 15:24, John Mazzitelli wrote:
>
> > OK, so if we use Hawkular Kubernetes Agent then the gitrepo would be
> named:
> >
> > hawkular/hawkular-kubernetes-agent
>
> Sounds good to me
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
4:19 p.m.
As far as I can tell this agent (as of today, think of the demo I showed yesterday) does
not use anything Open Shift specific. Its all k8s APIs we are calling. But I've only
ever run it against an Open Shift installation.
----- Original Message -----
So assume Hawkular Metrics is running "somewhere", is the
agent itself
dependent on OpenShift or Kubernetes ?
On Wed, Oct 19, 2016 at 3:51 PM, Thomas Heute <theute(a)redhat.com> wrote:
> +1 on the format and hawkular/hawkular-wildfly-agent (renaming sucks but
> we're still young enough to allow this)
>
> But we still need to decide betwen Openshift vs Kubernetes.
>
>
>
> On Wed, Oct 19, 2016 at 3:32 PM, Heiko W.Rupp <hrupp(a)redhat.com> wrote:
>
>> On 19 Oct 2016, at 15:24, John Mazzitelli wrote:
>>
>> > OK, so if we use Hawkular Kubernetes Agent then the gitrepo would be
>> named:
>> >
>> > hawkular/hawkular-kubernetes-agent
>>
>> Sounds good to me
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>>
>>
>
4:21 p.m.
As far as I can tell this agent (as of today, think of the demo I
showed
yesterday) does not use anything Open Shift specific. Its all k8s APIs we
are calling. But I've only ever run it against an Open Shift installation.
Here's the Go imports - notice all k8s - so nothing OS specific:
core "k8s.io/client-go/1.4/kubernetes/typed/core/v1"
"k8s.io/client-go/1.4/pkg/api"
"k8s.io/client-go/1.4/pkg/api/v1"
"k8s.io/client-go/1.4/pkg/fields"
"k8s.io/client-go/1.4/pkg/watch"
4:28 p.m.
How about the forseeable future ? I know it's a big question :)
Thomas
On Wed, Oct 19, 2016 at 4:21 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
> As far as I can tell this agent (as of today, think of the demo
I showed
> yesterday) does not use anything Open Shift specific. Its all k8s APIs we
> are calling. But I've only ever run it against an Open Shift
installation.
Here's the Go imports - notice all k8s - so nothing OS specific:
core "k8s.io/client-go/1.4/kubernetes/typed/core/v1"
"k8s.io/client-go/1.4/pkg/api"
"k8s.io/client-go/1.4/pkg/api/v1"
"k8s.io/client-go/1.4/pkg/fields"
"k8s.io/client-go/1.4/pkg/watch"
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
4:31 p.m.
I defer to Matt :)
He seems to have his finger on the pulse of Open Shift and could say if he thinks there
are some specific OS features (current or future features) we will want to take advantage
of.
----- Original Message -----
How about the forseeable future ? I know it's a big question :)
Thomas
On Wed, Oct 19, 2016 at 4:21 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
> > As far as I can tell this agent (as of today, think of the demo I showed
> > yesterday) does not use anything Open Shift specific. Its all k8s APIs we
> > are calling. But I've only ever run it against an Open Shift
> installation.
>
> Here's the Go imports - notice all k8s - so nothing OS specific:
>
> core "k8s.io/client-go/1.4/kubernetes/typed/core/v1"
> "k8s.io/client-go/1.4/pkg/api"
> "k8s.io/client-go/1.4/pkg/api/v1"
> "k8s.io/client-go/1.4/pkg/fields"
> "k8s.io/client-go/1.4/pkg/watch"
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
>
9:34 p.m.
From my comments earlier today:
"The agent itself should only be using the Kubernetes API and shouldn't have
anything specific to OpenShift. So the agent here shouldn't care or know if its really
connecting to Kubernetes or OpenShift.
The problem is more that the Hawkular Metrics integration we have with OpenShift wont work
in plain Kubernetes and we don't test it there. It would be possible to make it work
on Kubernetes, but it wouldn't be a trivial change and would take some effort and
testing to get it working there. We don't have the spare cycles or manpower to support
the Kubernetes use case right now and this isn't even on our radar. It might be cool
to have something usable with the upstream Kubernetes community though."
Since we don't have a Hawkular Metrics version that is being used and tested in
Kubernetes, I would be against using a name with 'Kubernetes' in it at this
moment. Its going to be confusing to anyone who wants to try this in the Kubernetes
directly, as the agent may work, but what it writes to will not.
We may also want to add in some OpenShift specific features in there as well.
I would vote to call it the "Hawkular OpenShift Agent" rather than the
"Hawkular Kubernetes Agent" for these reasons.
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Wednesday, 19 October, 2016 10:31:07 AM
Subject: Re: [Hawkular-dev] open shift agent - what to call it?
I defer to Matt :)
He seems to have his finger on the pulse of Open Shift and could say if he
thinks there are some specific OS features (current or future features) we
will want to take advantage of.
----- Original Message -----
> How about the forseeable future ? I know it's a big question :)
>
> Thomas
>
> On Wed, Oct 19, 2016 at 4:21 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
>
> > > As far as I can tell this agent (as of today, think of the demo I
> > > showed
> > > yesterday) does not use anything Open Shift specific. Its all k8s APIs
> > > we
> > > are calling. But I've only ever run it against an Open Shift
> > installation.
> >
> > Here's the Go imports - notice all k8s - so nothing OS specific:
> >
> > core "k8s.io/client-go/1.4/kubernetes/typed/core/v1"
> > "k8s.io/client-go/1.4/pkg/api"
> > "k8s.io/client-go/1.4/pkg/api/v1"
> > "k8s.io/client-go/1.4/pkg/fields"
> > "k8s.io/client-go/1.4/pkg/watch"
> > _______________________________________________
> > 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
3:29 p.m.
----- Original Message -----
From: "Thomas Heute" <theute(a)redhat.com>
To: "John Mazzitelli" <mazz(a)redhat.com>, "Discussions around
Hawkular development" <hawkular-dev(a)lists.jboss.org>
Sent: Wednesday, 19 October, 2016 3:20:54 AM
Subject: Re: [Hawkular-dev] open shift agent - what to call it?
Personally I would vote for:
- Renaming the existing "Hawkular Agent" to "Hawkular WildFly Agent"
and
reduce its scope to the embedded WF scenario (+ remote for domains). Small
in scope == easier to maintain, document, understand...
+1
- Name this one "Hawkular Kubernetes Agent", or
"Hawkular OpenShift Agent"
+1
if
it really depends on OpenShift (but I'm not sure why), because the discovery
is a key feature and I guess (will) use Kubernetes API.
This is a bit interesting.
The agent itself should only be using the Kubernetes API and shouldn't have anything
specific to OpenShift. So the agent here shouldn't care or know if its really
connecting to Kubernetes or OpenShift.
The problem is more that the Hawkular Metrics integration we have with OpenShift wont work
in plain Kubernetes and we don't test it there. It would be possible to make it work
on Kubernetes, but it wouldn't be a trivial change and would take some effort and
testing to get it working there. We don't have the spare cycles or manpower to support
the Kubernetes use case right now and this isn't even on our radar. It might be cool
to have something usable with the upstream Kubernetes community though.
I can understand this could be extended to other usecases that don't involve
WildFly or Kubernetes, but I'm afraid that we just make things more
complex/harder to understand while those 2 targets are key.
PS: I don't think we need yet another cryptic name as GoHawk / Hawkulark (and
in theory requires legal implication)
Yeah, they are cool for codenames, but I don't think we want to go through the whole
legal stuff for this. And as already mentioned, when we start to have more agents, its
going to be confusing over each one of them having unique names.
Thomas
On Tue, Oct 18, 2016 at 7:08 PM, John Mazzitelli < mazz(a)redhat.com > wrote:
OK, folks, as much as I hate these "what should we name this thing?" threads,
I have to do it.
We are at the point where we are going to start going full-throttle on
building out an agent that can monitor things on Open Shift (and Heiko wants
to be able to monitor things outside of Open Shift - I'll let him chime in
on what his use cases are to get a better feel for what he's thinking)
We need a name ASAP so we can create a repository under the Hawkular github
namespace and put the code up there so people can start working on it. I
would like to do this sooner rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k"
==
kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in
"Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really
targeting Open Shift and even then doesn't have to run in Open Shift (back
to the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a
group - but I nominate Thomas H, Heiko R, and John D. as the committee to
give the final approval/tie-breaking authority :) It won't be me. I suck at
coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you can
enter your submissions and vote for other submissions?
_______________________________________________
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
2:52 p.m.
We can also try a name that aligns with our upstream parent projects, Origin and Atomic.
I can't think of any at the moment :)
Viet
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, October 18, 2016 7:08:35 PM
Subject: [Hawkular-dev] open shift agent - what to call it?
OK, folks, as much as I hate these "what should we name this thing?" threads, I
have to do it.
We are at the point where we are going to start going full-throttle on building out an
agent that can monitor things on Open Shift (and Heiko wants to be able to monitor things
outside of Open Shift - I'll let him chime in on what his use cases are to get a
better feel for what he's thinking)
We need a name ASAP so we can create a repository under the Hawkular github namespace and
put the code up there so people can start working on it. I would like to do this sooner
rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k" ==
kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in "Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really targeting Open Shift and even then doesn't have to run in Open Shift (back to
the ideas Heiko has for this thing).
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a group -
but I nominate Thomas H, Heiko R, and John D. as the committee to give the final
approval/tie-breaking authority :) It won't be me. I suck at coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you can enter your
submissions and vote for other submissions?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:19 p.m.
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, 18 October, 2016 1:08:35 PM
Subject: [Hawkular-dev] open shift agent - what to call it?
OK, folks, as much as I hate these "what should we name this thing?" threads,
I have to do it.
We are at the point where we are going to start going full-throttle on
building out an agent that can monitor things on Open Shift (and Heiko wants
to be able to monitor things outside of Open Shift - I'll let him chime in
on what his use cases are to get a better feel for what he's thinking)
We need a name ASAP so we can create a repository under the Hawkular github
namespace and put the code up there so people can start working on it. I
would like to do this sooner rather than later - say, by Thursday???
Matt was thinking "hawkulark" (Hawk-U-Lark, Hawkular-K) because "k"
==
kubernetes.
I was thinking "GoHawk" (rhymes with "mohawk") because it is
implemented in
"Go"
I wasn't keen on relying on "kubernetes" as part of the name since its
really
targeting Open Shift and even then doesn't have to run in Open Shift (back
to the ideas Heiko has for this thing).
I am not sure if I like the idea of one agent handling multiple scenarios, I think it
makes sense to keep them as separate agents.
I do think it makes sense to share a common go library though, so that we can avoid code
duplication. But the end result would still be separate agents.
Eg the OpenShift agent would have code to connect to monitor the OpenShift cluster, figure
out where the endpoints are, add in the tags, determine the schedule etc and then would
just pass this information to a common go lang agent library to actually fetch the metrics
and send to Hawkular Metrics.
"GoHawk" doesn't seem to be a winner simply because what happens if we
implement other hawkular feeds in Golang?
I'm assuming we'll come up with a name and agree to it collectively as a
group - but I nominate Thomas H, Heiko R, and John D. as the committee to
give the final approval/tie-breaking authority :) It won't be me. I suck at
coming up with names.
--John Mazz
P.S. Who knows how to setup one of those online polls/surveys where you can
enter your submissions and vote for other submissions?
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3:22 p.m.
then would just pass this information to a common go lang
agent library to actually fetch the metrics and send to Hawkular Metrics.
We have part of that already - Micke's hawkular-client-go library sends to Hawkular
Metrics.
We could split out the prometheus scraping code that currently exists in the Go agent for
a "fetch the metrics" library.
3:32 p.m.
On 19 Oct 2016, at 15:19, Matt Wringe wrote:
> I wasn't keen on relying on "kubernetes" as part of
the name since
> its really
> targeting Open Shift and even then doesn't have to run in Open Shift
> (back
> to the ideas Heiko has for this thing).
I am not sure if I like the idea of one agent handling multiple
scenarios, I think it makes sense to keep them as separate agents.
My thinking went along the lines, that it should be possible to
test it and/or the interaction with the monitored resource without
the need for a full (mini)kube/shift.
As you say, we can also have a "library" for interaction with
hawkular and the monitored resource and then build multiple
apps on top that talk to k8s or OS or just run on a 'normal'
command line
2746
days inactive
2747
days old
31 comments
11 participants
participants (11)
-
Heiko W.Rupp -
Jay Shaughnessy -
Jiri Kremser -
Joel Takvorian -
John Doyle -
John Mazzitelli -
Matt Wringe -
mike thompson -
Stefan Negrea -
Thomas Heute -
Viet Nguyen