Re: [Linux-ha-dev] [Openais] An OCF agent for LXC (Linux Containers) - Linux-HA-Dev Digest, Vol 90, Issue 2

2011-05-04 Thread Darren Thompson
Florian

I have tried to re-base on your version but it just will not run for me.

I keep getting Failed to parse the metadata of LXC syntax error line
1, column 1

I've no idea where this error is as it all looks fine...

I'll attach my copy and a screen-shot of the error, HELP!!!

Darren


On Tue, 2011-05-03 at 07:59 -0600,
linux-ha-dev-requ...@lists.linux-ha.org wrote:

 Date: Tue, 03 May 2011 08:20:56 +0200
 From: Florian Haas florian.h...@linbit.com
 Subject: Re: [Linux-ha-dev] [Openais] An OCF agent for LXC (Linux
 Containers) - Linux-HA-Dev Digest, Vol 89, Issue 32
 To: High-Availability Linux Development List
 linux-ha-dev@lists.linux-ha.org
 Message-ID: 4dbf9ec8.4060...@linbit.com
 Content-Type: text/plain; charset=utf-8
 
 Hello Darren,
 
 Please get the current version from
 https://github.com/fghaas/resource-agents/blob/lxc/heartbeat/lxc, and
 also review the commit history at
 https://github.com/fghaas/resource-agents/commits/lxc/heartbeat/lxc.
 
 When you send more updates, please do make sure they track the latest
 version in my repo. I am doing my best splitting this up into patches
 as
 I can and check them in individually, but the re-introduction of
 errors
 that have already been fixed is not something that gives me thrills.
 Thanks.
 
 Cheers,
 Florian
attachment: Screenshot-Message.png

lxc
Description: application/shellscript
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] [Openais] An OCF agent for LXC (Linux Containers) - Linux-HA-Dev Digest, Vol 90, Issue 2

2011-05-04 Thread Florian Haas
On 05/04/2011 08:44 AM, Darren Thompson wrote:
 Florian
 
 I have tried to re-base on your version but it just will not run for me.
 
 I keep getting Failed to parse the metadata of LXC syntax error line
 1, column 1
 
 I've no idea where this error is as it all looks fine...
 
 I'll attach my copy and a screen-shot of the error, HELP!!!

It's probably not a wise approach to test with the GUI while you're
not even sure the resource agent will run. You will have to start the
script from the command line and see where your error is coming from.

Florian




signature.asc
Description: OpenPGP digital signature
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] [Openais] An OCF agent for LXC (Linux Containers) - Linux-HA-Dev Digest, Vol 90, Issue 2

2011-05-04 Thread Florian Haas
On 05/04/2011 09:09 AM, Florian Haas wrote:
 On 05/04/2011 08:44 AM, Darren Thompson wrote:
 Florian

 I have tried to re-base on your version but it just will not run for me.

 I keep getting Failed to parse the metadata of LXC syntax error line
 1, column 1

 I've no idea where this error is as it all looks fine...

 I'll attach my copy and a screen-shot of the error, HELP!!!
 
 It's probably not a wise approach to test with the GUI while you're
 not even sure the resource agent will run. You will have to start the
 script from the command line and see where your error is coming from.

Btw, your patch contains this:

diff --git a/heartbeat/lxc b/heartbeat/lxc
index 25ef6e3..9819a47 100755
--- a/heartbeat/lxc
+++ b/heartbeat/lxc
@@ -123,7 +123,6 @@ LXC_start() {
if ! LXC_monitor ; then
touch $TRANS_RES_STATE
ocf_log info Starting ${OCF_RESKEY_container}
-   cd `dirname ${OCF_RESKEY_config`
ocf_run ${STARTCMD} || exit $OCF_ERR_GENERIC
else
# If already running, consider start
successful

Sorry, that was a typo on my part, should have been cd `dirname
${OCF_RESKEY_config}` (with closing brace) of course. Should I correct
the typo, or can we drop that line altogether?

Cheers,
Florian



signature.asc
Description: OpenPGP digital signature
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] Linux-HA-Dev Digest, Vol 90, Issue 4

2011-05-04 Thread Darren Thompson
Florian/Team

