On Thu, Mar 14, 2013 at 6:22 AM, Riccardo Bicelli <r.bice...@gmail.com> wrote: > > Hello, > >> This is possible (you can have rules for the instance attributes), > > Could you provide me an example?
This should do it: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_using_rules_to_control_resource_options.html > >> *but* it is a really bad idea for administrative reasons. It'll be a >> nightmare to remember, and bite you in every single script. It's usually a >> lot better to rename the ports via udev/ipaddr rules. Not sure how to do >> that for IB > > In this case is not possible (or is more nightmare than defining parameter > in RA), because is the target created by SCST, that is not mapped to a > device but only creates control interface under sysfs. > Each port has a specific GUID. > I need to control where to migrate the scsi target, because "different > boards do different things". > > Regards, > Riccardo > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org