On Thu, Aug 11, 2011 at 5:37 PM, Ulrich Windl <ulrich.wi...@rz.uni-regensburg.de> wrote: > Hi! > > Using crm shell, you cannot rename a running resource. However I managed to > do it via a shadow cib: I renamed the resource in the shadow cib, then > committed the shadow cib. > From the XML changes, I got the impression that the old primitive is removed, > and then the new primitive is added. This caused the old resource to be > stopped, the new one to be started, and one resource that was a successor in > the group to be restarted. > > There was a temporary "active orphan" (the old name) and "Configuration > WARNINGs found during PE processing", but that vanished when the states > changed (transitions completed). > > So obviously there is no rename operation for resources. However when you add > more and more resources to your cluster, one might find the point where some > renaming for consistency might be a good idea. In priniple that could be done > online without taking any resource down, but LRM seems to be not prepared for > that. Are there any technical reasons for that?
The resource name is the equivalent of a primary key in a database table. Its the sole point of comparison when deciding if two resources are the same, therefor rename is not a valid operation to consider. Any implementation would have to use delete + create underneath. > > Regards, > Ulrich > > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