I have succeeded in re-basing my work on the version in the repository.
That should make re-integrating my changes much more straight forward.. 

It is much more succinct now.

Changes in this version:

1. Re-based on Florian's version in
https://github.com/fghaas/resource-agents/blob/lxc/heartbeat/lxc;
2. Removed root variable requirements (it was only used once and did
not add significant value to configuration)
3. Removed mention of root from verify and stop sections
3. Cleaned up and expanded meta-data section, added to descriptions etc
4. remove superfluous cd in start section as no longer requires with
full config path specified.

I really do not know what happend to my first few attempts at re-basing,
I'm assuming an invalid character got into the file somewhere... 

Darren

On Wed, 2011-05-04 at 00:44 -0600,
linux-ha-dev-requ...@lists.linux-ha.org wrote:

 Florian
 
 I have tried to re-base on your version but it just will not run for
 me.
 
 I keep getting Failed to parse the metadata of LXC syntax error line
 1, column 1
 
 I've no idea where this error is as it all looks fine...
 
 I'll attach my copy and a screen-shot of the error, HELP!!!
 
 Darren


lxc
Description: application/shellscript
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] [Openais] An OCF agent for LXC (Linux Containers) - Linux-HA-Dev Digest, Vol 90, Issue 3

2011-05-04 Thread Florian Haas
On 05/04/2011 10:52 AM, Darren Thompson wrote:
 Florian/Team
 
 I have now updated my re-based ocf file to include the experimental
 support for upstart and systemd using containers.
 
 I can confirm that this is still working correctly for containers
 running 'sysv init' and in theory should now also work for containers
 using 'upstart' and 'systemd'.
 
 I'm currently doing a crash course' in installing containers to use
 these 'init replacments' but have not yet succedded in testing either
 'upstart' or 'systemd' containers yet.
 
 If there is anyone with a better understanding of LXC containers and
 one/both of these other 'init systems', please contact me as your
 information/assistance would be invaluable.

OK, updated my git branch. You really want to double check your
rebasing method; you're constantly re-introducing things that I've
removed or fixed in earlier commits.

Florian



signature.asc
Description: OpenPGP digital signature
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] cluster-glue-1.0.7: WARNING: linux/errqueue.h: present but cannot be compiled

2011-05-04 Thread Dejan Muhamedagic
On Thu, Apr 28, 2011 at 04:52:21PM +0200, Ermete Gaudenzi wrote:
 Ok with the patch the warning message disappears and the program works.
 In config.log the checks for errqueue.h have the same results (present
 but not usable).

OK. Thanks for testing.

 The same problem is found on pacemaker-1.0.10
 downloaded from:
 http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/da7075976b5f.tar.bz2
 
 Will this be fixed in next release?

Yes.

Thanks,

Dejan

 Thanks for your help ;-)
 Ermete Gaudenzi
 ___
 Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
 http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
 Home Page: http://linux-ha.org/
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] New OCF RA: symlink

2011-05-04 Thread Florian Haas
Coming back to this one, as the discussion seems to have died down.

On 2011-04-20 19:00, Lars Ellenberg wrote:
 Oh, well, thinking about non-roots that may have cibadmin karma,
 they now can configure a resource that will remove /etc/passwd.
 I'm not sure if I like that.
 
 How about a staged system? Double symlinks?
 Similar to the alternatives system in Debian or others.
 
 The RA will force a single directory that will contain the indirection
 symlinks, and will sanitize (or force) link names to not contain slashes.
 
 The real symlinks will point to that indirection symlink, which will
 point to the end location.
 
 /etc/postfix/main.cf
- /var/lib/wherever-indirection-dir/postfix_main.cf ===
   - /mnt/somewhere/you/want/to/point/to/main.cf
 
 And === will be managed by the resource agent.

Considering we have an anything resource agent which, well, lets us do
anything, I consider this pointless cluttering of the resource agent
which creates a false sense of security. Thoughts?

Cheers,
Florian



signature.asc
Description: OpenPGP digital signature
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] New OCF RA: symlink

