Review Request 837: journald: Add support for iterators
by Stephen Gallagher
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-openlmi.rhcloud.com/r/837/
-----------------------------------------------------------
Review request for OpenLMI Developers.
Repository: openlmi-providers
Description
-------
journald: Add support for iterators
This implements CIM_MessageLog iterator functionality according to
the model. The only limitation, or, let's say shortcoming, is a
free-form output data format from the GetRecord call. Currently we
feed the uint8 array with UTF-8 chars and it's up to the client to
deal with it (as suggested in the model). This may be subject to
change.
Many methods are returning modified iterator that has been passed
in and that allows having persistent iterators. As long as CIMOMs
may destroy the instances and unload providers on inactivity, any
particular delay would cause loss of the iterator. The iterator
string contains journal cursor string, uniquely identifying a
record. When this part of the iterator string is valid, the
provider is able to reopen journal and seek to that position,
allowing seamless continuation of the itearation process. If the
cursor points to non-existing record, an error is returned. This
typically happens when journal is rotated or the cursor is very
old.
The provider keeps track of active iterators during its lifetime,
keeping the journal open for fast access. Clients are supposed to
close the iterator by calling the CancelIteration method.
--
some TODOs will be addressed in future patches
tests will be published soon
Diffs
-----
src/journald/LMI_JournalMessageLogProvider.c PRE-CREATION
src/journald/instutil.h PRE-CREATION
src/journald/instutil.c PRE-CREATION
Diff: http://reviewboard-openlmi.rhcloud.com/r/837/diff/
Testing
-------
Thanks,
Tomáš Bžatek
10 years, 6 months
Review Request 723: Rewrite the registration script in preparation for further improvements
by Stephen Gallagher
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-openlmi.rhcloud.com/r/723/
-----------------------------------------------------------
Review request for OpenLMI Developers.
Repository: openlmi-providers
Description
-------
Here's a new registration script. It's a merge of the existing openlmi-mof-register and openlmi-register pegasus and should work as drop-in replacement for the openlmi-mof-register. The only slight difference is that the Pegasus interop namespace is not hard coded into the Pegasus registration calls but now there's an attempt to detect the right one. And the whole thing is now written in (sort of) Python.
This is only the first step in the registration rewrite: Python should make it easier for manipulating a "side database" that would keep the registration data independently of the CIMOMs and eventually allow for re-registration when a new CIMOM is installed or upgraded. This will also make possible for the providers package not to depend on a CIMOM. I will prepare some design sketches of the registration process I envision to gather feedback and ideas: doing this correctly and robustly enough is going to be rather difficult.
Diffs
-----
openlmi-mof-register.py PRE-CREATION
Diff: http://reviewboard-openlmi.rhcloud.com/r/723/diff/
Testing
-------
Thanks,
Tomas Smetana
10 years, 6 months
Review Request 899: Release 0.3.0
by Stephen Gallagher
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-openlmi.rhcloud.com/r/899/
-----------------------------------------------------------
Review request for OpenLMI Developers.
Repository: openlmi-providers
Description
-------
Release 0.3.0
Diffs
-----
mof/30_LMI_Jobs.mof 1de87b8991afee6b4c65494315052e344a78122c
mof/60_LMI_Account.mof a4cfdda4b92533573296ccfb9abee9cfe6c4c9df
mof/60_LMI_Fan.mof 9a6e5d9dd96037ff043870125cbac96ba6c4d5c4
mof/60_LMI_Hardware.mof 74e1ee5afc422506ca6769d025bfa4a4dedbd9f3
mof/60_LMI_LogicalFile.mof dd693d12f2feec1c0db53e264b6ecc97863b6513
mof/60_LMI_PowerManagement.mof b1991d2a1f672a5a2ebc6fa9a8bac7bf82d8eca8
mof/60_LMI_Realmd.mof 0817d4f98a307b1470a838d254609230a90eac9e
mof/60_LMI_Service.mof 1a86fec8462402d5f5b5ff4f2661596dca470433
mof/60_LMI_Software.mof 46290946602f6fc080b41aee5338da91f361d753
mof/60_LMI_Software_MethodParameters.mof 51d8d58921f9ecd991729f4a2f7fc87396f58583
openlmi-providers.spec e3f1e68c20cae517ad95d99c4df59ef7a492db5f
Diff: http://reviewboard-openlmi.rhcloud.com/r/899/diff/
Testing
-------
Thanks,
Roman Rakus
10 years, 6 months