Date: Wed, 7 May 2014 08:39:01 -0400 From: =?iso-8859-1?B?QnJ1bm8gTGF1euk=?= <brunolauze@msn.com> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: wbem, cim and instrumentation Message-ID: <BLU179-W47420B2601981CBE65DEA2C64E0@phx.gbl>
next in thread | raw e-mail | index | archive | help
One thing I feel FreeBSD always ignored =A0is instrumentation frameworks.= =0A= I am talking about wbem=2C cim model and implementation like OpenPegasus. W= hy is that?=0A= I ported OpenPegasus to work in FreeBSD with few patches.=0A= However=2C of course without providers a wbem doesn't go far. I started to = see how to shape providers for freebsd at:=0A= =0A= github.com/brunolauze/openpegasus-providers=0A= =0A= my openpegasus port is at:=0A= =0A= github.com/brunolauze/freebsd-ports/tree/master/net-mgmt/openpegasus=0A= =0A= =0A= Apple ships a wbem=0A= Microsoft ships a wbem / non-standard=0A= RedHat ships it.=0A= Suse ships it.=0A= z/OS ships it.=0A= Ubuntu and distro-like ships it.=0A= And Solaris does also.=0A= =0A= Why not us?=0A= =0A= The advantage outside of this idea is better coding technique and design to= expose API first and utility based on those APIs.=0A= if any utility can be used as API=2C this discard the need for application = to use system() or popen() to execute shell code to accomplish system tasks= =2C which is really bad but widely widespread in lack of good =A0API exposu= re of those utilities. This reduce a lot of error with changes in utilities= switches=2C etc. and mitigate security risks.=0A= =0A= Wouldn't it be great to query FreeBSD with queries like:=0A= select * from UNIX_DiskDrive where Storage_Capacity> 1000=0A= or=A0=0A= select * from UNIX_SCSIController WHERE LastErrorCode <> 0=0A= =0A= =0A= Anyway=2C this is just to talk=2C let me know your opinions!=0A= =0A= =0A= =0A= =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU179-W47420B2601981CBE65DEA2C64E0>