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

Start with making a general description on the wiki in the area 
Developers -> Future Planning.  Put enough in there that the whole 
thing could be discussed and then if you want to you can set in in an 
agenda on one of the Thursday morning telecons to push others into 
reviewing the idea.  This should only be a few paragraphs long and 
provide requirement and possibly current ideas about implementation.

That way with limited work you can determine a) agreement with idea, 
b) interest from others in possibly contributing, c) alternative to 
your concept

At this point we would have an idea of the concept but not commitment 
to do it and probably not actual defintion of functionality, interfaces, etc.

Then it is time for PEP but generally doing a PEP is a commitment to 
do the work itself which is where the fun begins.  If the idea is 
simple, the PEP is probably not much more than the description in the 
wiki with commitments to schedule, etc.  If solution is complex, it 
would include more design info.  The goal of the PEP is documentation 
sufficient for arch team to do formal vote on implementation itself, 
not just the concept.

You could actually start with the PEP but the wiki is a way to get 
informal opinion and generate discussion before having to write a document.

Hope this helps and I agree that we do not have this process well 
laid out in documentation.

Karl
Thanks for your message at 08:28 AM 12/8/2011. Your message was:
>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
>>>
>>>
>>
>>

Karl Schopmeyer                   Inova Development Inc.
305 Spring Creek Village, Suite 475 -  Dallas TX, 75248 USA
EMAIL: [email protected]       FAX: 1-972-239-0326
Phone 1-972-814-5581
Skype: kschopmeyer         Skype Phone: (214) 556-5971