January 2014 - openlmi-devel - Fedora Mailing-Lists

TOG-Pegasus client library and X509 verification

by Peter Hatina

Hi, when using TOG-Pegasus client library and trying to connect to cimserver via SSL, I came across this issue: TOG-Pegasus does *not* verify server's certificate in terms of matching subject's Common Name, subject's Alternative Names (if x509v3 used). To be able to properly verify, who we are talking to, I made some changes to mentioned client's library [1]: 1. user is able to pass his own data via void-pointer 2. user is able to get Subject's Common Name in verification callback 3. user is able to get Subject's Alternative Names (if x509v3 used) For a simple example, see [1]. I could not find reasonable way, how to implement a default verification callback in the library (as pywbem does). Feel free to comment. [1] http://bugzilla.openpegasus.org/show_bug.cgi?id=9848 -- Peter Hatina ENG Server Experience, System Management Red Hat Czech, Brno

10 years, 3 months

1
0
0 / 0

openlmi-reviews Digest, Vol 9, Issue 15

by openlmi-reviews-request＠lists.fedorahosted.org

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 1453: Hardware: added LMI_DiskDriveATAPortProvider (Jan Synacek) 2. Re: Review Request 1452: account: Use lckpwdf() to protect passwd files (=?utf-8?b?VG9tw6HFoSBCxb5hdGVr?=) 3. Re: Review Request 1453: Hardware: added LMI_DiskDriveATAPortProvider (Peter Schiffer) 4. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 5. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 6. Review Request 1454: [1/1] service: wait for finish of systemd method call and return proper result (Vitezslav Crhonek) 7. Re: Review Request 1454: [1/1] service: wait for finish of systemd method call and return proper result (scanbot) 8. Review Request 1455: Hardware: added LMI_DiskDriveDeviceSAPImplementationProvider (Peter Schiffer) 9. Re: Review Request 1455: Hardware: added LMI_DiskDriveDeviceSAPImplementationProvider (scanbot) 10. Re: Review Request 1455: Hardware: added LMI_DiskDriveDeviceSAPImplementationProvider (scanbot) 11. Re: Review Request 1454: [1/1] service: wait for finish of systemd method call and return proper result (scanbot) 12. Re: Review Request 1453: Hardware: added LMI_DiskDriveATAPortProvider (scanbot) 13. buildbot failure in OpenLMI on storage-rawhide (openlmiproject(a)gmail.com) 14. buildbot failure in OpenLMI on storage-rhel7 (openlmiproject(a)gmail.com) 15. Review Request 1457: spec: dbus-devel is named dbus-1-devel in SUSE (=?utf-8?q?Klaus_K=C3=A4mpf?=) 16. Review Request 1460: Use %%cmake in comment (=?utf-8?q?Klaus_K=C3=A4mpf?=) 17. Re: Review Request 1455: Hardware: added LMI_DiskDriveDeviceSAPImplementationProvider (Jan Synacek) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

10 years, 3 months

1
0
0 / 0

openlmi-reviews Digest, Vol 9, Issue 14

by openlmi-reviews-request＠lists.fedorahosted.org

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 1418: tools [1/6] added lmi.scripts namespace package (Michal Minar) 2. Re: Review Request 1425: tools [2/6] merged documentations of shell and meta-command (Michal Minar) 3. Re: Review Request 1421: tools [4/6] added jewerly belonging to lmi meta-command (Michal Minar) 4. Re: Review Request 1422: tools [5/6] updated AUTHORS and README (Michal Minar) 5. Re: Review Request 1423: tools [6/6] updated setup script with lmi meta-command modules (Michal Minar) 6. Review Request 1453: Hardware: added LMI_DiskDriveATAPortProvider (Peter Schiffer) 7. Re: Review Request 1453: Hardware: added LMI_DiskDriveATAPortProvider (scanbot) 8. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 9. buildbot success in OpenLMI on networking-rhel7 (openlmiproject(a)gmail.com) 10. buildbot failure in OpenLMI on storage-rhel7 (openlmiproject(a)gmail.com) 11. buildbot failure in OpenLMI on storage-rawhide (openlmiproject(a)gmail.com) 12. Re: Review Request 1453: Hardware: added LMI_DiskDriveATAPortProvider (Jan Synacek) 13. Re: Review Request 1451: providers [1/1] spec: Remove openlmi-pcp post script (Jan Synacek) 14. Re: Review Request 1451: providers [1/1] spec: Remove openlmi-pcp post script (Radek Novacek) 15. Re: Review Request 1451: providers [1/1] spec: Remove openlmi-pcp post script (Radek Novacek) 16. Re: Review Request 1453: Hardware: added LMI_DiskDriveATAPortProvider (Peter Schiffer) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

