Re: [Hawkular-dev] Identification of WildFly in container in a Kube/Openshift env
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.
Updating the feed name ex post:
https://git.io/vKAl2
Calculating the feed ID based on discovered resources... - identity hashes
in inventory, Lukas knows
On Wed, Jul 27, 2016 at 6:51 PM, John Mazzitelli <mazz(a)redhat.com> 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.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
Attachments:
- attachment.html (text/html — 2.3 KB)