openlmi-reviews Digest, Vol 16, Issue 2
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 1935: software-dbus [3/3] software-dbus:
optimalized FindIdentity() function (Michal Minar)
2. Re: Review Request 1918: providers [1/1] software: use full
path for configure_file destination (Michal Minar)
3. Re: Review Request 1918: providers [1/1] software: use full
path for configure_file destination (Radek Novacek)
4. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
5. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
6. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
7. Review Request 1941: tests: base modules enhancements and
fixes (Michal Minar)
8. Review Request 1942: tests-sw: fixed repository setup
(Michal Minar)
9. Review Request 1943: tests-sw: use pkcon for repository
enablement/disablement (Michal Minar)
10. Review Request 1944: tests-sw: software installation service
test fixes (Michal Minar)
11. Review Request 1945: tests-sw: added package downgrade tests
(Michal Minar)
12. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
13. Re: Review Request 1941: tests: base modules enhancements and
fixes (Peter Schiffer)
14. Re: Review Request 1942: tests-sw: fixed repository setup
(Peter Schiffer)
15. Re: Review Request 1943: tests-sw: use pkcon for repository
enablement/disablement (Peter Schiffer)
16. Re: Review Request 1944: tests-sw: software installation
service test fixes (Peter Schiffer)
17. Re: Review Request 1945: tests-sw: added package downgrade
tests (Peter Schiffer)
18. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
19. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
20. buildbot success in OpenLMI on networking-rhel7
(openlmiproject(a)gmail.com)
21. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
22. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
23. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
24. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
25. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
26. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
27. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
28. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
29. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
30. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
31. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
32. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
33. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
34. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
35. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
36. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
37. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
38. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
39. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
40. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
41. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
42. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
43. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
44. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
45. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
46. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
47. buildbot success in OpenLMI on networking-rhel7
(openlmiproject(a)gmail.com)
48. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
49. Re: Review Request 1941: tests: base modules enhancements and
fixes (Michal Minar)
50. Re: Review Request 1941: tests: base modules enhancements and
fixes (Michal Minar)
51. Review Request 1946: tests-sw: added utility function to
access environment (Michal Minar)
52. Re: Review Request 1943: tests-sw: use pkcon for repository
enablement/disablement (Michal Minar)
53. Re: Review Request 1941: tests: base modules enhancements and
fixes (Peter Schiffer)
54. Re: Review Request 1946: tests-sw: added utility function to
access environment (Peter Schiffer)
55. Re: Review Request 1943: tests-sw: use pkcon for repository
enablement/disablement (Peter Schiffer)
56. Re: Review Request 1941: tests: base modules enhancements and
fixes (Michal Minar)
57. Re: Review Request 1942: tests-sw: fixed repository setup
(Michal Minar)
58. Re: Review Request 1946: tests-sw: added utility function to
access environment (Michal Minar)
59. Re: Review Request 1943: tests-sw: use pkcon for repository
enablement/disablement (Michal Minar)
60. Re: Review Request 1944: tests-sw: software installation
service test fixes (Michal Minar)
61. Re: Review Request 1945: tests-sw: added package downgrade
tests (Michal Minar)
62. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
63. Review Request 1947: tests: fallback to pywbem when lmiwbem
is unavailable (Michal Minar)
64. Re: Review Request 1947: tests: fallback to pywbem when
lmiwbem is unavailable (Peter Schiffer)
65. Re: Review Request 1947: tests: fallback to pywbem when
lmiwbem is unavailable (Michal Minar)
66. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
67. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
68. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
69. Review Request 1948: tests-sw: first round of tests alignment
for software-dbus (Peter Schiffer)
70. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
71. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
72. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
73. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
74. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
75. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
76. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
77. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
78. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
79. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
80. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
81. Re: Review Request 1948: tests-sw: first round of tests
alignment for software-dbus (Michal Minar)
82. Re: Review Request 1948: tests-sw: first round of tests
alignment for software-dbus (Peter Schiffer)
83. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
84. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
85. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
86. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
87. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
88. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
89. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
_______________________________________________
openlmi-reviews mailing list
openlmi-reviews(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews
9 years, 9 months
- 1
- 0
Re: FreeIPA&OpenLMI integration use cases
by John Dennis
On 08/07/2014 05:21 PM, Dmitri Pal wrote:
> On 08/04/2014 07:48 AM, Jan Safranek wrote:
>> On 07/30/2014 02:42 PM, Martin Kosek wrote:
>>> Hello all,
>>>
>>> In the last month, FreeIPA [1] team was discussing options for remote
>>> management and deployment of FreeIPA servers, replicas and clients. We see the
>>> OpenLMI as the transport layer of choice for that task. We would like to share
>>> our use cases with this list and hopefully get advise and recommendations about
>>> the ways we should take (and avoid reinventing the wheel).
>>>
>>> In short, we have 2 main scenarios in mind:
>>> A) Extend FreeIPA Web UI&CLI and allow Administrators to easily enroll hosts in
>>> the network to FreeIPA install additional FreeIPA replica servers or control
>>> which services are supported by existing FreeIPA servers
>>> B) Allow deploying FreeIPA infrastructure from other tools, like Foreman
>>>
>>> Drop down of the particular use cases we identified for the 2 main scenarios:
>>>
>>> == FreeIPA management scenarios ==
>>>
>>> A1) Retrieve status of a host
>>> User wants to detect what clients are available and enabled for OpenLMI and
>>> check whether they are already connected to FreeIPA. User interacts with
>>> FreeIPA Web UI/CLI that in turn invokes a remote OpenLMI call per system to
>>> check the state of the system. The system should be able to return at least
>>> following status:
>>> - I do not understand OpenLMI
>>> - I am not enrolled
>>> - I am enrolled with a particular domain of given type (FreeIPA, AD, LDAP, ...)
>> These three are already implemented.
>>
>>> - I am a FreeIPA server with following services configured (AD Trusts, Legacy
>>> clients, DNS, DNSSEC, PKI, Vault, ...), I am master server for following
>>> services (PKI/DNSSEC/...)
>>> - I am a FreeIPA server/client and I am in the middle of a particular
>>> deployment operation (see below)
>> These two are not. AFAIK realmd does not report 'I'm in the middle of a
>> particular operation', it just has synchronous 'join domain' method. And
>> it does not support FreeIPA _server_ management.
>>
>>> As Stephen Gallagher already suggested, this should be able to work with SLP
>>> discovery protocol and query systems individually to be just a fallback. I
>>> think some of the data could be already retrieved via existing realmd provider
>>> [2] that John Dennis wrote.
>>>
>>> A2) FreeIPA Client enrollment
>>> User wants to change a system into a FreeIPA client. User calls FreeIPA UI/CLI,
>>> that in turn connects to remote host over OpenLMI and checks the enrollment
>>> status. If the machine does not have FreeIPA client bits installed, command to
>>> enroll a client is issued. While this is happening status checks above should
>>> return status indicating that system is in process of becoming a client.
>>>
>>> This is already mostly possible, as per Stephen's blog [3].
>> Almost. As I wrote, realmd does not report 'I am enrolling just now',
>> thus OpenLMI provider does not report it too. [2] is really the complete
>> API we provide for domain membership and you can see it's really simple
>> one. We're open for suggestions and/or patches.
>>
>>> A3) FreeIPA Replica deployment
>>> User wants to promote a FreeIPA Client to a Replica. User calls FreeIPA UI/CLI,
>>> that in turn connects to a remote host over OpenLMI and issues a command for a
>>> client to become a replica. Client turns into a replica. While this is
>>> happening status checks above should return status indicating that system is in
>>> process of becoming replica.
>>>
>>> Stephen suggested this should be implemented via Server Roles.
>>>
>>>
>>> A4) FreeIPA Replica decommissioning
>>> User wants to remove a FreeIPA Replica. User calls FreeIPA UI/CLI, that in turn
>>> removes the replica from FreeIPA replication agreements, connects to a remote
>>> host over OpenLMI and issues a command for a replica to uninstall.
>>>
>>> Stephen suggested this should be implemented via Server Roles.
>>>
>>>
>>> A5) Configure FreeIPA service
>>> User wants to configure an optional service on FreeIPA server (DNS, AD Trusts,
>>> ...). User calls FreeIPA Web UI/CLI, that in turn connects to a remote host
>>> over OpenLMI and issues a command to install the service. While this is
>>> happening status checks above should return status indicating that system is in
>>> a process of installing a service.
>>>
>>> Stephen suggested this may be implemented via Server Roles.
>> I am also inclined to implement A3-A6 as server role - you write the
>> DBus API (for the role) and then anyone can use it, regardless if it is
>> CLI, GUI (Cockpit) or remote API (OpenLMI).
>>
>> Or, it doesn't need to be a server role, it may be IPA's own
>> configuration API (DBus is preferred).
>>
>>
>>> A6) Configure FreeIPA master service
>>> Some FreeIPA services require a single FreeIPA node in the infrastructure to be
>>> the master for that service and e.g. generate CRL in case of PKI service or
>>> generate DNSSEC keys in case of DNS service.
>>>
>>> User wants to configure FreeIPA server as the new service master Server. User
>>> calls FreeIPA UI/CLI, that in turn connects to remote host over OpenLMI and
>>> issues a command to turn it in a master server for given service.
>>>
>>> This is tricky, as for some services, it may be also necessary to connect to
>>> previous master server and turn it into regular server and do additional
>>> migration steps. While this is happening status checks above should return
>>> status indicating that system is in a process of configuring a master server.
>>>
>> Well, OpenLMI is just a remote API. It can do anything that someone
>> writes providers for. Architecturally, the above is possible. Out of
>> curiosity, how does your UI/CLI talk to remote nodes now?
>>
>>> A7) Log gathering
>>> User wants to send logs to e.g. Red Hat Access Portal using integration with
>>> FreeIPA Web UI. User selects a different server or client. FreeIPA server
>>> connects to a selected host over OpenLMI and inspects available logs. User then
>>> chooses logs to upload. Server then issues a command over OpenLMI to collect
>>> the chosen logs.
>>>
>>> As per Stephen's info, log collection is under investigation in OpenLMI, though
>>> without a given time frame yet.
>> We do have simple API to read journald logs. It's not particularly fast
>> (ssh + cat will always be much faster), but it _can_ iteratively read
>> logs. See its API and use cases at:
>>
>> http://www.openlmi.org/sites/default/files/doc/admin/openlmi-providers/la...
>>
>> Is it enough or do you need something better? We're open for suggestions
>> here.
>>
>>> == Remote management systems scenarios ==
>>>
>>> B1) Deploy cluster of FreeIPA servers
>>> User of a provisioning system invokes a UI/CLI that calls OpenLMI to deploy a
>>> cluster of several IPA servers. It is expected that it would connect to a
>>> chosen node, pass the required work plan that might include following
>>> information: list of nodes (by IP or names or MACs) with user names (if not
>>> Pegasus user) and passwords to use, admin and DM passwords, topology to use
>>> (full, ring, star, hub and spoke, etc). It is expected that the first node will
>>> process the work plan, install the first server, connect to other systems using
>>> use case A1, configures clients using A2 and promote them into replicas by
>>> using A3. Since this procedure takes time the provisioning system might fire
>>> the work plan and periodically check. In this case the head node should respond
>>> with the corresponding status: installing server, deploying clients, promoting
>>> clients to replicas, etc.
>>>
>>>
>>> B2) FreeIPA Replica deployment
>>> User of a provisioning system invokes a UI/CLI that calls OpenLMI to deploy
>>> another replica in the existing cluster. This case is a sub case of B1 when
>>> provisioning system has a work plan to extend an existing cluster. In this
>>> case, it provides a modification work plan and then IPA node processes it using
>>> capabilities covered in section A.
>>>
>>> B3) Create Trust relationship between FreeIPA and other domain (like Active
>>> Directory)
>>> User of a provisioning system invokes a UI/CLI that calls OpenLMI to get a
>>> status of the trust relations of a specific IPA domain. This is a slightly
>>> different type of status than covered in A1 as it needs to be exposed over
>>> OpenLMI only for external systems.
>>>
>>> B4) Change Trust relationship between FreeIPA and other domain
>>> User of a provisioning system invokes a UI/CLI that calls OpenLMI to change
>>> trust relationships between a selected IPA realm and other AD forests. Required
>>> information is provided and corresponding trusts are added or removed.
>>>
>> I do not see any obvious obstacles in B1-B3, all should be possible. I
>> am not sure if current OpenLMI realmd provider is good enough, it's
>> quite primitive. The same applies to underlying realmd.
>>
>> I would propose that someone from IPA looks if realmd (both the DBus
>> service and OpenLMI API) is good enough and we can then together make
>> the OpenLMI provider better.
>>
>> For all the scenarios above, everything is possible, still it implies
>> quite lot of work. CIM (and OpenLMI) is just remote API and someone has
>> to implement the API.
>>
>>> ==========================
>>>
>>> This is the main set of use cases, we will be looking forward to your
>>> recommendation on how to address them with OpenLMI. We would be also interested
>>> whether you would recommend designing&implementing simply via our own CIM
>>> model, not integrated in DMTF ecosystem (i.e. mostly just implementing RPC
>>> interface) or rather going the hard way and follow the DMTF models and profiles?
>> DMTF does not say anything about AD or Kerberos server management. I
>> would recommend to write your own models and make them as close to
>> underlying implementation (DBus API or IPA libraries) as possible.
>>
>> If CIM is just a protocol between various IPA components (e.g. GUI
>> talking to remote IPA installation to turn itself to be a replica), it
>> may be even proprietary, not documented and unstable. And it does not
>> need to be CIM at all.
>>
>> if CIM is used as public remote API to manage IPA, it _should_ be stable
>> and somewhat generic to allow future modifications without breaking
>> existing users of the API, but you know, sometimes is the best just to
>> break the API. CIM allows versioning, so the client can check what
>> version of the API remote server supports and adapt accordingly.
>>
>>> [2]
>>> http://www.openlmi.org/sites/default/files/doc/admin/openlmi-providers/0....
> Why are you thinking realmd? I was thinking about a new provider that
> will be in some way related to realmd.
> This is something to figure out.
>
> I agree with John and Martin on CIM models - let us try to use existing
> ones if they make sense.
>
> It is implied that we work jointly on this effort.
>
> We will start with D-BUS API for sure and then provide different means
> to invoke it, OpenLMI being one of them.
>
I sent a mail that apparently got lost somehow. It was a follow-up an
earlier email that listed some profiles etc. that Jan later said he
thought some were abandoned. I went back to my cache of mof's and looked
again. This is what I came up with, it's not the same as the first list
I sent (but there is overlap). Hoping it points you at something to
start looking at.
A really quick search of mof's turned up these that are directly related
to Kerberos
Policy/CIM_KerberosAuthentication.mof
User/CIM_KerberosKeyDistributionCenter.mof
User/CIM_KerberosCredential.mof
User/CIM_KerberosTicket.mof
User/CIM_KDCIssuesKerberosTicket.mof
And these mof's reference Kerberos in some fashion.
User/CIM_SharedSecret.mof
User/CIM_SharedCredential.mof
Policy/CIM_AcceptCredentialFrom.mof
System/CIM_BIOSServiceCapabilities.mof
User/CIM_SharedSecretService.mof
Network/CIM_iSCSICapabilities.mof
Network/CIM_iSCSIConnection.mof
Network/CIM_iSCSIConnectionSettings.mof
--
John
9 years, 9 months
- 1
- 0
Certificate verify failed when connecting via lmishell
by Stewart, Sean
Hi all,
I'm using Fedora 19 on a client system, RHEL7 on the server, trying to
get openlmi running, but am running into a problem with SSL
verification. I have followed the instructions on Red Hat's
documentation to the t to set up the self-signed certificates:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/...
I've copied the client.pem from the server to the client: scp
root@wica-fo-freestate:/etc/Pegasus/client.pem /etc/pki/ca-trust/source/anchors/pegasus-wica-fo-freestate.pem
Then run on the server: update-ca-trust extract
Then I tried connecting to the server through lmishell:
connect("wica-fo-freestate","pegasus")
and I always get "ERROR: Error connecting to wica-fo-freestate,
certificate verify failed"
The troubleshooting page on openlmi.org is just confusing me more,
because the red hat documentation says to copy the client.pem, the
troubleshooting page says server.pem.. I've tried every combination of
copying each of them from the remote server to the client, and trying
both, and no matter what I get the same result: "certificate verify
failed".
I can't find any further documentation, the documentation I do find
contradicts other documentation.
Any assistance would be greatly appreciated.
Thanks,
Sean
9 years, 9 months
- 2
- 1
Ideas for API
by Alois Mahdal
Hi,
as a follow-up to discussion we had last week regarding LMI API. Sorry
for replying that late, I was working on it but then something else popped
up and I had to work on RHEL7 wor a while.
First: yes the lmiwbem is basically the API I was searching for and
that I believe should be presented as main API for potential LMI users.
For
me as Python test developer, it is far more readable and accessible than
LMIShell, which seems to be aimed for interactive use.
Other thing: as I mentioned, attempt to help fix the subscription problems
right
in the LMIShell got me thinking and I compiled up my own idea of how such
an API
could look like. I called it LPI, LMI Programming API:
http://git.engineering.redhat.com/git/users/amahdal/lpi.git/tree/README.py
Highlight here is probably the query*() and query1*() methods of
`BaseLPIObjectCollection`. I tried to outline an interface where
everything of
interest (i.e. namespace and query result) is child of
`BaseLPIObjectCollection(set)`, and these collections can be created and
queried
by `query()` method, which allows for CQL, WQL, Name/Path-based querying
as well
as using the class itself (instead of "select * from SomeClass").
Other thing I tried to get into the usage pattern was ability to
repeatedly use
the `query()` method(s) on their result. This could allow for more
flexibility
when manipulating with objects and would be even usable in interactive
environment.
But the problem here (as I realized later) is that *I don't know if it's
possible
in WBEM*.
Last idea worth highlighting is the `lpi.q` submodule, which could be
created as
a repository of "pre-fabricated" queries that would follow common
scenarios. (That
could be even more useful in combination with the above "re-quering"
behavior.)
Thanks,
aL.
--
Alois Mahdal <amahdal(a)redhat.com>
Platform QE, BaseOS Daemons
#qa, #brno, #daemons
9 years, 9 months
- 1
- 0
openlmi-reviews Digest, Vol 16, Issue 1
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 1935: software-dbus [3/3] software-dbus:
optimalized FindIdentity() function (scanbot)
2. Re: Review Request 1933: software-dbus [1/3] software-dbus:
rename cleanup function of SwPackage (scanbot)
3. Re: Review Request 1934: software-dbus [2/3] software-dbus:
enhanced repository listing functions (scanbot)
4. Re: Review Request 1935: software-dbus [3/3] software-dbus:
optimalized FindIdentity() function (scanbot)
5. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
6. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
7. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
8. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
9. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
10. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
11. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
12. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
13. Re: Review Request 1936: lmishell, rewrite synchro methods
listener startup (Peter Hatina)
14. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
15. Re: Review Request 1935: software-dbus [3/3] software-dbus:
optimalized FindIdentity() function (Peter Schiffer)
16. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
17. Review Request 1937: Fixed values of LocalFileSystem
properties. (Jan Safranek)
18. Review Request 1938: Implemented LMI_ScsiScan method.
(Jan Safranek)
19. Review Request 1939: Fixed storage provider profile
registration (Jan Safranek)
20. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
21. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
22. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
23. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
24. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
25. buildbot failure in OpenLMI on networking-rhel7
(openlmiproject(a)gmail.com)
26. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
27. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
28. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
29. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
30. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
31. Re: Review Request 1939: Fixed storage provider profile
registration (Radek Novacek)
32. Re: Review Request 1939: Fixed storage provider profile
registration (Jan Safranek)
33. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
34. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
35. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
36. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
37. Review Request 1940: lmishell, introduce
LMIInstanceName.delete() (Peter Hatina)
38. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
39. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
40. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
41. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
42. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
43. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
44. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
45. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
46. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
47. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
48. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
49. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
50. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
51. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
52. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
53. buildbot failure in OpenLMI on networking-rhel7
(openlmiproject(a)gmail.com)
54. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
55. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
56. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
57. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
58. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
59. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
60. Re: Review Request 1937: Fixed values of LocalFileSystem
properties. (Radek Novacek)
61. Re: Review Request 1938: Implemented LMI_ScsiScan method.
(Radek Novacek)
62. Re: Review Request 1940: lmishell, introduce
LMIInstanceName.delete() (Radek Novacek)
63. Re: Review Request 1940: lmishell, introduce
LMIInstanceName.delete() (Peter Hatina)
64. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
65. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
66. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
67. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
68. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
69. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
70. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
71. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
72. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
73. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
74. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
75. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
76. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
77. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
78. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
79. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
80. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
81. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
82. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
83. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
84. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
85. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
86. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
87. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
88. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
89. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
90. buildbot failure in OpenLMI on networking-rhel7
(openlmiproject(a)gmail.com)
91. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
92. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
93. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
94. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
95. buildbot failure in OpenLMI on networking-rhel6
(openlmiproject(a)gmail.com)
96. buildbot failure in OpenLMI on storage-rhel6
(openlmiproject(a)gmail.com)
97. buildbot failure in OpenLMI on networking-rhel7
(openlmiproject(a)gmail.com)
98. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
99. buildbot failure in OpenLMI on networking-rawhide
(openlmiproject(a)gmail.com)
100. buildbot failure in OpenLMI on storage-rhel7
(openlmiproject(a)gmail.com)
101. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
102. buildbot failure in OpenLMI on providers-rhel7stable
(openlmiproject(a)gmail.com)
103. buildbot failure in OpenLMI on storage-rawhide
(openlmiproject(a)gmail.com)
104. buildbot failure in OpenLMI on storage-rhel7stable
(openlmiproject(a)gmail.com)
105. buildbot failure in OpenLMI on providers-rawhide
(openlmiproject(a)gmail.com)
106. Re: Review Request 1932: jobmgr: don't truncate GType's
value (Jan Synacek)
107. Re: Review Request 1932: jobmgr: don't truncate GType's
value (Jan Synacek)
108. Re: Review Request 1932: jobmgr: don't truncate GType's
value (Michal Minar)
109. buildbot failure in OpenLMI on providers-rhel7
(openlmiproject(a)gmail.com)
110. Re: Review Request 1933: software-dbus [1/3] software-dbus:
rename cleanup function of SwPackage (Michal Minar)
111. buildbot failure in OpenLMI on providers-rhel6
(openlmiproject(a)gmail.com)
112. Re: Review Request 1934: software-dbus [2/3] software-dbus:
enhanced repository listing functions (Michal Minar)
113. Re: Review Request 1935: software-dbus [3/3] software-dbus:
optimalized FindIdentity() function (Michal Minar)
_______________________________________________
openlmi-reviews mailing list
openlmi-reviews(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/openlmi-reviews
9 years, 9 months
- 1
- 0