Current File : //lib/python2.7/site-packages/salt/beacons/service.pyo
�
���^c @@ s� d Z d d l m Z m Z d d l Z d d l Z d d l Z d d l m Z e j e
� Z i Z d Z
d � Z d � Z d S( u%
Send events covering service status
i ( t absolute_importt unicode_literalsN( t mapu servicec C@ s� t | t � s t d f Si } t t | j | � � d | k rK t d f Sx3 | d D]' } t | d | t � sV t d f SqV Wt d f S( u+
Validate the beacon configuration
u0 Configuration for service beacon must be a list.u servicesu3 Configuration for service beacon requires services.u@ Configuration for service beacon must be a list of dictionaries.u Valid beacon configuration( t
isinstancet listt FalseR t updatet dictt True( t configt _configt config_item( ( s8 /usr/lib/python2.7/site-packages/salt/beacons/service.pyt validate s
c C@ s� g } i } t t | j | � � xh| j d i � D]T} i } | d | } i t d | � d 6| | <| | d <| | d <t j � } | s� i } n d | k r� t | d <n d | k r� t | d <n d | k r� t | d <n d | k r� d
| d <n d | k rK| | d rK| d } t j j
| � r:t n t | | d <n d | k r|| d t k r|| t k r�| | t | <| d d
k r�| t | d <q�| d s�q5 q�| j | � n t | d | | d k r | | t | <| d d
k r
| t | d <q | j | � n d t | k r�t
t | t | d � � } | | d k ryt | d =| j | � qyq�q5 | j | � q5 W| S(
us
Scan for the configured services and fire events
Example Config
.. code-block:: yaml
beacons:
service:
- services:
salt-master: {}
mysql: {}
The config above sets up beacons to check for
the salt-master and mysql services.
The config also supports two other parameters for each service:
`onchangeonly`: when `onchangeonly` is True the beacon will fire
events only when the service status changes. Otherwise, it will fire an
event at each beacon interval. The default is False.
`delay`: when `delay` is greater than 0 the beacon will fire events only
after the service status changes, and the delay (in seconds) has passed.
Applicable only when `onchangeonly` is True. The default is 0.
`emitatstartup`: when `emitatstartup` is False the beacon will not fire
event when the minion is reload. Applicable only when `onchangeonly` is True.
The default is True.
`uncleanshutdown`: If `uncleanshutdown` is present it should point to the
location of a pid file for the service. Most services will not clean up
this pid file if they are shutdown uncleanly (e.g. via `kill -9`) or if they
are terminated through a crash such as a segmentation fault. If the file is
present, then the beacon will add `uncleanshutdown: True` to the event. If
not present, the field will be False. The field is only added when the
service is NOT running. Omitting the configuration variable altogether will
turn this feature off.
Please note that some init systems can remove the pid file if the service
registers as crashed. One such example is nginx on CentOS 7, where the
service unit removes the pid file when the service shuts down (IE: the pid
file is observed as removed when kill -9 is sent to the nginx master
process). The 'uncleanshutdown' option might not be of much use there,
unless the unit file is modified.
Here is an example that will fire an event 30 seconds after the state of nginx
changes and report an uncleanshutdown. This example is for Arch, which
places nginx's pid file in `/run`.
.. code-block:: yaml
beacons:
service:
- services:
nginx:
onchangeonly: True
delay: 30
uncleanshutdown: /run/nginx.pid
u servicesu service.statusu runningu service_nameu tagu oncleanshutdownu
emitatstartupu onchangeonlyu delayi u uncleanshutdownu time( R R R t gett __salt__t timeR R t ost patht existst LAST_STATUSt appendt intt round( R t retR
t servicet ret_dictt service_configt currtimet filenamet elapsedtime( ( s8 /usr/lib/python2.7/site-packages/salt/beacons/service.pyt beacon, sV =
)
( t __doc__t
__future__R R R t loggingR t salt.ext.six.movesR t getLoggert __name__t logR t __virtualname__R R ( ( ( s8 /usr/lib/python2.7/site-packages/salt/beacons/service.pyt <module> s
Mini Shell