Current File : //usr/lib/python2.7/site-packages/salt/states/jboss7.pyc
�
���^c @@ s- d Z d d l m Z m Z m Z d d l Z d d l Z d d l Z d d l Z d d l j
j Z d d l m
Z
d d l m Z e j e � Z e d d � Z d � Z d � Z d d � Z d d
� Z d d � Z d � Z d d
� Z d � Z d d d � Z d e d � Z d d � Z! d � Z" d S( ub
Manage JBoss 7 Application Server via CLI interface
.. versionadded:: 2015.5.0
This state uses the jboss-cli.sh script from a JBoss or Wildfly installation and parses its output to determine the execution result.
In order to run each state, a jboss_config dictionary with the following properties must be passed:
.. code-block:: yaml
jboss:
cli_path: '/opt/jboss/jboss-7.0/bin/jboss-cli.sh'
controller: 10.11.12.13:9999
cli_user: 'jbossadm'
cli_password: 'jbossadm'
If the controller doesn't require a password, then the cli_user and cli_password parameters are optional.
Since same dictionary with configuration will be used in all the states, it may be more convenient to move JBoss configuration and other properties
to the pillar.
Example of application deployment from local filesystem:
.. code-block:: yaml
application_deployed:
jboss7.deployed:
- salt_source:
target_file: '/tmp/webapp.war'
- jboss_config: {{ pillar['jboss'] }}
For the sake of brevity, examples for each state assume that jboss_config is contained in the pillar.
i ( t absolute_importt print_functiont unicode_literalsN( t CommandExecutionError( t sixc C@ s� t j d | � i | d 6t d 6i d 6d d 6} t } i } t d d | d | d
| � } | d r| d } | r�t d d | d | d
| � } | d r� | | d d
<n t | d <d | d | d <| St } t d d | d | d | d
| � }
|
d r| | d d <n t | d <d |
d | d <| St d d | d | d
| � } | d rm| d } qt | d <d | d | d <| Sq�t d d | d | d | d
| � }
|
d s�t | d <d |
d | d <n
d | d <t d d | d | d
| � } | d } n� | d d k r�t d d | d | d | d
| � }
|
d r�t d d | d | d
| � } | d } d | d <q�t | d <d |
d | d <n t d j | d � � � | d r�t j d | � t j d | � t j | | � } | j � } t
| � d k r>t } t | | | � | d d! <n | j � } t
| � d k rt } t | | | � | d d
<n | j
� } t
| � d k r�t } t | | | � | d d" <n | s�d# | d <q�n | S($ u�
Ensures that a datasource with given properties exist on the jboss instance.
If datasource doesn't exist, it is created, otherwise only the properties that are different will be updated.
name
Datasource property name
jboss_config
Dict with connection properties (see state description)
datasource_properties
Dict with datasource properties
recreate : False
If set to True and datasource exists it will be removed and created again. However, if there are deployments that depend on the datasource, it will not me possible to remove it.
profile : None
The profile name for this datasource (domain mode only)
Example:
.. code-block:: yaml
sampleDS:
jboss7.datasource_exists:
- recreate: False
- datasource_properties:
driver-name: mysql
connection-url: 'jdbc:mysql://localhost:3306/sampleDatabase'
jndi-name: 'java:jboss/datasources/sampleDS'
user-name: sampleuser
password: secret
min-pool-size: 3
use-java-context: True
- jboss_config: {{ pillar['jboss'] }}
- profile: full-ha
uE ======================== STATE: jboss7.datasource_exists (name: %s) u nameu resultu changesu u commentu jboss7.read_datasourcet jboss_configt namet profileu successu jboss7.remove_datasourceu removedu% Could not remove datasource. Stdout: u stdoutu jboss7.create_datasourcet datasource_propertiesu createdu% Could not create datasource. Stdout: u# Could not read datasource. Stdout: u jboss7.update_datasourcet new_propertiesu Could not update datasource. u Datasource updated.u err_codeu
JBAS014807u Datasource created.u Unable to handle error: {0}u failure-descriptionu ds_new_properties=%su ds_current_properties=%si u addedu changedu Datasource not changed.( t logt debugt Truet Falset __salt__R t formatt
dictdiffert difft addedt lent __format_ds_changest removedt changed( R R R t recreateR t rett has_changedt ds_current_propertiest ds_resultt
remove_resultt
create_resultt read_resultt ds_new_propertiest
update_resultR R R R ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyt datasource_exists8 s� #
%
%
%
c C@ s� t j d | | | � d } x� | D]� } t j d | � | | k r� | | k r� | | d t | | � d t | | � d 7} q# | | k r� | | d 7} q# | | k r# | | d t | | � d 7} q# q# W| S( Nu6 __format_ds_changes(keys=%s, old_dict=%s, new_dict=%s)u u key=%su :u ->u
( R
R t __get_ds_value( t keyst old_dictt new_dictt changest key( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR � s
3 &c C@ sI t j d | � | d k r d S| | d k r4 d St j | | � Sd S( Nu __get_value(dict,%s)u passwordu ***u undefined( R
R t NoneR t text_type( t dctR' ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR" � s c
C@ s� t j d | | � t j d | � i | d 6t d 6i d 6d d 6} t } xN| D]F} t j | | � } t d d | d
| d | � } | d r| d d
} | | k r�t d d | d | d
| d | � }
|
d r t } t | d d | | | � qt |
d � � q�qR | d d k r�t d d | d | d
| d | � } | d rut } t | d d | | � q�t | d � � qR t | d � � qR W| r�d | d <n | S( u�
Ensures that given JNDI binding are present on the server.
If a binding doesn't exist on the server it will be created.
If it already exists its value will be changed.
jboss_config:
Dict with connection properties (see state description)
bindings:
Dict with bindings to set.
profile:
The profile name (domain mode only)
Example:
.. code-block:: yaml
jndi_entries_created:
jboss7.bindings_exist:
- bindings:
'java:global/sampleapp/environment': 'DEV'
'java:global/sampleapp/configurationFile': '/var/opt/sampleapp/config.properties'
- jboss_config: {{ pillar['jboss'] }}
uP ======================== STATE: jboss7.bindings_exist (name: %s) (profile: %s) u bindings=%su nameu resultu changesu Bindings not changed.u commentu jboss7.read_simple_bindingt binding_nameR R u successu valueu jboss7.update_simple_bindingt valueu changedu failure-descriptionu err_codeu
JBAS014807u jboss7.create_simple_bindingu addedu Bindings changed.( R
R R R
R R) R t __log_binding_changeR ( R R t bindingsR R R R' R, t query_resultt
current_valueR R ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyt bindings_exist� s8
%
%
c C@ sl | | k r d | | <n | d k rD | | c | d | d 7<n$ | | c | d | d | d 7<d S( Nu u :u
u ->( R( ( R& t type_R' t newt old( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR- s
c
C@ s� t j d | � i | d 6t d 6i d 6d d 6} d } t | | � \ } } | s` t | | � St | � \ } } t j d | � t j d | � t d | d
| � } | d k r� t | | � St | | � \ } }
} | s� t | | � St j d |
� |
d k r)t d | |
� |
| d d
<n t d d | d | � } t j d | � | d r�t d d d
| � } | | d <| | d d <n+ t d d j
| � d
| � } t | | � S| S( u\ Ensures that the given application is deployed on server.
jboss_config:
Dict with connection properties (see state description)
salt_source:
How to find the artifact to be deployed.
target_file:
Where to look in the minion's file system for the artifact to be deployed (e.g. '/tmp/application-web-0.39.war'). When source is specified, also specifies where to save the retrieved file.
source:
(optional) File on salt master (e.g. salt://application-web-0.39.war). If absent, no files will be retrieved and the artifact in target_file will be used for the deployment.
undeploy:
(optional) Regular expression to match against existing deployments. When present, if there is a deployment that matches the regular expression, it will be undeployed before the new artifact is deployed.
Examples:
Deployment of a file from minion's local file system:
.. code-block:: yaml
application_deployed:
jboss7.deployed:
- salt_source:
target_file: '/tmp/webapp.war'
- jboss_config: {{ pillar['jboss'] }}
It is assumed that /tmp/webapp.war was made available by some
other means. No applications will be undeployed; if an existing
deployment that shares that name exists, then it will be replaced
with the updated version.
Deployment of a file from the Salt master's file system:
.. code-block:: yaml
application_deployed:
jboss7.deployed:
- salt_source:
source: salt://application-web-0.39.war
target_file: '/tmp/application-web-0.39.war'
undeploy: 'application-web-.*'
- jboss_config: {{ pillar['jboss'] }}
Here, application-web-0.39.war file is downloaded from Salt file system to /tmp/application-web-0.39.war file on minion.
Existing deployments are checked if any of them matches 'application-web-.*' regular expression, and if so then it
is undeployed before deploying the application. This is useful to automate deployment of new application versions.
If the source parameter of salt_source is specified, it can use
any protocol that the file states use. This includes not only
downloading from the master but also HTTP, HTTPS, FTP,
Amazon S3, and OpenStack Swift.
u< ======================== STATE: jboss7.deployed (name: %s) u nameu resultu changesu u commentu resolved_source=%su get_artifact_comment=%st new_commentt current_commentu
deployment=%su jboss7.undeployu
undeployedu
jboss7.deployR t source_fileu deploy_result=%su successu Deployment completed.u deployeduJ Deployment failed
return code={retcode}
stdout='{stdout}'
stderr='{stderr}N( R
R R t __validate_argumentst _errort __get_artifactt __append_commentR( t __find_deploymentR R (
R R t salt_sourceR t commentt validate_successt validate_commentt resolved_sourcet get_artifact_commentt find_successt
deploymentt find_commentt
deploy_result( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyt deployed s> 5
c C@ sm t | d d d g � \ } } | d k rB t } t d | � } n t | d d g | | � \ } } | | f S( Nu jboss_configu cli_pathu
controlleru No salt_source definedu salt_sourceu target_file( t __check_dict_containsR( R
R; ( R R= t resultR> ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR8 p s !c C@ s� d } t } d } t d | � } | d k r� d | k r� | d r� t j | d � } x] | D]R } | j | � r^ | d k r� t } d j | d d j | � � } q� | } q^ q^ Wn | | | f S( Nu u jboss7.list_deploymentsu undeployu� More than one deployment matches regular expression: {0}.
For deployments from Salt file system deployments on JBoss are searched to find one that matches regular expression in 'undeploy' parameter.
Existing deployments: {1}u ,( R( R R t ret compilet matchR
R t join( R R= RI t successR> t deploymentst
deployment_reRD ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR< y s "
c ! C@ s� d } d } | d k r. t j d � d } n�t | t � r�t j d � d | k r�y t d d | d d d d | d d
d d d d d d
d d d d d d t d d d d d t d d � \ } } } t d d | d d | d d d | d d | d d d
d d d d d d t d d d t d d d t d d d d � } | d rW| d } n
| d } Wq�t k
r�} t j t
j � � d j | � } q�Xq�| d } d! } n | | f S(" Nu salt_source == Noneu No salt_source definedu file from salt masteru sourceu file.get_managedR u target_filet templatet sourcet source_hasht source_hash_namet usert groupt modet attrst saltenvt contextt defaultst skip_verifyt kwargsu file.manage_filet sfnR t
source_sumt backupt makedirst show_difft contentst dir_modeu resultu commentu Unable to manage file: {0}u (
R( R
R t
isinstancet dictR t __env__R
R t Exceptiont tracebackt
format_excR ( R= RA R> R^ R_ t comment_t
manage_resultt e( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR: � sd
i< i c C@ s� t j d | � i | d 6t d 6i d 6d d 6} t d | � } | d s] | d d k ru t | d <d | d <| St d | � } | d s� d
| d k s� d | d k r�d } d } x^ | d k s� | d s� | d d k r| | k rt j | � | | 7} t d | � } q� W| d r[| d d k r[t | d <d | d <d | d d <q�t | d <d j | � | d <| d s�t d | d � | d <q�t d j | d � | d � | d <n t | d <d | d | d <| S( u�
Reloads configuration of jboss server.
jboss_config:
Dict with connection properties (see state description)
timeout:
Time to wait until jboss is back in running state. Default timeout is 60s.
interval:
Interval between state checks. Default interval is 5s. Decreasing the interval may slightly decrease waiting time
but be aware that every status check is a call to jboss-cli which is a java process. If interval is smaller than
process cleanup time it may easily lead to excessive resource consumption.
This step performs the following operations:
* Ensures that server is in running or reload-required state (by reading server-state attribute)
* Reloads configuration
* Waits for server to reload and be in running state
Example:
.. code-block:: yaml
configuration_reloaded:
jboss7.reloaded:
- jboss_config: {{ pillar['jboss'] }}
u< ======================== STATE: jboss7.reloaded (name: %s) u nameu resultu changesu u commentu
jboss7.statusu successu runningu reload-requiredu` Cannot reload server configuration, it should be up and in 'running' or 'reload-required' state.u
jboss7.reloadu Operation failed: Channel closedu stdoutuN Communication error: java.util.concurrent.ExecutionException: Operation failedi u Configuration reloadedu
configurationu reloadedu> Could not reload the configuration. Timeout ({0} s) exceeded. u& Could not connect to JBoss controller.u Server is in {0} stateu+ Could not reload the configuration, stdout:( u runningu reload-requiredN(
R
R R R R
R( t timet sleepR R; ( R R t timeoutt intervalR t statusRI t wait_time( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyt reloaded� s@
6
'
u c C@ sT xG | D]? } | t j | � k r t } t d j | | � | � } q q W| | f S( Nu Missing {0} in {1}( R t iterkeysR
R; R ( R* t dict_nameR# R> RI R' ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyRH s
"c C@ sH | d k r | d k r d S| d k r, | S| d k r< | S| d | S( Nu u
( R( ( R5 R6 ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR; s c C@ s t | d <| | d <| S( Nu resultu comment( R
( R t err_msg( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyR9 " s
(# t __doc__t
__future__R R R Rn t loggingRJ Ri t salt.utils.dictdiffert utilsR t salt.exceptionsR t salt.extR t getLoggert __name__R
R
R( R! R R" R1 R- RG R8 R< R: Rt R RH R; R9 ( ( ( s6 /usr/lib/python2.7/site-packages/salt/states/jboss7.pyt <module>% s, {
= _ ?D
Mini Shell