<div dir="ltr">what happen if you try ping db0 from your physical host?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/5 James Oakley <span dir="ltr"><<a href="mailto:jfunk@funktronics.ca" target="_blank">jfunk@funktronics.ca</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thursday, December 5, 2013 9:21:18 AM "Lars Marowsky-Bree" <<a href="mailto:lmb@suse.com">lmb@suse.com</a>> wrote:<br>
> > primitive lxc_db0 @lxc \<br>
> > params container="db0" config="/var/lib/lxc/db0/config" \<br>
> > meta remote-node="db0"<br>
><br>
> I think this is because crm doesn't know about the remote-node<br>
> attribute. It can render it, but it doesn't pass verify. Kristoffer?<br>
<br>
</div>That's why I used crm_resource to add it. If I dump the config with cibadmin, it looks consistent with the example here:<br>
<br>
<a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#_mile_high_view_of_configuration_steps" target="_blank">http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#_mile_high_view_of_configuration_steps</a><br>
<br>
<primitive id="lxc_db0" template="lxc"><br>
<instance_attributes id="lxc_db0-instance_attributes"><br>
<nvpair name="container" value="db0" id="lxc_db0-instance_attributes-container"/><br>
<nvpair name="config" value="/var/lib/lxc/db0/config" id="lxc_db0-instance_attributes-config"/><br>
</instance_attributes><br>
<meta_attributes id="lxc_db0-meta_attributes"><br>
<nvpair id="lxc_db0-meta_attributes-remote-node" name="remote-node" value="db0"/><br>
<nvpair id="lxc_db0-meta_attributes-target-role" name="target-role" value="Started"/><br>
</meta_attributes><br>
</primitive><br>
<br>
However, the nodes do not show up in crm status output as in the examples in the documentation. I also tried creating a resource to run on a remote node, but it said the node didn't exist.<br>
<div class="im"><br>
<br>
> > What am I missing? Is this somehow disabled on non-pcs clusters, and if so,<br>
> > why is the pacemaker-remote package even in the openSUSE repositories and<br>
> > pcs not?<br>
><br>
> We do provide pcs, but not as part of 13.1. Note that the preferred<br>
> shell on openSUSE/SLE HA is and will remain crmsh, not pcs.<br>
<br>
</div>Oh yes, I plan to use whatever is provided/recommend by SuSE, as I always have. I am just confused why pacemaker-remote is provided if it only works with pcs, which is not. However, it looks like it's not even a crm vs pcs thing, but a problem with Pacemaker itself as provided.<br>
<div class="im"><br>
<br>
> pacemaker-remote isn't fully tested on openSUSE yet. We welcome feedback<br>
> and patches. ;-)<br>
<br>
</div>I would be happy to provide feedback or a patch, but I don't even know where to start on this. All I can say is that pacemaker-remoted itself is running fine and listening on it's port. It's the Pacemaker side I'm having trouble with.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
James Oakley<br>
<a href="mailto:jfunk@funktronics.ca">jfunk@funktronics.ca</a><br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>esta es mi vida e me la vivo hasta que dios quiera
</div>