gmane.network.open-pegasus.general

Re: Generating release binaries

Pranav S — 2013-05-24T11:40:51

I am on gmail only.


On 24 May 2013 17:01, Devchandra L Meetei <dlmeetei< at >gmail.com> wrote:

Re: Generating release binaries

Devchandra L Meetei — 2013-05-24T10:13:30

For which platform you want the binaries?
As far as I remember, we don't ship windows binaries currently.

If you are into nice world of rpm, rpmbuild internally takes care of
stripping.


On Fri, May 24, 2013 at 3:29 PM, Pranav S <pranav026< at >gmail.com> wrote:

Generating release binaries

Pranav S — 2013-05-24T09:59:02

Hello,

I am looking into Pegasus source and I did not get on how to build release
binaries. Once I build the bins, I do not see binaries being stripped(I
expect release bins to be stripped). I don't even get any reference of
strip in the Makefiles. Let me know if there is provision to it or we need
to add separately in Makefiles. I want to reduce the library/binary size. I
see some piece of code for OpenVms platform in platform Makefile. Should we
add this to other platforms also with config option? So that one can
enable/disable of stripping of binaries.

Re: building tog-pegasus on 64-bit ARM

Karl Schopmeyer — 2013-05-23T18:38:46

Thanks for working on this.  There are others who need this support 
and I guess that we are going to find some porting issues as we move 
ahead.  We already have an indication that there may be an issue in 
the CMPI header files (struct padding) but have not confirmed this 
with pegasus.

The big problem here is going to be testing because of the very 
limited availabilty of arm 64 platforms that you can test on.

Karl

Thanks for your message at 01:32 PM 5/21/2013. Your message was:


Karl Schopmeyer                   Inova Development Inc.
305 Spring Creek Village, Suite 475 -  Dallas TX, 75248 USA
EMAIL: k.schopmeyer< at >swbell.net       FAX: 1-972-239-0326
Phone 1-972-814-5581
Skype: kschopmeyer         Skype Phone: (214) 556-5971

Re: HPUX aCC compile flags for IA64 platform

Pranav S — 2013-05-23T11:22:21

I have same changes as you have done. Thank You for the HP WBEM pointers.


On 23 May 2013 11:33, Deshpande, Rohini (IESL) <rohini.deshpande< at >hp.com>wrote:

RE: HPUX aCC compile flags for IA64 platform

Deshpande, Rohini (IESL — 2013-05-23T06:03:50

Hi Pranav,

See http://cvs.opengroup.org/cgi-bin/viewcvs.cgi/pegasus/mak/platform_HPUX_IA64_ACC.mak?rev=1.16&content-type=text/vnd.viewcvs-markup, -AA is used.

On HP-UX OpenPegasus(OP) is already available as part of HP-UX WBEM services(See http://h71028.www7.hp.com/enterprise/cache/11380-0-0-225-121.html?404m=aspxtohtml ) This is installed by default. Is there any reason why you need another OP? It is available in IA and PA platforms on 11iv1, 11iv2 and 11iv3. If you need additional information on this I can connect you with the HP-UX WBEM services team.

If you want to separately download the bits, it is available at http://h71028.www7.hp.com/enterprise/cache/9931-0-0-225-121.html. The latest HP-UX WBEM services is based on OP 2.11.

Regards,
Rohini Deshpande
Software Engineer/OpenPegasus Committer
Hewlett Packard

From: Kandepu, Anusha
Sent: Thursday, May 23, 2013 11:10 AM
To: Pranav S; pegasus-l< at >openpegasus.org
Subject: RE: HPUX aCC compile flags for IA64 platform

Hi Pranav,
                  I could s

RE: HPUX aCC compile flags for IA64 platform

Kandepu, Anusha — 2013-05-23T05:40:24

Hi Pranav,
                  I could see that Pegasus is already using "AA" flag for HP-UX IA with aCC compiler. You can check the make file "platform_HPUX_IA64_ACC.mak" under Pegasus/mak directory for further details.

Regards,
Anusha.

From: Pranav S [mailto:pranav026< at >gmail.com]
Sent: Wednesday, May 22, 2013 2:55 PM
To: pegasus-l< at >openpegasus.org
Subject: Re: HPUX aCC compile flags for IA64 platform

Hello,
I am able to compile the Pegasus with -AA aCC(hpux) compiler flag. Thank you. Will get back to you if I face any issues with built binaries. Also we should consider incorporating -AA flag for HPUX. Let me know your comments on this.

On 22 May 2013 11:22, Pranav S <pranav026< at >gmail.com<mailto:pranav026< at >gmail.com>> wrote:
Hello,
I am trying to compile Pegasus source on HPUX IA64 using aCC compiler. I see Pegasus using older C++ run time libraries(-AP). Compiler option. Shouldn't it be using the -AA option to compile, which turns on turns on newly supported ANSI C++ Standard features? Does it need some face

Re: HPUX aCC compile flags for IA64 platform

Pranav S — 2013-05-22T11:14:11

Thank You Devachandra.


On 22 May 2013 15:04, Devchandra L Meetei <dlmeetei< at >gmail.com> wrote:

RE: HPUX aCC compile flags for IA64 platform

Kandepu, Anusha — 2013-05-22T10:21:27

Hi Pranav,
              Can you share the HP-UX version details ?.Is it  IA or PA?. "AP" flag is the default for PA systems. For IA systems you can choose to use "AA" option. You can file a bug for the same as mentioned below.

Note: changing to -AA on PA would have problems if you are depending on any third party aC++ libs, which may not be available with -AA.

Regards,
Anusha.

From: Devchandra L Meetei [mailto:dlmeetei< at >gmail.com]
Sent: Wednesday, May 22, 2013 3:05 PM
To: Pranav S
Cc: pegasus-l< at >openpegasus.org
Subject: Re: HPUX aCC compile flags for IA64 platform

You will be welcome for the change request,
Please open a bug at http://bugzilla.openpegasus.org/ so that HPUX representative will do the necessary things

On Wed, May 22, 2013 at 2:54 PM, Pranav S <pranav026< at >gmail.com<mailto:pranav026< at >gmail.com>> wrote:
Hello,
I am able to compile the Pegasus with -AA aCC(hpux) compiler flag. Thank you. Will get back to you if I face any issues with built binaries. Also we should consider incorporating -AA flag

Re: HPUX aCC compile flags for IA64 platform

Devchandra L Meetei — 2013-05-22T09:34:34

You will be welcome for the change request,
Please open a bug at http://bugzilla.openpegasus.org/ so that HPUX
representative will do the necessary things


On Wed, May 22, 2013 at 2:54 PM, Pranav S <pranav026< at >gmail.com> wrote:

Re: HPUX aCC compile flags for IA64 platform

Pranav S — 2013-05-22T09:24:49

Hello,

I am able to compile the Pegasus with -AA aCC(hpux) compiler flag. Thank
you. Will get back to you if I face any issues with built binaries. Also we
should consider incorporating -AA flag for HPUX. Let me know your comments
on this.



On 22 May 2013 11:22, Pranav S <pranav026< at >gmail.com> wrote:

HPUX aCC compile flags for IA64 platform

Pranav S — 2013-05-22T05:52:42

Hello,

I am trying to compile Pegasus source on HPUX IA64 using aCC compiler. I
see Pegasus using older C++ run time libraries(-AP). Compiler option.
Shouldn't it be using the -AA option to compile, which turns on turns on
newly supported ANSI C++ Standard features? Does it need some facelift on
HPUX platform?

Also after using the compile flag I am getting some errors which I am
trying to resolve. Any pointers would be helpful. I am using pegasus 2.11.

Re: building tog-pegasus on 64-bit ARM

Devchandra L Meetei — 2013-05-22T04:45:26

Thanks David  for opening the bug. Let us get it done.


On Wed, May 22, 2013 at 1:26 AM, David Marlin <dmarlin< at >redhat.com> wrote:

Re: building tog-pegasus on 64-bit ARM

David Marlin — 2013-05-21T19:56:05

Devchandra L Meetei wrote:

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


Thank you,

d.marlin
===========

Re: building tog-pegasus on 64-bit ARM

Devchandra L Meetei — 2013-05-21T19:24:16

Hello David
Patch looks good for building,
Thanks for the work.

For full support, Just Guessing that You might like to tweak
mak/SDKMakefile and add ARM specific file for the SDK at
src/SDK/samples/mak

and as usual, we will open a BZ to for the change, BZ is the vehicle for
any change in pegasus.

Please feel free and do let us know if you need anything else


On Wed, May 22, 2013 at 12:02 AM, David Marlin <dmarlin< at >redhat.com> wrote:

building tog-pegasus on 64-bit ARM

David Marlin — 2013-05-21T18:32:33

The attached patch adds support to build on a 64-bit ARM system 
(aarch64).  This is only intended to add initial support for building, 
since hardware is not currently available.

Options CXX_MACHINE_OPTIONS and LINK_MACHINE_OPTIONS were only included 
as placeholders in platform_LINUX_AARCH64_GNU.mak, since no 
platform-specific optimizations are currently known.

I successfully completed a test build using a software simulator:

   http://fedoraproject.org/wiki/Architectures/ARM/AArch64/QuickStart

Please let me know if anything else should be needed, or if any changes 
to this patch are required.


Thank you,

d.marlin

Re: Terminating provider process

Jan Safranek — 2013-05-20T08:16:40

Python terminates pretty quickly, that's fine. Problem is it cannot be
started again *in the same process*, it uses some global variables etc.
Therefore the only sane way is to exit the ProviderAgent process
immediately when the provider is unloaded.

Of course, fixing Python would be the best solution, but it seems it's
like this on purpose and changing this behavior would need really
significant changes in its design.

Jan

Re: Terminating provider process

Devchandra L Meetei — 2013-05-17T17:10:21

Hi Jan
As Marek pointed out, We have this in our radar. Please look at bug
9657<http://bugzilla.openpegasus.org/show_bug.cgi?id=9657>which will
track this.
Have started working on it and left it for some time now due to urgent
provider work.
I hate myself as a pegasus developer( would consider myself as pegasus
developer rather than a provider writer) to say that, unfortunately,it will
not make it to 2.13 from my end.
Volunteers like yourself are welcome.

Also was little alarmed by the figure you gave(15 mint), I was under the
impression that it is 5 minute(unless modified at packaging).

It has also been my experience that sometimes bad provider take longer time
to unload.







On Fri, May 17, 2013 at 5:22 PM, Jan Safranek <jsafrane< at >redhat.com> wrote:

Re: Terminating provider process

Kirk Augustin — 2013-05-17T15:54:25

Not sure I am following exactly, but isn't the problem more to do with the time delay in Python unloading?
I don't think the ProviderAgent closing down can be hastened if Python itself is slow to unload.
Nor do I think there should there be a crash because the provider is called again before the ProviderAgent process has shut down.
Which is why I wonder if both problems are really coming from Python, and not the ProviderAgent?
Is it possible to watch the Python process to see if it is what is causing the delay in the ProviderAgent closing?

Kirk  Augustin
11821 NW McNamee Rd
Portland, OR 97231


HM: 503-289-4356


>

Re: Terminating provider process

Jan Safranek — 2013-05-17T11:52:17

Hi Marek,

thanks for a reply.

On 05/17/2013 01:49 PM, Marek Szermutzky wrote:

Yes, that's it. As soon as the last provider is uloaded, I need to stop
ProviderAgent and it process (assuming there is such process).

Jan

Re: Terminating provider process

Marek Szermutzky — 2013-05-17T11:49:03

Hi Jan.


First I want to say thank you for reporting that issue.

Thank you Jan!

Secondly, we have picked up on this specific case of behavior, but 
we(OpenPegasus) do not have a performing and nice solution for it right 
now. But you started the discussion.
We have this issue on our radar, we talked about it in Architecture 
discussion on Thursday.



Now ... lets talk technical ... (I prefer this...> =))
Basically what you need is a ProviderAgent which closes down as soon as 
all providers have cleaned up, right ?


Marek 



From:   Jan Safranek <jsafrane< at >redhat.com>
To:     "pegasus-l< at >openpegasus.org" <pegasus-l< at >openpegasus.org>, 
Date:   15.05.2013 15:50
Subject:        Terminating provider process



I use cmpi-bindings to write CMPI providers in Python to speed up the
development. I noticed that Pegasus unloads providers in 15 minutes. Ok,
that's reasonable. The provider process itself then lives for another 15
minutes before it is destroyed.

My problem is that Python cannot un-initialize itself pr