10 years, 3 months

1
0
0 / 0

Fwd: Re: Inter-WG coordination: Stable application runtimes

by Stephen Gallagher

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I figured I should forward on this thread from the Fedora-devel mailing list, as a community member raises some interesting ideas for the OpenLMI project here. I'm not sure I understand it well enough yet to say if this is a good fit, but it's worth sharing with the wider OpenLMI community at least. Please continue discussion in this thread on devel(a)lists.fedoraproject.org, since that's where it started. - -------- Original Message -------- Subject: Re: Inter-WG coordination: Stable application runtimes Date: Sun, 12 Jan 2014 22:34:19 +0200 From: Alek Paunov <alex(a)declera.com> Reply-To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org> To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org> On 10.01.2014 21:12, Matthew Miller wrote: > On Thu, Jan 09, 2014 at 07:58:44PM -0800, Adam Williamson wrote: >> So the question becomes, what is it appropriate for a >> distribution to do in this situation? My personal opinion is that >> what's appropriate for a distribution to do is also, happily, >> what's easiest for a distribution to do: punt on it. Entirely >> punt on the whole thing. > > > And, this ultimately makes a better experience for users, because > if Fedora's included tools are aware of the native packaging > system, we can do things like system auditing, security alerts (if > not updates), maybe even integration with selinux policy. > Basically, we don't hammer all of the possible universe into the > distribution model, and we don't include all of the packages of > everything in the base Fedora distribution as RPMs, but we do > include those ecosystems in the Fedora _Project_, including the > tools and documentation to make them feel natural. > Your expression " ... tools aware of the native packaging system" and the Andrew comment about the pip behaviors above in the thread, encouraged me to share my "big hammer of the DB plumber style" :-) opinion on the problem. TL;DR: What follows is SCC: An idea for optional DB and service which caches bits from YumDB, the local state (RPMDB and /etc) plus the "native" systems like NPM in the unified way for the purposes of planning, resolving and performing system state transitions. Initially I meant to say just few words to mark the possibility, but obviously my English and talent for easy for reading and well focused messages are both far from good, so the whole thing become too long and I am going to split some additional notes into self replays - Excuses! RPMDB and YumDB are two rich datasets present on every Fedora instance representing respectively the local state and distribution+ state of the package universe. '+' because +Fusion*, +COPRs, +LocalOrg, etc. Unfortunately they are somewhat hidden in the dark, because lack of interfaces - we even missing SVG or other explorer for the YumDB graph. The (let think of them as "virtual") Maven DB, PyPI DB, NPM DB, LuaRocks DB, etc, technically are subsets of YumDB (in sense richness of encoded logical relations between the DB nodes used in their schemes - e.g. PyPI DB, before the pip egg, do not knows which file from which module comes, nor have the concept of higher than package NV granularity of the requirement points - Provides and Requires in YumDB). Also, the depsolving of the "native" packaging systems is less sophisticated than both current yum and hawkey ones. These observation naturally lead to the idea of SCC: System Configuration Cache DB representing the merge of RPMDB, YumDB and e.g. local pip egs, PyPI DB (if e.g. additional python modules/versions are needed for the given deployment) where the depsolving could be shifted, somewhat in the same fashion as Data warehouse solutions are used in the enterprises for merging the significant datasets from various ERP systems into single DB for interactive time reporting and decision making. I am using the term SCC (vs. e.g. UPMC: Unified Package Metadata Cache) in attempt to cover a (paraphrased) Mirek question from the beginning of the thread - "OK, we have Fedora and PyPI integrated, at one point of the time for a given instance, the Fedora packaged module has been chosen. What happens if we upgrade Fedora along with am incompatible version this Python module for given installed service" - obviously we need to register in the SCC the dependencies of the installed machine roles with the same effect like Require clauses in the our packages, so the SCC machinery to validate (with negative result in this described case) the yum upgrade or to resolve the upgrade including installation of newest available compatible version from PyPI as an alternative provision during upgrade preparation. Further, I think that ideally SCC should parse/absorb as much as possible system object properties and relations from /etc (plus /lib and /var configuration areas) to allow sysadmins and devops to inject rules for effective use of these sets latter in the depsolving (and other DB functionality). That said, the integration with OpenLMI, or even implementing the whole thing under the OpenLMI umbrella, both seems natural. So, finally on that road we have: - - choice for good enough DB engine for SCC, query language, compiler [*], etc. design decisions like sync protocol and plugable data sources. - - Yum/RPM datasets: optional rpm, yum, hawkey hooks for syncing their DBs, alternatively just sync tools. - - optional pip, npm, luarocks, etc. hooks for the same, alternatively just sync tools. - - OpenLMI integration for absorbing system configuration, alternatively just Augeas import + transformation rules to sync the DB representation of the system objects. - - sccd capable to: - depsolving (on top of cumulative - YumDB + native managers DBs, preferably providing interfaces to the system libsolv for using SCC DB in place of the libsolv own filestores. - invoke package operations with yum/dnf + "native" managers - provides sysadmins, developers and devops with the capability of defining system overlays - services/applications trees and their relations with the rest of the DB. - supports live textual views (e.g. trough FUSEs) for cases when local preferred deployment style is ansible, salt, etc. based. As alternative/complementing the own daemon approach the above above functionality might be implemented in the form of OpenLMI providers (or existing provider extensions). - - sccd-web: WebUI exposing full functionality, alternatively Cockpit (OpenLMI WebUI) extension. - - scc [**] command line shortcut for few simple tasks. - - providing pip, luarocks, etc patches for sccd integration if present, alternatively "native" managers command lines/api implementations on top of sccd; providing yum and hawkey plugins for "native" packages conflicts handling - - NTH: remote SCC DB for the instance, - - NTH: SCC local state for multiple instances (e.g. deployment nodes or local containers) kept in the same SCC DB - - NTH: SCC local state inheritance between instances Kind Regards, Alek [*] Crucial aspect of any sophisticated data management system is the data query and manipulation language. Unfortunately the choices are rather limited - Imperative approaches (recently resurrected by some NoSQL DBs) are weak and error prone; SQL and few more "text prose" languages have proven their incompatibility with the vast majority of the developers (these without years of specific experience around the data volumes processing). The predominant workaround seems to be ORMs, but ORMs and "sophisticated/fast" should not be mixed in same project :-). [**] scc resolve python module hgsubversion output: Found 2 resolutions, Transaction IDs: 1921, 1922 output: Recommended: http://scc-geteway/machine-id/transaction/1921 user: browsing, thinking ... (hgsubversion comes from PyPI), but happily spotting that subvertpy dependency is satisfied by fedora provided package - it is linked with the system subversion. scc transaction 1921 add resolve luajit 2.0 module zmq min-version 0.3.3 output: Found 17 resolutions, Transaction IDs: 1921, 1924, ... output: Recommended: http://scc-geteway/machine-id/transaction/1921 user: browsing, ... lua zmq will use the system zmq library, which is the in the desired version range - OK scc transaction 1921 apply etc ... - -- devel mailing list devel(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLT7OcACgkQeiVVYja6o6MSGgCbBtNte28dl0FQzCJthPhVbMzO 84AAnj9NySBB748gRJrMGtJ81ivB/pfa =+z/y -----END PGP SIGNATURE-----

