Difference between revisions of "SUSE Manager/osa-dispatcher"

From MicroFocusInternationalWiki
Jump to: navigation, search
(osa-dispatcher)
Line 11: Line 11:
 
===jabberd2===
 
===jabberd2===
  
A deamon that implements the XMPP protocol defined in RFC 3920 and RFC 3921. osad and osa-dispatcher both connect to this daemon. It handles authentication as well.
+
A deamon that implements the XMPP protocol defined in RFC 3920 and RFC 3921. osad and osa-dispatcher both connect to this daemon. Jabberd2 also handles authentication.
  
 
===How these fit together===
 
===How these fit together===

Revision as of 14:13, 5 August 2015

Introduction to OSAD

osad

Client-side service written in Python that responds to pings and runs rhn_check when commanded to by osa-dispatcher.

osa-dispatcher

Server-side service written in Python that determines when an osad instance needs to be pinged or run rhn_check and send a message commanding them to do so.

jabberd2

A deamon that implements the XMPP protocol defined in RFC 3920 and RFC 3921. osad and osa-dispatcher both connect to this daemon. Jabberd2 also handles authentication.

How these fit together

osa-dispatcher runs a query every 5 seconds that checks to see if there are any clients which are overdue for a ping. If a client due for a ping is found, it sends a message through jabberd to the osad instances running on the clients it needs responses from. The osad instances then respond to the message sent through the jabberd server. osa-dispatcher receives the response, and marks the client as 'online'. If osa-dispatcher doesn't receive a response from an osad instance within the timeout range, it is marked 'offline'. The osa-dispatcher daemon also periodically performs a select within the database to see if any clients have any actions they need to perform which have been initiated from the CLI or WebUI. If there are, it sends a message through jabberd to osad telling it to run rhn_check on the client. rhn_check then takes over performing the action.


The osa-dispatcher.notify_threshold option is used to adjust the maximum number of osad clients that are simultaneously served actions by the SUSE Manager Server.

The notifiy_threshold parameter is required as actions performed on clients configured with the OSAD contact method are performed instantly. The issues occure when an action is scheduled on a high number of clients at the same time, the SUSE Manager server can then be overloaded. Setting this parameter to 100 for example will serve 100 clients at once and queue up the remaining actions at a later time. The recommended default parameter is 100.

The default settings are located at:

/usr/share/rhn/config-defaults/rhn_osa-dispatcher.conf


To override the default values add the notify_threshold = 100 parameter to the following file underneath the # OSA configuration # section heading.

/etc/rhn/rhn.conf