Re: Restricting network interfaces Pegasus is listening to (was Re: Port selection)

Vitezslav,

This feature is definitely useful and i don't think there will be any 
disagreement for this feature to be implemented. I have filed an 
enhancement bugzilla for the same.

http://bugzilla.openpegasus.org/show_bug.cgi?id=9136

-Venkat



From:   Vitezslav Crhonek <[email protected]>
To:     Venkateswara R Puvvada/India/IBM@IBMIN
Cc:     "[email protected]" <[email protected]>
Date:   08/12/2011 19:58
Subject:        Restricting network interfaces Pegasus is listening to 
(was Re: Port selection)



On 10/28/2011 08:42 AM, Venkateswara R Puvvada wrote:
> Vitezslav,
>
> Currently Pegasus listens on all network interfaces and there is no
> mechanism available to restrict this.
>
> Regards,
> Venkat

Hi,

I'm still thinking about it and I believe that this would be very useful 
for many users and hopefully not a source of disagreement as using 
arbitrary ports:)

I'd like to request it as new feature for future OpenPegasus releases, 
but I don't exactly know how to do it...

Should I create new PEP (I saw that there are also implementation 
details etc. which I don't know of course)? Or report it to the 
OpenPegasus Bugzilla Database?

Do you think there's a chance that this feature will be accepted and 
implemented?

Thanks for help,
Vitezslav Crhonek


>
>
>
> From:   Vitezslav Crhonek<[email protected]>
> To:     Venkateswara R Puvvada/India/IBM@IBMIN
> Cc:     "[email protected]"<[email protected]>
> Date:   25/10/2011 17:43
> Subject:        Re: Port selection
>
>
>
> On 10/21/2011 07:37 AM, Venkateswara R Puvvada wrote:
>> Vitezslav,
>>
>> Some runtime config options are fixed and hidden in release builds.
>> httpPort is part of those config options.
>>
>>
> 
http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/*checkout*/pegasus/doc/BuildAndReleaseOptions.html?rev=1.24.2.1

>
>>
>> If there is a requirement to run multiple cimservers on a single 
system,
>> use Pegasus PEGASUS_FLAVOR option which makes httpPort and httpsPort
>> visible/ not fixed.
>
> Thanks Venkat, this is it.
>
>>
>> http://www.openpegasus.org/pp/uploads/40/21277/PEP350_MultiCIMOM.htm
>>
>> PEP 290 was not implemented. There was a debate to use HTTP Host header
> to
>> identify target host instead of using the port.
>
> I'm looking for mechanism restricting network interfaces Pegasus is
> listening to, so PEP350 is not addressing it.
>
> Is there any mechanism for this?
>
> Best regards,
> Vitezslav Crhonek
>
>
>>
>> Venkat
>>
>>
>>
>>
>> From:   Vitezslav Crhonek<[email protected]>
>> To:     "[email protected]"<[email protected]>
>> Date:   20/10/2011 20:56
>> Subject:        Port selection
>>
>>
>>
>> Hello,
>>
>> Is there any possibility to set own http/https port values?
>>
>> I see httpPort and httpsPort options, but it seems that these options
>> are disabled:
>>
>> $ cimconfig -g httpPort
>> Specified property name was not found.
>> CIM_ERR_NOT_FOUND: Configuration property "httpPort"
>>
>> Is there any way how to enable them? (Probably some env. variable 
during
>> build time?)
>>
>> I'm also curious what happened with PEP #290:
>> http://www.openpegasus.org/pp/upreviews/40/2362/orig/PEP290.html
>>
>> Because this feature would be useful in some situations.
>>
>> Best regards,
>> Vitezslav Crhonek
>>
>>
>>
>
>
>