Committing revsion 2642 to the source code repository completed the buildsystem conversion to CMake today.
It now supports building and installation of all openwsman components (libraries, plugins, authenticators, include files, openwsmand).
Some numbers:
- total size of all Makefiles:
551018 for autotools
255517 for CMake
- total time spent for Makefile creations (from scratch):
26 seconds for autotools (bootstrap; configure)
2 seconds for CMake
Openwsman now (as of svn rev 2609) supports building with CMake (see www.cmake.org) as an alternative to autoconf/automake (also known as 'autotools').
The initial CMake support is limited to local builds on Linux, sufficient for development not a complete autotools replacement yet.
Openwsman 2.0.0 is planned for end of March. Beta 1 was released 2 weeks ago.
I know from many of you, especially those I talked to in person, that you might have some local changes to earlier releases fixing some issues and even adding some features. Some even promised to send patches and fixes, but nothing happened so far.
The python bindings are still very basic and cover just a few of the client features of openwsman, however, with just the limited functionality a lot can be done as can be seen in the newly checked in python code with CIM bindings.
The code can be found in subversion under the new sub-project pywsman. This is basically a simple wrapper around the bindings that full expose CIM data in a pythonic way. Code as simple as the following snippet yields useful data that can be reused in any python application:
Just found this announcement on openwsman-discuss:
"Starting with VMware's VIPerl Toolkit v1.5, an experimental version of Perl WS-Management library is included for infrastructure management with Web Services. The library currently supports 7 out of the 11 generic operations described in the WS-Management - CIM Binding.
The library is available for download at http://www.vmware.com/support/developer/viperltoolkit/
and the documentation for the Perl WS-Management library can be found at:
http://www.vmware.com/support/developer/viperltoolkit/viperl15/doc/technoteWSmgmt.pdf
The library is completely written in Perl and tested with the help of Openwsman"
Lets see how this compares against the openwsman language bindings ...
WS-Management On Rails shows how to combine the beauty of the Openwsman Ruby bindings and Ruby On Rails to create a web based management application.
Hopefully more languages will follow soon (Perl?, Java?). Klaus made the announcement of the changes on the mailing list today:
We have just added support for anonymous identify and also enhanced the server to support custom identify responses (currently only anonymous) loadable from an external file.
Basically it will be possible now to create your own identify response in a file with additional information (such as DASH requirements) and configure openwsman to load this file when there is an identify request.
The DMTF announced the public release of Version 1.1 of its Desktop and mobile Architecture for System Hardware (DASH) standard. Benefits of this updated standard include tightened security and protocol requirements for IT deployments.
As you noticed, openwsman.org has a new look. The old content is still available but will be removed once everything has been migrated to the new site. Old content can be accessed via http://trac.openwsman.org. Some features of the old site are still accessible from here, for example the timeline, the source browser and other great trac features.