Version 3 (modified by bartek, 13 years ago) (diff) |
---|
QCG Notification Installation
Within QosCosGrid the QCG Notification service is used for brokering notification messages about the job state changes. All instances of the QCG BES/AR services acts as the information Producers while the QCG Broker as the Consumer. In most cases it is enough that only one instance of the QCG Notification is deployed per Administrative Domain (i.e.: not necessary one per Cluster).
Note: The implementation name of the QCG Notification service is Smoa Notification and this name is used as a common in this guide.
Installation
Similar to the Smoa Computing (QCG BES/AR) service the Smoa Notification requires the Smoa Core library to be installed. If this prerequisite is fulfilled the Smoa Notification installation can be done in a few simple steps:
$ tar xf smoa-ntf-latest.tar $ cd smoa-ntf-1.1.2 $ ./configure --prefix=/opt/QCG/smoa/ --with-smoa-core=/opt/QCG/smoa/ $ make $ sudo make install
In order to verify later the installation, it is recommended to provide an additional option to ./configure: --with-consumer
Configuration
Before you start you need to create a new system user (e.g. smoa_ntf) that will be used to start the service:
# useradd -d /opt/QCG/smoa/var/log/smoa-ntf/ -M smoa_ntf
Give the smoa_ntf user ownership of the log directory:
# chown smoa_ntf /opt/QCG/smoa/var/log/smoa-ntf/
Service configuration
Minimal configuration requires only the host and port to be changed in the main service configuration file: PREFIX/etc/smoa-ntfd.xml. The complete configuration guide can be found in the PREFIX/share/smoa-ntf/doc/ directory.
Starting the service
As the smoa_ntf user type:
$ /opt/QCG/smoa/sbin/smoa-ntfd
or if you want the service not to daemonize and print all logs to console type:
$ /opt/QCG/smoa/sbin/smoa-ntfd -d
otherwise the logs can be found in /opt/QCG/smoa/var/log/smoa-ntf/smoa-ntfd.log.
Stopping the service
The service is stopped by sending SIGTERM signal, e.g.:
$ pkill smoa-ntfd
Verifying the installation
If the service was configured with the option --with-consumer attached to ./configure, the basic verification scenario may be proceeded in a following way:
- Set the Host and Port parameters in the configuration files of the Smoa Notification service and sample consumer, respectivetly in /opt/QCG/etc/smoa-ntfd.xml and /opt/QCG/etc/smoa-ntf-consumer.xml. For example, the key part of the smoa-ntfd.xml file may looks as foolows:
<sm:Module xsi:type="sm:ecm_gsoap.service"> <sm:Host>0.0.0.0</sm:Host> <sm:Port>2211</sm:Port> ... </sm:Module>
Similarly the part of smoa-ntf-consumer.xml may have a following form:
<sm:Module xsi:type="sm:ecm_gsoap.service"> <sm:Host>0.0.0.0</sm:Host> <sm:Port>2212</sm:Port> ... </sm:Module>
- Start the smoa-ntfd service on the selected port:
$ /opt/QCG/smoa/sbin/smoa-ntfd -d
Smoa Computing (QCG BES/AR) configuration
After finishing the Smoa Notification configuration you must edit the Smoa Computing service configuration file again and update the content of the <ServiceURL> elements (in <Module xsi:type="smc:notification_wsa"> section). For e.g if in the PREFIX/etc/smoa-ntfd.xml one can find <Host>example.com<Host> and <Port>19005<Port> the <ServiceURL> must be set to http://example.com:19005/.
Note: You must restart the Smoa Computing service after updating the smoa-compd.xml configuration file.
When you start the Smoa Notification service and update the SMOA Computing configuration try to submit a simple job and check the Smoa Computing log file to see if there are now any error messages on sending notifications, e.g.:
$ tail -f /opt/QCG/smoa/var/log/smoa-comp/smoa-comp.log INF Sep 17 16:15:01 24201 0x44b22940 [notification_ws] Sending notify message (topic = ActivityState/TerminalState/Finished, activity_id = 0544b24a-e960-400e-4910-f1a893632610, status = Finished)