22.07.2016 00:38, Klaus Wenninger пишет:
> On 07/21/2016 06:40 PM, Andrei Borzenkov wrote:
>> 19.07.2016 18:24, Klaus Wenninger пишет:
>>> On 07/19/2016 04:17 PM, Ken Gaillot wrote:
On 07/19/2016 09:00 AM, Andrei Borzenkov wrote:
> On Tue, Jul 19, 2016 at 4:52 PM, Ken Gaillot
On 07/21/2016 06:40 PM, Andrei Borzenkov wrote:
> 19.07.2016 18:24, Klaus Wenninger пишет:
>> On 07/19/2016 04:17 PM, Ken Gaillot wrote:
>>> On 07/19/2016 09:00 AM, Andrei Borzenkov wrote:
On Tue, Jul 19, 2016 at 4:52 PM, Ken Gaillot wrote:
...
>> primitive
Thanks for all of the help!
On Thu, Jul 21, 2016 at 4:16 PM, Jan Pokorný wrote:
> On 21/07/16 16:02 -0400, Stephano-Shachter, Dylan wrote:
> > So I should be using "pcs cluster cib > file" to get the config and then
> > "pcs cluster cib-push --config file" to push it?
>
>
So I should be using "pcs cluster cib > file" to get the config and then
"pcs cluster cib-push --config file" to push it?
Also I shouldn't have to add --config to the pcs -f commands right?
On Thu, Jul 21, 2016 at 3:51 PM, Jan Pokorný wrote:
> On 21/07/16 13:52 -0500, Ken
On 21/07/16 13:52 -0500, Ken Gaillot wrote:
> On 07/21/2016 01:35 PM, Stephano-Shachter, Dylan wrote:
>> I want to put the pacemaker config for my two node cluster in puppet
>> but, since it is just one cluster, it seems overkill to use the corosync
>> module. If I just have puppet push cib.xml to
On 07/21/2016 02:20 PM, Stephano-Shachter, Dylan wrote:
> I am familiar with pcs cluster cib.
>
> What I am thinking of doing is running "pcs cluster cib --config >
> config.xml" to get a valid config.
>
> I will then put config.xml on the puppet server and have it push the
> file and run "pcs
I am familiar with pcs cluster cib.
What I am thinking of doing is running "pcs cluster cib --config >
config.xml" to get a valid config.
I will then put config.xml on the puppet server and have it push the file
and run "pcs cluster cib-push --config config.xml" every hour.
Will this cause any
On 07/21/2016 01:35 PM, Stephano-Shachter, Dylan wrote:
> Hello all,
>
> I want to put the pacemaker config for my two node cluster in puppet
> but, since it is just one cluster, it seems overkill to use the corosync
> module. If I just have puppet push cib.xml to each machine, will that
> work?
Hello all,
I want to put the pacemaker config for my two node cluster in puppet but,
since it is just one cluster, it seems overkill to use the corosync module.
If I just have puppet push cib.xml to each machine, will that work? To make
changes, I would just use pcs to update things and then copy
Okay! This is incredibly helpful. Thank you. After digging through the resource
agents, it looks like what I actually want is to use the implementation “lio-t”
since that uses the targetcli utilities.
--
[ jR ]
M: +1 (703) 628-2621
@: ja...@eramsey.org
there is no path to greatness;
21.07.2016 09:49, Ulrich Windl пишет:
Ken Gaillot schrieb am 19.07.2016 um 16:17 in
Nachricht
> :
>
> [...]
>> You're right -- if not told otherwise, Pacemaker will query the device
>> for the target list. In this
On 07/21/2016 08:49 AM, Ulrich Windl wrote:
Ken Gaillot schrieb am 19.07.2016 um 16:17 in
Nachricht
> > :
> >
> > [...]
>
> >> You're right -- if not told otherwise, Pacemaker will query the device>>
> >> for the
Ken Gaillot wrote:
> On 07/20/2016 07:32 PM, Andrew Beekhof wrote:
> > On Thu, Jul 21, 2016 at 2:47 AM, Adam Spiers wrote:
> >> Ken Gaillot wrote:
> >>> Hello all,
> >>>
> >>> I've been meaning to address the implementation of "reload"
Thanks for the response, but as I indicated in a previous response, lio-utils
is deprecated, having been replaced by targetcli. It seems as though Pacemaker
is trying to invoke a set of utilities/libraries that aren’t currently
supported to perform iSCSI Target/LUN clustering. My question
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 dlm_controld is first started outside the
cluster
15 matches
Mail list logo