<br clear="all"><br><div class="gmail_quote">On Tue, Jul 26, 2011 at 9:52 PM, Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Thu, Jul 21, 2011 at 2:36 AM, Bobbie Lind <<a href="mailto:blind@sms-fed.com" target="_blank">blind@sms-fed.com</a>> wrote:<br>
> Hi group,<br>
><br>
> I am running a 6 node system, 4 of which mount the LUNs for my Lustre file<br>
> system. I currently have 29 LUNs per server set up in 4 Resource Groups. I<br>
> understand the default startup/shudown order of the resource but I was<br>
> wondering if there is a way to override that and have all the resources in<br>
> the group startup or shutdown at the same time. Ideally what I am looking<br>
> for is all the resources in the group OSS1group to startup and shutdown at<br>
> the same time since none of them are dependent on each other, they just<br>
> belong on the same server.<br>
<br>
</div>I'd suggest just not using a group in this case.<br>
If all you want is colocation, use a colocation set.<br></blockquote><div><br>Thank you. That did exactly what I was looking for.<br>
Changing the groups to a colocation and adding a Dummy resource to map to the specific servers fixed the issue.<br>
<br>
I have attached an updated crm configuration for reference.<br><br></div></div>Bobbie Lind<br>Systems Engineer<br><i><b>Solutions Made Simple, Inc (SMSi)</b></i><br>