pcp
[Top] [All Lists]

[Bug 1270176] Python PMAPI pmSetOptionHostList no workie

To: pcp@xxxxxxxxxxx
Subject: [Bug 1270176] Python PMAPI pmSetOptionHostList no workie
From: bugzilla@xxxxxxxxxx
Date: Mon, 12 Oct 2015 07:41:05 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <bug-1270176-355098@xxxxxxxxxxxxxxxxxxx>
References: <bug-1270176-355098@xxxxxxxxxxxxxxxxxxx>
https://bugzilla.redhat.com/show_bug.cgi?id=1270176



--- Comment #3 from Nathan Scott <nathans@xxxxxxxxxx> ---
(In reply to Marko Myllynen from comment #2)
> (In reply to Nathan Scott from comment #1)
> > There's a bit of a conceptual disconnect here, I think Marko...
> 
> Sorry for being horribly unclear here.
> 

Ah, I see where you're coming from now.

> pcp.pmapi makes it clear that multiple contexts are not supported and I
> wasn't after multiple contexts support but rather a way to specify the

Well, there is some support - even the fromOptions context builder interface
allows for multiple contexts, via iterative calling (there are several
non-default parameters there, one of which is "index").  But anyway, not what
you're after here.

> source for a context but given that pmSetOptionHostList() exists, I thought
> using it with one host would be possible prior context creation as above
> (otherwise I wonder why it exists at all in Python PMAPI?).
> 
> A practical use case would be to allow supporting "source" configuration
> file directive in pmrep configuration file.

Yep, I see where you're coming from now - not sure off the top of my head why
your hostlist approach didn't work.  Could you make a little minimal test case
script & send it through (will save me some time) - I'll take a look tomorrow.

cheers.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=12RF4436gU&a=cc_unsubscribe

<Prev in Thread] Current Thread [Next in Thread>