[Hawkular-dev] open shift agent - what to call it?

[Matt Wringe]

----- Original Message -----
> From: "Thomas Heute" <theute at redhat.com>
> To: "John Mazzitelli" <mazz at redhat.com>, "Discussions around Hawkular development" <hawkular-dev at 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 at 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 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
>