Hi, On Mon, Aug 17, 2009 at 01:46:14PM -0600, Dan Urist wrote: > Andrew Beekhof wrote: > > > Possibly, but not in this case. > > I'd guess you had some constraints that reference the vsvg1 resource. > > > > Deleting the resource would therefore leave dangling dependancies > > which is not allowed. > > Thanks, that makes sense.
The crm shell removes depending constraints, that's why you were able to delete the resource. > > Btw. if you used the "shadow" feature of the crm shell, you'd have > > been able to make it into a group without deleting or stopping it. > > I'm actually managing my config with a homegrown perl script that merges > chunks of XML together and then installs a new CIB. This way I can keep > a resource definition and the relevant constraints together in the same > file, which keeps things clearer for me, and since I have four clusters > that all run similar services, it simplifies management since I can just > copy the identical pieces of XML around and use templates for the rest. Why did you use a custom script and not the crm shell? BTW, the crm shell is also scriptable. Thanks, Dejan > -- > Dan Urist > dur...@ucar.edu > 303-497-2459 (office) > 303-961-2675 (cell) > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
