Hi Vladislav, On Mon, Oct 20, 2014 at 09:03:40AM +0300, Vladislav Bogdanov wrote: > Hi Kristoffer, > > do you plan to add support for recently added "remote node attributes" > feature to chmsh? > > Currently (at least as of 2.1, and I do not see anything relevant in the > git log) crmsh fails to update CIB if it contains node attributes for > remote (bare-metal) node, complaining that duplicate element is found.
No wonder :) The uname effectively dubs as an element id. > But for bare-metal nodes it is natural to have ocf:pacemaker:remote > resource with name equal to remote node uname (I doubt it can be > configured differently). Is that required? > If I comment check for 'obj_id in id_set', then it fails to update CIB > because it inserts above primitive definition into the node section. Could you please show what would the CIB look like with such a remote resource (in crmsh notation). Given that nodes are for the most part referenced by uname (instead of by id), do you think that a configuration where a primitive element is named the same as a node, the user can handle that in an efficient manner? (NB: No experience here with ocf:pacemaker:remote :) Cheers, Dejan > > Best, > Vladislav > _______________________________________________ > 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