10 years, 3 months

1
0
0 / 0

the future of software provider

by Michal Minář

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello dear OpenLMI followers. I'd like to know your opinion on migrating LMI Software Provider to PackageKit. In particular what priority does it have? All the pros and cons are listed in upstream ticket: https://fedorahosted.org/openlmi/ticket/199 Certainly this migration is desired. What I'd like to know is whether this shall take precedence over other feature requests targeted for OpenLMI 1.1.0. If not, yum implementation would get some enhancements, but rewrite would be delayed thanks to them, and it would take more time to complete it. Main features to be implented in software provider: * listing updates * listing package dependencies * support for mass update I'm in favor of making the rewrite the highest priority. What do you think? Best regards, Michal Minar -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS09RGAAoJEPezUylxRFUDHxUIAIOTK77dioYhD3K/5r040dGu AmXPIDapFe07mvYlLFpKL8L7Pq9Z0a1qXC2aoHa9/fTYcCzU6YMYl2TUC915NoG5 651uavqdPl8U9zjwPaMstz+lF5UwNgcTq8dK4V70YEoe5qYf1dzMO/B+gi1zyHu3 0m9B74qUAoT8oKObUXAMvmkF2d335Y6mn0Ry7iRzrUZtVCr5ccyyafYiFIA/l5Qa MfKhTfuh+YgIYIASl7FfzSjrzelpYClk2vvxUSLx4DBWp2yblEAlLQig5EOQdqBu QmYW0jJSQrv4Vo1xRB5t4QX0IFeL3JEoAq4DsBwxLR9x8rwDreAI5ibJsLVGaQM= =+HZy -----END PGP SIGNATURE-----

