openlmi-devel August 2013

openlmi-devel@lists.fedorahosted.org

13 participants
47 discussions

[RFC] New provider registration process
by Tomáš Smetana 23 Oct '13

23 Oct '13

Hello, I'm now trying to figure out how to improve the provider registration process to make things at least look less fragile from the user's perspective. We're still facing problems with the providers and CIMOMs installation: the openlmi-* provider packages depend on a virtual require (cim-server) and it's beyond our control which package is installed by yum to satisfy the dependency (sblim-sfcb currently IIRC). If this is not what the user wants or the user decides to switch the CIMOM, install another one etc., then the providers have to be re-registered again manually which is not an easy task since the order of the mofs/regs is not saved anywhere and each CIMOM (and even CIMOMs version) requires special procedure. My plan is to store the registrations in a special CIMOM-independent database which would enable the user to re-do the registrations at any time. Most notably we should be able to re-register whatever provider is installed on the system from the CIMOMs package post-install scriptlets. The new script should offer three actions: register, unregister and reregister. Registration and unregistration will require the same arguments as the current script. I'm pretty sure there are many details and combinations that can't be handled reasonably well. However here's some idea dump on how I suppose things might work: ============================================================================= Registration The user specifies one or more MOF files zero or one REG file. Optionally will request the CIMOM to register for, namespace and version of the provider for the REG file. If the CIMOM was not explicitly requested register for all the known CIMOMs in the database and for all the CIMOMs installed/found. Registration should handle the update transparently. The files, version string, CIMOM and namespace form the "registration object" which is what we need to be able to re-assemble during re-registration. 1 if (none of the MOFs/REG in the database yet) { 2 registration = create new registration (id + timestamp) 3 } else if (the known MOFs/REG belong to the same registration) { 4 registration = the one the MOFs/REG belong to 5 if (requested CIMOMs != CIMOMs of the existing registration) 6 exit with error: upgrade must be valid for all the previous 7 registrations 8 } else { 9 exit with error: only one registration can be replaced 10 } 11 unregister the previous registration from CIMOM(s) 12 if (error) { 13 exit 14 } 15 remove the old files backups 16 copy the new MOFs/REG to the backup location 17 update/insert database records (don't overwrite existing registration timestamps) ============================================================================= Unregistration Nothing fancy happens here: We only have to be careful to keep the registration data consistent and allow to unregister the same and complete set of classes that has been registered previously. 1 for every selected CIMOM: 2 if (MOFs/REG not in the same registration || unknown) { 3 exit with error 4 unregister in the CIMOM 5 } 6 delete the database records (MOFs/REG, registration) 7 delete the backup files ============================================================================= Re-registration: Should be simple: just reconstruct the command line from the database. The ordering of the registration is determined by the timestamp of their initial registration (updates don't change the timestamp). 1 for every selected CIMOM { 2 get MOFs/REG/namespaces/version in the reverse timestamp order 3 re-run the CIMOM registration (using backup MOF/REG files) 4 } I'm not quite sure how clear I made myself with the ideas and I assume many problems get spotted in the real world testing. However if you have some ideas or corrections... I'm all ear. Thanks and regards, -- Tomáš Smetana Platform Engineering, Red Hat

3 4

ANNOUNCE: KonkretCMPI 0.9.0 released
by Radek Novacek 15 Oct '13

15 Oct '13

Disclaimer: I know this is OpenLMI mailing list, but I will post announcements about new versions of KonkretCMPI here, because many of OpenLMI providers use it. Since KonkretCMPI upstream [1] is dead for long time (last upstream version 0.8.7 was released 2008-10-22) I've decided to continue development myself. I don't have access to original SCM repository or web page, so I've created git repo at github [2]. Highlights of version 0.9.0: * Use CMake as buildsystem (added FindCMPI.cmake and FindKonkretCMPI.cmake modules) * Python bindings for the MOF parser * Fixed using experimental schema * Assertion crash fixed * Add missing headers * Many other minor bugs fixed You can download the new version from github [3]. It is already in Fedora rawhide and it's coming to Fedora 18 soon. Radek Novacek [1] http://konkretcmpi.org/ [2] https://github.com/rnovacek/konkretcmpi [3] https://github.com/rnovacek/konkretcmpi/archive/0.9.0/konkretcmpi-0.9.0.tar…

2 1

openlmi-reviews Digest, Vol 4, Issue 26
by openlmi-reviews-request＠lists.fedorahosted.org 31 Aug '13

31 Aug '13

1 0

openlmi-reviews Digest, Vol 4, Issue 25
by openlmi-reviews-request＠lists.fedorahosted.org 30 Aug '13

30 Aug '13

Send openlmi-reviews mailing list submissions to openlmi-reviews(a)lists.fedorahosted.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews or, via email, send a message with subject or body 'help' to openlmi-reviews-request(a)lists.fedorahosted.org You can reach the person managing the list at openlmi-reviews-owner(a)lists.fedorahosted.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openlmi-reviews digest..." Today's Topics: 1. Re: Review Request 771: storage: Update logging documentation with recent changes. (Jan Safranek) 2. Re: Review Request 772: storage: Rework documentation generator to two steps. (Jan Safranek) 3. Re: Review Request 773: Ship documentation in openlmi-doc.rpm. (Jan Safranek) 4. Re: Review Request 774: storage: Bump release. (Jan Safranek) 5. Review Request 780: storage: Update logging documentation with recent changes. (Jan Safranek) 6. Review Request 781: storage: Rework documentation generator to two steps. (Jan Safranek) 7. Review Request 783: Added documentation page about how to identify a block device and volume group. (Jan Safranek) 8. Review Request 784: Added InstanceID to CIM_StorageExtent. (Jan Safranek) 9. Review Request 785: Added Name property to LMI_VGStoragePool. (Jan Safranek) 10. Review Request 782: Ship documentation in openlmi-doc.rpm. (Jan Safranek) 11. Review Request 786: storage: Bump release. (Jan Safranek) 12. Review Request 787: Fixed lvm-instance.uml figure. (Jan Safranek) 13. Re: Review Request 781: storage: Rework documentation generator to two steps. (Radek Novacek) 14. Re: Review Request 780: storage: Update logging documentation with recent changes. (Radek Novacek) 15. Re: Review Request 783: Added documentation page about how to identify a block device and volume group. (Radek Novacek) 16. Re: Review Request 784: Added InstanceID to CIM_StorageExtent. (Radek Novacek) 17. Re: Review Request 786: storage: Bump release. (Radek Novacek) 18. Re: Review Request 785: Added Name property to LMI_VGStoragePool. (Radek Novacek) 19. Re: Review Request 782: Ship documentation in openlmi-doc.rpm. (Radek Novacek) 20. Review Request 788: Hardware: Fixed Coverity findings (Peter Schiffer) 21. Re: Review Request 787: Fixed lvm-instance.uml figure. (Michal Minar) 22. Re: Review Request 787: Fixed lvm-instance.uml figure. (Radek Novacek) 23. Re: Review Request 788: Hardware: Fixed Coverity findings (Radek Novacek) 24. Re: Review Request 786: storage: Bump release. (Jan Safranek) 25. Re: Review Request 786: storage: Bump release. (Radek Novacek) 26. Re: Review Request 781: storage: Rework documentation generator to two steps. (Michal Minar) 27. Re: Review Request 788: Hardware: Fixed Coverity findings (Peter Schiffer) 28. Review Request 789: openlmi-providers [1/1] Add cim-schema as dependency to README (Radek Novacek) 29. Re: Review Request 789: openlmi-providers [1/1] Add cim-schema as dependency to README (Michal Minar) 30. Re: Review Request 789: openlmi-providers [1/1] Add cim-schema as dependency to README (Radek Novacek) 31. Re: Review Request 780: storage: Update logging documentation with recent changes. (Jan Safranek) 32. Re: Review Request 781: storage: Rework documentation generator to two steps. (Jan Safranek) 33. Re: Review Request 782: Ship documentation in openlmi-doc.rpm. (Jan Safranek) 34. Re: Review Request 783: Added documentation page about how to identify a block device and volume group. (Jan Safranek) 35. Re: Review Request 784: Added InstanceID to CIM_StorageExtent. (Jan Safranek) 36. Re: Review Request 785: Added Name property to LMI_VGStoragePool. (Jan Safranek) 37. Re: Review Request 786: storage: Bump release. (Jan Safranek) 38. Re: Review Request 787: Fixed lvm-instance.uml figure. (Jan Safranek) 39. Re: Review Request 583: [2/2] Add LUKS version 1. (Jan Synacek) 40. Re: Review Request 583: [2/2] Add LUKS version 1. (Jan Safranek) 41. Review Request 776: [RFC, Repost] New registration script with a separate registration database (Tomas Smetana) 42. Re: Review Request 776: [RFC, Repost] New registration script with a separate registration database (Radek Novacek) 43. Review Request 790: Delete user [1/2] Account: Don't delete home dir if user is not owner (Roman Rakus) 44. Review Request 791: Delete user [2/2] Account: New delete method (Roman Rakus) 45. Re: Review Request 791: Delete user [2/2] Account: New delete method (Roman Rakus) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

1 0

ANNOUNCE: openlmi-storage 0.6.0
by Jan Safranek 29 Aug '13

29 Aug '13

There is a new release of OpenLMI-Storage available. New in this version: * Updated logging to use the same infrastructure and options as OpenLMI-Software provider. Note that /etc/openlmi/storage /storage.conf format changed a bit. * Added LMI_VGStoragePool.Name and LMI_StorageExtent.InstanceID properties. This applies also to all LMI classes inherited from CIM_StorageExtent. (This is the reason the minor version is bumped) * Fixed some of bugs and improved test coverage and documentation. * Full documentation sources are shipped in the tarball, only Sphinx is required to generate it. Enjoy! Jan Safranek

1 0

[PATCH] Backslash missing from openlmi-software preinstall script
by Klaus Kaempf 29 Aug '13

29 Aug '13

This one should be obvious ;-) --- openlmi-providers.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openlmi-providers.spec b/openlmi-providers.spec index 502f42a..1558895 100644 --- a/openlmi-providers.spec +++ b/openlmi-providers.spec @@ -501,7 +501,7 @@ if [ "$1" -gt 1 ]; then %{_datadir}/%{name}/90_LMI_Software_Profile.mof || :; %{_bindir}/openlmi-mof-register --just-mofs -c tog-pegasus unregister \ %{_datadir}/%{name}/60_LMI_Software_MethodParameters.mof || :; - %{_bindir}/openlmi-mof-register -v %{version} unregister + %{_bindir}/openlmi-mof-register -v %{version} unregister \ %{_datadir}/%{name}/60_LMI_Software.mof \ %{_datadir}/%{name}/LMI_Software.reg || :; fi >> %logfile 2>&1 -- 1.8.1.4 -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany

2 1

openlmi-reviews Digest, Vol 4, Issue 24
by openlmi-reviews-request＠lists.fedorahosted.org 29 Aug '13

29 Aug '13

1 0

openlmi-reviews Digest, Vol 4, Issue 23
by openlmi-reviews-request＠lists.fedorahosted.org 28 Aug '13

28 Aug '13

1 0

ANNOUNCE: openlmi-providers 0.2.0
by Michal Minář 28 Aug '13

28 Aug '13

There is a new release of openlmi-providers available. There was a change in API of software, resulting in increment of minor version number. News in this version: * Account * added documentation * Python * renamed python eggs from *lmi* to *openlmi* * improved compability for other openlmi python project installed to user path * logging improvements (API change) * Software * added FindIdentity() method to LMI_SoftwareInstallationService * lot of bugfixes * improved tests and utilities Enjoy! Michal Minar

1 0

Continuous Integration results
by Radek Novacek 27 Aug '13

27 Aug '13

Hi all, BuildBot instance is up and running for some time now [1]. There is a couple of issues I would like to discuss here: 1) The tests are fragile When some test fails to clean after itself it might affect other test or the next run of the test. We want to make sure that we make the tests as solid as possible but there will always be troubles (like issues in provider backends - blivet, NetworkManager). I'm working on improving this - I'm going to remove all openlmi-* packages, CIMOM and any other leftovers (like CIMOM repository in /var) before (or rather after?) the test. 2) Results are not visible enough There is IRC bot on #openlmi channel of freenode notifying when test status changes (it used to fail and now it succeeds and vice versa). But it not visible enough. Also we don't want to send email to this list because it will be quite a lot of traffic. So, should I create another mailing list? openlmi- build? openlmi-ci? 3) Building machines updates Now the test machines are updated manually but this should be probably automated too. But we need to know whether the build/test fails because of change in providers or system update. So the workflow should probably be like: * Build our packages and run the test suite * Update the system * Build and test our packages again to see if the result is the same * Report it Does it make sense? Any better ideas? Tips and suggestions how to deal with these issues are welcomed. Radek Novacek [1] http://openlmi-rnovacek.rhcloud.com/waterfall

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

openlmi-devel August 2013