[Hawkular-dev] Identification of WildFly in container in a Kube/Openshift env

Juraci Paixão Kröhling jpkroehling at redhat.com
Wed Jul 27 13:08:46 EDT 2016


On 27.07.2016 19:06, Juraci Paixão Kröhling wrote:
> On 27.07.2016 18:51, John Mazzitelli wrote:
>>> - feed-id: sha1sum(sha1sum(foobar.war) + sha1sum(foobar-ds.xml))
>>> result: a4f36be49f641967e51e2707c1fe6d0a29c2f682
>>
>> Calculating the feed ID based on discovered resources is going to be very difficult if not impossible with the current implementation - the agent needs the feed ID upfront during startup before it even runs discovery (i.e. before it even knows about any resources - let along child resources like deployments) - it requires the feed ID internally to start many components, it can't talk to hawkular-inventory without it, and it needs the feed ID to connect to the hawkular cmdgw server.
>
> I considered this, but I thought it wouldn't be a problem to implement a
> separate Wildfly extension that would calculate this during the boot and
> put the resulting value in a system property for later use by the agent
> itself. Would that work?

By the way: I don't think this extension needs to wait for the deployers 
either: all it would need to do is to get a VirtualJarInputStream for 
each of the deployments, and calculate the sha1sum based on that.

- Juca.


More information about the hawkular-dev mailing list