06.12.2013 19:13, James Oakley wrote:
> On Thursday, December 5, 2013 9:55:47 PM "Vladislav Bogdanov"
> wrote:
>
>> Does 'db0' resolve to a correct IP address? If not, then you probably
>> want either fix that or use remote-addr option as well. I saw that you
>> can ping/ssh that container, but
On Thursday, December 5, 2013 9:55:47 PM "Vladislav Bogdanov"
wrote:
> Does 'db0' resolve to a correct IP address? If not, then you probably
> want either fix that or use remote-addr option as well. I saw that you
> can ping/ssh that container, but it is not clear did you use 'db0' name
> for th
06.12.2013 11:41, Lars Marowsky-Bree wrote:
> On 2013-12-06T08:55:47, Vladislav Bogdanov wrote:
>
>> BTW, pacemaker cib accepts any meta attributes (and that is very
>> convenient way for me to store some 'meta' information), while crmsh
>> limits them to a pre-defined list. While that is probabl
On 2013-12-06T08:55:47, Vladislav Bogdanov wrote:
> BTW, pacemaker cib accepts any meta attributes (and that is very
> convenient way for me to store some 'meta' information), while crmsh
> limits them to a pre-defined list. While that is probably fine for
> novices, that limits some advanced usa
05.12.2013 19:57, James Oakley wrote:
> I have Pacemaker 1.1.10 cluster running on openSUSE 13.1 and I am
> trying to get pacemaker-remote working so I can manage resources in LXC
> containers. I have pacemaker_remoted running in the containers.
>
> However, I can't seem to get crm configured to t
On Thursday, December 5, 2013 11:51:01 AM "Lars Marowsky-Bree"
wrote:
> > 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.
>
> Right. Do they show u
On 2013-12-05T10:10:08, James Oakley wrote:
> That's why I used crm_resource to add it. If I dump the config with cibadmin,
> it looks consistent with the example here:
>
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#_mile_high_view_of_configuration_steps
Right
On Thursday, December 5, 2013 10:21:01 AM "emmanuel segura"
wrote:
> what happen if you try ping db0 from your physical host?
Yes, networking is fine. I can ping ssh, etc. and there is no firewall running.
--
James Oakley
jf...@funktronics.ca
___
Pa
what happen if you try ping db0 from your physical host?
2013/12/5 James Oakley
> On Thursday, December 5, 2013 9:21:18 AM "Lars Marowsky-Bree" <
> l...@suse.com> wrote:
> > > primitive lxc_db0 @lxc \
> > > params container="db0" config="/var/lib/lxc/db0/config" \
> > > meta rem
On Thursday, December 5, 2013 9:21:18 AM "Lars Marowsky-Bree"
wrote:
> > primitive lxc_db0 @lxc \
> > params container="db0" config="/var/lib/lxc/db0/config" \
> > meta remote-node="db0"
>
> I think this is because crm doesn't know about the remote-node
> attribute. It can render
Follow the Lars comment "I think this is because crm doesn't know about the
remote-node
attribute"
2013/12/5 James Oakley
> On Thursday, December 5, 2013 9:08:46 AM "emmanuel segura" <
> emi2f...@gmail.com> wrote:
> > did you try in this following way?
> >
> > primitive lxc_db0 ocf:heartbeat:lx
On Thursday, December 5, 2013 9:08:46 AM "emmanuel segura"
wrote:
> did you try in this following way?
>
> primitive lxc_db0 ocf:heartbeat:lxc \
> params container="db0" config="/var/lib/lxc/db0/config" \
> meta remote-node="db0"
I get the same behavior this way, unfortunately.
--
James Oakle
On 2013-12-05T08:57:48, James Oakley wrote:
> Unfortunately, crm does not let me add it. I tried forcing it using
> crm_resource, but it's not working. It shows up now:
>
> primitive lxc_db0 @lxc \
> params container="db0" config="/var/lib/lxc/db0/config" \
> meta remote-node="d
did you try in this following way?
primitive lxc_db0 ocf:heartbeat:lxc \
params container="db0" config="/var/lib/lxc/db0/config" \
meta remote-node="db0"
2013/12/5 James Oakley
> I have Pacemaker 1.1.10 cluster running on openSUSE 13.1 and I am trying
> to get pacemaker-remote
I have Pacemaker 1.1.10 cluster running on openSUSE 13.1 and I am trying to get
pacemaker-remote working so I can manage resources in LXC containers. I have
pacemaker_remoted running in the containers.
However, I can't seem to get crm configured to talk to the daemons. The only
documentation I
15 matches
Mail list logo