Menu
▾
▴
sblim-devel — All SBLIM-related discussion, including tech support
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
(3) |
Oct
(2) |
Nov
(22) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(1) |
Feb
(7) |
Mar
(23) |
Apr
(34) |
May
(2) |
Jun
(5) |
Jul
|
Aug
(1) |
Sep
(5) |
Oct
(14) |
Nov
(10) |
Dec
(4) |
| 2003 |
Jan
(7) |
Feb
(2) |
Mar
(19) |
Apr
(11) |
May
(12) |
Jun
(5) |
Jul
(7) |
Aug
(2) |
Sep
|
Oct
(10) |
Nov
(5) |
Dec
(13) |
| 2004 |
Jan
(1) |
Feb
(27) |
Mar
(7) |
Apr
(22) |
May
(18) |
Jun
(7) |
Jul
(4) |
Aug
(32) |
Sep
(9) |
Oct
|
Nov
(21) |
Dec
(15) |
| 2005 |
Jan
(12) |
Feb
(9) |
Mar
(15) |
Apr
(24) |
May
(44) |
Jun
(45) |
Jul
(12) |
Aug
(19) |
Sep
(36) |
Oct
(20) |
Nov
(22) |
Dec
(8) |
| 2006 |
Jan
(10) |
Feb
(24) |
Mar
(8) |
Apr
(2) |
May
(17) |
Jun
(10) |
Jul
(3) |
Aug
(12) |
Sep
(3) |
Oct
(12) |
Nov
(25) |
Dec
(52) |
| 2007 |
Jan
(9) |
Feb
(30) |
Mar
(68) |
Apr
(23) |
May
(17) |
Jun
(68) |
Jul
(26) |
Aug
(17) |
Sep
(14) |
Oct
(41) |
Nov
(66) |
Dec
(16) |
| 2008 |
Jan
(39) |
Feb
(41) |
Mar
(22) |
Apr
(54) |
May
(28) |
Jun
(50) |
Jul
(26) |
Aug
(34) |
Sep
(21) |
Oct
(20) |
Nov
(16) |
Dec
(10) |
| 2009 |
Jan
(20) |
Feb
(29) |
Mar
(49) |
Apr
(30) |
May
(15) |
Jun
(35) |
Jul
(18) |
Aug
(12) |
Sep
(32) |
Oct
(18) |
Nov
(19) |
Dec
(23) |
| 2010 |
Jan
(22) |
Feb
(38) |
Mar
(24) |
Apr
(18) |
May
(28) |
Jun
(11) |
Jul
(6) |
Aug
(20) |
Sep
(26) |
Oct
(18) |
Nov
(11) |
Dec
(18) |
| 2011 |
Jan
(21) |
Feb
(7) |
Mar
(31) |
Apr
(23) |
May
(28) |
Jun
(17) |
Jul
(7) |
Aug
(3) |
Sep
(2) |
Oct
(3) |
Nov
|
Dec
(4) |
| 2012 |
Jan
(3) |
Feb
(5) |
Mar
(13) |
Apr
(2) |
May
|
Jun
(16) |
Jul
(3) |
Aug
(10) |
Sep
(19) |
Oct
(1) |
Nov
(8) |
Dec
(10) |
| 2013 |
Jan
(9) |
Feb
(4) |
Mar
(28) |
Apr
(24) |
May
(27) |
Jun
(3) |
Jul
(4) |
Aug
(11) |
Sep
(15) |
Oct
(10) |
Nov
(7) |
Dec
(8) |
| 2014 |
Jan
(8) |
Feb
(27) |
Mar
(6) |
Apr
(6) |
May
(6) |
Jun
(14) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(7) |
Nov
(4) |
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
(6) |
May
(4) |
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Marcin G. <go...@go...> - 2001-11-20 02:28:04
|
On Mon 19. November 2001 15:44, you wrote: > In terms of data consistency and performance a provider cache > would not be the best solution for FSVOL . That solution > would force overhead in memory management and you lose > performance . Its not necessary for this kind of provider . > Maybe in another content such a solution would be the best > way to go but here I recommend to use the direct access . Well, some kind cache is inevitable IMHO. Simply enumInstancesNames returns names of currently mounted filesystems but before CIMOM issues a getInstance somebody could remount some of the filesystems, so getInstance would have to return an error which isn't an expected behaviour. Or was this whole situation thought of before and it's covered somewhere in the CIMOM specs I haven't got the opportunity to read? -- Marcin Gozdalik <go...@go...> |
|
From: Marcin G. <go...@go...> - 2001-11-19 14:35:01
|
Hi
I've run into sum trouble compiling NPI (latest from CVS) for Pegasus (latest
from CVS) (the compiler errors are interleaved with my explanations for
better readability):
In file included from NPIAssociationProvider.cpp:23:
NPIAssociationProvider.h:81: conflicting return type specified for virtual
function `void Pegasus::NPIAssociationProvider::referenceNames(const
Pegasus::OperationContext &, const Pegasus::CIMReference &, const
Pegasus::String &, const Pegasus::String &,
Pegasus::ResponseHandler<Pegasus::CIMReference> &)'
/home/gozdal/DMTF/Pegasus/pegasus/src/Pegasus/Provider2/CIMAssociationProvider.h:82:
overriding definition as `class Pegasus::Array<Pegasus::CIMReference>
Pegasus::CIMAssociationProvider::referenceNames(const
Pegasus::OperationContext &, const Pegasus::CIMReference &, const
Pegasus::String &, const Pegasus::String &,
Pegasus::ResponseHandler<Pegasus::CIMReference> &)'
the NPIAssocationProvider::referenceNames is declared in
NPIAssociationProvider.h as:
class PEGASUS_PROVIDER_LINKAGE NPIAssociationProvider :
public NPIBaseProvider,
public virtual CIMAssociationProvider
{
public:
// [..snipped unimportant things..]
// CIMAssociationProvider interface
void associators(
void associatorNames(
void references(
void referenceNames(
}
whereas in CIMAssociationProvider.h CIMAssociationProvider is declared as:
class PEGASUS_PROVIDER_LINKAGE CIMAssociationProvider : public CIMBaseProvider
{
public:
CIMAssociationProvider(void);
virtual ~CIMAssociationProvider(void);
virtual void associators(
virtual void associatorNames(
virtual void references(
virtual Array<CIMReference> referenceNames(
};
so the referenceNames should clearly return an Array<CIMReference> and not
void.
NPIAssociationProvider.cpp: In method `void
Pegasus::NPIAssociationProvider::associators(const Pegasus::OperationContext
&, const Pegasus::CIMReference &, const Pegasus::String &, const
Pegasus::String &, const Pegasus::String &, const Pegasus::String &, unsigned
int, const Pegasus::Array<Pegasus::String> &,
Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath> &)':
NPIAssociationProvider.cpp:45: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::processing ()'
NPIAssociationProvider.cpp:96: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::deliver
(Pegasus::CIMObjectWithPath &)'
NPIAssociationProvider.cpp:100: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::complete ()'
NPIAssociationProvider.cpp:104: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::complete ()'
NPIAssociationProvider.cpp: In method `void
Pegasus::NPIAssociationProvider::associatorNames(const
Pegasus::OperationContext &, const Pegasus::CIMReference &, const
Pegasus::String &, const Pegasus::String &, const Pegasus::String &, const
Pegasus::String &, Pegasus::ResponseHandler<Pegasus::CIMReference> &)':
NPIAssociationProvider.cpp:118: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::processing ()'
NPIAssociationProvider.cpp:156: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::deliver
(Pegasus::CIMReference &)'
NPIAssociationProvider.cpp:159: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::complete
()'
NPIAssociationProvider.cpp:163: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::complete
()'
NPIAssociationProvider.cpp: In method `void
Pegasus::NPIAssociationProvider::references(const Pegasus::OperationContext
&, const Pegasus::CIMReference &, const Pegasus::String &, const
Pegasus::String &, unsigned int, const Pegasus::Array<Pegasus::String> &,
Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath> &)':
NPIAssociationProvider.cpp:177: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::processing ()'
NPIAssociationProvider.cpp:221: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::deliver
(Pegasus::CIMObjectWithPath &)'
NPIAssociationProvider.cpp:225: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::complete ()'
NPIAssociationProvider.cpp:229: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMObjectWithPath>::complete ()'
NPIAssociationProvider.cpp: In method `void
Pegasus::NPIAssociationProvider::referenceNames(const
Pegasus::OperationContext
&, const Pegasus::CIMReference &, const Pegasus::String &, const
Pegasus::String &, Pegasus::ResponseHandler<Pegasus::CIMReference> &)':
NPIAssociationProvider.cpp:241: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::processing ()'
NPIAssociationProvider.cpp:276: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::deliver
(Pegasus::CIMReference &)'
NPIAssociationProvider.cpp:279: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::complete
()'
NPIAssociationProvider.cpp:283: no matching function for call to
`Pegasus::ResponseHandler<Pegasus::CIMReference>::complete
()'
make: *** [NPIAssociationProvider.o] Error 1
All of the above errors are caused by the PROVIDER_ENTRY and PROVIDER_EXIT
macros defined in NPIProvider.h as:
#define PROVIDER_ENTRY \
_npiHandle->thisObject = (void *)CreateEnv(&_cimomHandle, nameSpace); \
handler.processing();
#define PROVIDER_EXIT \
DeleteEnv((NPIenv *)_npiHandle->thisObject); \
handler.complete();
and by calling handler.deliver()
the handler is an object of the ResponseHandler class which is declared in
ResponseHandler.h as follows:
template<class object_type>
class ResponseHandler
{
public:
public:
ResponseHandler(void) { };
virtual ~ResponseHandler(void) { };
virtual void setStatus(const RESPONSE_HANDLER_STATUS status) = 0;
virtual void putObject(const object_type & object) = 0;
// virtual void reserve(const Uint32 size) = 0;
};
I'd assume the handler.processing() call should be changed into
handler.setStatus(PROCESSING), handler.complete into
handler.setStatus(COMPLETED) and handler.deliver(ref) into
handler.putObject(ref). I'm not sending any patches as I don't understand the
code fully and I'm drawing conclusions from declarations and from the names
of objects and methods and not from their implementation.
Also there are slight bugs in #includes also as some files try to include
<Pegasus/Common/CIMOMHandle.h> and <Pegasus/Common/OperationContext.h> and in
the latest Pegasus version CIMOMHandle.h resides in Pegasus/Repository and
OperationContext.h in Pegasus/Provider2.
I've tried to contect Markus Mueller a week ago regarding similar troubles
but haven't received any reply since then so I'm sending the report here.
Hope it gets fixed.
Cheers,
Marcin
--
Marcin Gozdalik <go...@go...>
|
|
From: Marcin G. <go...@go...> - 2001-11-18 21:56:10
|
On Sun 18. November 2001 19:45, you wrote: > rationale behind your "Provider Cache" thoughts, as I do not see that a > getInstance call would result in enumInstances (although I could imagine > that this happens for associators). The rationale behind my idea is the new getInstance fsvol implementation: nameSpace = CIMObjectPathGetNameSpace( nh , cop ); cLD = CIMObjectPathNew( nh, "Linux_LocalFileSystem" ); CIMObjectPathSetNameSpace( nh , cLD , nameSpace ); ->vi = CIMOMEnumInstances( nh , cLD ,0 ,0); size = VectorSize(nh,vi); nm = CIMObjectPathGetStringKeyValue( nh, cop, "Name"); I think that it's simply easier to do this locally, without involving CIMOM to do enumInstances for us. Since getInstance is called after enumInstances has been called I think enumInstances could cache all the relevant information so that getInstance would be faster. This observation also grew from the speed of executing getInstance on not-so-weak machine (Duron 750,384MB RAM) with SNIA CIMOM - enumInstances was acceptable but clicking on any Linux_LocalFileSystem in openCIMOM browser takes 1-2 seconds to execute which I think is pretty bad. Cheers, Marcin -- Marcin Gozdalik <go...@go...> |
|
From: <mih...@t-...> - 2001-11-18 21:47:35
|
Hi Marcin, I let Heidi answer the fsvol and LVM questions (out of politeness and as I'm not competent enough to do so :-). But I wanted to understand the rationale behind your "Provider Cache" thoughts, as I do not see that a getInstance call would result in enumInstances (although I could imagine that this happens for associators). Marcin Gozdalik (by way of Marcin Gozdalik ) wrote: > > I'm not sure, but from what you're saying getInstance gets only "Name" > property? I couldn't find any NPI docs and I haven't got so much time to dig > all the way through NPI code to find out. If so then it would be rational to > create some sort of a "provider cache" because enumeration of all the > instances stored in the CIMOM for every getInstance operation can be pretty > expensive (in regard both to CPU and to network utilization). > Regards, Viktor |
|
From: Marcin G. <go...@go...> - 2001-11-17 00:40:27
|
On Mon 12. November 2001 14:26, you wrote: > The effect is based on the implementation of the "getInstance" Hmm, I can see the problem, but probably the JVM shouldn't crash anyway ;-) > method . As you can see in the code the CIMObjectPath parameter > is used to extract the mount point of the filesystem ( in the > current implementation stored in key "Name" ) . this mount point > is then used to get all the other information about this special > filesystem instance ( via getmntent() and a comparision between > "Name" and mnt_dir ) . If you swap the content of the properties > this possibility is lost . Now you need the instance instead of I'm not sure, but from what you're saying getInstance gets only "Name" property? I couldn't find any NPI docs and I haven't got so much time to dig all the way through NPI code to find out. If so then it would be rational to create some sort of a "provider cache" because enumeration of all the instances stored in the CIMOM for every getInstance operation can be pretty expensive (in regard both to CPU and to network utilization). I thought of a simple cache that would be able to hold the result of enumInstances so that getInstance would only need to look up in the cache whether object of given name exists or not. The cache should be as general as possible - i.e. it should be useful for RPM, fsvol and also for future providers. I thought of a simple hashing table implementation, though maybe some kind of Trie tree would be better? Another question that needs to be answered before trying to implement such a cache is what kind of information exactly has to be stored in the cache. The Name property serves as the key (together with the namespace) but what is the value? Is it enough to store CIMInstance returned by makeInst? With such a cache enumInstance would invalidate all the existing cache entries of the same class in the same namespace and create a vector of all instances currently available on the computer. The vector would be returned to CIMOM and also the elements stored in the cache. Then getInstance would be a mere check if the object exists in the cache or not. > This change has impact to the association LVM_ResidesOnExtent.c > too . I was thinking about implementing its functionality in only > one provider ( this would be Linux_ResidesOnExtent.c ) . What do > you think ? Would this make sense ? Frankly I do not feel competent to say anything as I haven't got LVM on my computer and haven't had (yet) contact with LVM. Hope to change it in the nearest future ;-) > http://w3.opensource.ibm.com/projects/ibmcimom/ What is the ibmcimom project? Is IBM involved in creating it's own CIMOM? gozdal@master:~$ host -t ns ibm.com ibm.com NS NS.AUSTIN.ibm.com ibm.com NS NS.WATSON.ibm.com ibm.com NS NS.ALMADEN.ibm.com ibm.com NS INTERNET-SERVER.ZURICH.ibm.com ibm.com NS NS.ERS.ibm.com gozdal@master:~$ host -a w3.opensource.ibm.com NS.ERS.ibm.com w3.opensource.ibm.com does not exist at NS.ERS.ibm.com (Authoritative answer) -- Marcin Gozdalik <go...@go...> |
|
From: Viktor M. <mih...@de...> - 2001-11-14 17:14:16
|
Hi community,
this is to inform you that we have released a new version of NPI (0.9.2)
aimed to improve the Pegasus compatibility. It is using the Pegasus
provider2 interface and requires new stubs for the NPI providers running
under Pegasus. RPM 0.9.4 sports these new stubs.
Note: you won't need these if you are only using SNIA CIMOM. Have fun.
Regards,
Viktor
|
|
From: Heidi N. <HEI...@de...> - 2001-11-13 08:32:51
|
Marcin , I swapped the "Root" and "Name" properties in Linux_LocalFileSystem . The effect was the same as you described ! The effect is based on the implementation of the "getInstance" method . As you can see in the code the CIMObjectPath parameter is used to extract the mount point of the filesystem ( in the current implementation stored in key "Name" ) . this mount point is then used to get all the other information about this special filesystem instance ( via getmntent() and a comparision between "Name" and mnt_dir ) . If you swap the content of the properties this possibility is lost . Now you need the instance instead of the CIMObjectPath to get this important mount point . You are right that the properties are swapped and I implemented your suggestion . This change had impact to the class Linux_ResidesOnExtent.c too . The fixed code is in the CVS now . Please have a look at it . This change has impact to the association LVM_ResidesOnExtent.c too . I was thinking about implementing its functionality in only one provider ( this would be Linux_ResidesOnExtent.c ) . What do you think ? Would this make sense ? ! I did not fix the LVM_ResidesOnExtent provider ! ! This provider will not run ! Have fun . by ... heidi Mfg / Regards Heidi Neumann Linux Technology Center - Systems Management - IBM Laboratory Boeblingen - Germany - Schönaicher Str. 220 - 71032 - Böblingen Phone : ++49 (0) 7031 / 16 - 3193 hei...@de... http://w3.opensource.ibm.com/projects/ibmcimom/ http://oss.software.ibm.com/developerworks/projects/sblim/ |
|
From: Heidi N. <HEI...@de...> - 2001-11-13 08:32:51
|
Arvin , the fixed code is in the CVS now ( FSVOL_0_9_3 ) . Please try again . Have fun ... heidi Mfg / Regards Heidi Neumann Linux Technology Center - Systems Management - IBM Laboratory Boeblingen - Germany - Schönaicher Str. 220 - 71032 - Böblingen Phone : ++49 (0) 7031 / 16 - 3193 hei...@de... http://oss.software.ibm.com/developerworks/projects/sblim/ |
|
From: Arvind J. <arv...@iv...> - 2001-11-13 03:14:02
|
Heidi, Thanks a lot for the prompt action. I checkout the updated CVS files. All the mofs compiled fine. Thanks again. Arvind. -----Original Message----- From: Heidi Neumann [mailto:HEI...@de...] Sent: Monday, November 12, 2001 7:10 AM To: Arvind Jain Cc: sbl...@ww...; 'Viktor Mihajlovski' Subject: RE: [Sblim-devel] LVM_Device.mof.snia error !! Arvin , the fixed code is in the CVS now ( FSVOL_0_9_3 ) . Please try again . Have fun ... heidi Mfg / Regards Heidi Neumann Linux Technology Center - Systems Management - IBM Laboratory Boeblingen - Germany - Schönaicher Str. 220 - 71032 - Böblingen Phone : ++49 (0) 7031 / 16 - 3193 hei...@de... http://oss.software.ibm.com/developerworks/projects/sblim/ |
|
From: Marcin G. <go...@go...> - 2001-11-12 00:32:53
|
Hi
I've noticed that the Name and Root properties in Linux_LocalFileSystem are
probably swapped in the code. The CIM_System25.MOF says that Root is "Path
name or other information defining the root of the FileSystem" and Name is
"The inherited Name serves as key of a FileSystem instance within a
ComputerSystem" whereas in the code of fsvol 0.9.2 Root was set to the device
on which the filesystem resides and Name was the mount point. I wanted to do
the simplest thing on earth: swap "Root" and "Name" in
Linux_LocalFileSystem.c. Here is the effect:
Unexpected Signal : 11 occurred at PC=0x40197754
Function
name=runtime_resolve_virtual_method__12LinkResolverR8CallInfoG12methodHandleG11KlassHandleG6HandleT3lP6Thread
Library=/usr/lib/j2re1.3/lib/i386/client/libjvm.so
Current Java thread:
at
org.snia.wbemcmd.xml.XMLGetInstance.execute(XMLGetInstance.java:117)
at org.snia.wbemcmd.xml.WBEMInput.executeIntrinsic(WBEMInput.java:338)
at org.snia.wbemcmd.xml.WBEMInput.executeXML(WBEMInput.java:216)
at
org.snia.wbemcmd.xml.HTTPInput$HTTPConnection.run(HTTPInput.java:293)
at java.lang.Thread.run(Thread.java:484)
Dynamic libraries:
[..snip of a lengthy listing of loaded shared libraries]
Local Time = Sun Nov 11 21:53:59 2001
Elapsed Time = 44
#
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002CC
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (Blackdown-1.3.1-FCS mixed mode)
Now, is this a bug in Java VM? I've already reported it at
ttp://java.sun.com/cgi-bin/bugreport.cgi, but I'm not quite sure. Maybe it's
a bug in NPI itself? Or maybe in JNI? Could anybody knowledgeable take a look
this? I'm using Debian sid/unstable with aformentioned Blackdown flavor of
J2SDK 1.3.1.
Cheers,
Marcin
--
Marcin Gozdalik <go...@go...>
|
|
From: Heidi N. <HEI...@de...> - 2001-11-09 09:54:07
|
Arvid , with the changes you will only get the mofs compiled . But the current implementation of the classes is partly based on this additional keys - the providers wont be able to run ! As I said in my last mail - a fix will be available by next week . ... heidi Mfg / Regards Heidi Neumann Linux Technology Center - Systems Management - IBM Laboratory Boeblingen - Germany - Schönaicher Str. 220 - 71032 - Böblingen Phone : ++49 (0) 7031 / 16 - 3193 hei...@de... http://oss.software.ibm.com/developerworks/projects/sblim/ |
|
From: Arvind J. <arv...@iv...> - 2001-11-09 02:20:33
|
Viktor, The MOF Linux_System.mof.snia compiled fine. The MOFs Linux_Device.mof.snia and LVM_Device.mof.snia gave errors. Temporarily, I changed the additional keys to properties and the MOFs compiled fine after that. Thanks, Arv. -----Original Message----- From: Viktor Mihajlovski [mailto:mih...@de...] Sent: Wednesday, November 07, 2001 8:52 AM To: sbl...@ww... Subject: Re: [Sblim-devel] LVM_Device.mof.snia error !! Hi Arvid, well it seems that we have to revise the classes as I fear Heidi had some good reasons to include the additional keys. Thanks for pointing that out, maybe you could try to modify the MOFs to remove the offending key qualifiers. BTW: did the other MOF files pass the test under OpenWBEM? > Arvind Jain > <arv...@iv... To: "'sbl...@ww...'" > m> <sbl...@ww...> > Sent by: cc: > sblim-devel-admin@www-1 Subject: [Sblim-devel] LVM_Device.mof.snia error !! > 26.ibm.com > > > 11/07/01 12:43 AM > Please respond to > Arvind Jain > > > > When I try to compile the mof file LVM_Device.mof.snia using: > > owmofc http://localhost:5988 /root LVM_Device.mof.snia > > I get the following error: > > File: LVM_Device.mof.snia Line: 0: Starting parsing > File: LVM_Device.mof.snia Line: 387: Finished parsing > File: LVM_Device.mof.snia Line: 37: Processing class: LVM_VolumeGroup > File: LVM_Device.mof.snia Line: 37: Updated class: LVM_VolumeGroup > File: LVM_Device.mof.snia Line: 91: Processing class: LVM_LogicalVolume > Recoverable error in file: LVM_Device.mof.snia on line: 91: Received error > from CIMOM: class does not exist (class does not exist (Parent class has > keys. Child cannot have additional key properties: LVM_LogicalVolume)) > File: LVM_Device.mof.snia Line: 138: Processing class: LVM_PhysicalVolume > Recoverable error in file: LVM_Device.mof.snia on line: 138: Received error > from CIMOM: class does not exist (class does not exist (Parent class has > keys. Child cannot have additional key properties: LVM_PhysicalVolume)) > File: LVM_Device.mof.snia Line: 193: Processing class: LVM_PVExtentRange > Recoverable error in file: LVM_Device.mof.snia on line: 193: Received error > from CIMOM: class does not exist (class does not exist (Parent class has > keys. Child cannot have additional key properties: LVM_PVExtentRange)) > File: LVM_Device.mof.snia Line: 218: Processing class: LVM_ResidesOnExtent > File: LVM_Device.mof.snia Line: 218: Updated class: LVM_ResidesOnExtent > File: LVM_Device.mof.snia Line: 241: Processing class: LVM_Mapping > File: LVM_Device.mof.snia Line: 241: Updated class: LVM_Mapping > File: LVM_Device.mof.snia Line: 265: Processing class: > LVM_PVExtentPartOfPhysicalVolume > File: LVM_Device.mof.snia Line: 265: Updated class: > LVM_PVExtentPartOfPhysicalVolume > File: LVM_Device.mof.snia Line: 289: Processing class: > LVM_LogicalVolumeBasedOnPhysicalVolume > File: LVM_Device.mof.snia Line: 289: Updated class: > LVM_LogicalVolumeBasedOnPhysicalVolume > File: LVM_Device.mof.snia Line: 310: Processing class: > LVM_PhysicalVolumeBasedOnVolume > File: LVM_Device.mof.snia Line: 310: Updated class: > LVM_PhysicalVolumeBasedOnVolume > File: LVM_Device.mof.snia Line: 335: Processing class: > LVM_LogicalVolumeInVolumeGroup > File: LVM_Device.mof.snia Line: 335: Updated class: > LVM_LogicalVolumeInVolumeGroup > File: LVM_Device.mof.snia Line: 360: Processing class: > LVM_PhysicalVolumeInVolumeGroup > File: LVM_Device.mof.snia Line: 360: Updated class: > LVM_PhysicalVolumeInVolumeGroup > Compilation finished. 3 errors occurred. > > Apparently the MOF file has additional key declared in the sub class > derived > from a class that already has keys. > > According to version 2.2 of the CIM Specification the CIMOM sub class > should > not additional key defined. > > Here is a paragraph taken from section 4.5.5 (Title: Key Properties) > of Version 2.2 of the CIM Specification: > > ========================================================== > If a new subclass is defined from a superclass, and the > superclass has key properties (including those inherited > from other classes), the new subclass _cannot_ define > any additional key properties. New key properties in the > subclass can be introduced only if all classes in the > inheritance chain of the new subclass are keyless. > ========================================================== > > I am using OpenWBEM to compile the MOF file in the repository. > I understand that SBLIM is not built for OpenWBEM from Caldera. However, > shouldn't other CIMOM have the same checks built in? > > Is there a way to get around this issue? thx, arv. > > _______________________________________________ > Sblim-devel mailing list > Sbl...@ww... > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel -- Kind Regards / Mit freundlichen Grüßen Viktor Mihajlovski Linux Technology Center IBM Laboratory Böblingen, Germany Phone +49-7031-16-2560 Email mih...@de... _______________________________________________ Sblim-devel mailing list Sbl...@ww... http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel |
|
From: Heidi N. <HEI...@de...> - 2001-11-08 08:18:27
|
Arvin , first thanks for calling my attention to this fact . I strongly agree to the paragraph you copied from the spec 2.2 . The only acceptable way to get around this issue is becoming in conformity with the spec . It is a inexcusable mistake of mine and it is my duty to fix it . In this first schema version I did not seperate the implemen- tation from the schema as clear as I should have done . To fasten the coding progress I used the enumeration returning ObjectPathes . The additional properties I declared as key are the ones I need to create the association instances between the classes . The code will be fixed and in the CVS by next monday (11/12) . thanks ... heidi Mfg / Regards Heidi Neumann Linux Technology Center - Systems Management - IBM Laboratory Boeblingen - Germany - Schönaicher Str. 220 - 71032 - Böblingen Phone : ++49 (0) 7031 / 16 - 3193 hei...@de... http://oss.software.ibm.com/developerworks/projects/sblim/ |
|
From: Viktor M. <mih...@de...> - 2001-11-08 08:16:29
|
Hi Arvid, well it seems that we have to revise the classes as I fear Heidi had some good reasons to include the additional keys. Thanks for pointing that out, maybe you could try to modify the MOFs to remove the offending key qualifiers. BTW: did the other MOF files pass the test under OpenWBEM? > Arvind Jain > <arv...@iv... To: "'sbl...@ww...'" > m> <sbl...@ww...> > Sent by: cc: > sblim-devel-admin@www-1 Subject: [Sblim-devel] LVM_Device.mof.snia error !! > 26.ibm.com > > > 11/07/01 12:43 AM > Please respond to > Arvind Jain > > > > When I try to compile the mof file LVM_Device.mof.snia using: > > owmofc http://localhost:5988 /root LVM_Device.mof.snia > > I get the following error: > > File: LVM_Device.mof.snia Line: 0: Starting parsing > File: LVM_Device.mof.snia Line: 387: Finished parsing > File: LVM_Device.mof.snia Line: 37: Processing class: LVM_VolumeGroup > File: LVM_Device.mof.snia Line: 37: Updated class: LVM_VolumeGroup > File: LVM_Device.mof.snia Line: 91: Processing class: LVM_LogicalVolume > Recoverable error in file: LVM_Device.mof.snia on line: 91: Received error > from CIMOM: class does not exist (class does not exist (Parent class has > keys. Child cannot have additional key properties: LVM_LogicalVolume)) > File: LVM_Device.mof.snia Line: 138: Processing class: LVM_PhysicalVolume > Recoverable error in file: LVM_Device.mof.snia on line: 138: Received error > from CIMOM: class does not exist (class does not exist (Parent class has > keys. Child cannot have additional key properties: LVM_PhysicalVolume)) > File: LVM_Device.mof.snia Line: 193: Processing class: LVM_PVExtentRange > Recoverable error in file: LVM_Device.mof.snia on line: 193: Received error > from CIMOM: class does not exist (class does not exist (Parent class has > keys. Child cannot have additional key properties: LVM_PVExtentRange)) > File: LVM_Device.mof.snia Line: 218: Processing class: LVM_ResidesOnExtent > File: LVM_Device.mof.snia Line: 218: Updated class: LVM_ResidesOnExtent > File: LVM_Device.mof.snia Line: 241: Processing class: LVM_Mapping > File: LVM_Device.mof.snia Line: 241: Updated class: LVM_Mapping > File: LVM_Device.mof.snia Line: 265: Processing class: > LVM_PVExtentPartOfPhysicalVolume > File: LVM_Device.mof.snia Line: 265: Updated class: > LVM_PVExtentPartOfPhysicalVolume > File: LVM_Device.mof.snia Line: 289: Processing class: > LVM_LogicalVolumeBasedOnPhysicalVolume > File: LVM_Device.mof.snia Line: 289: Updated class: > LVM_LogicalVolumeBasedOnPhysicalVolume > File: LVM_Device.mof.snia Line: 310: Processing class: > LVM_PhysicalVolumeBasedOnVolume > File: LVM_Device.mof.snia Line: 310: Updated class: > LVM_PhysicalVolumeBasedOnVolume > File: LVM_Device.mof.snia Line: 335: Processing class: > LVM_LogicalVolumeInVolumeGroup > File: LVM_Device.mof.snia Line: 335: Updated class: > LVM_LogicalVolumeInVolumeGroup > File: LVM_Device.mof.snia Line: 360: Processing class: > LVM_PhysicalVolumeInVolumeGroup > File: LVM_Device.mof.snia Line: 360: Updated class: > LVM_PhysicalVolumeInVolumeGroup > Compilation finished. 3 errors occurred. > > Apparently the MOF file has additional key declared in the sub class > derived > from a class that already has keys. > > According to version 2.2 of the CIM Specification the CIMOM sub class > should > not additional key defined. > > Here is a paragraph taken from section 4.5.5 (Title: Key Properties) > of Version 2.2 of the CIM Specification: > > ========================================================== > If a new subclass is defined from a superclass, and the > superclass has key properties (including those inherited > from other classes), the new subclass _cannot_ define > any additional key properties. New key properties in the > subclass can be introduced only if all classes in the > inheritance chain of the new subclass are keyless. > ========================================================== > > I am using OpenWBEM to compile the MOF file in the repository. > I understand that SBLIM is not built for OpenWBEM from Caldera. However, > shouldn't other CIMOM have the same checks built in? > > Is there a way to get around this issue? thx, arv. > > _______________________________________________ > Sblim-devel mailing list > Sbl...@ww... > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel -- Kind Regards / Mit freundlichen Grüßen Viktor Mihajlovski Linux Technology Center IBM Laboratory Böblingen, Germany Phone +49-7031-16-2560 Email mih...@de... |
|
From: Arvind J. <arv...@iv...> - 2001-11-07 02:43:49
|
When I try to compile the mof file LVM_Device.mof.snia using: owmofc http://localhost:5988 /root LVM_Device.mof.snia I get the following error: File: LVM_Device.mof.snia Line: 0: Starting parsing File: LVM_Device.mof.snia Line: 387: Finished parsing File: LVM_Device.mof.snia Line: 37: Processing class: LVM_VolumeGroup File: LVM_Device.mof.snia Line: 37: Updated class: LVM_VolumeGroup File: LVM_Device.mof.snia Line: 91: Processing class: LVM_LogicalVolume Recoverable error in file: LVM_Device.mof.snia on line: 91: Received error from CIMOM: class does not exist (class does not exist (Parent class has keys. Child cannot have additional key properties: LVM_LogicalVolume)) File: LVM_Device.mof.snia Line: 138: Processing class: LVM_PhysicalVolume Recoverable error in file: LVM_Device.mof.snia on line: 138: Received error from CIMOM: class does not exist (class does not exist (Parent class has keys. Child cannot have additional key properties: LVM_PhysicalVolume)) File: LVM_Device.mof.snia Line: 193: Processing class: LVM_PVExtentRange Recoverable error in file: LVM_Device.mof.snia on line: 193: Received error from CIMOM: class does not exist (class does not exist (Parent class has keys. Child cannot have additional key properties: LVM_PVExtentRange)) File: LVM_Device.mof.snia Line: 218: Processing class: LVM_ResidesOnExtent File: LVM_Device.mof.snia Line: 218: Updated class: LVM_ResidesOnExtent File: LVM_Device.mof.snia Line: 241: Processing class: LVM_Mapping File: LVM_Device.mof.snia Line: 241: Updated class: LVM_Mapping File: LVM_Device.mof.snia Line: 265: Processing class: LVM_PVExtentPartOfPhysicalVolume File: LVM_Device.mof.snia Line: 265: Updated class: LVM_PVExtentPartOfPhysicalVolume File: LVM_Device.mof.snia Line: 289: Processing class: LVM_LogicalVolumeBasedOnPhysicalVolume File: LVM_Device.mof.snia Line: 289: Updated class: LVM_LogicalVolumeBasedOnPhysicalVolume File: LVM_Device.mof.snia Line: 310: Processing class: LVM_PhysicalVolumeBasedOnVolume File: LVM_Device.mof.snia Line: 310: Updated class: LVM_PhysicalVolumeBasedOnVolume File: LVM_Device.mof.snia Line: 335: Processing class: LVM_LogicalVolumeInVolumeGroup File: LVM_Device.mof.snia Line: 335: Updated class: LVM_LogicalVolumeInVolumeGroup File: LVM_Device.mof.snia Line: 360: Processing class: LVM_PhysicalVolumeInVolumeGroup File: LVM_Device.mof.snia Line: 360: Updated class: LVM_PhysicalVolumeInVolumeGroup Compilation finished. 3 errors occurred. Apparently the MOF file has additional key declared in the sub class derived from a class that already has keys. According to version 2.2 of the CIM Specification the CIMOM sub class should not additional key defined. Here is a paragraph taken from section 4.5.5 (Title: Key Properties) of Version 2.2 of the CIM Specification: ========================================================== If a new subclass is defined from a superclass, and the superclass has key properties (including those inherited from other classes), the new subclass _cannot_ define any additional key properties. New key properties in the subclass can be introduced only if all classes in the inheritance chain of the new subclass are keyless. ========================================================== I am using OpenWBEM to compile the MOF file in the repository. I understand that SBLIM is not built for OpenWBEM from Caldera. However, shouldn't other CIMOM have the same checks built in? Is there a way to get around this issue? thx, arv. |
|
From: djpark <dj...@ha...> - 2001-10-29 11:03:11
|
1) SBLIM NPI the latest version(npi-0.9)
compile error : in
$ cd sublim/npi-0.9/pegasus
$ make
error : CIMParamvalue undecleared in namespace Pegasus
Pegasus::CIMParamValue decleared in NPIExternalImpl.h file
but
CIMParamValue does not decleared in Pegasus
Question1.) I don't know this solution...Could you advice to me this
problems
please let me know solution, references or documents.
Question2) How to fully operate Pegasus provider in Snia CIMOM ?
( Can I use that Pegasus Provider does not changed ?) |
|
From: <mih...@t-...> - 2001-10-12 22:46:09
|
Hi, long awaited and finally available, the new NPI release 0.9 adds support for the Pegasus CIMOM. Thanks go to Markus Mueller for making this possible. Hope you will find it useful. Bye, Viktor. |
|
From: Viktor M. <MIH...@de...> - 2001-09-27 19:14:52
|
Hi Sharath,
first of all welcome to SBLIM. There are various ways to contribute,
depending on your background. If you would like to write instrumentation
code the best way to get familiar with the environment is to obtain a CIMOM
(SNIA is the first choice at the moment, although Pegasus support will
follow shortly), download the SBLIM provider and NPI code and get it to
work. Once you succeed you will belong to a very exclusive set of people on
this planet :-).
Looking at the code will probably help to either understand the howtos of
provider programming or lead to sensible questions which could be the
foundation for a FAQ. Documentation and Testing efforts are equally
welcome.
Concrete items we would like to see implemented are NPI adaptations to WBEM
Services (should be straigthforward)) and OpenWBEM. Other than that we love
any providers for CIM classes especially from the CIM_System and CIM_Device
schemas.
Thanks for your interest!
Mit freundlichen Grüßen / Kind Regards
Viktor Mihajlovski
Linux Technology Center
IBM Laboratory Böblingen, Germany
Phone +49-7031-16-2560
E-Mail mih...@de...
Sharath Udupa
<sk...@ya...> To: sbl...@ww...
Sent by: cc:
sblim-devel-admin@www-1 Subject: [Sblim-devel] Re: Sblim-devel digest, Vol 1 #4
26.ibm.com - 1 msg
09/27/01 09:06 AM
Please respond to
Sharath Udupa
hi,
i am actively following the CIM and WBEM in dmtf.org .
i am very interested in contributing to the sblim
project. could you please provide some definitive
pointers towards what i could do, i have gone through
the things to be done, so please tell which i could
try.
thnx and regards.
Sharath
--- sbl...@ww... wrote:
> Send Sblim-devel mailing list submissions to
> sbl...@ww...
>
> To subscribe or unsubscribe via the World Wide Web,
> visit
>
>
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel
>
> or, via email, send a message with subject or body
> 'help' to
> sbl...@ww...
>
> You can reach the person managing the list at
> sbl...@ww...
>
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of Sblim-devel digest..."
>
>
> Today's Topics:
>
> 1. SBLIM FSVOL 0.8 released (Heidi Neumann)
>
> --__--__--
>
> Message: 1
> To: sbl...@ww...
> From: "Heidi Neumann" <HEI...@de...>
> Date: Sat, 22 Sep 2001 08:47:56 +0200
> Subject: [Sblim-devel] SBLIM FSVOL 0.8 released
>
>
> Hi all ,
>
> I want to announce the release 0.8 of the module
> FSVOL .
>
> The first stage of the Filesystem & Volume
> Management Instrumentation is
> now finished . The providers allows the listing of
> filesystem objects ,
> physical partitions , logical volume manager objects
> (logical and physical
> volumes , volume groups , extent ranges ) and all
> relevant associations
> between the different instances .
>
>
> News :
> A method provider to execute a script via a CIM
> instance is in test
> status (method runCommand in class
> Linux_UnitaryComputerSystem) .
>
>
> Schemata :
> If you are interested in the schemata behind please
> go to :
> http://oss.software.ibm.com/sblim/SBLIM_Schemata.pdf
>
>
> Documentation :
> The code is documented . An extra documentation is
> available under :
>
http://oss.software.ibm.com/developerworks/oss/sblim/fsvol.html
>
>
> Prerequisites :
> * SNIA CIMOM
> * NPI for SNIA CIMOM 0.8
>
http://oss.software.ibm.com/developerworks/projects/sblim/
> * CIM_Core25 , CIM_System25 , CIM_Device25
> http://www.dmtf.org/standards/cim_schema_v25.php
>
>
> Since the end of july an group hosted by WBEMsource
> is starting an open
> discussion about the opportunities of consistent
> schemata . Actual there
> is a schema discussion in progress concerning
> Logical Volume Manager but
> there will be more light thrown on other areas too (
> /proc structure /
> contents , package mgmt. , process mgmt. , ... ) .
> If you are interested
> please subscribe to the
> wbe...@op...
> mailing list (
> http://www.opengroup.org/wbemsource/mailinglists.htm
> ) .
>
>
> SBLIM link :
>
http://oss.software.ibm.com/developerworks/projects/sblim/
>
>
>
> Thanks ... Heidi
>
>
>
> Mfg / Regards
>
> Heidi Neumann
>
> IBM Laboratory Boeblingen - Germany
> -- Linux Technology Center --
> Systems Management
>
> Phone : ++49 (0) 7031 / 16 - 3193
> Schönaicher Str. 220, 71032 Böblingen
> hei...@de...
>
>
http://oss.software.ibm.com/developerworks/projects/sblim/
>
>
>
> --__--__--
>
> _______________________________________________
> Sblim-devel mailing list
> Sbl...@ww...
>
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel
>
>
> End of Sblim-devel Digest
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo!
Messenger. http://im.yahoo.com
_______________________________________________
Sblim-devel mailing list
Sbl...@ww...
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel
|
|
From: Sharath U. <sk...@ya...> - 2001-09-27 10:06:25
|
hi, i am actively following the CIM and WBEM in dmtf.org . i am very interested in contributing to the sblim project. could you please provide some definitive pointers towards what i could do, i have gone through the things to be done, so please tell which i could try. thnx and regards. Sharath --- sbl...@ww... wrote: > Send Sblim-devel mailing list submissions to > sbl...@ww... > > To subscribe or unsubscribe via the World Wide Web, > visit > > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel > > or, via email, send a message with subject or body > 'help' to > sbl...@ww... > > You can reach the person managing the list at > sbl...@ww... > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of Sblim-devel digest..." > > > Today's Topics: > > 1. SBLIM FSVOL 0.8 released (Heidi Neumann) > > --__--__-- > > Message: 1 > To: sbl...@ww... > From: "Heidi Neumann" <HEI...@de...> > Date: Sat, 22 Sep 2001 08:47:56 +0200 > Subject: [Sblim-devel] SBLIM FSVOL 0.8 released > > > Hi all , > > I want to announce the release 0.8 of the module > FSVOL . > > The first stage of the Filesystem & Volume > Management Instrumentation is > now finished . The providers allows the listing of > filesystem objects , > physical partitions , logical volume manager objects > (logical and physical > volumes , volume groups , extent ranges ) and all > relevant associations > between the different instances . > > > News : > A method provider to execute a script via a CIM > instance is in test > status (method runCommand in class > Linux_UnitaryComputerSystem) . > > > Schemata : > If you are interested in the schemata behind please > go to : > http://oss.software.ibm.com/sblim/SBLIM_Schemata.pdf > > > Documentation : > The code is documented . An extra documentation is > available under : > http://oss.software.ibm.com/developerworks/oss/sblim/fsvol.html > > > Prerequisites : > * SNIA CIMOM > * NPI for SNIA CIMOM 0.8 > http://oss.software.ibm.com/developerworks/projects/sblim/ > * CIM_Core25 , CIM_System25 , CIM_Device25 > http://www.dmtf.org/standards/cim_schema_v25.php > > > Since the end of july an group hosted by WBEMsource > is starting an open > discussion about the opportunities of consistent > schemata . Actual there > is a schema discussion in progress concerning > Logical Volume Manager but > there will be more light thrown on other areas too ( > /proc structure / > contents , package mgmt. , process mgmt. , ... ) . > If you are interested > please subscribe to the > wbe...@op... > mailing list ( > http://www.opengroup.org/wbemsource/mailinglists.htm > ) . > > > SBLIM link : > http://oss.software.ibm.com/developerworks/projects/sblim/ > > > > Thanks ... Heidi > > > > Mfg / Regards > > Heidi Neumann > > IBM Laboratory Boeblingen - Germany > -- Linux Technology Center -- > Systems Management > > Phone : ++49 (0) 7031 / 16 - 3193 > Schönaicher Str. 220, 71032 Böblingen > hei...@de... > > http://oss.software.ibm.com/developerworks/projects/sblim/ > > > > --__--__-- > > _______________________________________________ > Sblim-devel mailing list > Sbl...@ww... > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/sblim-devel > > > End of Sblim-devel Digest __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com |
|
From: Heidi N. <HEI...@de...> - 2001-09-23 07:30:05
|
Hi all , I want to announce the release 0.8 of the module FSVOL . The first stage of the Filesystem & Volume Management Instrumentation is now finished . The providers allows the listing of filesystem objects , physical partitions , logical volume manager objects (logical and physical volumes , volume groups , extent ranges ) and all relevant associations between the different instances . News : A method provider to execute a script via a CIM instance is in test status (method runCommand in class Linux_UnitaryComputerSystem) . Schemata : If you are interested in the schemata behind please go to : http://oss.software.ibm.com/sblim/SBLIM_Schemata.pdf Documentation : The code is documented . An extra documentation is available under : http://oss.software.ibm.com/developerworks/oss/sblim/fsvol.html Prerequisites : * SNIA CIMOM * NPI for SNIA CIMOM 0.8 http://oss.software.ibm.com/developerworks/projects/sblim/ * CIM_Core25 , CIM_System25 , CIM_Device25 http://www.dmtf.org/standards/cim_schema_v25.php Since the end of july an group hosted by WBEMsource is starting an open discussion about the opportunities of consistent schemata . Actual there is a schema discussion in progress concerning Logical Volume Manager but there will be more light thrown on other areas too ( /proc structure / contents , package mgmt. , process mgmt. , ... ) . If you are interested please subscribe to the wbe...@op... mailing list ( http://www.opengroup.org/wbemsource/mailinglists.htm ) . SBLIM link : http://oss.software.ibm.com/developerworks/projects/sblim/ Thanks ... Heidi Mfg / Regards Heidi Neumann IBM Laboratory Boeblingen - Germany -- Linux Technology Center -- Systems Management Phone : ++49 (0) 7031 / 16 - 3193 Schönaicher Str. 220, 71032 Böblingen hei...@de... http://oss.software.ibm.com/developerworks/projects/sblim/ |
|
From: Viktor M. <mih...@de...> - 2001-07-31 16:26:50
|
Hi all, there's a new release of NPI available in the download area and CVS. Please use this one. Note also that there are some updates to the documentation on the SBLIM homepage. Thanks! -- Kind Regards / Mit freundlichen Grüßen Viktor Mihajlovski Linux Technology Center IBM Laboratory Böblingen, Germany Phone +49-7031-16-2560 Email mih...@de... |
|
From: Viktor M. <mih...@de...> - 2001-07-18 16:50:04
|
Hi, something that comes to my mind would be a slight(?) modification of the schema. How about modelling extents as groups and not as single entities. I would expect that extents are usually handled in a way that <n> consecutive extents are assigned to a logical volume at once instead of one at a time. Of course one could still assign single extents, in which case we would end up with single-extent groups (being the just penalty for this kind of folly:-). Any thoughts or comments on that? > > "Heidi Neumann" <HEI...@de...> on 18/07/2001 16:08:06 > > Please respond to "Heidi Neumann" <HEI...@de...> > > To: sbl...@dw..., ibm...@op... > cc: > > Subject: [Ibmcimom-devel] discussion point : How to handle mass > operations ?!? > > Hi , > > the goal of this mail is to start a discussion about how > to handle mass operations . It is not always the best > solution to avoid them . > > At the moment I'm running in such a mass problem with > the instrumentation of "Filesystems & Volume Management" > and I'm not sure how to solve the forced crashes . > > PROBLEM DESCRIPTION > > - affected module : sblim-fsvol-0.6.1 ( tar.gz ) > FSVOL_0_6_1 ( CVS tag ) > - affected part : the instrumentation of the Logical > Volume Manager for Linux (LVM) > > - affected class : LVM_PVExtent > Each instance of the class LVM_PVExtent represents one > physical extent in the Linux Logical Volume Manager (LVM) . > > - provider code : > > * com/ibm/wbem/linux/device/LVM_PVExtent.java : > calling the NPI - uninteresting in the problem > environment > > * LVM_PVExtent.c : > > 1 step : enumeration of all physical volumes > -> 6 physical volumes > > 2 step : for each instance of the physical volume > all physical extents are collected in a list > -> ~ 4000 = sum of all physical extents > ! this happens in functions of the tool > library CimFsVMgmt.c whithout any problems ! > > 3 step : for each entry in the list of physical > extents one instance of LVM_PVExtent is > created ... no - should be created > > This enumeration of all instances of the class LVM_PVExtent > brings on the problem how to handle this mass operation > and avoid crashes . > > Now one discussion point can be why it seems to be > necessary to do such a "maybe useless" operation . It is, > from a systems management application view, really necessary > to get all the physical extents of one system to have a look > in the way they are connected to their corresponding logical > extents and the logical volume ? What might be a case where > this granularity becomes important ( Standard value fo a > physical extent is 4096 kB !!! ) . > Or shall there be other ways to offer detailed informations . > > An other discussion point can be, how to solve such problems > whithout avoiding enumerations with a mass result . I' sure > that there are other environments where it is not possible > to strike out operations that have a mass result . > > Now follow some possible solutions as discussion basics . > > POSSIBLE SOLUTIONS > > * increase the memory allocation size for the Java Virtual > Machine ??? > > * take this granularity out of the schema > ( delete LVM_PVExtent ) ??? > > * more suggestions ??? > > Thanks for your attention ... Heidi > > Mfg / Regards > > Heidi Neumann > > IBM Laboratory Boeblingen - Germany - Dept. 3243 > LTC - - Linux Technology Center -- 7UFA > Systems Management > > Phone : ++49 (0) 7031 / 16 - 3193 > Schönaicher Str. 220, 71032 Böblingen > > hei...@de... > --- try sametime to contact me --- > > http://w3.opensource.ibm.com/projects/ibmcimom/ > http://oss.software.ibm.com/developerworks/projects/sblim/ > > _______________________________________________ > Ibmcimom-devel mailing list > Ibm...@op... > http://w3.opensource.ibm.com/mailman/listinfo/ibmcimom-devel -- Kind Regards / Mit freundlichen Grüßen Viktor Mihajlovski Linux Technology Center IBM Laboratory Böblingen, Germany Phone +49-7031-16-2560 Email mih...@de... |
|
From: Heidi N. <HEI...@de...> - 2001-07-18 16:31:18
|
Hi ,
the goal of this mail is to start a discussion about how
to handle mass operations . It is not always the best
solution to avoid them .
At the moment I'm running in such a mass problem with
the instrumentation of "Filesystems & Volume Management"
and I'm not sure how to solve the forced crashes .
PROBLEM DESCRIPTION
- affected module : sblim-fsvol-0.6.1 ( tar.gz )
FSVOL_0_6_1 ( CVS tag )
- affected part : the instrumentation of the Logical
Volume Manager for Linux (LVM)
- affected class : LVM_PVExtent
Each instance of the class LVM_PVExtent represents one
physical extent in the Linux Logical Volume Manager (LVM) .
- provider code :
* com/ibm/wbem/linux/device/LVM_PVExtent.java :
calling the NPI - uninteresting in the problem
environment
* LVM_PVExtent.c :
1 step : enumeration of all physical volumes
-> 6 physical volumes
2 step : for each instance of the physical volume
all physical extents are collected in a list
-> ~ 4000 = sum of all physical extents
! this happens in functions of the tool
library CimFsVMgmt.c whithout any problems !
3 step : for each entry in the list of physical
extents one instance of LVM_PVExtent is
created ... no - should be created
This enumeration of all instances of the class LVM_PVExtent
brings on the problem how to handle this mass operation
and avoid crashes .
Now one discussion point can be why it seems to be
necessary to do such a "maybe useless" operation . It is,
from a systems management application view, really necessary
to get all the physical extents of one system to have a look
in the way they are connected to their corresponding logical
extents and the logical volume ? What might be a case where
this granularity becomes important ( Standard value fo a
physical extent is 4096 kB !!! ) .
Or shall there be other ways to offer detailed informations .
An other discussion point can be, how to solve such problems
whithout avoiding enumerations with a mass result . I' sure
that there are other environments where it is not possible
to strike out operations that have a mass result .
Now follow some possible solutions as discussion basics .
POSSIBLE SOLUTIONS
* increase the memory allocation size for the Java Virtual
Machine ???
* take this granularity out of the schema
( delete LVM_PVExtent ) ???
* more suggestions ???
Thanks for your attention ... Heidi
Mfg / Regards
Heidi Neumann
IBM Laboratory Boeblingen - Germany - Dept. 3243
LTC - - Linux Technology Center -- 7UFA
Systems Management
Phone : ++49 (0) 7031 / 16 - 3193
Schönaicher Str. 220, 71032 Böblingen
hei...@de...
--- try sametime to contact me ---
http://w3.opensource.ibm.com/projects/ibmcimom/
http://oss.software.ibm.com/developerworks/projects/sblim/
|
|
From: Heidi N. <HEI...@de...> - 2001-07-13 15:04:20
|
Hi , the goal of the module "Filesystem & Volume Management" (short FSVOL) Instrumentation is to offer system informations concerning filesystems, volumes, the organization of volumes in partitions and disks managed by the "Logial Volume Manager" (LVM) for Linux (see http://www.sistina.com) . The documentation for the module FSVOL can be visited under : http://oss.software.ibm.com/developerworks/opensource/sblim/fsvol.html If you are interessted in the schmemata for the module FSVOL see chapter 3 in the documentation . Basis of the schema is the CIM Schema (see Common Information Model on http://www.dmtf.org) . ______________________________________________________________________ To visit the module and have a look into its structure go to http://oss.software.ibm.com/developerworks/opensource/cvs/sblim/fsvol/ To download the module FSVOL you can choose between the tar.gz file from http://oss.software.ibm.com/developerworks/project/showfiles.php?group_id=69 or CVS. For informations hot to setup your system for CVS read http://oss.software.ibm.com/developerworks/cvs/os-cvs.php?group_id=69 and use cvs checkout fsvol to get this module . ______________________________________________________________________ VERSION sblim-fsvol-0.5 The version 0.5 consists of all providers necessary for the instrumentation of a "native" Linux . Native means that the filesystems are hosted direct on the partitions of a disk . The instrumented classes and associations are : - Linux_UnitaryComputerSystem - Linux_HostedFileSystem (association) - Linux_LocalFileSystem - Linux_ResidesOnExtent (association) - Linux_LogicalDisk - Linux_LogicalDiskBasedOnVolume (association) - Linux_StorageVolume VERSION sblim-fsvol-0.6 The version 0.6 consists of the providers of 0.5 and includes the first providers for LVM instrumentation . The instrumented classes and associations for LVM are : - LVM_ResidesOnExtent (association) - LVM_VolumeGroup - LVM_LogicalVolumenVolumeGroup (association) - LVM_LogicalVolume - LVM_PhysicalVolume Thanks ... Heidi Mfg / Regards Heidi Neumann IBM Laboratory Boeblingen - Germany - Dept. 3243 LTC - - Linux Technology Center -- 7UFA Systems Management Phone : ++49 (0) 7031 / 16 - 3193 Schönaicher Str. 220, 71032 Böblingen hei...@de... http://oss.software.ibm.com/developerworks/projects/sblim/ |
75 messages has been excluded from this view by a project administrator.