2011-05-04 Thread Florian Haas
On 2011-04-22 14:25, Alan Robertson wrote:
 Drbdlinks was never converted to an OCF RA, that I recall.  It handles 
 cases of needing to restart the logging system when you changed symlnks 
 around - mainly for chroot services.  I've used it for many years.  You 
 can find the source for it here:
  http://www.tummy.com/Community/software/drbdlinks/
 
 It's pretty well thought out, and works quite well.  I'd certainly look 
 it over before reinventing the wheel.

AFAICS drbdlinks does some things on its own which in a Pacemaker
cluster would be under Pacemaker control (restarting daemons, for
example). The symlink RA does none of this, it's simple and effective
and ties in quite well with Pacemaker management.

Cheers,
Florian



signature.asc
Description: OpenPGP digital signature
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] New OCF RA: symlink

2011-05-04 Thread Lars Ellenberg
On Wed, May 04, 2011 at 03:06:27PM +0200, Florian Haas wrote:
 Coming back to this one, as the discussion seems to have died down.
 
 On 2011-04-20 19:00, Lars Ellenberg wrote:
  Oh, well, thinking about non-roots that may have cibadmin karma,
  they now can configure a resource that will remove /etc/passwd.
  I'm not sure if I like that.
  
  How about a staged system? Double symlinks?
  Similar to the alternatives system in Debian or others.
  
  The RA will force a single directory that will contain the indirection
  symlinks, and will sanitize (or force) link names to not contain slashes.
  
  The real symlinks will point to that indirection symlink, which will
  point to the end location.
  
  /etc/postfix/main.cf
 - /var/lib/wherever-indirection-dir/postfix_main.cf ===
- /mnt/somewhere/you/want/to/point/to/main.cf
  
  And === will be managed by the resource agent.
 
 Considering we have an anything resource agent which, well, lets us do
 anything, I consider this pointless cluttering of the resource agent
 which creates a false sense of security. Thoughts?

Trying to think out loud...
There are a few aspects.

* if we don't have ACLs, anyone with write access to the CIB
  is de facto root on the cluster nodes.  Which makes privilege
  escalation bugs non-existent by definition ;-)

* potential privilege escalation

  Well, to make this an issue, we would need to establish that
   * the cib ACL system is in place,
   * and used,
   * and properly configured,
  which would probably also mean that access would be limited to only
  certain resource agent types.

  Most likely the ACL will be short as well: one role that can do
  cleanup and otherwise only view things,
  one role that can do everything (equivalent to root).

  Services running under Pacemaker control are probably critical,
  so a malicious person with even only stop access on the CIB
  can do a DoS. I guess we have to assume people with any write access
  at all to the CIB are trusted, and not malicious.

  Adding more insecure RAs would just keep the white list shorter.
  No problem with me.

  White list would probably be really short anyways.

  Still we may want to try and limit the potential damage
  that can be done by roles that have only limited rights
  (start/stop/reconfigure existing).

  /me not sure about all this ACL stuff anyways,
  I'd try to avoid it where ever possible ;-)

* limit potential damage on accidental carelessness

  Well, yes, I think that is something we could aim for, too.

And a some more thoughts, but I would probably need a few beers to make
them appear coherent even to myself ;-)

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-ha-dev] [Openais] An OCF agent for LXC (Linux Containers) - Linux-HA-Dev Digest, Vol 90, Issue 6

2011-05-04 Thread Darren Thompson
Florian/Team

There was an error in the GIT-Hub version that was causing my re-base
attempts to fail, so I was forced to try to bring my last known good
version to the same configuration (mostly successful).

I have since found the error in the GIT-Hub version (the initialisation
section was wrong, the meta-data error was a 'red herring') so have been
found and resolved so I have done an actual re-base now based on the
GIT-Hub version. 

Changes:

1. Corrected error in utilisation causing ocf to fail in HB_GUI.
2. Added information  to stop  section, to provide more feedback on
container shutdown/stop (and to assist with future development of
containers using alternate 'init' systems).

Regards
Darren


