<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<font face="Calibri">Actually, the resource types are global across
[hawkular] servers as well, right? We'd likely use the same agent
config files across multiple server instances.</font><br>
<br>
<div class="moz-cite-prefix">On 10/13/2017 3:03 AM, Joel Takvorian
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJo5TFmaPsy4=uEf7huXa-8-=zotmRmqwVg6tXeGszqo_KMDWg@mail.gmail.com">
<div dir="ltr">Just adding here, that the new model (as it is
currently defined) makes it mandatory to have unique resource
type definition per server ; that is, the resource types
definitions cannot vary from an agent to another.
<div>Technically speaking, it doesn't have feedId.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 12, 2017 at 11:20 PM, Jay
Shaughnessy <span dir="ltr"><<a
href="mailto:jshaughn@redhat.com" target="_blank"
moz-do-not-send="true">jshaughn@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""><br>
<br>
On 10/12/2017 3:18 PM, John Mazzitelli wrote:<br>
>> It might also be good to reserve a time to have a
call to discuss this over<br>
>> bluejeans.<br>
>><br>
>> As far as I can tell, the plan isn't to have
server side configurations<br>
>> (like you would with a pull model) but instead to
continue to have client<br>
>> side configurations but have the server be able
to push out updates to the<br>
>> client.<br>
> The idea isn't a "push from server to agent", rather
its the agent pulling its config from the server.<br>
<br>
</span>When you say, "As far as I can tell, the plan isn't
to have server side<br>
configurations", where is that coming from? It's true
that in the<br>
past we had agent-side<br>
config, but it has been a while now that we've planned on
going to a<br>
centralized config, to avoid unnecessary complexity and to
minimize the<br>
need to update<br>
agents. Anyway, as Mazz points out, the mechanism is
already there to<br>
serve up the files. I just wanted to make sure there isn't
a change in<br>
plan, or a doc, that<br>
I'm not aware of.<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
>> Will this require a new component to expose
REST endpoints at the server<br>
>> level? or are we planning on reusing an
existing component?<br>
> We already have something in place today:<br>
><br>
> <a
href="https://github.com/hawkular/hawkular-commons/blob/mwm-wildfly/hawkular-inventory-parent/hawkular-inventory-service/src/main/java/org/hawkular/inventory/handlers/InventoryHandlers.java#L78-L94"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/hawkular/<wbr>hawkular-commons/blob/mwm-<wbr>wildfly/hawkular-inventory-<wbr>parent/hawkular-inventory-<wbr>service/src/main/java/org/<wbr>hawkular/inventory/handlers/<wbr>InventoryHandlers.java#L78-L94</a><br>
><br>
>> Are we going to be able to have individual
configurations per server, or<br>
>> are we lumping things into server types (eg all
EAP7 instances have the<br>
>> same configuration)<br>
> Preferably we are going to be grouping config based
on server type. I mention an example in the JIRA
comment:<br>
><br>
> These server-side configuration files are centrally
located and will define types for all servers to be
managed. There is not going to be one uber file. There
will be two files per server kind (two files because one
is for jmx exporter, the other is for our agent).<br>
><br>
> e.g.<br>
> EAP-7.0.0-Final-jmx-exporter.<wbr>yaml<br>
> EAP-7.0.0-Final-inventory.yaml<br>
> Fuse-1.1.0-RC2-jmx-exporter.<wbr>yaml<br>
> Fuse-1.1.0-RC2-inventory.yaml<br>
><br>
> So when EAP 7.1 is released, we'll just add two new
files to the central location on the server and the
agent can start downloading those to managed EAP 7.1
servers.<br>
> ______________________________<wbr>_________________<br>
> hawkular-dev mailing list<br>
> <a href="mailto:hawkular-dev@lists.jboss.org"
moz-do-not-send="true">hawkular-dev@lists.jboss.org</a><br>
> <a
href="https://lists.jboss.org/mailman/listinfo/hawkular-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.jboss.org/<wbr>mailman/listinfo/hawkular-dev</a><br>
><br>
<br>
______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org"
moz-do-not-send="true">hawkular-dev@lists.jboss.org</a><br>
<a
href="https://lists.jboss.org/mailman/listinfo/hawkular-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.jboss.org/<wbr>mailman/listinfo/hawkular-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
hawkular-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/hawkular-dev">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>