<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hello,</p>
<p>It seems pacemaker has a weird way to manage resource:</p>
<p>And also it seems it's focusing more on defining individual resources and not to much flexibility for creating resource Groups</p>
<p><br /></p>
<p>Now, let's take this example: RG1 + deps [ fs1,fs2,fs3] = > ALL 3 file system must be mounted before starting of daemon</p>
<p>1. RG = rg1 + following resources: fs1, fs2,fs3, ocf:heartbeat[my custom systemd script]</p>
<p><br /></p>
<p>Ok, So i define the rg + fs1,fs2, ( by mistake heartbeat ), fs3</p>
<p>So in this case RG1 will fail to start as the order of defining resources instead of fs1, fs2,fs3, heartbeat is fs1, fs2,heartbea,fs3</p>
<p>Now, what solution exists ? export cib, edit cib and re-import cib; what if I will need a new fs:fs4, so what: export cib, create new resource inside exported cib and re-import it.</p>
<p><br /></p>
<p>Well, this approach seems way to moronic; wouldn't be better when create a resource to be able to specify resid, or a much easier way to manipulate resource order ??</p>
</body></html>