On Wed, 2011-05-04 at 12:00 -0600,
linux-ha-dev-requ...@lists.linux-ha.org wrote:

  Florian/Team
  
  I have now updated my re-based ocf file to include the
 experimental
  support for upstart and systemd using containers.
  
  I can confirm that this is still working correctly for containers
  running 'sysv init' and in theory should now also work for
 containers
  using 'upstart' and 'systemd'.
  
  I'm currently doing a crash course' in installing containers to use
  these 'init replacments' but have not yet succedded in testing
 either
  'upstart' or 'systemd' containers yet.
  
  If there is anyone with a better understanding of LXC containers and
  one/both of these other 'init systems', please contact me as your
  information/assistance would be invaluable.
 
 OK, updated my git branch. You really want to double check your
 rebasing method; you're constantly re-introducing things that I've
 removed or fixed in earlier commits.
 
 Florian
 


lxc
Description: application/shellscript
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/


Re: [Linux-HA] get haresources2cib.py

2011-05-04 Thread Andrew Beekhof
On Tue, May 3, 2011 at 9:50 PM, Vinay Nagrik vnag...@gmail.com wrote:
 Hello Andrew,

 We have been goint in small details and I still did not get any answer,
 which will put me on the right path.

 I apologise to ask you these questions.  But these are important for my
 work.

 I have down loaded

 *eat-3-0-STABLE-3.0.4.tar.bz2*

heartbeat != pacemaker

 and unzipped it.

 I looked for crm shell and any .dtd .DTD file and did not find any.

 Please please tell me where to get the crm shell or what are the steps or
 did I download a wrong .tar.bz2 file.

 There were these files as well

 glue-1.0.7.tar.bz2 http://hg.linux-ha.org/glue/archive/glue-1.0.7.tar.bz2
 and
 *gents-1.0.4.tar.gz*

 Do I have to download these files also.

 My first and  very first step is to create a cib.xml file.  And I am running
 in small circles.

 Kindly help.  I will greatly apprecite this.

 Thanks.

 arun
 On Mon, May 2, 2011 at 11:16 PM, Andrew Beekhof and...@beekhof.net wrote:

 On Mon, May 2, 2011 at 9:33 PM, Vinay Nagrik vnag...@gmail.com wrote:
  Thank you Andrew.
 
  Could you please tell me where to get the DTD for cib.xml and where from
 can
  I download crm shell.

 Both get installed with the rest of pacemaker

 
  thanks in anticipation.
 
  With best regards.
 
  nagrik
 
  On Mon, May 2, 2011 at 12:56 AM, Andrew Beekhof and...@beekhof.net
 wrote:
 
  On Sun, May 1, 2011 at 9:26 PM, Vinay Nagrik vnag...@gmail.com wrote:
   Dear Andrew,
  
   I read your document clusters from scratch and found it very
 detailed.
   It
   gave lots of information, but I was looking for creating a cib.xml and
  could
   not decipher the language as to the syntex and different fields to be
 put
  in
   cib.xml.
 
  Don't look at the xml.  Use the crm shell.
 
  
   I am still looking for the haresources2cib.py script.
 
  Don't. It only creates configurations conforming to the older and now
  unsupported syntax.
 
    I searched the web
   but could not find anywhere.
  
   I have 2 more questions.
  
   Do I have to create the cib.xml file on the nodes I am running
 heartbeat
  v.2
   software.
   Does cib.xml has to reside in /var/lib/crm directory or can it reside
   anywhere else.
  
   Kindly provide these answers.  I will greatly appreciate your help.
  
   Have a nice day.
  
   Thanks.
  
   nagrik
  
   On Sat, Apr 30, 2011 at 1:32 AM, Andrew Beekhof and...@beekhof.net
  wrote:
  
   Forget the conversion.
   Use the crm shell to create one from scratch.
  
   And look for the clusters from scratch doc relevant to your version
   - its worth the read.
  
   On Sat, Apr 30, 2011 at 1:19 AM, Vinay Nagrik vnag...@gmail.com
  wrote:
Hello Group,
   
Kindly tell me where can I download
   
haresources2cib.py file
   
from.
   
Please also tell me can I convert haresources file on a node where
 I
  am
   not
running high availability service and then can I copy the converted
  ..xml
file in
   
/var/lib/heartbeat
   
directory on which I am running the high availability.
   
Also does
   
cib file
   
must resiede under
   
/var/lib/heartbeat
   
directory or can it reside under any directory like under
   
/etc.
   
please let me know.  I am just a beginner.
   
Thanks in advance.
   
--
Thanks
   
Nagrik
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
   
   ___
   Linux-HA mailing list
   Linux-HA@lists.linux-ha.org
   http://lists.linux-ha.org/mailman/listinfo/linux-ha
   See also: http://linux-ha.org/ReportingProblems
  
  
  
  
   --
   Thanks
  
   Nagrik
   ___
   Linux-HA mailing list
   Linux-HA@lists.linux-ha.org
   http://lists.linux-ha.org/mailman/listinfo/linux-ha
   See also: http://linux-ha.org/ReportingProblems
  
  ___
  Linux-HA mailing list
  Linux-HA@lists.linux-ha.org
  http://lists.linux-ha.org/mailman/listinfo/linux-ha
  See also: http://linux-ha.org/ReportingProblems
 
 
 
 
  --
  Thanks
 
  Nagrik
  ___
  Linux-HA mailing list
  Linux-HA@lists.linux-ha.org
  http://lists.linux-ha.org/mailman/listinfo/linux-ha
  See also: http://linux-ha.org/ReportingProblems
 
 ___
 Linux-HA mailing list
 Linux-HA@lists.linux-ha.org
 http://lists.linux-ha.org/mailman/listinfo/linux-ha
 See also: http://linux-ha.org/ReportingProblems




 --
 Thanks

 Nagrik
 ___
 Linux-HA mailing list
 Linux-HA@lists.linux-ha.org
 http://lists.linux-ha.org/mailman/listinfo/linux-ha
 See also: http://linux-ha.org/ReportingProblems

___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org

Re: [Linux-HA] Filesystem do not start on Pacemaker-Cluster

2011-05-04 Thread Andrew Beekhof
On Tue, May 3, 2011 at 10:39 AM, KoJack kojac...@web.de wrote:

 Hi,
 i was trying to set up a pacemaker cluster. After I added all resources, the
 filesystem will not start at one Node.

 crm_verify -L -V


 crm_verify[30068]: 2011/05/03_10:35:39 WARN: unpack_rsc_op: Processing
 failed op WebFS:0_start_0 on apache01: unknown error (1)
 crm_verify[30068]: 2011/05/03_10:35:39 WARN: unpack_rsc_op: Processing
 failed op WebFS:0_stop_0 on apache01: unknown exec error (-2)
 crm_verify[30068]: 2011/05/03_10:35:39 WARN: common_apply_stickiness:
 Forcing WebFSClone away from apache01 after 100 failures (max=100)
 crm_verify[30068]: 2011/05/03_10:35:39 WARN: common_apply_stickiness:
 Forcing WebFSClone away from apache01 after 100 failures (max=100)
 crm_verify[30068]: 2011/05/03_10:35:39 WARN: common_apply_stickiness:
 Forcing WebFSClone away from apache01 after 100 failures (max=100)
 crm_verify[30068]: 2011/05/03_10:35:39 ERROR: clone_rsc_colocation_rh:
 Cannot interleave clone WebSiteClone and WebIP because they do not support
 the same number of resources per node
 crm_verify[30068]: 2011/05/03_10:35:39 ERROR: clone_rsc_colocation_rh:
 Cannot interleave clone WebSiteClone and WebIP because they do not support
 the same number of resources per node
 crm_verify[30068]: 2011/05/03_10:35:39 WARN: should_dump_input: Ignoring
 requirement that WebFS:0_stop_0 comeplete before WebFSClone_stopped_0:
 unmanaged failed resources cannot prevent clone shutdown
 Errors found during check: config not valid


 crm configure show

 node apache01
 node apache02
 primitive ClusterIP ocf:heartbeat:IPaddr2 \
        params ip=10.1.1.5 cidr_netmask=8 nic=eth0
 clusterip_hash=sourceip \
        op monitor interval=30s
 primitive WebData ocf:linbit:drbd \
        params drbd_resource=wwwdata \
        op monitor interval=60s \
        op start interval=0 timeout=240s \
        op stop interval=0 timeout=100s
 primitive WebFS ocf:heartbeat:Filesystem \
        params device=/dev/drbd/by-res/wwwdata directory=/var/www/html
 fstype=gfs2 \
        op start interval=0 timeout=60s \
        op stop interval=0 timeout=60s
 primitive WebSite ocf:heartbeat:apache \
        params configfile=/etc/httpd/conf/httpd.conf \
        op monitor interval=1min \
        op start interval=0 timeout=40s \
        op stop interval=0 timeout=60s
 primitive dlm ocf:pacemaker:controld \
        op monitor interval=120s \
        op start interval=0 timeout=90s \
        op stop interval=0 timeout=100s
 primitive gfs-control ocf:pacemaker:controld \
        params daemon=gfs_controld.pcmk args=-g 0 \
        op monitor interval=120s \
        op start interval=0 timeout=90s \
        op stop interval=0 timeout=100s
 ms WebDataClone WebData \
        meta master-max=2 master-node-max=1 clone-max=2
 clone-node-max=1 notify=true
 clone WebFSClone WebFS
 clone WebIP ClusterIP \
        meta globally-unique=true clone-max=2 clone-node-max=2
 clone WebSiteClone WebSite
 clone dlm-clone dlm \
        meta interleave=true
 clone gfs-clone gfs-control \
        meta interleave=true
 colocation WebFS-with-gfs-control inf: WebFSClone gfs-clone
 colocation WebSite-with-WebFS inf: WebSiteClone WebFSClone
 colocation fs_on_drbd inf: WebFSClone WebDataClone:Master
 colocation gfs-with-dlm inf: gfs-clone dlm-clone
 colocation website-with-ip inf: WebSiteClone WebIP
 order WebFS-after-WebData inf: WebDataClone:promote WebFSClone:start
 order WebSite-after-WebFS inf: WebFSClone WebSiteClone
 order apache-after-ip inf: WebIP WebSiteClone
 order start-WebFS-after-gfs-control inf: gfs-clone WebFSClone
 order start-gfs-after-dlm inf: dlm-clone gfs-clone
 property $id=cib-bootstrap-options \
        dc-version=1.1.4-ac608e3491c7dfc3b3e3c36d966ae9b016f77065 \
        cluster-infrastructure=openais \
        expected-quorum-votes=2 \
        stonith-enabled=false \
        no-quorum-policy=ignore
 rsc_defaults $id=rsc-options \
        resource-stickiness=100


 Did you see any mistake in my configuration?

You mean apart from the 2 errors and the apache resource that cant
stop in the crm_verify output?


 Thanks a lot
 --
 View this message in context: 
 http://old.nabble.com/Filesystem-do-not-start-on-Pacemaker-Cluster-tp31530410p31530410.html
 Sent from the Linux-HA mailing list archive at Nabble.com.

 ___
 Linux-HA mailing list
 Linux-HA@lists.linux-ha.org
 http://lists.linux-ha.org/mailman/listinfo/linux-ha
 See also: http://linux-ha.org/ReportingProblems

___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


Re: [Linux-HA] [PATCH] Low: adding cluster-glue-extras subpackage

2011-05-04 Thread Dejan Muhamedagic
On Tue, May 03, 2011 at 07:30:04PM -0400, Vadym Chepkov wrote:
 
 On May 3, 2011, at 10:02 AM, Dejan Muhamedagic wrote:
  
  Dependency can certainly be filtered out, but this would just mask the
  problem, not solve it.
  
  I don't think that this is a problem at all. Whoever wants to
  use vcenter will have to install whatever the plugin needs.
  That's how it has always been with stonith plugins. Or do you
  propose to create a package per stonith plugin?
 
 If it is justified, why not?

Well, it could actually make sense to have one package per
plugin. Still, it's up to people packaging. And that's not me/us :)

 It's not something unheard of:
 
 # rpm -qlp nagios-plugins-oracle-1.4.15-2.el5.x86_64.rpm 
 /usr/lib64/nagios/plugins/check_oracle

OK. But what does that prove? Should I now show you other
packages which look different?

 There are plenty of packages out there with no files at all, by the way.
 They serve as meta package, just to pull n proper dependencies.

I know, but that's still different.

Well, we can go on like this forever. Seems to be a matter of
taste/style.

Thanks,

