Re: [Hawkular-dev] Resourcetype again
And a major question still to be addressed is how and when does the agent get the type
metadata? Right now, it "owns" the metadata in standalone.xml. But it would be
nice for metadata to be downloaded from the hawkular server - if there is no metadata
available, then the agent can fallback and use its standalone.xml definitions.
I have not thought long about the metadata storage in hawkular and the interface the agent
should use to get it. We need to figure that out.
----- Original Message -----
Hey,
I want to pick up this discussion again. Especially as we had a point in
time some days ago, where the agent code was supporting the "JDR"
operation, but only the Hawkular-server-internal one had it in its
meta-data, while a standalone one was missing it, which was
inconsistent.
I have attached a diagram, that I labeled "Fallback"-Graph. Basically a
type on the top, if it does not exist yet in inventory, the code should
be fall back to the definition below.
E.g. if a WildFly10 server definition does not yet exist, the one for
WF9 should be taken.
There are tricky places though:
- Product 2.1 may run on top of a Product 1, but also get some
additional capabilities from Infinispan 8
- Product 2 may be a Hawkular Server, but where some experimental
features are disabled. It will also run on top of Product 1, while the
Hawkular Server runs on top of WF9
- Product 1 may have a reduced feature set over WF 10
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev