CIM/WBEM packages (SBLIM) - call to advocate

Sat Nov 28 02:00:16 GMT 2009

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mathias Gug wrote:
> Hi,
> 
> On Fri, Nov 27, 2009 at 6:39 AM, Ancoron Luciferis
> <ancoron at chaoslayer.de> wrote:
>> Hi Guillaume,
>>
>> I didn't realize that they made it into Karmic, but I just saw them
>> right after I wrote my mail. Sorry that I forgot them. But the problem
>> remains the same that there are just too few providers.
>>
>> Just providing a very basic set isn't enough to compete with the other
>> distributions and as the OpenDRIM providers also depend on SFCB it
>> shouldn't matter which provider set we provide as long as the enterprise
>> users get what they need/want.
> 
> If a list of the schemas and profiles supported by existing management
> tools could be created, it would be very helpful in choosing which
> providers to include (or start developing) in Ubuntu.
> 

Well, I did some research to find out what those management tools but
couldn't find any specific documentation about that but on the other
hand I found some docs describing the profiles that are provided from
the various implementations:

Sun ILOM
- --------

- - DSP1004 - Base Server Profile
- - DSP1009 - Sensors Profile
- - DSP1010 - Record Log Profile
- - DSP1011 - Physical Asset Profile
- - DSP1018 - Service Processor Profile
- - DSP1022 - CPU Profile
- - DSP1026 - System Memory Profile
- - DSP1033 - Profile Registration
- - DSP1074 - Indicator LED Profile

Reference:
http://docs.sun.com/source/820-6413-11/WS_MAN_CIM.html#50647112_53720

IBM System z Hardware Management Console
- ----------------------------------------

- - DSP1004 - Base Server Profile
- - DSP1011 - Physical Asset Profile
- - DSP1012 - Boot Control Profile
- - DSP1018 - Service Processor Profile
- - DSP1023 - Software Inventory Profile
- - DSP1042 - System Virtualization Profile
- - DSP1057 - Virtual System Profile

Reference:
http://www-01.ibm.com/support/docview.wss?uid=isg2633d0c87855f6a2d852573f700527ecb

HP Insight Management
- ---------------------

- - DSP1004 - Base Server Profile (specialized)
- - DSP1009 - Sensors Profile
- - DSP1010 - Record Log Profile
- - DSP1011 - Physical Asset Profile
- - DSP1013 - Fan Profile
- - DSP1014 - Ethernet Port Profile (specialized)
- - DSP1015 - Power Supply Profile
- - DSP1022 - CPU Profile
- - DSP1023 - Software Inventory Profile
- - DSP1026 - System Memory Profile
- - DSP1027 - Power State Management Profile
- - DSP1029 - OS Status Profile 1.0
- - DSP1033 - Profile Registration
- - DSP1035 - Host LAN Network Port Profile
- - DSP1036 - IP Interface Profile
- - DSP1040 - Platform Watchdog Profile
- - DSP1052 - Computer System Profile
- - DSP1075 - PCI Device Profile

Reference:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01382288/c01382288.pdf

Although this is regarding Windows servers there are separate docs about
the Linux providers HP offers:
http://docs.hp.com/en/linuxredhat.html#HP%20Integrity%20Essentials%20Foundation%20Pack%20for%20Linux

According to this document:

http://sourceforge.net/apps/mediawiki/sblim/index.php?title=SFCB,_How_low_can_you_go#Components.2C_versions_and_test_environment

And according to the most common providers (I think the most common ones
must be the ones most needed/wanted) I suggest a list of profiles for
required implementation:

- - DSP1004 - Base Server Profile
- - DSP1009 - Sensors Profile
- - DSP1010 - Record Log Profile
- - DSP1011 - Physical Asset Profile
- - DSP1013 - Fan Profile
- - DSP1015 - Power Supply Profile
- - DSP1022 - CPU Profile
- - DSP1023 - Software Inventory Profile
- - DSP1026 - System Memory Profile
- - DSP1033 - Profile Registration
- - DSP1052 - Computer System Profile

When I take that and compare it to our choices of implementations so far
(SBLIM, OpenDRIM) we have the following situation:

None of the SBLIM providers comply completely to any management profile
as far as I can see in the code. However, at least parts of the
following profiles are implemented (either released or unreleased
provider code):

- - DSP1002 - Diagnostics Profile
- - DSP1004 - Base Server Profile
- - DSP1010 - Record Log Profile
- - DSP1011 - Physical Asset Profile
- - DSP1012 - Boot Control Profile
- - DSP1014 - Ethernet Port Profile
- - DSP1016 - Telnet Service Profile
- - DSP1017 - SSH Service Profile
- - DSP1022 - CPU Profile
- - DSP1023 - Software Inventory Profile
- - DSP1026 - System Memory Profile
- - DSP1033 - Profile Registration
- - DSP1035 - Host LAN Network Port Profile
- - DSP1036 - IP Interface Profile
- - DSP1039 - Role Based Authorization Profile
- - DSP1052 - Computer System Profile
- - DSP1053 - Base Metrics Profile
- - DSP1054 - Indications Profile
- - DSP1061 - BIOS Management Profile
- - DSP1075 - PCI Device Profile
- - DSP1080 - Enabled Logical Element Profile

The OpenDRIM providers seem to be a lot better here. They seem well
designed in terms of profile compliance. The following profiles seem
completely implemented:

- - DSP1002 - Diagnostics Profile
- - DSP1004 - Base Server Profile
- - DSP1010 - Record Log Profile
- - DSP1011 - Physical Asset Profile
- - DSP1014 - Ethernet Port Profile
- - DSP1026 - System Memory Profile
- - DSP1033 - Profile Registration
- - DSP1036 - IP Interface Profile
- - DSP1052 - Computer System Profile
- - DSP1053 - Base Metrics Profile
- - DSP1054 - Indications Profile
- - DSP1080 - Enabled Logical Element Profile

According to available source in the upstream svn trunk the following
profiles are implemented at least partly:

- - DSP1009 - Sensors Profile
- - DSP1012 - Boot Control Profile
- - DSP1016 - Telnet Service Profile
- - DSP1017 - SSH Service Profile
- - DSP1022 - CPU Profile
- - DSP1023 - Software Inventory Profile
- - DSP1029 - OS Status Profile
- - DSP1034 - Simple Identity Management Profile
- - DSP1035 - Host LAN Network Port Profile
- - DSP1038 - DNS Client Profile
- - DSP1061 - BIOS Management Profile
- - DSP1075 - PCI Device Profile
- - DSP1077 - USB Redirection Profile
- - DSP1086 - Media Redirection Profile

Sorry if I forgot anything. Just doing a quick overview.

So, in the end I think the OpenDRIM project really is the right way to
go. Unfortunately as long as we have no GPL alternative to SFCB this
won't go into main either.

Best regards,

Ancoron

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksQhCcACgkQHwxOsqv2bG3YpACgltmEXLcMAQ6/INMJsrwzTvoD
uvoAn0b0hQMBZ32p1m7VrpQTnTFrzBJY
=2VeV
-----END PGP SIGNATURE-----