Changes between Version 8 and Version 9 of Infrastructure/AdminScripts


Ignore:
Timestamp:
04/07/2013 05:03:23 PM (4 years ago)
Author:
GaretJax
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Infrastructure/AdminScripts

    v8 v9  
    100100=== How to start/stop/restart services ===
    101101
     102Each service has its own Fabric namespace. Actions are available as part of each namespace. For example, the `dns` service can be started, stopped,  and restarted as follows:
     103
     104{{{
     105#!sh
     106fab dns.start
     107}}}
     108{{{
     109#!sh
     110fab dns.stop
     111}}}
     112{{{
     113#!sh
     114fab dns.restart
     115}}}
     116
    102117=== How to update existing services ===
     118
     119Similarly as done for managing the running states, an `update` task lives in each service namespace. It can be run as follows:
     120
     121{{{
     122#!sh
     123fab dns.update
     124}}}
     125
     126Note that a restart is still needed after updating a service.
    103127
    104128=== How to install new services ===
    105129
     130A service which was just added to the fabfile can be installed by running its `install` task:
     131
     132{{{
     133#!sh
     134fab dns.install
     135}}}
     136
     137Note, however, that while the previous actions did not require root privileges (being member of the `service-admin` group was sufficient), installing a new service requires to be able to `sudo` to `root`. This is needed to create the necessary users, install additional packages and create the base environment.
     138
    106139=== How to give service administration privileges to another user ===
     140
     141An existing user which does not currently have service administration tasks can be added to the `service-admin` group by executing the `make_service_admin` task and supplying a username:
     142{{{
     143#!sh
     144fab make_service_admin:<username>
     145}}}
    107146
    108147=== How to setup a new server from scratch ===