Contents 1 Plugins 1.1 Overview 1.2 Technology 1.3 Supported Plugins 1.3.1 Distribution Model Plugins 1.3.2 Publisher Plugins 1.3.3 Conductor Plugins

Plugins

Overview

OTS currently consists of two distributed Applications:

• Worker

• Server

These Applications are made up of Components. The Components perform a specific task in the system (and are distributable in their own right).

Some of the Components are essential for the Applications to operate. The Plugins are the non-essential (pluggable!) Components.

Technology

OTS allows for a configurable distribution by using a plug-in mechanism using Package Resources

Supported Plugins

Some of the plug-ins are requiring Django environment. This is mentioned in the plug-ins instructions.

Distribution Model Plugins

Name	Entry point	Purpose
History	ots.plugin.history.distribution_model:get_model	Test package distribution model based on last execution time

Publisher Plugins

Name	Entry point	Purpose
HTTP Logger	ots.plugin.logger.logger_plugin:LoggerPlugin	Plug-in for enabling HTTP based logging and monitoring
Email	ots.plugin.email.email_plugin:EmailPlugin	Plug-in for enabling email sending
QA-Reports	ots.plugin.qareports.qareports_plugin:QAReportsPlugin	Plug-in for sending results to QA Reports
History	ots.plugin.history.history_plugin:HistoryPlugin	Plug-in for storing execution times to database
Monitor	ots.plugin.monitor.monitor_plugin:MonitorPlugin	Plug-in for collecting statistical information

Conductor Plugins

Name	Entry point	Purpose
Rich-core	ots.plugin.conductor.richcore.richcore_plugin:RichCorePlugin	Plug-in for uploading rich-core dumps to post-processing. Rich-core plug-in is part of crash reporting functionality.