Hi,
Running multiple servers per pod sounds like a defeat of the whole idea of docker ;). If
you run multiple instances of this same pod, each one will have a different hostname (the
hawkular-cassandra would stay the same, but the part after it would change).
- Micke
----- Original Message -----
From: "Jay Shaughnessy" <jshaughn(a)redhat.com>
To: hawkular-dev(a)lists.jboss.org
Sent: Friday, July 29, 2016 9:09:02 PM
Subject: Re: [Hawkular-dev] Identification of WildFly in container in a Kube/Openshift
env
Are multiple servers/agents per container a possibility? If so we'd need to append a
differentiator to the container identifier.
Also, with respect to a feedid based on deployments, isn't it possible that multiple
containers run the same deployments for load-balancing purposes? Wouldn't that result
in multiple agents running with the same feedid? Anyway, It seems if we could derive a
feedid from the container, with perhaps a new token like autogenerate-from-container, that
could be a nice way to easily identify a feed for a container. This doesn't solve the
issue of replacing a stopped container with a new container, thus generating new inventory
and orphaning the existing inventory. But in that situation I think we may just want to
look for a decent way to kill that inventory, like TTL or something.
On 7/28/2016 1:08 PM, John Mazzitelli wrote:
Is there any reason the agent can't use container as identification?
HOSTNAME="hawkular-cassandra-1-6o1y8"
Things like that would work well.
We could even allow the agent to support notation like this:
<storage-adapter feed-id="%envvar(HOSTNAME)" ... />
or whatever syntax makes sense
_______________________________________________
hawkular-dev mailing list hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev