All,
We are pleased to announce the general availability of kronosnet v1.8
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features ability to use multiple
links between nodes, active/active and active/passive link failover
On 2019-03-26 4:12 p.m., Brian Reichert wrote:
> This will sound like a dumb question:
>
> The manpage for pcs(8) implies that to set up a cluster, one needs
> to provide a name.
>
> Why do clusters have names?
>
> Is there a use case wherein there would be multiple clusters visible
> in an
This will sound like a dumb question:
The manpage for pcs(8) implies that to set up a cluster, one needs
to provide a name.
Why do clusters have names?
Is there a use case wherein there would be multiple clusters visible
in an administrative UI, such that they'd need to be differentiated?
--
On Tue, 2019-03-26 at 09:33 -0600, JCA wrote:
> Making some progress with Pacemaker/DRBD, but still trying to grasp
> some of the basics of this framework. Here is my current situation:
>
> I have a two-node cluster, pmk1 and pmk2, with resources ClusterIP
> and DrbdFS. In what follows, commands
On Tue, 2019-03-26 at 22:12 +0300, Andrei Borzenkov wrote:
> 26.03.2019 17:14, Ken Gaillot пишет:
> > On Tue, 2019-03-26 at 14:11 +0100, Thomas Singleton wrote:
> > > Dear all
> > >
> > > I am encountering an issue with colocation constraints.
> > >
> > > I have created a 4 nodes cluster (3
On Tue, 2019-03-26 at 11:36 -0700, Cole Miller wrote:
> Hi,
>
> Thank you very much Andrei, Ken and Ulrich for your input!
>
> I should have mentioned that I did start with trying apachectl
> graceful, but it fails to find the process because the httpd process
> is not being run via systemd.
26.03.2019 17:14, Ken Gaillot пишет:
> On Tue, 2019-03-26 at 14:11 +0100, Thomas Singleton wrote:
>> Dear all
>>
>> I am encountering an issue with colocation constraints.
>>
>> I have created a 4 nodes cluster (3 "main" and 1 "spare") with 3
>> resources and I wish to have each resource run only
Hi,
Thank you very much Andrei, Ken and Ulrich for your input!
I should have mentioned that I did start with trying apachectl graceful, but it
fails to find the process because the httpd process is not being run via
systemd.
The explanation of why this capability is not present in the
26.03.2019 18:33, JCA пишет:
> Making some progress with Pacemaker/DRBD, but still trying to grasp some of
> the basics of this framework. Here is my current situation:
>
> I have a two-node cluster, pmk1 and pmk2, with resources ClusterIP and
> DrbdFS. In what follows, commands preceded by
Making some progress with Pacemaker/DRBD, but still trying to grasp some of
the basics of this framework. Here is my current situation:
I have a two-node cluster, pmk1 and pmk2, with resources ClusterIP and
DrbdFS. In what follows, commands preceded by '[pmk1] #' are to be
understood as commands
On Tue, 2019-03-26 at 14:11 +0100, Thomas Singleton wrote:
> Dear all
>
> I am encountering an issue with colocation constraints.
>
> I have created a 4 nodes cluster (3 "main" and 1 "spare") with 3
> resources and I wish to have each resource run only on its own node
> (or
> on the spare) and
11 matches
Mail list logo