10 years, 3 months

2
1
0 / 0

openlmi-reviews Digest, Vol 9, Issue 13

by openlmi-reviews-request＠lists.fedorahosted.org

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. buildbot failure in OpenLMI on storage-rawhide (openlmiproject(a)gmail.com) 2. buildbot failure in OpenLMI on storage-rhel7 (openlmiproject(a)gmail.com) 3. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 4. buildbot failure in OpenLMI on networking-rhel7 (openlmiproject(a)gmail.com) 5. Re: Review Request 1452: account: Use lckpwdf() to protect passwd files (Jan Synacek) 6. Re: Review Request 1425: tools [2/6] merged documentations of shell and meta-command (Peter Hatina) 7. Re: Review Request 1418: tools [1/6] added lmi.scripts namespace package (Peter Hatina) 8. Re: Review Request 1421: tools [4/6] added jewerly belonging to lmi meta-command (Peter Hatina) 9. Re: Review Request 1422: tools [5/6] updated AUTHORS and README (Peter Hatina) 10. Re: Review Request 1423: tools [6/6] updated setup script with lmi meta-command modules (Peter Hatina) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

10 years, 3 months

1
0
0 / 0

openlmi-reviews Digest, Vol 9, Issue 12

by openlmi-reviews-request＠lists.fedorahosted.org

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. buildbot failure in OpenLMI on providers-rawhide (openlmiproject(a)gmail.com) 2. buildbot failure in OpenLMI on storage-rawhide (openlmiproject(a)gmail.com) 3. buildbot success in OpenLMI on networking-rawhide (openlmiproject(a)gmail.com) 4. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 5. buildbot failure in OpenLMI on storage-rhel7 (openlmiproject(a)gmail.com) 6. buildbot failure in OpenLMI on networking-rhel7 (openlmiproject(a)gmail.com) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

10 years, 3 months

1
0
0 / 0

openlmi-reviews Digest, Vol 9, Issue 11

