Naming ambiguity in reports

Discussion:

Amir Pakdel

2010-05-15 09:13:24 UTC

Dear developers,

I have got a problem with naming of "Storage" and "Disk(s)":
Storage shows my Physical storages which can also be called Disk!
Disk(s) shows my mount points which may be called also storage area!
May we change the naming to resolve this ambiguity?

Best Regards,

Amir

Guillaume PROTET

2010-05-15 10:57:41 UTC

Permalink

Hi Amir,

The "Storage" and "Diks" icons are named as it because it refers to the "storages" table and the "drives" table in the database.

"storages" table refers to the the kind of storages like hard drive, floppy or CDROM drives.

"drives" table refers to the windows drives or mount points in Unix systems.

The "Disks" icon name for the "drives" table may make effectively a confusion.

So, if you want to change the names of the icons, you just have to modify the ocsreports PHP code.

Maybe we can change the "Disks" icon name by "Drives" offcially in ocsreports ? Does it I may create again another confusion ?

What are your opinions all other ?

Kind regards,

--
Guillaume

----- Mail original -----

Post by Amir Pakdel
Dear developers,
Storage shows my Physical storages which can also be called Disk!
Disk(s) shows my mount points which may be called also storage area!
May we change the naming to resolve this ambiguity?
Best Regards,
Amir

Amir Pakdel

2010-05-16 02:54:06 UTC

Permalink

Hi Guillaume,

I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or even
"File System(s)" itself).

One more thing about the currently named Disk(s) section:
On Linux servers I get something like:
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*

/ ext3 6889 6171 /dev/vg00/lvol0

But On HP-UX I get:
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*

vxfs / 2097152 1758760 /dev/vg00/lvol3

As you see there is a confusion about "Type" and "File System".
I think either Linux or HP-UX should be changed.

Kind Regards,

Amir

------------------------------------------------------------------------
*From:* Guillaume PROTET <guillaume.protet-Q/0Kkk6T+***@public.gmane.org>
*Sent:* Sat 15/05/2010 3:27:41 PM +0450
*To:* developers en <developers.en-XRi04JE7P7s3GMRc9dnpK0B+***@public.gmane.org>
*Subject:* [team] Naming ambiguity in reports

Post by Guillaume PROTET
Hi Amir,
The "Storage" and "Diks" icons are named as it because it refers to the "storages" table and the "drives" table in the database.
"storages" table refers to the the kind of storages like hard drive, floppy or CDROM drives.
"drives" table refers to the windows drives or mount points in Unix systems.
The "Disks" icon name for the "drives" table may make effectively a confusion.
So, if you want to change the names of the icons, you just have to modify the ocsreports PHP code.
Maybe we can change the "Disks" icon name by "Drives" offcially in ocsreports ? Does it I may create again another confusion ?
What are your opinions all other ?
Kind regards,
--
Guillaume
----- Mail original -----

Stéphane Urbanovski

2010-05-19 10:30:53 UTC

Permalink

Post by Amir Pakdel
Hi Guillaume,
I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or even
"File System(s)" itself).
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*
/ ext3 6889 6171 /dev/vg00/lvol0
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*
vxfs / 2097152 1758760 /dev/vg00/lvol3
As you see there is a confusion about "Type" and "File System".
I think either Linux or HP-UX should be changed.

Hi

I suggest rethinking all internal information representation (XML and Database) using DMTF standards :

http://www.dmtf.org/standards/cim/cim_schema_v2250/

http://www.vmware.com/support/developer/cim-sdk/smash/u3/ga/apirefdoc/CIM_FileSystem.html
http://msdn.microsoft.com/en-us/library/aa387273(VS.85).aspx
http://publib.boulder.ibm.com/infocenter/iseries/v1r1/en_US/index.htm?info/ciminfo/eicahcim_filesystem.htm
http://www.javasystemsolutions.com/documentation/thirdparty/cdm/BMC_FileSystem.html

Here is sample use of WBEM (wich use CIM schema) :
( Tested host use top-pegasus with sblim providers on RHEL5)

METHOD=EnumerateInstances
CLASS=CIM_FileSystem

cat <<__EOM__ > request.xml
<?xml version="1.0" ?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="3075" PROTOCOLVERSION="1.0">
<SIMPLEREQ>
<IMETHODCALL NAME="$METHOD">
<LOCALNAMESPACEPATH>
<NAMESPACE NAME="root"/>
<NAMESPACE NAME="cimv2"/>
</LOCALNAMESPACEPATH>
<IPARAMVALUE NAME="CLASSNAME">
<CLASSNAME NAME="$CLASS"/>
</IPARAMVALUE>
</IMETHODCALL>
</SIMPLEREQ>
</MESSAGE>
</CIM>
__EOM__

