Whamcloud - gitweb
EX-6372 lipe: Remove colocation constraint from lamigo/lpurge resources
authorGaurang Tapase <gtapase@ddn.com>
Fri, 11 Nov 2022 18:26:30 +0000 (23:56 +0530)
committerAndreas Dilger <adilger@whamcloud.com>
Sat, 19 Nov 2022 17:32:17 +0000 (17:32 +0000)
commiteae3dbffd9624959eef8a1c153f0ff2fddc2f63d
tree1a95cd0aaff29f1ba494abd5bbc5f2dece060f6c
parent451b4ac514dd03c4fe91726da2f95a1f5575a5a6
EX-6372 lipe: Remove colocation constraint from lamigo/lpurge resources

We now rely on node attribute *-recovered to start HP resources.
Hence, starting ES 5.2.7 colocation constraints are not needed
to start resources. Moreover, with the rules added, base FS
target resources cannot start on the designated nodes as node
get -inf score. This prevents resources failback in case original
server comes back up after failover.

Test-Parameters: trivial

Signed-off-by: Gaurang Tapase <gtapase@ddn.com>
Change-Id: I890b12bf8a0d75d618a041be1eb27960dc62cc7e
Reviewed-on: https://review.whamcloud.com/c/ex/lustre-release/+/49179
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Artur Novik <anovik@ddn.com>
Reviewed-by: Minh Diep <mdiep@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
lipe/scripts/stratagem-hp-config.sh