Re: [Hawkular-dev] Identification of WildFly in container in a Kube/Openshift env
On 28.07.2016 16:20, Heiko W.Rupp wrote:
There is one case we need to consider here:
we have an image with foobar.war;v1 with a certain sha.
Now the user creates a new image with foobar.war;v2.
For the user this is logically the same thing but with a
different version.
We should not treat that as different applications.
In this case we would rather need to record the fact
that v1 was replaced by v2 (by putting a tag) and
continue the already recorded metrics for the same
(logical) application.
Do you mean that the contents of v1 are different of that for v2? If so,
only the feed-id will be different. Everything else is as it is today:
it's the same case as if the company had deployed a new VM with the v2,
router some traffic to it for A/B testing, and shut down the v1 once
they are happy with v2.
If it is important to have consistent feed-ids across the whole life of
the application, then I see no other option than to "force" the consumer
to specify a feed-id on the image building process.
- Juca.