<div dir="ltr">see this comment (the last part of it) that mentions a somewhat similar dynamic concept <br><br><a href="http://talk.manageiq.org/t/rethinking-providers-and-managers/2494/11">http://talk.manageiq.org/t/rethinking-providers-and-managers/2494/11</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 26, 2017 at 7:05 PM, Heiko Rupp <span dir="ltr"><<a href="mailto:hrupp@redhat.com" target="_blank">hrupp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Now that Caina is doing a PoC I want to revisit the<br>
source of metadata question again.<br>
<span class=""><br>
On 30 May 2017, at 23:11, Jay Shaughnessy wrote:<br>
<br>
> changes to MIQ. As Mazz said, it's a throwback to RHQ where<br>
> persistence and UI was generically implemented. The<br>
<br>
</span>This is to quickly get a 70% version out and to be able to<br>
quickly add new monitored stuff. This should and will not<br>
prevent us from generating more dedicated UI screens later.<br>
<br>
> * the UI config may need more presentation-only info, I'm not sure<br>
<br>
Yes<br>
<br>
> * the UI config wouldn't necessarily need everything in the agent<br>
> config<br>
> * it maintains our current decentralized approach to agent config<br>
<br>
This one I am no longer sure about. It was a great idea<br>
back in the day. I see two cases<br>
<br>
* user uses the same config for all WildFlys - why do we<br>
want to duplicate the metadata for all of those if<br>
the (RT) config is effectively the same?<br>
* user has modified the agent config to have<br>
more/less fields. In this case the current MiQ UI would<br>
not adapt to it and in either way just not show the<br>
data. And it may not even be clear when there are<br>
two WildFly in inventory with different configs, why they<br>
don't show this difference<br>
<br>
For WildFly in container it may even be less interesting<br>
with the current approach as here all the WildFlys will be<br>
built on one base image (that we supply with a baked in<br>
config?).<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>_________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/hawkular-dev</a><br>
</div></div></blockquote></div><br></div>