pcp
[Top] [All Lists]

[Bug 1109] fuzzy container hex-id naming leads to nondeterminism

To: pcp@xxxxxxxxxxx
Subject: [Bug 1109] fuzzy container hex-id naming leads to nondeterminism
From: bugzilla-daemon@xxxxxxxxxxx
Date: Fri, 15 May 2015 01:16:02 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <bug-1109-835@xxxxxxxxxxxxxxxx/bugzilla/>
References: <bug-1109-835@xxxxxxxxxxxxxxxx/bugzilla/>
changed bug 1109
What Removed Added
CC   nathans@debian.org

Comment # 1 on bug 1109 from
(In reply to comment #0)
> [...]
> In short, it is a non-identifying identifier, even within the lifetime
> of a single pcp client.

Hmm.  By design, what is supposed to be happening is the "fully qualified" name
(once looked up via the docker fuzzy matching, just like the docker client
tools do) is returned to the requesting PMDA, which can then use it as a unique
identifier going forward in subsequent requests - rendering this a non-issue.

However, on inspection it would appear that only the cgroups PDU is actually
doing this - will need to go back and resolve the PID PDU at least, possible
one or two others.

Thanks for the test case, its almost a QA test already.


You are receiving this mail because:
  • You are on the CC list for the bug.
  • You are the assignee for the bug.
<Prev in Thread] Current Thread [Next in Thread>