by openlmi-reviews-request＠lists.fedorahosted.org

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 1441: Hardware: added SAPAvailableForElementProvider (Peter Schiffer) 2. Re: Review Request 1441: Hardware: added SAPAvailableForElementProvider (scanbot) 3. Re: Review Request 1441: Hardware: added DiskDriveSAPAvailableForElementProvider (Peter Schiffer) 4. Re: Review Request 1441: Hardware: added DiskDriveSAPAvailableForElementProvider (Michal Minar) 5. Re: Review Request 1441: Hardware: added DiskDriveSAPAvailableForElementProvider (scanbot) 6. Re: Review Request 1441: Hardware: added DiskDriveSAPAvailableForElementProvider (Peter Schiffer) 7. buildbot failure in OpenLMI on providers-rawhide (openlmiproject(a)gmail.com) 8. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 9. Review Request 1452: account: Use lckpwdf() to protect passwd files (=?utf-8?b?VG9tw6HFoSBCxb5hdGVr?=) 10. Re: Review Request 1452: account: Use lckpwdf() to protect passwd files (scanbot) 11. Re: Review Request 1452: account: Use lckpwdf() to protect passwd files (scanbot) 12. buildbot failure in OpenLMI on storage-rawhide (openlmiproject(a)gmail.com) 13. buildbot failure in OpenLMI on storage-rhel7 (openlmiproject(a)gmail.com) 14. buildbot success in OpenLMI on networking-rawhide (openlmiproject(a)gmail.com) 15. buildbot failure in OpenLMI on networking-rhel7 (openlmiproject(a)gmail.com) 16. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

10 years, 3 months

1
0
0 / 0

openlmi-reviews Digest, Vol 9, Issue 10

by openlmi-reviews-request＠lists.fedorahosted.org

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 1438: Hardware: added ATAProtocolEndpointProvider (Peter Schiffer) 2. buildbot failure in OpenLMI on providers-rawhide (openlmiproject(a)gmail.com) 3. buildbot failure in OpenLMI on providers-rawhide (openlmiproject(a)gmail.com) 4. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 5. Re: Review Request 1435: Use re-entrant version of strerror() for thread safety (=?utf-8?b?VG9tw6HFoSBCxb5hdGVr?=) 6. Review Request 1441: Hardware: added SAPAvailableForElementProvider (Peter Schiffer) 7. Review Request 1442: providers [1/3] spec: prevent version mismatch caused by openlmi metapackage (Radek Novacek) 8. Re: Review Request 1441: Hardware: added SAPAvailableForElementProvider (scanbot) 9. Review Request 1446: providers [1/1] software: SoftwareIdentityFileCheck test fixes (Michal Minar) 10. Review Request 1445: providers [1/3] spec: mark 0.4.1 as OpenLMI 1.0.1 (Radek Novacek) 11. Re: Review Request 1445: providers [2/3] spec: mark 0.4.1 as OpenLMI 1.0.1 (Radek Novacek) 12. Review Request 1449: providers [3/3] spec: sync changes from Fedora downstream spec file (Radek Novacek) 13. Re: Review Request 1435: Use re-entrant version of strerror() for thread safety (Jan Synacek) 14. Re: Review Request 1449: providers [3/3] spec: sync changes from Fedora downstream spec file (Jan Safranek) 15. Re: Review Request 1445: providers [2/3] spec: mark 0.4.1 as OpenLMI 1.0.1 (Jan Safranek) 16. Re: Review Request 1442: providers [1/3] spec: prevent version mismatch caused by openlmi metapackage (Jan Safranek) 17. Re: Review Request 1435: Use re-entrant version of strerror() for thread safety (=?utf-8?b?VG9tw6HFoSBCxb5hdGVr?=) 18. Re: Review Request 1446: providers [1/1] software: SoftwareIdentityFileCheck test fixes (Jan Safranek) 19. Re: Review Request 1440: [1/1] logicalfile: replace thread-unsafe functions (Michal Minar) 20. Re: Review Request 1440: [1/1] logicalfile: replace thread-unsafe functions (Jan Safranek) 21. Re: Review Request 1441: Hardware: added SAPAvailableForElementProvider (scanbot) 22. Re: Review Request 1441: Hardware: added SAPAvailableForElementProvider (Michal Minar) 23. Re: Review Request 1442: providers [1/3] spec: prevent version mismatch caused by openlmi metapackage (Radek Novacek) 24. Re: Review Request 1445: providers [2/3] spec: mark 0.4.1 as OpenLMI 1.0.1 (Radek Novacek) 25. Re: Review Request 1449: providers [3/3] spec: sync changes from Fedora downstream spec file (Radek Novacek) 26. Re: Review Request 1440: [1/1] logicalfile: replace thread-unsafe functions (Jan Synacek) 27. Re: Review Request 1446: providers [1/1] software: SoftwareIdentityFileCheck test fixes (Michal Minar) 28. Review Request 1450: [1/1] logicalfile: don't automatically fill FSName and FSCreationClassName (Jan Synacek) 29. Re: Review Request 1450: [1/1] logicalfile: don't automatically fill FSName and FSCreationClassName (scanbot) 30. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 31. Re: Review Request 1450: [1/1] logicalfile: don't automatically fill FSName and FSCreationClassName (scanbot) 32. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 33. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 34. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 35. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 36. buildbot success in OpenLMI on networking-rawhide (openlmiproject(a)gmail.com) 37. buildbot success in OpenLMI on networking-rhel7 (openlmiproject(a)gmail.com) 38. buildbot failure in OpenLMI on storage-rawhide (openlmiproject(a)gmail.com) 39. buildbot failure in OpenLMI on storage-rhel7 (openlmiproject(a)gmail.com) 40. Re: Review Request 1450: [1/1] logicalfile: don't automatically fill FSName and FSCreationClassName (Jan Safranek) 41. Re: Review Request 1450: [1/1] logicalfile: don't automatically fill FSName and FSCreationClassName (Jan Synacek) 42. Review Request 1451: providers [1/1] spec: Remove openlmi-pcp post script (Radek Novacek) 43. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

