23.07.2016 01:37, Nate Clark пишет:
> Hello,
>
> I am running pacemaker 1.1.13 with corosync and think I may have
> encountered a start up timing issue on a two node cluster. I didn't
> notice anything in the changelog for 14 or 15 that looked similar to
> this or open bugs.
>
> The rough out
23.07.2016 00:07, TEG AMJG пишет:
...
> Master: kamailioetcclone
> Meta Attrs: master-max=1 master-node-max=1 clone-max=2 clone-node-max=1
> notify=true
> Resource: kamailioetc (class=ocf provider=linbit type=drbd)
>Attributes: drbd_resource=kamailioetc
>Operations: start interval=0s
Hi
I am having a problem with a very simple Active/Passive cluster using DRBD.
This is my configuration:
Cluster Name: kamcluster
Corosync Nodes:
kam1vs3 kam2vs3
Pacemaker Nodes:
kam1vs3 kam2vs3
Resources:
Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2)
Attributes:
Great! Thanks for the pointer! Any ideas on the other stuff I was asking about
(i.e. how to use any other backstore other than block with Pacemaker)?
--
[ jR ]
@: ja...@eramsey.org
there is no path to greatness; greatness is the path
On 7/22/16, 12:24 PM, "Andrei Borzenkov"
From the command line parameters for the pcs resource create or is it something
internal (not exposed to the user)? If the former, what parameter?
--
[ jR ]
@: ja...@eramsey.org
there is no path to greatness; greatness is the path
On 7/22/16, 11:08 AM, "Andrei Borzenkov"
22.07.2016 09:52, Ulrich Windl пишет:
> That could be. Should there be a node list to configure, or can't the agent
> find out itself (for SBD)?
>
It apparently does it already
gethosts)
echo `sbd -d $sbd_device list | cut -f2 | sort | uniq`
exit 0
22.07.2016 17:43, Jason A Ramsey пишет:
> Additionally (and this is just a failing on my part), I’m
> unclear as to where the resource agent is fed the value for
> “${OCF_RESOURCE_INSTANCE}” given the limited number of parameters one
> is permitted to supply with “pcs resource create…”
>
It is
I’m struggling to understand how to fully exploit the capabilities of targetcli
using the Pacemaker resource agent for iSCSILogicalUnit. From this block of
code:
lio-t)
# For lio, we first have to create a target device, then
# add it to the Target Portal Group as an LU.
Hello,
On 07/21/2016 09:31 PM, Da Shi Cao wrote:
I've built the dlm_tool suite using the source from
https://git.fedorahosted.org/cgit/dlm.git/log/. The resource uisng
ocf:pacemaker:controld will always fail to start because of timeout, even if
start timeout is set to 120s! But if
On 21/07/16 21:51 +0200, Jan Pokorný wrote:
> Yes, it's counterintuitive to have this asymmetry and it could be
> made to work with some added effort at the side of pcs with
> the original, disapproved, sequence as-is, but that's perhaps
> sound of the future per the referenced pcs bug.
> So take
>>> Andrei Borzenkov schrieb am 21.07.2016 um 18:39 in
Nachricht :
> 21.07.2016 09:49, Ulrich Windl пишет:
> Ken Gaillot schrieb am 19.07.2016 um 16:17 in
Nachricht
>>
The manual "Pacemaker 1.1 Clusters from Scratch" gives the false impression
that gfs2 relies only on dlm, but I cannot make it work without gfs_controld.
Again this little daemon is heavily coupled with cman. I think it is quite hard
to use gfs2 in a cluster build only using
12 matches
Mail list logo