curl -0 --insecure https://root:pass-6oycki5b4yazjhxJD/***@public.gmane.org:5989/cimom --data @request.xml \
-H 'Content-Type: application/xml; charset="utf-8"' \
-H 'CIMProtocolVersion: 1.0' \
-H 'CIMOperation: MethodCall' \
-H "CIMMethod: $METHOD" \
-H 'CIMObject: root%2Fcimv2' | xmllint --format -

Result output

<?xml version="1.0" encoding="utf-8"?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="3075" PROTOCOLVERSION="1.0">
<SIMPLERSP>
<IMETHODRESPONSE NAME="EnumerateInstances">
<IRETURNVALUE>
<VALUE.NAMEDINSTANCE>
<INSTANCENAME CLASSNAME="Linux_Ext3FileSystem">
<KEYBINDING NAME="CreationClassName">
<KEYVALUE VALUETYPE="string">Linux_Ext3FileSystem</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="CSCreationClassName">
<KEYVALUE VALUETYPE="string">Linux_ComputerSystem</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="CSName">
<KEYVALUE VALUETYPE="string">host.ocsinventory-ng.org</KEYVALUE>
</KEYBINDING>
<KEYBINDING NAME="Name">
<KEYVALUE VALUETYPE="string">/dev/vg1/opt</KEYVALUE>
</KEYBINDING>
</INSTANCENAME>
<INSTANCE CLASSNAME="Linux_Ext3FileSystem">
<PROPERTY NAME="Caption" TYPE="string">
<VALUE>Ext3 local file system</VALUE>
</PROPERTY>
<PROPERTY NAME="Description" TYPE="string">
<VALUE>Represents the file store controlled by a ComputerSystem through local means.</VALUE>
</PROPERTY>
<PROPERTY NAME="ElementName" TYPE="string">
<VALUE>/opt</VALUE>
</PROPERTY>
<PROPERTY NAME="InstallDate" TYPE="datetime"></PROPERTY>
<PROPERTY.ARRAY NAME="OperationalStatus" TYPE="uint16"></PROPERTY.ARRAY>
<PROPERTY.ARRAY NAME="StatusDescriptions" TYPE="string"></PROPERTY.ARRAY>
<PROPERTY NAME="Status" TYPE="string">
<VALUE>OK</VALUE>
</PROPERTY>
<PROPERTY NAME="HealthState" TYPE="uint16"></PROPERTY>
<PROPERTY NAME="EnabledState" TYPE="uint16">
<VALUE>3</VALUE>
</PROPERTY>
<PROPERTY NAME="OtherEnabledState" TYPE="string">
<VALUE>NULL</VALUE>
</PROPERTY>
<PROPERTY NAME="RequestedState" TYPE="uint16">
<VALUE>3</VALUE>
</PROPERTY>
<PROPERTY NAME="EnabledDefault" TYPE="uint16">
<VALUE>2</VALUE>
</PROPERTY>
<PROPERTY NAME="TimeOfLastStateChange" TYPE="datetime"></PROPERTY>
<PROPERTY NAME="CSCreationClassName" TYPE="string">
<VALUE>Linux_ComputerSystem</VALUE>
</PROPERTY>
<PROPERTY NAME="CSName" TYPE="string">
<VALUE>host.ocsinventory-ng.org</VALUE>
</PROPERTY>
<PROPERTY NAME="CreationClassName" TYPE="string">
<VALUE>Linux_Ext3FileSystem</VALUE>
</PROPERTY>
<PROPERTY NAME="Name" TYPE="string">
<VALUE>/dev/vg1/opt</VALUE>
</PROPERTY>
<PROPERTY NAME="Root" TYPE="string">
<VALUE>/opt</VALUE>
</PROPERTY>
<PROPERTY NAME="BlockSize" TYPE="uint64">
<VALUE>4096</VALUE>
</PROPERTY>
<PROPERTY NAME="FileSystemSize" TYPE="uint64">
<VALUE>3325812736</VALUE>
</PROPERTY>
<PROPERTY NAME="AvailableSpace" TYPE="uint64">
<VALUE>2276294656</VALUE>
</PROPERTY>
<PROPERTY NAME="ReadOnly" TYPE="boolean">
<VALUE>FALSE</VALUE>
</PROPERTY>
<PROPERTY NAME="EncryptionMethod" TYPE="string"></PROPERTY>
<PROPERTY NAME="CompressionMethod" TYPE="string"></PROPERTY>
<PROPERTY NAME="CaseSensitive" TYPE="boolean"></PROPERTY>
<PROPERTY NAME="CasePreserved" TYPE="boolean"></PROPERTY>
<PROPERTY.ARRAY NAME="CodeSet" TYPE="uint16"></PROPERTY.ARRAY>
<PROPERTY NAME="MaxFileNameLength" TYPE="uint32">
<VALUE>255</VALUE>
</PROPERTY>
<PROPERTY NAME="ClusterSize" TYPE="uint32"></PROPERTY>
<PROPERTY NAME="FileSystemType" TYPE="string">
<VALUE>ext3</VALUE>
</PROPERTY>
<PROPERTY NAME="PersistenceType" TYPE="uint16"></PROPERTY>
<PROPERTY NAME="OtherPersistenceType" TYPE="string"></PROPERTY>
<PROPERTY NAME="NumberOfFiles" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="FreeInodes" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="TotalInodes" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="FSReservedCapacity" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="PercentageSpaceUse" TYPE="uint8">
<VALUE>26</VALUE>
</PROPERTY>
</INSTANCE>
</VALUE.NAMEDINSTANCE>
....

Using a subset of this schema should be enough of course.

Regards

--
Stéphane Urbanovski

Guillaume PROTET

2010-05-16 19:14:17 UTC

Permalink

Hi Amir,

About HPUX confusion i think it is a mistacke in the file Ocsinventory::Agent::Backend::OS::HPUX::Drives.pm from the unix agent and specially here:

for ( `fstyp -l | grep -v nfs` ) {
$type=$_;
for ( `bdf -t $type `) {
if ( /Filesystem/ ) { ; } ;
if ( /^(\S+)\s(\d+)\s+(\d+)\s+(\d+)\s+(\d+%)\s+(\S+)/ ) {
$lv=$1;
$total=$2;
$free=$3;
$fs=$6;
$inventory->addDrives({
FREE => $free,
FILESYSTEM => $fs,
TOTAL => $total,
TYPE => $type,
VOLUMN => $lv,
});

};

I can't test it because I don't have a HPUX computer but I think there could a mistacke about $fs (not $6 of the regex ?) or a conversely between $fs and $type.
You can try to correct this to delete the confusion and we will commit it in the unix agent.

Kind regards,

--
Guillaume

----- Mail original -----

Post by Amir Pakdel
Hi Guillaume,
I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or even
"File System(s)" itself).
Letter Type File System Total (MB) Free (MB) Designation
Letter Type File System Total (MB) Free (MB) Designation
vxfs / 2097152 1758760 /dev/vg00/lvol3 As you see there is a confusion
about "Type" and "File System".
I think either Linux or HP-UX should be changed.
Kind Regards,
Amir
Sent: Sat 15/05/2010 3:27:41 PM +0450
Subject: [team] Naming ambiguity in reports
Hi Amir,
The "Storage" and "Diks" icons are named as it because it refers to
the "storages" table and the "drives" table in the database.
"storages" table refers to the the kind of storages like hard drive,
floppy or CDROM drives.
"drives" table refers to the windows drives or mount points in Unix
systems.
The "Disks" icon name for the "drives" table may make effectively a
confusion.
So, if you want to change the names of the icons, you just have to
modify the ocsreports PHP code.
Maybe we can change the "Disks" icon name by "Drives" offcially in
ocsreports ? Does it I may create again another confusion ?
What are your opinions all other ?
Kind regards,
-- Guillaume
----- Mail original -----
Dear developers,
Storage shows my Physical storages which can also be called Disk!
Disk(s) shows my mount points which may be called also storage area!
May we change the naming to resolve this ambiguity?
Best Regards,
Amir

Amir Pakdel

2010-05-18 06:17:04 UTC

Permalink

Hi Guillaume,

So you mean that it should report something like:
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*

/
vxfs 2097152 1290888 /dev/vg00/lvol3

Although I prefer the other way around (the current output of HP-UX
agent), if it is the convention in the current rlease I would change the
agent.

Kind regards,

Amir

------------------------------------------------------------------------
*From:* Guillaume PROTET <guillaume.protet-Q/0Kkk6T+***@public.gmane.org>
*Sent:* Sun 16/05/2010 11:44:17 PM +0450
*To:* developers en <developers.en-XRi04JE7P7s3GMRc9dnpK0B+***@public.gmane.org>
*Subject:* [team] Naming ambiguity in reports

Post by Guillaume PROTET
Hi Amir,
for ( `fstyp -l | grep -v nfs` ) {
$type=$_;
for ( `bdf -t $type `) {
if ( /Filesystem/ ) { ; } ;
if ( /^(\S+)\s(\d+)\s+(\d+)\s+(\d+)\s+(\d+%)\s+(\S+)/ ) {
$lv=$1;
$total=$2;
$free=$3;
$fs=$6;
$inventory->addDrives({
FREE => $free,
FILESYSTEM => $fs,
TOTAL => $total,
TYPE => $type,
VOLUMN => $lv,
});
};
I can't test it because I don't have a HPUX computer but I think there could a mistacke about $fs (not $6 of the regex ?) or a conversely between $fs and $type.
You can try to correct this to delete the confusion and we will commit it in the unix agent.
Kind regards,
--
Guillaume
----- Mail original -----

Post by Amir Pakdel
Hi Guillaume,
I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or even
"File System(s)" itself).
Letter Type File System Total (MB) Free (MB) Designation
Letter Type File System Total (MB) Free (MB) Designation
vxfs / 2097152 1758760 /dev/vg00/lvol3 As you see there is a confusion
about "Type" and "File System".
I think either Linux or HP-UX should be changed.
Kind Regards,
Amir
Sent: Sat 15/05/2010 3:27:41 PM +0450
Subject: [team] Naming ambiguity in reports
Hi Amir,
The "Storage" and "Diks" icons are named as it because it refers to
the "storages" table and the "drives" table in the database.
"storages" table refers to the the kind of storages like hard drive,
floppy or CDROM drives.
"drives" table refers to the windows drives or mount points in Unix
systems.
The "Disks" icon name for the "drives" table may make effectively a
confusion.
So, if you want to change the names of the icons, you just have to
modify the ocsreports PHP code.
Maybe we can change the "Disks" icon name by "Drives" offcially in
ocsreports ? Does it I may create again another confusion ?
What are your opinions all other ?
Kind regards,
-- Guillaume
----- Mail original -----
Dear developers,
Storage shows my Physical storages which can also be called Disk!
Disk(s) shows my mount points which may be called also storage area!
May we change the naming to resolve this ambiguity?
Best Regards,
Amir

Amir Pakdel

2010-05-18 07:50:37 UTC

Permalink

Hi all,

One more thing:
I want to add "OS installation Date/Time" into the inventory. Where
should I add it?

Kind regards,

Amir

------------------------------------------------------------------------
*From:* Amir Pakdel <a.pakdel-***@public.gmane.org>
*Sent:* Tue 18/05/2010 10:47:04 AM +0450
*To:* "developers.en-XRi04JE7P7s3GMRc9dnpK0B+***@public.gmane.org"
<developers.en-XRi04JE7P7s3GMRc9dnpK0B+***@public.gmane.org>
*Subject:* [team] Naming ambiguity in reports

Post by Amir Pakdel
Hi Guillaume,
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*
/
vxfs 2097152 1290888 /dev/vg00/lvol3
Although I prefer the other way around (the current output of HP-UX
agent), if it is the convention in the current rlease I would change
the agent.
Kind regards,
Amir
------------------------------------------------------------------------
*Sent:* Sun 16/05/2010 11:44:17 PM +0450
*Subject:* [team] Naming ambiguity in reports

Post by Amir Pakdel
Hi Guillaume,
I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or even
"File System(s)" itself).
Letter Type File System Total (MB) Free (MB) Designation
Letter Type File System Total (MB) Free (MB) Designation
vxfs / 2097152 1758760 /dev/vg00/lvol3 As you see there is a confusion
about "Type" and "File System".
I think either Linux or HP-UX should be changed.
Kind Regards,
Amir
Sent: Sat 15/05/2010 3:27:41 PM +0450
Subject: [team] Naming ambiguity in reports
Hi Amir,
The "Storage" and "Diks" icons are named as it because it refers to
the "storages" table and the "drives" table in the database.
"storages" table refers to the the kind of storages like hard drive,
floppy or CDROM drives.
"drives" table refers to the windows drives or mount points in Unix
systems.
The "Disks" icon name for the "drives" table may make effectively a
confusion.
So, if you want to change the names of the icons, you just have to
modify the ocsreports PHP code.
Maybe we can change the "Disks" icon name by "Drives" offcially in
ocsreports ? Does it I may create again another confusion ?
What are your opinions all other ?
Kind regards,
-- Guillaume
----- Mail original -----
Dear developers,
Storage shows my Physical storages which can also be called Disk!
Disk(s) shows my mount points which may be called also storage area!
May we change the naming to resolve this ambiguity?
Best Regards,
Amir

Guillaume PROTET

2010-05-18 21:27:29 UTC

Permalink

Hi Amir,

The "Filesystem" column is use to show the file system type (NTFS,FTA32,ext3,vxfs etc...) and not the mount point. But, I think putting the mount point is a mistacke with Unix system because the "Type" column does not correspond to this.
On Windows system, the "Type" column correponds to "Hard drives", "CDROM" etc... I think we coul put the mount the Unix mount points in the "Letter" column instead of the "Type" one because the "Letter" colum is more appropriate. For Unix systems, we could leave the "Type" column empty if we are not able to get this kind of informations.
This would need to modify all the Drives.pm files for every OS in the Unix agnent if we deceide to use the "Letter" column instead of the "Type" column.

What's are your opinion all others ?

--
Guillaume

----- Mail original -----

Post by Amir Pakdel
Hi Guillaume,
Letter Type File System Total (MB) Free (MB) Designation
/
vxfs 2097152 1290888 /dev/vg00/lvol3 Although I prefer the other way
around (the current output of HP-UX agent), if it is the convention in
the current rlease I would change the agent.
Kind regards,
Amir
Sent: Sun 16/05/2010 11:44:17 PM +0450
Subject: [team] Naming ambiguity in reports
Hi Amir,
About HPUX confusion i think it is a mistacke in the file
Ocsinventory::Agent::Backend::OS::HPUX::Drives.pm from the unix agent
for ( `fstyp -l | grep -v nfs` ) {
$type=$_; for ( `bdf -t $type `) {
if ( /Filesystem/ ) { ; } ;
if ( /^(\S+)\s(\d+)\s+(\d+)\s+(\d+)\s+(\d+%)\s+(\S+)/ ) {
$lv=$1; $total=$2;
$free=$3; $fs=$6;
$inventory->addDrives({ FREE => $free,
FILESYSTEM => $fs,
TOTAL => $total,
TYPE => $type,
VOLUMN => $lv,
});
};
I can't test it because I don't have a HPUX computer but I think there
could a mistacke about $fs (not $6 of the regex ?) or a conversely
between $fs and $type.
You can try to correct this to delete the confusion and we will commit
it in the unix agent.
Kind regards,
-- Guillaume
----- Mail original -----
Hi Guillaume,
I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or even
"File System(s)" itself).
Letter Type File System Total (MB) Free (MB) Designation
Letter Type File System Total (MB) Free (MB) Designation
vxfs / 2097152 1758760 /dev/vg00/lvol3 As you see there is a confusion
about "Type" and "File System".
I think either Linux or HP-UX should be changed.
Kind Regards,
Amir
15/05/2010 3:27:41 PM +0450
Naming ambiguity in reports
Hi Amir,
The "Storage" and "Diks" icons are named as it because it refers to
the "storages" table and the "drives" table in the database.
"storages" table refers to the the kind of storages like hard drive,
floppy or CDROM drives.
"drives" table refers to the windows drives or mount points in Unix
systems.
The "Disks" icon name for the "drives" table may make effectively a
confusion.
So, if you want to change the names of the icons, you just have to
modify the ocsreports PHP code.
Maybe we can change the "Disks" icon name by "Drives" offcially in
ocsreports ? Does it I may create again another confusion ?
What are your opinions all other ?
Kind regards,
-- Guillaume
----- Mail original -----
Dear developers,
Storage shows my Physical storages which can also be called Disk!
Disk(s) shows my mount points which may be called also storage area!
May we change the naming to resolve this ambiguity?
Best Regards,
Amir

Amir Pakdel

2010-05-19 03:17:47 UTC

Permalink

Hi Guillaume,

I have currently changed the HP-UX agent so that its result look like
the following:
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*

/ vxfs 2097152 796952 /dev/vg00/lvol3

And the Linux has been as the following:
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*

/ ext3 5905 5249 /dev/vg00/lvol0

I think before deciding about the ""Letter" column, it would work. I
have pushed the latest changes and proposed for merging.
<https://code.launchpad.net/%7Epakdel-gmail/ocsinventory-unix-agent/hpux/+register-merge>

Kind Regards,

Amir

------------------------------------------------------------------------
*From:* Guillaume PROTET <guillaume.protet-Q/0Kkk6T+***@public.gmane.org>
*Sent:* Wed 19/05/2010 1:57:29 AM +0450
*To:* developers en <developers.en-XRi04JE7P7s3GMRc9dnpK0B+***@public.gmane.org>
*Subject:* [team] Naming ambiguity in reports

Post by Guillaume PROTET
Hi Amir,
The "Filesystem" column is use to show the file system type (NTFS,FTA32,ext3,vxfs etc...) and not the mount point. But, I think putting the mount point is a mistacke with Unix system because the "Type" column does not correspond to this.
On Windows system, the "Type" column correponds to "Hard drives", "CDROM" etc... I think we coul put the mount the Unix mount points in the "Letter" column instead of the "Type" one because the "Letter" colum is more appropriate. For Unix systems, we could leave the "Type" column empty if we are not able to get this kind of informations.
This would need to modify all the Drives.pm files for every OS in the Unix agnent if we deceide to use the "Letter" column instead of the "Type" column.
What's are your opinion all others ?
--
Guillaume
----- Mail original -----

Guillaume PROTET

2010-05-18 21:41:59 UTC

Permalink

Hi Amir,

Do you want to add the OS installation date manually in the inventory or do you want to get it by the agent and stored in the databse by OCS server ?

If you want to do it manually, you can create an admin info to do it. You jsut have to create and admin info withe type "Date" and fill it manullay in the iinventory pages of your computers.

If you want to get automatically, we can take a look to get it from the agent (if we can get this information from the OS) and store it in the database by creating a new column in the hardware table for example. The main goal would be to get this OS installation date from windows agent and unix agent but it could be interesting to do it.

--
Guillaume

----- Mail original -----

Post by Amir Pakdel
Hi all,
I want to add "OS installation Date/Time" into the inventory. Where
should I add it?
Kind regards,
Amir
Sent: Tue 18/05/2010 10:47:04 AM +0450
Subject: [team] Naming ambiguity in reports
Hi Guillaume,
Letter Type File System Total (MB) Free (MB) Designation
/
vxfs 2097152 1290888 /dev/vg00/lvol3 Although I prefer the other way
around (the current output of HP-UX agent), if it is the convention in
the current rlease I would change the agent.
Kind regards,
Amir
Sent: Sun 16/05/2010 11:44:17 PM +0450
Subject: [team] Naming ambiguity in reports
Hi Amir,
About HPUX confusion i think it is a mistacke in the file
Ocsinventory::Agent::Backend::OS::HPUX::Drives.pm from the unix agent
for ( `fstyp -l | grep -v nfs` ) {
$type=$_; for ( `bdf -t $type `) {
if ( /Filesystem/ ) { ; } ;
if ( /^(\S+)\s(\d+)\s+(\d+)\s+(\d+)\s+(\d+%)\s+(\S+)/ ) {
$lv=$1; $total=$2;
$free=$3; $fs=$6;
$inventory->addDrives({ FREE => $free,
FILESYSTEM => $fs,
TOTAL => $total,
TYPE => $type,
VOLUMN => $lv,
});
};
I can't test it because I don't have a HPUX computer but I think there
could a mistacke about $fs (not $6 of the regex ?) or a conversely
between $fs and $type.
You can try to correct this to delete the confusion and we will commit
it in the unix agent.
Kind regards,
-- Guillaume
----- Mail original -----
Hi Guillaume,
I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or even
"File System(s)" itself).
Letter Type File System Total (MB) Free (MB) Designation
Letter Type File System Total (MB) Free (MB) Designation
vxfs / 2097152 1758760 /dev/vg00/lvol3 As you see there is a confusion
about "Type" and "File System".
I think either Linux or HP-UX should be changed.
Kind Regards,
Amir
15/05/2010 3:27:41 PM +0450
Naming ambiguity in reports
Hi Amir,
The "Storage" and "Diks" icons are named as it because it refers to
the "storages" table and the "drives" table in the database.
"storages" table refers to the the kind of storages like hard drive,
floppy or CDROM drives.
"drives" table refers to the windows drives or mount points in Unix
systems.
The "Disks" icon name for the "drives" table may make effectively a
confusion.
So, if you want to change the names of the icons, you just have to
modify the ocsreports PHP code.
Maybe we can change the "Disks" icon name by "Drives" offcially in
ocsreports ? Does it I may create again another confusion ?
What are your opinions all other ?
Kind regards,
-- Guillaume
----- Mail original -----
Dear developers,
Storage shows my Physical storages which can also be called Disk!
Disk(s) shows my mount points which may be called also storage area!
May we change the naming to resolve this ambiguity?
Best Regards,
Amir

Amir Pakdel

2010-05-19 03:01:48 UTC

Permalink

Hi Guillaume,

On HP-UX, /opt/ignite/bin/print_manifest gives something like the following:

System Information

Your Hewlett-Packard computer has software installed and

configured as follows.

* The system was created October 06, 2009, 16:52:02 EDT.*

It was created with Ignite-UX revision C.6.5.61.

On Linux, however, I do not know any simple way to do that. I would
query installation date of packages like setup, rootfiles, filesystem,
coreutils, glibc, glibc-common, libgcc; or even date/time of
anaconda-ks.cfg (kick-start config file).

Worst of all, I have no idea about Windows! I will ask my colleagues ;)

Kind regards,

Amir

------------------------------------------------------------------------
*From:* Guillaume PROTET <guillaume.protet-Q/0Kkk6T+***@public.gmane.org>
*Sent:* Wed 19/05/2010 2:11:59 AM +0450
*To:* developers en <developers.en-XRi04JE7P7s3GMRc9dnpK0B+***@public.gmane.org>
*Subject:* [team] Naming ambiguity in reports

Post by Guillaume PROTET
Hi Amir,
Do you want to add the OS installation date manually in the inventory or do you want to get it by the agent and stored in the databse by OCS server ?
If you want to do it manually, you can create an admin info to do it. You jsut have to create and admin info withe type "Date" and fill it manullay in the iinventory pages of your computers.
If you want to get automatically, we can take a look to get it from the agent (if we can get this information from the OS) and store it in the database by creating a new column in the hardware table for example. The main goal would be to get this OS installation date from windows agent and unix agent but it could be interesting to do it.
--
Guillaume
----- Mail original -----

Guillaume PROTET

2010-05-19 22:01:48 UTC

Permalink

Hi Stephane,

Thank you for suggestion and it looks like interesting...

I am absolutly not an expert about the CIM schema and I am asking myself about the really earnings if we use it in OCS. Should it be easy to integrate it in the OCS structure like the windows agents, the unix agent and the communication server ?

How does the schema works exactly ? Does the big work for integrate it in OCS will really pay later or will it only give few earnings for OCS ?

Kind regards,

--
Guillaume

----- Mail original -----

Post by Amir Pakdel
Hi Guillaume,
I would suggest "Physical Drive" or "Physical Storage" for the hard
disks and "Driver Letter / Mount Point" for the file systems (or
even "File System(s)" itself).
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*
/ ext3 6889 6171 /dev/vg00/lvol0
*Letter * * Type * * File System * * Total (MB) * * Free (MB) * *
Designation*
vxfs / 2097152 1758760 /dev/vg00/lvol3
As you see there is a confusion about "Type" and "File System".
I think either Linux or HP-UX should be changed.

Hi
I suggest rethinking all internal information representation (XML and
http://www.dmtf.org/standards/cim/cim_schema_v2250/
http://www.vmware.com/support/developer/cim-sdk/smash/u3/ga/apirefdoc/CIM_FileSystem.html
http://msdn.microsoft.com/en-us/library/aa387273(VS.85).aspx
http://publib.boulder.ibm.com/infocenter/iseries/v1r1/en_US/index.htm?info/ciminfo/eicahcim_filesystem.htm
http://www.javasystemsolutions.com/documentation/thirdparty/cdm/BMC_FileSystem.html
( Tested host use top-pegasus with sblim providers on RHEL5)
METHOD=EnumerateInstances
CLASS=CIM_FileSystem
cat <<__EOM__ > request.xml
<?xml version="1.0" ?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="3075" PROTOCOLVERSION="1.0">
<SIMPLEREQ> <IMETHODCALL NAME="$METHOD">
<LOCALNAMESPACEPATH> <NAMESPACE NAME="root"/>
<NAMESPACE NAME="cimv2"/>
</LOCALNAMESPACEPATH> <IPARAMVALUE NAME="CLASSNAME">
<CLASSNAME NAME="$CLASS"/>
</IPARAMVALUE> </IMETHODCALL>
</SIMPLEREQ> </MESSAGE>
</CIM>
__EOM__
curl -0 --insecure
@request.xml \
-H 'Content-Type: application/xml; charset="utf-8"' \
-H 'CIMProtocolVersion: 1.0' \
-H 'CIMOperation: MethodCall' \
-H "CIMMethod: $METHOD" \
-H 'CIMObject: root%2Fcimv2' | xmllint --format -
Result output
<?xml version="1.0" encoding="utf-8"?>
<CIM CIMVERSION="2.0" DTDVERSION="2.0">
<MESSAGE ID="3075" PROTOCOLVERSION="1.0">
<SIMPLERSP> <IMETHODRESPONSE NAME="EnumerateInstances">
<IRETURNVALUE> <VALUE.NAMEDINSTANCE>
<INSTANCENAME CLASSNAME="Linux_Ext3FileSystem">
<KEYBINDING NAME="CreationClassName">
<KEYVALUE VALUETYPE="string">Linux_Ext3FileSystem</KEYVALUE>
</KEYBINDING> <KEYBINDING NAME="CSCreationClassName">
<KEYVALUE VALUETYPE="string">Linux_ComputerSystem</KEYVALUE>
</KEYBINDING> <KEYBINDING NAME="CSName">
<KEYVALUE VALUETYPE="string">host.ocsinventory-ng.org</KEYVALUE>
</KEYBINDING> <KEYBINDING NAME="Name">
<KEYVALUE VALUETYPE="string">/dev/vg1/opt</KEYVALUE>
</KEYBINDING> </INSTANCENAME>
<INSTANCE CLASSNAME="Linux_Ext3FileSystem">
<PROPERTY NAME="Caption" TYPE="string">
<VALUE>Ext3 local file system</VALUE>
</PROPERTY> <PROPERTY NAME="Description" TYPE="string">
<VALUE>Represents the file store controlled by a ComputerSystem
through local means.</VALUE>
</PROPERTY> <PROPERTY NAME="ElementName" TYPE="string">
<VALUE>/opt</VALUE> </PROPERTY>
<PROPERTY NAME="InstallDate" TYPE="datetime"></PROPERTY>
<PROPERTY.ARRAY NAME="OperationalStatus"
TYPE="uint16"></PROPERTY.ARRAY> <PROPERTY.ARRAY
NAME="StatusDescriptions" TYPE="string"></PROPERTY.ARRAY>
<PROPERTY NAME="Status" TYPE="string">
<VALUE>OK</VALUE> </PROPERTY>
<PROPERTY NAME="HealthState" TYPE="uint16"></PROPERTY>
<PROPERTY NAME="EnabledState" TYPE="uint16">
<VALUE>3</VALUE> </PROPERTY>
<PROPERTY NAME="OtherEnabledState" TYPE="string">
<VALUE>NULL</VALUE> </PROPERTY>
<PROPERTY NAME="RequestedState" TYPE="uint16">
<VALUE>3</VALUE> </PROPERTY>
<PROPERTY NAME="EnabledDefault" TYPE="uint16">
<VALUE>2</VALUE> </PROPERTY>
<PROPERTY NAME="TimeOfLastStateChange" TYPE="datetime"></PROPERTY>
<PROPERTY NAME="CSCreationClassName" TYPE="string">
<VALUE>Linux_ComputerSystem</VALUE> </PROPERTY>
<PROPERTY NAME="CSName" TYPE="string">
<VALUE>host.ocsinventory-ng.org</VALUE> </PROPERTY>
<PROPERTY NAME="CreationClassName" TYPE="string">
<VALUE>Linux_Ext3FileSystem</VALUE> </PROPERTY>
<PROPERTY NAME="Name" TYPE="string">
<VALUE>/dev/vg1/opt</VALUE> </PROPERTY>
<PROPERTY NAME="Root" TYPE="string">
<VALUE>/opt</VALUE> </PROPERTY>
<PROPERTY NAME="BlockSize" TYPE="uint64">
<VALUE>4096</VALUE> </PROPERTY>
<PROPERTY NAME="FileSystemSize" TYPE="uint64">
<VALUE>3325812736</VALUE> </PROPERTY>
<PROPERTY NAME="AvailableSpace" TYPE="uint64">
<VALUE>2276294656</VALUE> </PROPERTY>
<PROPERTY NAME="ReadOnly" TYPE="boolean">
<VALUE>FALSE</VALUE> </PROPERTY>
<PROPERTY NAME="EncryptionMethod" TYPE="string"></PROPERTY>
<PROPERTY NAME="CompressionMethod" TYPE="string"></PROPERTY>
<PROPERTY NAME="CaseSensitive" TYPE="boolean"></PROPERTY>
<PROPERTY NAME="CasePreserved" TYPE="boolean"></PROPERTY>
<PROPERTY.ARRAY NAME="CodeSet" TYPE="uint16"></PROPERTY.ARRAY>
<PROPERTY NAME="MaxFileNameLength" TYPE="uint32">
<VALUE>255</VALUE> </PROPERTY>
<PROPERTY NAME="ClusterSize" TYPE="uint32"></PROPERTY>
<PROPERTY NAME="FileSystemType" TYPE="string">
<VALUE>ext3</VALUE> </PROPERTY>
<PROPERTY NAME="PersistenceType" TYPE="uint16"></PROPERTY>
<PROPERTY NAME="OtherPersistenceType" TYPE="string"></PROPERTY>
<PROPERTY NAME="NumberOfFiles" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="FreeInodes" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="TotalInodes" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="FSReservedCapacity" TYPE="uint64"></PROPERTY>
<PROPERTY NAME="PercentageSpaceUse" TYPE="uint8">
<VALUE>26</VALUE> </PROPERTY>
</INSTANCE> </VALUE.NAMEDINSTANCE>
....
Using a subset of this schema should be enough of course.
Regards
-- Stéphane Urbanovski

Stéphane Urbanovski

2010-05-20 08:45:34 UTC

Permalink

Post by Guillaume PROTET
Hi Stephane,

Hi Guillaume

Post by Guillaume PROTET
Thank you for suggestion and it looks like interesting...
I am absolutly not an expert about the CIM schema and I am asking myself about the really earnings if we use it in OCS.
Should it be easy to integrate it in the OCS structure like the windows agents, the unix agent and the communication server ?

Like any major restructuration, it's easy to understand that it's not an easy work to switch to a new schema.

Windows agent use WMI wish is based on CIM :
http://www.microsoft.com/whdc/archive/WMI-CIM.mspx

Post by Guillaume PROTET
How does the schema works exactly ? Does the big work for integrate it in OCS will really pay later or will it only give few earnings for OCS ?

CIM is a mature, well documented schema and a widely used industrial standard.

They are some schema issues to fix in OCS (filesystems, processors, hardware table, etc ) : using a subset of CIM should be an elegant way to fix those problems.

Regards

--
Stéphane Urbanovski