Changes between Version 1 and Version 2 of Documentation/Instructions/KNUClusterAdminInstructions


Ignore:
Timestamp:
Aug 4, 2015 8:28:56 PM (9 years ago)
Author:
Andrii Salnikov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/Instructions/KNUClusterAdminInstructions

    v1 v2  
    1 = Instructuion for KNU Cluster administrators and operators =
     1= Basic Instructuions for KNU Cluster Administrators and Operators =
    22== Root access to the nodes ==
    33Getting root access by means of {{{su}}} or {{{sudo}}} is prohibited.
    … …  
    2525
    2626== Managing services ==
    27 KNU Cluster is RHEL7-based and use Systemd for services management. Get ready you cannot find LSB scripts and [[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/chap-Managing_Services_with_systemd.html|obtain systemd basic skills]].
     27KNU Cluster is RHEL7-based and use Systemd for services management. Get ready to works without LSB scripts and [[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/chap-Managing_Services_with_systemd.html|obtain systemd basic skills]].
    2828
     29High Availablity services that should be maintened accross the cluster rely on Pacemaker operation.
     30
     31Services under Pacemaker control '''SHOULD NOT''' be stoped/started/restarted manually! This includes:
     32 - All clustered filesystems
     33 - A-nodes DRBD
     34 - A-nodes NFS
     35 - A-nodes FhGFS Management LXC container
     36 - PBS Mom
     37 - FhGFS Client
     38
     39In case of node/service maintenance that should be done without Pacemaker interaction, corresponding node '''SHOULD BE''' put into standby mode with {{{pcs cluster standby <node>}}}. To unstandby use {{{pcs cluster unstandby <node>}}}.