Bug 1026718 - [RFE] Notification service - use API instead of health servlet for keep alive
Summary: [RFE] Notification service - use API instead of health servlet for keep alive
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Services.Notifier
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Eli Mesika
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On: 1009843
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-05 09:53 UTC by Alon Bar-Lev
Modified: 2022-02-25 07:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-27 06:57:13 UTC
oVirt Team: Infra
Embargoed:
sherold: Triaged+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44872 0 None None None 2022-02-25 07:58:33 UTC

Description Alon Bar-Lev 2013-11-05 09:53:22 UTC
The health servlet is a legacy interface that IMO should not be used at all, marked obsolete and removed as soon as we can.

Please make the notification service use the formal supported API to pull engine status.

It should be simple either use the java binding of our sdk, or just perform HTTP request and expect valid response.

Thanks!

Comment 1 Itamar Heim 2013-11-05 23:32:17 UTC
for easy configuration, would need api to expose this info to anonymous user?

Comment 2 Alon Bar-Lev 2013-11-05 23:35:36 UTC
(In reply to Itamar Heim from comment #1)
> for easy configuration, would need api to expose this info to anonymous user?



you are right (bug#1009843), in this case (unlike the setup and hosted) we do not have account information.

Comment 4 Alon Bar-Lev 2015-08-05 14:52:03 UTC
*MUST* be for 4.0.

Comment 5 Alon Bar-Lev 2015-08-05 14:55:01 UTC
(In reply to Alon Bar-Lev from comment #4)
> *MUST* be for 4.0.

sorry, not a must, I see I already used the /services/ servlet, but it should not be used any more and dropped in 4.0.

Comment 7 Oved Ourfali 2016-01-27 06:57:13 UTC
The API doesn't perform authentication, it is performed by the AAA
subsystem. However, the AAA subsystem currently doesn't allow "guest" or "anonymous" access to anything so the API will not be able to serve such requests to public queries.

As we don't plan work around allowing that in the AAA layer, closing it as WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.