Dejan


 
 Vadym
 
 ___
 Linux-HA mailing list
 Linux-HA@lists.linux-ha.org
 http://lists.linux-ha.org/mailman/listinfo/linux-ha
 See also: http://linux-ha.org/ReportingProblems
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


[Linux-HA] upgrading heartbeat 2.0 configuration files

2011-05-04 Thread Vinay Nagrik
Hello Group,

My immediate problem is to convert my haresources to cib.xml file.

I am working with Virtual Machine on Linux platform and I have heartbeat 2.0
installed on both the nodes.  Since the configuration files are 1.0
compliant, I want to upgrade those files to 2.0.

I am on this problem since last one week, but did not get any constructive
lead.  I have read the document clusters from scratch from end to end.
This document is created by Andrew Beekhof.
If someone please tell me the tar file from where I can install crm shell I
will greatly apprecite this.  At this time I am not interested in
pacemaker.  Just upgrading haresources to cib.xml file.  If I have to
install something else I will do it to achieve my original goal.

If I can get haresources2cib.py, I will be happy with that also.  I just
want to get started in creating my first cib.xml file and understand its
contents.

Can someone please enumerate all steps and please tell me how can I achieve
this goal of creating my first cib.xml file.

I am sure there are people out there who must have similar problems.

Thanks in anticipation.

-- 
Thanks

Nagrik
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


Re: [Linux-HA] upgrading heartbeat 2.0 configuration files

2011-05-04 Thread Lars Ellenberg
On Wed, May 04, 2011 at 03:55:06PM -0700, Vinay Nagrik wrote:
 Hello Group,
 
 My immediate problem is to convert my haresources to cib.xml file.
 
 I am working with Virtual Machine on Linux platform and I have heartbeat 2.0

You do not want heartbeat 2.0. Seriously.

You want Pacemaker.
Using either heartbeat 3.0 or corosync.

Pacemaker comes with the crm shell,
so you can and should forget about XML.

 installed on both the nodes.  Since the configuration files are 1.0
 compliant, I want to upgrade those files to 2.0.
 
 I am on this problem since last one week, but did not get any constructive
 lead.  I have read the document clusters from scratch from end to end.
 This document is created by Andrew Beekhof.
 If someone please tell me the tar file from where I can install crm shell I
 will greatly apprecite this.

http://lmgtfy.com/?q=crm+shelll=1

(same goes for pacemaker,
and the other things you are so eager to learn about)

The CRM shell is part of Pacemaker.

 At this time I am not interested in pacemaker.

That is a major mistake on your side.

The thing in heartbeat that uses and interprets the cib.xml
is called CRM (cluster resource manager).

There has been a package split (about three or four years ago).

Heartbeat is now only the basic communication layer.

cluster- glue and agents is what you need in addition to that.

The CRM part of it is now called Pacemaker.

Pacemaker is not something entirely different.
Pacemaker is that very CRM,
only four years of development and bug fixes later.

So if you are interested in the cib,
you are interested in pacemaker.

Again: you do want pacemaker.

If however you insist on using software from 2007 (or earlier),
and insist on ignoring the development and bug fixes it has received
over the last four years, don't expect much help.

Using heartbeat 2.0 in crm mode with a cib.xml config
is bordering on irresponsible.

Sorry for being so verbose, and direct.
But somehow we need to get this message across.

 Just upgrading haresources to cib.xml file.  If I have to
 install something else I will do it to achieve my original goal.
 
 If I can get haresources2cib.py, I will be happy with that also.  I just
 want to get started in creating my first cib.xml file and understand its
 contents.
 
 Can someone please enumerate all steps and please tell me how can I achieve
 this goal of creating my first cib.xml file.

First step: forget about cib.xml. Forget about xml.

Second step: get a modern distribution.
Third step: install pacemaker (with heartbeat or corosync, your choice).

http://theclusterguy.clusterlabs.org/post/178680309/configuring-heartbeat-v1-was-so-simple

http://www.clusterlabs.org/
http://www.clusterlabs.org/doc/
http://clusterlabs.org/wiki/FAQ

http://www.linux-ha.org/

http://www.drbd.org/mc/management-console/

http://www.linbit.com/
http://www.linbit.com/en/products-services/drbd-consulting/


-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems