pywbem-devel — PyWBEM development related topics

[pywbem-devel] SMI-S Prometheus Exporter Development

[Răzvan V. <raz...@me...>]

Hy Guys,

I'm trying to write a SMI-S Prometheus exporter that works at least with: 3Par Inform, Tivoli SVC, HyperMaxOS, Purity, but I'd rather have it work with any generic SMI-S/BlockServerPerformance array.

From what I gather, the order of operations specifically for block storage systems is:
connection to the interop namespace
check for the SNIA Block Server Performance Profile
Get Central Instances on it
HELPME: Somehow this should make the jump to the non-Interop namespace but I couldn't find how.
Search for the CIM_BlockStatisticsCapabilities and see the ElementTypesSupported
List and cache all the above element types for information that is needed for processing (WWIDs, Capacities, etc.)
Maybe attach an Indication Subscription to see if anything changed (LUN was expanded or renamed or something else changed)
List and cache all the CIM_BlockStorageStatistics associations to the CIM_LogicalElement named above (Volumes, Disks, Ports, etc.) <-- HELPME: 3Par doesn't have associations, but IBM, Purestorage and probably (haven't checked) EMC have them.
EnumerateInstances for CIM_BlockStorageStatistics at some interval that is a multiple of ClockTickInterval of the BlockStatisticsCapabilities and save the data.

Am I missing anything? I've tried directly doing the last step, but getting the correct LUN ID or Port ID from the CIM_BlockStorageStatistics is impossible for IBM and vendor-specific for the rest.

Can you help me understand how to make the jump from the interop namespace to the correct SMI-S vendor namespace?
Can you help me understand how to make the association between the LogicalElement and the StorageStatistic?

This is what I have until now, but I'm stuck in interop:
class smisStorage:

    def __init__(self, url, username, password):
        self.url = url
        self.username = username
        self.password = password
        self.wbemConn = WBEMConnection(self.url, (self.username, self.password), no_verification=True)
        self.wbemServer = WBEMServer(self.wbemConn)
        self.profile = {'RegisteredVersion': '0'}
        self.validate_smis()
        self.find_managed_element()

    def validate_smis(self):
        smis_profiles = self.wbemServer.get_selected_profiles('SNIA', 'Block Server Performance')
        for smis_profile in smis_profiles:
            if version.parse(smis_profile['RegisteredVersion']) > version.parse(self.profile['RegisteredVersion']):
                self.profile = smis_profile
        if self.profile['RegisteredVersion'] == '0':
            raise Exception("Couldn't find any BlockServerPerformance registered subprofiles.")

    def find_managed_element(self):
        pprint(self.wbemConn.AssociatorNames(self.profile.path, AssocClass='CIM_ElementConformsToProfile', ResultClass='CIM_System'))
        # Or should I GetCentralInstances?
        #pprint(self.wbemServer.get_central_instances(self.profile.path))

Thanks,

[pywbem-devel] SSL: UNSUPPORTED_PROTOCOL

[Claudio K. <ck...@cl...>]

Hi all

I read about the SSL: UNSUPPORTED PROTOCOL error in
https://pywbem.readthedocs.io/en/latest/appendix.html . Is the client side
protocol lowering only possible by adjusting /etc/ssl/openssl.cnf (on
Linux) or is there another way to tell pywbem / python which ssl protocol
to use?

My goal would be to tell the script, which uses pywbem, with a parameter
which version to use. Maybe some special environment variables are
considered by python/openssl?

Any ideas?

cheers, ck

[pywbem-devel] Survol: UI using pywbem

[Remi C. <rem...@gm...>]

Dear All,

You might be interested by "Survol", an open-source tool for investigating
Legacy software.

It is partly based on WBEM, uses many of its concepts and of course uses
pywbem.

http://primhillcomputers.com/survol.htm

Any questions welcome, many thanks for the work provided on pywbem

Regards

Remi

[pywbem-devel] M2Crypto issue & cim_provider2 usage

[Andreas M. <ma...@de...>]

Remi,
On your pywbem upgrade problem:

   If you use the Python package M2CryptoWin32/64 instead of M2Crypto, you
   get a binary installation that does not invoke Swig. This is what the
   setup.py of Pywbem does automatically. However, because we provide
   pywbem as a wheel-type package, its setup.py does not get invoked at
   install time anymore. Instead, its dependencies have been gathered at
   package build time and have been transformed into a data format that is
   part of the wheel package. In that data format, the runtime-dependent
   distinction between M2Crypto and M2CryptoWin32/64 gets lost, and the
   wheel package selects M2Crypto also when being installed on Windows. I
   don't know yet how to improve that situation.

   In the mean time, if you can ensure somehow that M2CryptoWin32/64 is
   installed instead of M2Crypto, your upgrade problem will be solved.

   An alternative would be to go with M2Crypto and to provide the missing
   include files for the Swig processing during M2Crypto installation. The
   specific file showing up as missing is from openssl. See this article:
   http://stackoverflow.com/questions/25110774/how-to-install-m2crypto-on-windows

On the CIMError:

   It seems your provider is a Python provider based upon the cim_provider2
   Python package. That package is no longer part of the pywbem PyPI
   package. We moved it into an "attic" subdirectory, because we were not
   aware of any usage. For now, please copy the file cim_provider2.py from
   the "attic" subdirectory of a pywbem repo clone into the Python
   site-packages directory that is used with that CIMOM. Ensure that you
   can do an import of the "cim_provider2" module. Which CIMOM are you
   using with that?

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

----- Forwarded by Andreas Maier/Germany/IBM on 16.01.2017 09:11 -----

From:	Remi Chateauneu <rem...@gm...>
To:	pywbem-devel <pyw...@li...>
Date:	14.01.2017 14:38
Subject:	[pywbem-devel] (no subject)



Hi All

I am using on Windows with Python 2.7  this version of wbem
>>> pywbem.__version__
'0.8.0-dev'

... and I cannot upgrade pywbem due to this error when installing m2crypto:


pip install pywbem --upgrade
...
    SWIG/_m2crypto_wrap.c(6519) : fatal error C1083: Cannot open include
file: 'poll.h': No such file or directory

So here is my problem:

>>> conn = pywbem.WBEMConnection("https://192.168.1.88:5989" ,
('my-user','my-pass') )
>>> lst = conn.EnumerateInstanceNames
(ClassName="CIM_Process",namespace="root/cimv2")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python27\lib\site-packages\pywbem\cim_operations.py", line 926,
in EnumerateInstanceNames
    **params)
  File "C:\Python27\lib\site-packages\pywbem\cim_operations.py", line 672,
in imethodcall
    raise CIMError(code, tt[1]['DESCRIPTION'])
pywbem.cim_operations.CIMError: (1, u'CIM_ERR_FAILED: Error initializing
CMPI MI /home/rchateau/TestProviderOpenLMI/tutorial_final/T
UT_UnixProcess.py, the following MI factory function(s) returned an error:
_Generic_Create_InstanceMI, message was: cmpi:Traceback (
most recent call last):<br>  File
"/usr/lib64/python2.7/site-packages/cmpi_pywbem_bindings.py", line 34, in
<module><br>    from pyw
bem.cim_provider2 import ProviderProxy<br>ImportError: No module named
cim_provider2<br>')

With other classes such as LMI_Account or PG_UnixProcess (Which is a
derived class of CIM_Process), it works fine.

Any clue, please ?

Thanks

Remi

PS: Also, still with the same fault command, sometimes it loses a
connection with the message:

EnumerateInstanceNames: entity_host=http://192.168.1.88:5988
nameSpace=root/cimv2 className=CIM_UnixProcess. Caught:(1,
u'CIM_ERR_FAILED: Lost connection with cimprovagt "pyCmpiProvider".')
------------------------------------------------------------------------------

Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
pywbem-devel mailing list
pyw...@li...
https://lists.sourceforge.net/lists/listinfo/pywbem-devel

[pywbem-devel] (no subject)

[Remi C. <rem...@gm...>]

Hi All

I am using on Windows with Python 2.7  this version of wbem
>>> pywbem.__version__
'0.8.0-dev'

... and I cannot upgrade pywbem due to this error when installing m2crypto:


pip install pywbem --upgrade
...
    SWIG/_m2crypto_wrap.c(6519) : fatal error C1083: Cannot open include
file: 'poll.h': No such file or directory

So here is my problem:

>>> conn = pywbem.WBEMConnection("https://192.168.1.88:5989" ,
('my-user','my-pass') )
>>> lst =
conn.EnumerateInstanceNames(ClassName="CIM_Process",namespace="root/cimv2")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python27\lib\site-packages\pywbem\cim_operations.py", line 926,
in EnumerateInstanceNames
    **params)
  File "C:\Python27\lib\site-packages\pywbem\cim_operations.py", line 672,
in imethodcall
    raise CIMError(code, tt[1]['DESCRIPTION'])
pywbem.cim_operations.CIMError: (1, u'CIM_ERR_FAILED: Error initializing
CMPI MI /home/rchateau/TestProviderOpenLMI/tutorial_final/T
UT_UnixProcess.py, the following MI factory function(s) returned an error:
_Generic_Create_InstanceMI, message was: cmpi:Traceback (
most recent call last):<br>  File
"/usr/lib64/python2.7/site-packages/cmpi_pywbem_bindings.py", line 34, in
<module><br>    from pyw
bem.cim_provider2 import ProviderProxy<br>ImportError: No module named
cim_provider2<br>')

With other classes such as LMI_Account or PG_UnixProcess (Which is a
derived class of CIM_Process), it works fine.

Any clue, please ?

Thanks

Remi

PS: Also, still with the same fault command, sometimes it loses a
connection with the message:

*EnumerateInstanceNames: entity_host=http://192.168.1.88:5988
<http://192.168.1.88:5988> nameSpace=root/cimv2 className=CIM_UnixProcess.
Caught:(1, u'CIM_ERR_FAILED: Lost connection with cimprovagt
"pyCmpiProvider".')*

Re: [pywbem-devel] pywbem v0.10.0 has been released!

[Karl S. <k.s...@sw...>]

That is good to hear as there is no way we can make our own testing 100% 
complete.  As far as performance, this has a very big effect on memory 
usage, in particular on large responses. However, the impact on code 
efficiency is minor since it is still processing the entire response and 
the basic parser of the incoming xml to the client is about the same.  
If a user was using the pull operations and returning small responses, 
there would be minimal impact but since we just added the pull 
operations in September 2016 and the iter... operations in this release, 
we expect that most users are still using the original 
enumerate/references/associators operations and that is where you will 
see the big improvement.

Karl
On 12/21/2016 05:31 AM, Claudio Kuenzler wrote:
> Thanks guys! Tested it with check_esxi_hardware and everything works 
> smooth.
>
> On Tue, Dec 20, 2016 at 6:32 PM, Andreas Maier <ma...@de... 
> <mailto:ma...@de...>> wrote:
>
>     Hi,
>     We have released pywbem v0.10.0 today.
>
>     There is some new functionality, such as:
>     - use of SAX parser instead of minidom
>     - finalized the indications API
>     - added Iter* enumeration and association operations with a Python
>     generator/iterator interface that use the pull operations if
>     available or else the traditional operations.
>
>     See the 0.10.0 change log (
>     _https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-10-0_
>     <https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-9-0>)
>     for
>     details.
>
>     You can download this version from PyPI:
>     _https://pypi.python.org/pypi/pywbem/0.10.0_
>     <https://pypi.python.org/pypi/pywbem/0.9.0>
>
>     Please report any issues to the pywbem issue tracker:
>     _https://github.com/pywbem/pywbem/issues_
>     <https://github.com/pywbem/pywbem/issues>
>
>     Andy & Karl
>
>
>     ------------------------------------------------------------------------------
>     Developer Access Program for Intel Xeon Phi Processors
>     Access to Intel Xeon Phi processor-based developer platforms.
>     With one year of Intel Parallel Studio XE.
>     Training and support from Colfax.
>     Order your platform today.http://sdm.link/intel
>     _______________________________________________
>     pywbem-devel mailing list
>     pyw...@li...
>     <mailto:pyw...@li...>
>     https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>     <https://lists.sourceforge.net/lists/listinfo/pywbem-devel>
>
>


-- 
================
Karl Schopmeyer
email: k.s...@sw..., k.s...@op...
tel: 972-814-5581

Re: [pywbem-devel] pywbem v0.10.0 has been released!

[Andreas M. <ma...@de...>]

Remi,
SAX is much faster and uses less memory than minidom. That's the only
reason we did it.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

----- Forwarded by Andreas Maier/Germany/IBM on 09.01.2017 09:21 -----

From:	Remi Chateauneu <rem...@gm...>
To:	Andreas Maier/Germany/IBM@IBMDE
Cc:	"k.schopmeyer" <k.s...@sw...>, pywbem-devel
            <pyw...@li...>
Date:	21.12.2016 09:47
Subject:	Re: [pywbem-devel] pywbem v0.10.0 has been released!



Hi
Thanks for this work !
Question please : What is the performance impact of using Sax vs Minidom ?


Thanks



Le 20 déc. 2016 18:33, "Andreas Maier" <ma...@de...> a écrit :
  Hi,
  We have released pywbem v0.10.0 today.

  There is some new functionality, such as:
  - use of SAX parser instead of minidom
  - finalized the indications API
  - added Iter* enumeration and association operations with a Python
  generator/iterator interface that use the pull operations if available or
  else the traditional operations.

  See the 0.10.0 change log (
  https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-10-0) for
  details.

  You can download this version from PyPI:
  https://pypi.python.org/pypi/pywbem/0.10.0

  Please report any issues to the pywbem issue tracker:
  https://github.com/pywbem/pywbem/issues

  Andy & Karl


  ------------------------------------------------------------------------------

  Developer Access Program for Intel Xeon Phi Processors
  Access to Intel Xeon Phi processor-based developer platforms.
  With one year of Intel Parallel Studio XE.
  Training and support from Colfax.
  Order your platform today.http://sdm.link/intel
  _______________________________________________
  pywbem-devel mailing list
  pyw...@li...
  https://lists.sourceforge.net/lists/listinfo/pywbem-devel

Re: [pywbem-devel] pywbem v0.10.0 has been released!

[Andreas M. <ma...@de...>]

Thanks, Claudio.

Good to hear!

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

----- Forwarded by Andreas Maier/Germany/IBM on 09.01.2017 09:22 -----

From:	Claudio Kuenzler <ck...@cl...>
To:	Andreas Maier/Germany/IBM@IBMDE
Cc:	pyw...@li..., Karl Schopmeyer
            <k.s...@sw...>
Date:	21.12.2016 12:32
Subject:	Re: [pywbem-devel] pywbem v0.10.0 has been released!



Thanks guys! Tested it with check_esxi_hardware and everything works
smooth.

On Tue, Dec 20, 2016 at 6:32 PM, Andreas Maier <ma...@de...> wrote:
  Hi,
  We have released pywbem v0.10.0 today.

  There is some new functionality, such as:
  - use of SAX parser instead of minidom
  - finalized the indications API
  - added Iter* enumeration and association operations with a Python
  generator/iterator interface that use the pull operations if available or
  else the traditional operations.

  See the 0.10.0 change log (
  https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-10-0) for
  details.

  You can download this version from PyPI:
  https://pypi.python.org/pypi/pywbem/0.10.0

  Please report any issues to the pywbem issue tracker:
  https://github.com/pywbem/pywbem/issues

  Andy & Karl


  ------------------------------------------------------------------------------

  Developer Access Program for Intel Xeon Phi Processors
  Access to Intel Xeon Phi processor-based developer platforms.
  With one year of Intel Parallel Studio XE.
  Training and support from Colfax.
  Order your platform today.http://sdm.link/intel
  _______________________________________________
  pywbem-devel mailing list
  pyw...@li...
  https://lists.sourceforge.net/lists/listinfo/pywbem-devel

Re: [pywbem-devel] pywbem v0.10.0 has been released!

[Claudio K. <ck...@cl...>]

Thanks guys! Tested it with check_esxi_hardware and everything works smooth.

On Tue, Dec 20, 2016 at 6:32 PM, Andreas Maier <ma...@de...> wrote:

> Hi,
> We have released pywbem v0.10.0 today.
>
> There is some new functionality, such as:
> - use of SAX parser instead of minidom
> - finalized the indications API
> - added Iter* enumeration and association operations with a Python
> generator/iterator interface that use the pull operations if available or
> else the traditional operations.
>
> See the 0.10.0 change log (
> *https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-10-0*
> <https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-9-0>) for
> details.
>
> You can download this version from PyPI:
> *https://pypi.python.org/pypi/pywbem/0.10.0*
> <https://pypi.python.org/pypi/pywbem/0.9.0>
>
> Please report any issues to the pywbem issue tracker:
> *https://github.com/pywbem/pywbem/issues*
> <https://github.com/pywbem/pywbem/issues>
>
> Andy & Karl
>
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>
>

Re: [pywbem-devel] pywbem v0.10.0 has been released!

[Remi C. <rem...@gm...>]

Hi
Thanks for this work !
Question please : What is the performance impact of using Sax vs Minidom ?

Thanks

Le 20 déc. 2016 18:33, "Andreas Maier" <ma...@de...> a écrit :

> Hi,
> We have released pywbem v0.10.0 today.
>
> There is some new functionality, such as:
> - use of SAX parser instead of minidom
> - finalized the indications API
> - added Iter* enumeration and association operations with a Python
> generator/iterator interface that use the pull operations if available or
> else the traditional operations.
>
> See the 0.10.0 change log (
> *https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-10-0*
> <https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-9-0>) for
> details.
>
> You can download this version from PyPI:
> *https://pypi.python.org/pypi/pywbem/0.10.0*
> <https://pypi.python.org/pypi/pywbem/0.9.0>
>
> Please report any issues to the pywbem issue tracker:
> *https://github.com/pywbem/pywbem/issues*
> <https://github.com/pywbem/pywbem/issues>
>
> Andy & Karl
>
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>
>

[pywbem-devel] pywbem v0.10.0 has been released!

[Andreas M. <ma...@de...>]

Hi,
We have released pywbem v0.10.0 today.

There is some new functionality, such as:
- use of SAX parser instead of minidom
- finalized the indications API
- added Iter* enumeration and association operations with a Python
generator/iterator interface that use the pull operations if available or
else the traditional operations.

See the 0.10.0 change log (
https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-10-0) for
details.

You can download this version from PyPI:
https://pypi.python.org/pypi/pywbem/0.10.0

Please report any issues to the pywbem issue tracker:
https://github.com/pywbem/pywbem/issues

Andy & Karl

[pywbem-devel] v0.9.1 released

[Andreas M. <and...@gm...>]

Hi,
we have released pywbem v0.9.1 today.

It is a fix release for v0.9.0.

See the 0.9.1 change log (
https://pywbem.readthedocs.io/en/stable/changes.html#pywbem-v0-9-1 
<https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-9-0>) for
details.

You can download this version from PyPI:
https://pypi.python.org/pypi/pywbem/0.9.1 
<https://pypi.python.org/pypi/pywbem/0.9.0>

Please report any issues to the pywbem issue tracker:
https://github.com/pywbem/pywbem/issues

Andy & Karl

[pywbem-devel] pywbem 0.9.0 has been released

[Andreas M. <ma...@de...>]

Hi,
after quite some development time, we have released pywbemv0.9.0 today.

It is a release with major new functionality (WBEM server API, WBEM
indication API, Pulled enumerations) and many fixes.

See the 0.9.0 change log (
https://pywbem.readthedocs.io/en/latest/changes.html#pywbem-v0-9-0) for
details.
You can download this version from PyPI:
https://pypi.python.org/pypi/pywbem/0.9.0

Please report any issues to the pywbem issue tracker:
https://github.com/pywbem/pywbem/issues

Andy & Karl

[pywbem-devel] pywbem.cim_http.ConnectionError: Socket error: check_hostname requires server_ho stname

[Andreas M. <MA...@de...>]

Hi,
That seems to be the same problem as the one reported in
https://github.com/pywbem/pywbem/issues/150.

We are working on that one, but don't have a solution yet.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

----- Forwarded by Andreas Maier/Germany/IBM on 08.04.2016 09:42 -----

From:	cnm marketing <cnn...@gm...>
To:	pyw...@li...
Date:	07.04.2016 21:52
Subject:	[pywbem-devel] pywbem.cim_http.ConnectionError: Socket error:
            check_hostname requires server_ho stname



Hi,

Does anyone know what cause the following code fails and how to make it
work. It seems input param "no_verification=True" in WBEMConnection() is
not working. Here are the infomration:

platform: Windows 7 64 bits.
python version: 3.5.1 (v3.5.1:37a07cee5969, Dec  6 2015, 01:38:48).
pywbem
version: pywbem-0.9.0.dev0
OR
version: pywbem-0.8.2.

python:


=== using 'https' and fails, even no_verification=True is set =========
c:\test\pywbem-0.9.0.dev0>python
>>> import pywbem
>>> conn=pywbem.WBEMConnection('https://usenABCx2l',
... ('admin','#1Password'),'root/xyz',no_verification=True)
>>> ein=conn.EnumerateInstanceNames('CIM_ComputerSystem','root/xyz')
Traceback (most recent call last):
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 606, in
wbem_request

    client.endheaders()
  File "C:\Program Files (x86)\Python35-32\lib\http\client.py", line 1079,
in en
dheaders
    self._send_output(message_body)
  File "C:\Program Files (x86)\Python35-32\lib\http\client.py", line 911,
in _se
nd_output
    self.send(msg)
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 356, in send
    self.connect()
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 431, in connect
    self.sock = ctx.wrap_socket(self.sock)
  File "C:\Program Files (x86)\Python35-32\lib\ssl.py", line 376, in
wrap_socket

    _context=self)
  File "C:\Program Files (x86)\Python35-32\lib\ssl.py", line 705, in
__init__
    raise ValueError("check_hostname requires server_hostname")
ValueError: check_hostname requires server_hostname

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_operations.py", line 1087, in
Enume
rateInstanceNames
    **extra)
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_operations.py", line 651, in
imetho
dcall
    timeout=self.timeout)
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 611, in
wbem_request

    raise ConnectionError("Socket error: %s" % exc)
pywbem.cim_http.ConnectionError: Socket error: check_hostname requires
server_ho
stname
>>>

========= using 'http' it works =======

>>> conn=pywbem.WBEMConnection('http://usenABCx2l',
... ('admin','#1Password'))
>>> ein=conn.EnumerateInstanceNames('CIM_ComputerSystem','root/xyz')
>>> print(ein)
[CIMInstanceName(classname='XYZ_StorageProcessorSystem',
keybindings=NocaseDict({'CreationClassName': 'XYZ_StorageProcessorSystem',
'Name': '39705a23579f4b0fb69413b96aeb7f54'}), namespace='root/xyz',
host=None), CIMInstanceName(classname='XYZ_StorageProcessorSystem',
keybindings=NocaseDict({'CreationClassName': 'XYZ_StorageProcessorSystem',
'Name': 'd09a81aead6e4419a598236ccafc917b'}), namespace='root/xyz',
host=None), CIMInstanceName(classname='XYZ_StorageSystem',
keybindings=NocaseDict({'CreationClassName': 'XYZ_StorageSystem', 'Name':
'f6316d9631b6443a9606db13393009c6'}), namespace='root/xyz', host=None)]
>>>



Thanks,
cnm
------------------------------------------------------------------------------

_______________________________________________
pywbem-devel mailing list
pyw...@li...
https://lists.sourceforge.net/lists/listinfo/pywbem-devel

[pywbem-devel] pywbem.cim_http.ConnectionError: Socket error: check_hostname requires server_ho stname

[cnm m. <cnn...@gm...>]

Hi,

Does anyone know what cause the following code fails and how to make it
work. It seems input param "no_verification=True" in WBEMConnection() is
not working. Here are the infomration:

platform: Windows 7 64 bits.
python version: 3.5.1 (v3.5.1:37a07cee5969, Dec  6 2015, 01:38:48).
pywbem
version: pywbem-0.9.0.dev0
OR
version: pywbem-0.8.2.

python:


=== using 'https' and fails, even no_verification=True is set =========
c:\test\pywbem-0.9.0.dev0>python
>>> import pywbem
>>> conn=pywbem.WBEMConnection('https://usenABCx2l',
... ('admin','#1Password'),'root/xyz',no_verification=True)
>>> ein=conn.EnumerateInstanceNames('CIM_ComputerSystem','root/xyz')
Traceback (most recent call last):
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 606, in
wbem_request

    client.endheaders()
  File "C:\Program Files (x86)\Python35-32\lib\http\client.py", line 1079,
in en
dheaders
    self._send_output(message_body)
  File "C:\Program Files (x86)\Python35-32\lib\http\client.py", line 911,
in _se
nd_output
    self.send(msg)
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 356, in send
    self.connect()
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 431, in connect
    self.sock = ctx.wrap_socket(self.sock)
  File "C:\Program Files (x86)\Python35-32\lib\ssl.py", line 376, in
wrap_socket

    _context=self)
  File "C:\Program Files (x86)\Python35-32\lib\ssl.py", line 705, in
__init__
    raise ValueError("check_hostname requires server_hostname")
ValueError: check_hostname requires server_hostname

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_operations.py", line 1087, in
Enume
rateInstanceNames
    **extra)
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_operations.py", line 651, in
imetho
dcall
    timeout=self.timeout)
  File "c:\test\pywbem-0.9.0.dev0\pywbem\cim_http.py", line 611, in
wbem_request

    raise ConnectionError("Socket error: %s" % exc)
pywbem.cim_http.ConnectionError: Socket error: check_hostname requires
server_ho
stname
>>>

========= using 'http' it works =======

>>> conn=pywbem.WBEMConnection('http://usenABCx2l',
... ('admin','#1Password'))
>>> ein=conn.EnumerateInstanceNames('CIM_ComputerSystem','root/xyz')
>>> print(ein)
[CIMInstanceName(classname='XYZ_StorageProcessorSystem',
keybindings=NocaseDict({'CreationClassName': 'XYZ_StorageProcessorSystem',
'Name': '39705a23579f4b0fb69413b96aeb7f54'}), namespace='root/xyz',
host=None), CIMInstanceName(classname='XYZ_StorageProcessorSystem',
keybindings=NocaseDict({'CreationClassName': 'XYZ_StorageProcessorSystem',
'Name': 'd09a81aead6e4419a598236ccafc917b'}), namespace='root/xyz',
host=None), CIMInstanceName(classname='XYZ_StorageSystem',
keybindings=NocaseDict({'CreationClassName': 'XYZ_StorageSystem', 'Name':
'f6316d9631b6443a9606db13393009c6'}), namespace='root/xyz', host=None)]
>>>



Thanks,
cnm

Re: [pywbem-devel] PyWBEM Client v0.8.1 released on PyPI

[Claudio K. <ck...@cl...>]

It was about time pywbem gets an (official) update.
Thanks for all your work, appreciate that a lot!
Let's hope the new version makes it into the OS package repos asap.

On Fri, Mar 18, 2016 at 7:36 PM, Andreas Maier <MA...@de...> wrote:

> Hi,
> today Karl and I decided to release the PyWBEM Client 0.8 to PyPI.
>
> The Travis CI environment runs fine, my own CI environment at home with 10
> distros runs fine as well. Karl tested it against OpenPegasus. So we felt
> confident enough, after nearly 8 years of no release...
>
> This version has not been tested much yet on Windows, but I'll do that in
> the next days, and release the Windows installable.
>
> The NEWS file (http://pywbem.github.io/pywbem/doc/0.8.1/changelog.html
> <http://pywbem.github.io/pywbem/doc/latest/changelog.html>) describes all
> the changes.
>
> Please migrate to the new version, after reading the CHANGES section in
> the NEWS file carefully.
>
> If you encounter issues, please use the issue tracker for the PyWBEM
> Client at GitHub: https://github.com/pywbem/pywbem/issues
> or visit us in the #pywbem IRC channel at freenode.
>
> Andy
>
> Andreas Maier
> IBM Senior Technical Staff Member, OpenStack for z Systems
> IBM Research & Development Laboratory Boeblingen, Germany
> ma...@de..., +49-7031-16-3654
> ________________________________________________________________________
> IBM Deutschland Research & Development GmbH
> Vorsitzende des Aufsichtsrats: Martina Koederitz
> Geschaeftsfuehrung: Dirk Wittkopp
> Sitz der Gesellschaft: Boeblingen
> Registergericht: Amtsgericht Stuttgart, HRB 243294
>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
> _______________________________________________
> pywbem-devel mailing list
> pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywbem-devel
>
>

[pywbem-devel] PyWBEM Client v0.8.1 released on PyPI

[Andreas M. <MA...@de...>]

Hi,
today Karl and I decided to release the PyWBEM Client 0.8 to PyPI.

The Travis CI environment runs fine, my own CI environment at home with 10
distros runs fine as well. Karl tested it against OpenPegasus. So we felt
confident enough, after nearly 8 years of no release...

This version has not been tested much yet on Windows, but I'll do that in
the next days, and release the Windows installable.

The NEWS file (http://pywbem.github.io/pywbem/doc/0.8.1/changelog.html)
describes all the changes.

Please migrate to the new version, after reading the CHANGES section in the
NEWS file carefully.

If you encounter issues, please use the issue tracker for the PyWBEM Client
at GitHub: https://github.com/pywbem/pywbem/issues
or visit us in the #pywbem IRC channel at freenode.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] IRC channel for pywbem

[Andreas M. <MA...@de...>]

Hi,
Karl and I decided today that we would from now on use an IRC channel
#pywbem on Freenode.

A reference to that has been put on the PyWBEM Client page:
http://pywbem.github.io/pywbem/index.html

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

Re: [pywbem-devel] Installability of PyWBEM

[Claudio K. <ck...@cl...>]

Hi Andy,

On Tue, Nov 10, 2015 at 6:36 PM, Andreas Maier <MA...@de...> wrote:

>
> Hi,
> I have recently worked on the installability of PyWBEM.
>

Thanks!


> It is particularly interesting to run it on distros that I have not yet
> tested with. For example, Debian would also be interesting (M2Crypto
> requires special treatment of Ubuntu and likely also of Debian); but I
> failed to get it installed properly on VirtualBox on Windows 7.
>

Just tested a clone of the current pywbem repo (20151125) on a Debian
Wheezy.

# cat /etc/debian_version
7.2

# uname -a
Linux debian-wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux

The setup fails because a newer version of setuptools is required.

# python setup.py install
Error: The required version of setuptools (>=12.0) is not available, and
can't be
installed while this script is running. Please install the required version
first, using:

    pip install --upgrade setuptools>=12.0


Wheezy ships with:

# dpkg -l | grep setuptool | awk '{print $2" "$3}'
python-setuptools 0.6.24-1
python-setuptools-git 0.4.2-1


So I installed python-pip and ran:

# pip install --upgrade setuptools>=12.0

Now the setup started and seems to be successful. Full output can be found
here:
https://gist.github.com/Napsty/a9e0951c9fae33351606


Verified pywbem in python:

root@debian-wheezy:~/src/pywbem/src# python
Python 2.7.3 (default, Jan  2 2013, 13:56:14)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pywbem
>>> import pkg_resources
>>> pkg_resources.get_distribution("pywbem").version
'0.8.0rc1'
>>>


Thanks again.

cheers,
Claudio

[pywbem-devel] Installability of PyWBEM

[Andreas M. <MA...@de...>]

Hi,
I have recently worked on the installability of PyWBEM.

The command "python setup.py install" either in the "src" directory of your
local repo clone, or in the directory of an unpacked PyWBEM distribution
archive installs not only PyWBEM, but also all of its dependencies for
using it, including Python packages (e.g. setuptools, M2Crypto) and
OS-level packages (e.g. openssl-devel etc.), and it even rebuilds the Swig
tool which is too old for M2Crypto on some Linux systems (e.g. on RHEL 6).

M2Crypto was a particularly complex thing to deal with, I had to create a
fork of it to fix some of its installation issues. That fork is used during
PyWBEM installation. I am working with the M2Crypto folks to get that
solved also in their main repository, so we can get rid of the fork at some
point again.

The installation of Python packages is compatible with virtual Python
environments, it targets the currently active Python environment, whether
virtual or system.

The installation of OS-level packages is done using sudo at this point. I
am still looking for some means to have a choice to also install OS-level
packages in your HOME tree.

The Swig version is verified, and if it is lower than 2.0, it is downloaded
and rebuilt, after its development prerequisites are installed (e.g. the
pcre-devel package). Currently, it then replaces the one in /usr, using
sudo. Again, a more gentle approach would be desirable.

All of this is supported for RedHat-based, Debian-based, and SUSE-based
Linux distros. The packages often have different names,depending on the
distro. I have not yet invested in getting this to run on Windows, but plan
to do so soon.

The command "python setup.py develop" in the "src" directory of your local
repo clone installs everything that is needed for developing PyWBEM. That
is a superset of what is needed to use it, and the difference includes
things like epydoc (including the patches that are needed for its latest
3.0.1 version), lxml, pyyaml, and some supporting OS-level packages
including PyLint. Again, the Python packages go into the current Python
environment, and the OS-level packages are installed using sudo. Some
things that I consider basic are not installed; they are assumed to be
there, such as make, grep, sed, etc.

The makefile has been extended to support this as well, invoke "make" to
get a help text explaining the various targets. (I changed the default make
target from "build" to "help").

-> Please review the src/setup.py file and test the installation approach
for both the "install" and "develop" commands and let me know whether you
succeed and what changes you would like to see.

So far, I have tested with:

Ubuntu 12.04, x86 64-bit
Ubuntu 14.04, x86 64-bit and 32-bit
OpenSUSE 13, x86 64-bit and 32-bit
CentOS 6.7, x86 64-bit and 32-bit
CentOS 7, x86 64-bit
RHEL 6.7, x86 64-bit
Fedora 22, x86 64-bit and 32-bit

It is particularly interesting to run it on distros that I have not yet
tested with. For example, Debian would also be interesting (M2Crypto
requires special treatment of Ubuntu and likely also of Debian); but I
failed to get it installed properly on VirtualBox on Windows 7.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] m2crypto usage

[Andreas M. <MA...@de...>]

Hi Remi,
M2Crypto apparently addresses a number of security issues the standard SSL
package of PyWBEM still has.

I am currently working with the M2Crypto folks on its installability.

In the mean time, I have created a fork of M2Crypto on GitHub in which I
fixed some major issues on its installability. I have tested my fixes on a
number of Linux distributions, and so far they work fine.

Unfortunately (for you), I have not yet taken care of Windows
installability of M2Crypto so far, but it is on my list.

I have also improved the installability of PyWBEM itself quite a bit. It
now installs all of its dependencies automatically, and pulls M2Crypto in
from the form I mentioned. I'll post on that shortly.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

----- Forwarded by Andreas Maier/Germany/IBM on 10.11.2015 18:08 -----

"Remi Chateauneu (Imap)" <rem...@gm...> wrote on 26.10.2015
23:32:09:

> From: "Remi Chateauneu (Imap)" <rem...@gm...>
> To: deejross/python3-pywbem <reply
>
+002bd6c0838d1462e8718af...@re...>,

> deejross/python3-pywbem <pyt...@no...>, pywbem-
> de...@li...
> Date: 26.10.2015 23:33
> Subject: [pywbem-devel] python3-wbem and m2crypto
>
> Hi
>
> At the moment python3-wbem does not need m2crypto, apparently. Which
> is really great because installing it on Windows is extremely
> painful (for example, it does not work with the latest SWIG version:
> https://github.com/swig/swig/issues/344 ).
>
> Would it be also possible for pywbem python2, to use something else
> than m2crypto ?
>
> Thanks
>
> Remi

[pywbem-devel] Removed date from development archives

[Andreas M. <MA...@de...>]

I have removed the date from the development archives of the PyWBEM client.
The benefit the date provided (unique identification of the code level) was
not worth the trouble it caused in the build process.

If you have a need to precisely identify the code level (e.g. in issues you
want to report), do it by the commit ID shown on the download page for the
distribution archive, or simply by its commit date.

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] Travis CI has been set up for PyWBEM

[Andreas M. <MA...@de...>]

Hi,
i have set up a CI system for the PyWBEM client (just for that) in Travis:

https://travis-ci.org/pywbem/pywbem

Any push to GitHub triggers a CI run, currently for Python 2.6 and 2.7.
Again, just for the PyWBEM client.

The test results are visible as a small badge in the README section of the
GitHub project for the PyWBEM client:

https://github.com/pywbem/pywbem

Andy

Andreas Maier
IBM Senior Technical Staff Member, OpenStack for z Systems
IBM Research & Development Laboratory Boeblingen, Germany
ma...@de..., +49-7031-16-3654
________________________________________________________________________
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

[pywbem-devel] python3-wbem and m2crypto

[Remi C. (Imap) <rem...@gm...>]

Hi

At the moment python3-wbem does not need m2crypto, apparently. Which is 
really great because installing it on Windows is extremely painful (for 
example, it does not work with the latest SWIG version: 
https://github.com/swig/swig/issues/344 ).

Would it be also possible for pywbem python2, to use something else than 
m2crypto ?

Thanks

Remi

Le 12/10/2015 09:17, Andreas Maier a écrit :
>
> Hi Ross,
> I think it is generally possible to have a single source that supports 
> both Python 2.x and 3.x. If needed, there could even be runtime tests 
> for the version.
>
> It is definitely a requirement to maintain compatibility at the client 
> API for Python 2.x code.
>
> As far as the process goes, let me take a look at your changes, and 
> then I can integrate them upstream.
>
> All,
> backwards support for Python 2.x exists only for 2.6 and 2.7 (for the 
> pywbem client, not sure for the other subprojects). I recently 
> stumbled across a statement of supporting back to 2.3, but that is not 
> correct.
> If anyone has a requirement fir supporting earlier than 2.6, let me 
> know (including why).
>
> Cheers
> Andy
>
> —
> Reply to this email directly or view it on GitHub 
> <https://github.com/deejross/python3-pywbem/issues/2#issuecomment-147325607>.
>

Re: [pywbem-devel] Status of PyWBEM's move to GitHub

[Klaus K. <kk...@su...>]

* Andreas Maier <MA...@de...> [Oct 20. 2015 20:13]:
> 
> Hi,
> here is a short status update:
> 
> * Source code: Has been moved to GitHub under the https://github.com/pywbem
>    organisation, as five repositories. For example, the repository for the
>    PyWBEM client is: https://github.com/pywbem/pywbem.

Great, thanks for your efforts !

> 
> * Mailing list: Will stay on SourceForge. The pywbem-commit mailing list
>    there is now uninteresting, so we use only the pywbem-devel mailing list

People interested in commits can 'watch' the respective repositories
on Github.

Klaus
-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)