<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<font face="Calibri">OK, I can certainly see the advantage of being
able to add to or update our supported entities without requiring
changes to MIQ. As Mazz said, it's a throwback to RHQ where
persistence and UI was generically implemented. The question is
whether we can do something similar but more simple. It's not a
small undertaking to convert to a config-driven UI, especially
within the confines of MIQ. My suggestion to have the UI-config
differ from the agent config was motivated by a few things:<br>
</font>
<ul>
<li><font face="Calibri">the UI config may need more
presentation-only info, I'm not sure</font></li>
<li><font face="Calibri">the UI config wouldn't necessarily need
everything in the agent config<br>
</font></li>
<li><font face="Calibri">it maintains our current decentralized
approach to agent config</font></li>
</ul>
<p><font face="Calibri">On the downside, it would mean keeping
another config up to date and having the server provide it in
some way to the gem/ui. It's also not clear to me MIQ will
green-light a generic approach to the db-tables. When I tried
to do some generic things early on it was rejected in favor of
explicit fields and maintaining consistency with the way things
were being done elsewhere. Note that there are hooks with
events and alerts, and maybe metrics, that would likely need to
be revisited if we move to a more generic approach to the
tables.</font><br>
</p>
<br>
<div class="moz-cite-prefix">On 5/26/2017 9:25 AM, Heiko W.Rupp
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:81444A5C-4ADC-420A-B7B6-655B82A8EC81@redhat.com">
<pre wrap="">On 26 May 2017, at 5:58, Josejulio Martinez Magana wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Do we really need to drive off an agent or server-side config? Perhaps
</pre>
</blockquote>
<pre wrap="">+1
I think we should consider this option. The agent provides general
</pre>
</blockquote>
<pre wrap="">
I am not married to the agent providing this metadata, which
is shown by the "or on the server" part ;-)
Driving the UI from metadata on the Hawkular-services
side allows us to add support for new kinds of servers
- outside of MiQ release cycles
- by the people that write those servers without them becoming MiQ experts
Also issues like e.g. a missing property can be fixed on the H-S
side by adding this to the metdata.
_______________________________________________
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>