On 24 Feb 2015, at 10:36 pm, N, Ravikiran ravikira...@hp.com wrote:
Hi all,
I was trying to find out whether it is possible to START/STOP pacemaker, and
also run PCS commands as non-root user (in my case it is ‘admin’ user).
I did add the user(‘admin’) to haclient group, but it is of
Hi all,
I was trying to find out whether it is possible to START/STOP pacemaker, and
also run PCS commands as non-root user (in my case it is 'admin' user).
I did add the user('admin') to haclient group, but it is of no help. I get the
following error on start :
[admin@vm4 ~]$ service
I could resolve this by adding user 'admin' to sudoers list.. I added the user
to 'wheel' user. With this I can run all commands with a sude appended..
Thanks for your help.. :)
Ravikiran
-Original Message-
From: N, Ravikiran
Sent: Wednesday, February 25, 2015 10:11 AM
To: The
23.02.2015 21:50, David Vossel wrote:
- Original Message -
On 14 Feb 2015, at 1:10 am, Vladislav Bogdanov bub...@hoster-ok.com
wrote:
Hi,
I believe that is a bug that 'stop' operation uses set of instance
attributes from the original 'start' op, not what successful 'reload' had.
Hi Andrew,
Yes I tried 'pcs' commands. Even they do not work, they throw the same error.
Ravikiran
-Original Message-
From: Andrew Beekhof [mailto:and...@beekhof.net]
Sent: Wednesday, February 25, 2015 1:31 AM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Running
Pacemaker as a scheduler in Mesos or Kubernates does sound like a very
interesting idea. Packaging corosync into super privileged containers still
doesn't make too much sense to me. What's the reason in isolating something
and then giving it all permissions on a host machine?
On Mon, Feb 23, 2015