10 years, 3 months

1
0
0 / 0

openlmi-reviews Digest, Vol 9, Issue 9

by openlmi-reviews-request＠lists.fedorahosted.org

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. Review Request 1437: [1/1] logicalfile: replace thread-unsafe functions (Jan Synacek) 2. Re: Review Request 1437: [1/1] logicalfile: replace thread-unsafe functions (scanbot) 3. Re: Review Request 1437: [1/1] logicalfile: replace thread-unsafe functions (Jan Synacek) 4. Re: Review Request 1435: Use re-entrant version of strerror() for thread safety (Jan Synacek) 5. Review Request 1438: Hardware: added ATAProtocolEndpointProvider (Peter Schiffer) 6. Re: Review Request 1438: Hardware: added ATAProtocolEndpointProvider (scanbot) 7. Review Request 1439: providers [1/1] tests: ensure the use of exceptions is well defined (Michal Minar) 8. Re: Review Request 1439: providers [1/1] tests: ensure the use of exceptions is well defined (=?utf-8?b?VG9tw6HFoSBCxb5hdGVr?=) 9. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 10. buildbot failure in OpenLMI on providers-rawhide (openlmiproject(a)gmail.com) 11. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 12. buildbot failure in OpenLMI on networking-rhel7 (openlmiproject(a)gmail.com) 13. Re: Review Request 1438: Hardware: added ATAProtocolEndpointProvider (scanbot) 14. Re: Review Request 1437: [1/1] logicalfile: replace thread-unsafe functions (scanbot) 15. buildbot success in OpenLMI on networking-rawhide (openlmiproject(a)gmail.com) 16. buildbot failure in OpenLMI on providers-rhel7 (openlmiproject(a)gmail.com) 17. buildbot failure in OpenLMI on storage-rawhide (openlmiproject(a)gmail.com) 18. Re: Review Request 1438: Hardware: added ATAProtocolEndpointProvider (Michal Minar) 19. Review Request 1440: [1/1] logicalfile: replace thread-unsafe functions (Jan Synacek) 20. buildbot failure in OpenLMI on networking-rhel7 (openlmiproject(a)gmail.com) 21. Re: Review Request 1440: [1/1] logicalfile: replace thread-unsafe functions (scanbot) 22. buildbot failure in OpenLMI on storage-rhel7 (openlmiproject(a)gmail.com) 23. Re: Review Request 1440: [1/1] logicalfile: replace thread-unsafe functions (scanbot) _______________________________________________ openlmi-reviews mailing list openlmi-reviews(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

openlmi-devel January 2014