Re: Cluster stuff (cman,dlm,heartbeat,corosync,openais,pacemaker,drbd,lvm)
Dnia 2012-07-01, nie o godzinie 22:13 +0200, Jacek Konieczny pisze: On Sun, Jul 01, 2012 at 05:36:04PM +0200, Tomasz Rutkowski wrote: cluster.spec was my work of 3rd generation of redhat cluster suite (dlm+cman+gfs2+rgmanager), there is bcond in lvm2 to complete stack, but it's already outdated (needs polishing :)) I have replaced this bcond with something more up to date. Currently '3rd generation redhat cluster suite' is near being outdated. Keeping old cman and dlm as the default backend for lvmd just does not make any sense now. sorry, I'm on my vacations right now and family goes first... :) true, cluster2 line is outdated enough What do you mean by '3.1 won't build with pacemaker'? There was no pacemaker dependency in cluster.spec well, if You would like to control dlm space from within pacemaker You need daemon dlm_controld.pcmk - this one is build from cluster3 suite with pacemaker's files, perhaps You have made it build with 3.1 line, I haven't investigate much [at all I mean] why it's not building... (and You need dlm space for clvmd as far as I'm concerned) I have also played with pacemaker 1.1 (on branch currently) - after a bit of patching works with corosync 1.4.3 for me, so I think it could go to HEAD, unless there is a reason to keep pacemaker 1.0.x. Though, I don't remember why I use 1.1 and not 1.0 ;) me neither :) -- Tomasz Rutkowski , +48 604 419 913 , e-mail/xmpp: aluc...@nospheratu.net ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman,dlm,heartbeat,corosync,openais,pacemaker,drbd,lvm)
On Tue, Jul 03, 2012 at 10:15:18AM +0200, Tomasz Rutkowski wrote: What do you mean by '3.1 won't build with pacemaker'? There was no pacemaker dependency in cluster.spec well, if You would like to control dlm space from within pacemaker You need daemon dlm_controld.pcmk - this one is build from cluster3 suite with pacemaker's files, perhaps You have made it build with 3.1 line, I haven't investigate much [at all I mean] why it's not building... (and You need dlm space for clvmd as far as I'm concerned) I was working from I have found in the cluster.spec… there was not Pacemaker dependency that and nothing failed with my Pacemaker. As far as clvmd is concerned… I was not able to make it work with Pacemaker/corosync - yes that was probably the 'dlm_controld.pcmk' thing, but even Google couldn't help much (documentation for dlm/clvmd that is available is close to nothing). And I don't quite understand how the packages from cluster.spec are split (a dlm_conrold binary is in th group subpackage which pulls cman… but I didn't want cman and it didn't work anyway). Though, I was able to run clvmd with Pacemaker/openais/corosync and it seems that will be a good enough solution for me. openais does not look that scary as the stuff from cluster.spec ;) I can see place for improvement, though. Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman, dlm, heartbeat, corosync, openais, pacemaker, drbd, lvm)
2012/7/1 Jacek Konieczny jaj...@jajcus.net: On Sun, Jul 01, 2012 at 10:47:19PM +0300, Elan Ruusamäe wrote: On 07/01/2012 11:51 AM, Jacek Konieczny wrote: Do we need clvmd in the main lvm2 package? It pulls some dependencies irrelevant for non-clustered setups. i'm in for moving clustered deps to subpackages. if it's doable. Already done. Theoretically this could break a cluster on upgrade, but I don't think it would be a mass problem among PLD users ;) And production clusters are not a thing one upgrades without testing. I have a cluster setup but nobody is going to die if it breaks on an upgrade ;) While I think in a case like this it is probably more important that we have current working packages than that we don't break old ones, I do think this kind of talk happening on the forum highlights the need for some sort of warning channel: If some package upgrade is EXPECTED to break current configurations, poldek should warn and even expect acknowledgement before proceeding with that package. Has the possibility of manually adding some sort of warning flag between certain upgrades been considered? Ideally all upgrades would just work, but with the number of developers and amount of testing we have right now, that is simply not practical. Sometimes we do things that we know will require intervention to work. We need a fool proof way to warn folks before their systems break. Thoughts about where this functionality should be introduced? Caleb ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman, dlm, heartbeat, corosync, openais, pacemaker, drbd, lvm)
On 02.07.2012 14:41, Caleb Maclennan wrote: Has the possibility of manually adding some sort of warning flag between certain upgrades been considered? there is warning message that is displayed AFTER upgrade (via %triggerpostun or just %post) :) and if the upgrade breakage is really serious and detectable, package could abort upgrade with exit in %prein scriptlet. rarely used, afaik i saw it somewhere for warning before upgrades: read vcs commits list, pay attention to BIG FAT warnings :) -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman, dlm, heartbeat, corosync, openais, pacemaker, drbd, lvm)
On Mon, Jul 02, 2012 at 05:01:05PM +0300, Elan Ruusam??e wrote: and if the upgrade breakage is really serious and detectable, package could abort upgrade with exit in %prein scriptlet. rarely used, afaik i saw it somewhere e.g. glibc-preinstall in ALT Linux :) -- WBR, Michael Shigorin m...@altlinux.ru -- Linux.Kiev http://www.linux.kiev.ua/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Cluster stuff (cman,dlm,heartbeat,corosync,openais,pacemaker,drbd,lvm)
Hello, At work we use clusters. Currently based on Heartbeat/PaceMaker/DRBD, but I am trying to introduce Corosync and clustered LVM. All based on PLD packages… and I have found a bit of mess in our packages. We have both corosync and openais, but our openais is 0.80, not 1.x which uses corosync as its lower layer. Does anybody still needs openais 0.80? LVM by default build with the clvmd daemon, but the daemon is built only for the cman cluster manager. I guess it is part of some RedHat cluster suite. There is also a 'clvmd3' bcond which seems to enable building with the new version of cluster/cman… but it doesn't seem it would work. Do we need clvmd in the main lvm2 package? It pulls some dependencies irrelevant for non-clustered setups. Do we need to build it with the 'old cman'? Or should we now use only the new packages from 'cluster.spec'? We should probably build LVM2 drivers for other clusters by default - corosync/openais. We have PacePaker 1.0 on HEAD. I am wondering if we could switch to PaceMaker 1.1. 1.0 is 'bugfix release', 1.1 is 'feature release'. None of this is considered 'development', though 1.0 is probably expected to be more stable. 1.1 works well for me. There were mixed versions of heartbeat, pacemaker and related packages and eventually all of them were dropped from th-main. I think they could be restored. Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman, dlm, heartbeat, corosync, openais, pacemaker, drbd, lvm)
On Sun, Jul 01, 2012 at 10:51:13AM +0200, Jacek Konieczny wrote: Hello, At work we use clusters. Currently based on Heartbeat/PaceMaker/DRBD, but I am trying to introduce Corosync and clustered LVM. All based on PLD packages??? and I have found a bit of mess in our packages. We have both corosync and openais, but our openais is 0.80, not 1.x which uses corosync as its lower layer. Does anybody still needs openais 0.80? LVM by default build with the clvmd daemon, but the daemon is built only for the cman cluster manager. I guess it is part of some RedHat cluster suite. There is also a 'clvmd3' bcond which seems to enable building with the new version of cluster/cman??? but it doesn't seem it would work. Do we need clvmd in the main lvm2 package? It pulls some dependencies irrelevant for non-clustered setups. Do we need to build it with the 'old cman'? Or should we now use only the new packages from 'cluster.spec'? IMO we should switch to new corosync/openais and cluster/gfs (replacing its old parts currently existing in separate specs). We should probably build LVM2 drivers for other clusters by default - corosync/openais. If they can coexist, then yes. Old cluster (1.x/2.x) components could be dropped. (not using such configurations myself - just thinking about flexibility) -- Jakub Boguszhttp://qboosh.pl/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman,dlm,heartbeat,corosync,openais,pacemaker,drbd,lvm)
On Sun, Jul 01, 2012 at 10:51:13AM +0200, Jacek Konieczny wrote: Does anybody still needs openais 0.80? Updated question: does anybody still need openais at all? It seems not maintained any more and won't build with corosync 2.0… and other stuff seem to expect corosync 2 now… I guess openais can be dropped if no one was interested in it since the 0.80 release… Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman,dlm,heartbeat,corosync,openais,pacemaker,drbd,lvm)
On Sun, Jul 01, 2012 at 03:36:57PM +0200, Jacek Konieczny wrote: On Sun, Jul 01, 2012 at 10:51:13AM +0200, Jacek Konieczny wrote: Does anybody still needs openais 0.80? Updated question: does anybody still need openais at all? It seems not maintained any more and won't build with corosync 2.0… and other stuff seem to expect corosync 2 now… OK… cluster.spec still needs openais… so it must stay… Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman,dlm,heartbeat,corosync,openais,pacemaker,drbd,lvm)
Dnia 2012-07-01, nie o godzinie 15:41 +0200, Jacek Konieczny pisze: On Sun, Jul 01, 2012 at 03:36:57PM +0200, Jacek Konieczny wrote: On Sun, Jul 01, 2012 at 10:51:13AM +0200, Jacek Konieczny wrote: Does anybody still needs openais 0.80? Updated question: does anybody still need openais at all? It seems not maintained any more and won't build with corosync 2.0… and other stuff seem to expect corosync 2 now… OK… cluster.spec still needs openais… so it must stay… cluster.spec was my work of 3rd generation of redhat cluster suite (dlm+cman+gfs2+rgmanager), there is bcond in lvm2 to complete stack, but it's already outdated (needs polishing :)) openais 1.x is needed some times, but I belive it's not hard requirement corosync 1.4.x is now production used, cluster3 and clvmd won't build with 2.x however on horizon there is dlm4 dedicated to work with corosync 2 and in some short future lvm2 should also get to build/work with it in my work on PLD I'm using cluster3 + clvmd + gfs2 and in another line corosync 1.4.3 with pacemaker 1.1.6 (+clvmd+gfs2) so in summary: if we would like to have pacemaker+cluster3+lvm2 then now we need: cluster3 have to be line 3.0.x (3.1 won't build with pacemaker) corosync 1.4.x pacemaker any tommorow I'll try to put stuff I have in cvs with best regards -- Tomasz Rutkowski , +48 604 419 913 , e-mail/xmpp: aluc...@nospheratu.net ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman, dlm, heartbeat, corosync, openais, pacemaker, drbd, lvm)
On 07/01/2012 11:51 AM, Jacek Konieczny wrote: Do we need clvmd in the main lvm2 package? It pulls some dependencies irrelevant for non-clustered setups. i'm in for moving clustered deps to subpackages. if it's doable. personally not using any clustering setups -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman,dlm,heartbeat,corosync,openais,pacemaker,drbd,lvm)
On Sun, Jul 01, 2012 at 05:36:04PM +0200, Tomasz Rutkowski wrote: cluster.spec was my work of 3rd generation of redhat cluster suite (dlm+cman+gfs2+rgmanager), there is bcond in lvm2 to complete stack, but it's already outdated (needs polishing :)) I have replaced this bcond with something more up to date. Currently '3rd generation redhat cluster suite' is near being outdated. Keeping old cman and dlm as the default backend for lvmd just does not make any sense now. corosync 1.4.x is now production used, cluster3 and clvmd won't build with 2.x Yes, I found it out the hard way, so let it be corosync 1.4.x in Th for now. however on horizon there is dlm4 dedicated to work with corosync 2 and in some short future lvm2 should also get to build/work with it Yes, but let's not push it into PLD unless all the components are officially 'stable'. Now corosync 2 itself is ok, pacemaker will build with that, but there is no openais for it, so no cluster either (unless we go for the development '4th generation') in my work on PLD I'm using cluster3 + clvmd + gfs2 and in another line corosync 1.4.3 with pacemaker 1.1.6 (+clvmd+gfs2) I am going to try corosync 1.4.3 + pacemaker 1.1.7 + clvmd/drbd soon. corosync+pacemaker already installed on a test cluster and seem to work fin. so in summary: if we would like to have pacemaker+cluster3+lvm2 then now we need: cluster3 have to be line 3.0.x (3.1 won't build with pacemaker) What do you mean by '3.1 won't build with pacemaker'? There was no pacemaker dependency in cluster.spec I haven't tried the 3.0.9x versions, though… I don't trust those 'test releases' in the 'stable branch'. corosync 1.4.x pacemaker any I have prepared: corosync 1.4.3 openais 1.1.4 cluster 3.1.8 lvm builds with all that. I have also played with pacemaker 1.1 (on branch currently) - after a bit of patching works with corosync 1.4.3 for me, so I think it could go to HEAD, unless there is a reason to keep pacemaker 1.0.x. Though, I don't remember why I use 1.1 and not 1.0 ;) Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Cluster stuff (cman, dlm, heartbeat, corosync, openais, pacemaker, drbd, lvm)
On Sun, Jul 01, 2012 at 10:47:19PM +0300, Elan Ruusamäe wrote: On 07/01/2012 11:51 AM, Jacek Konieczny wrote: Do we need clvmd in the main lvm2 package? It pulls some dependencies irrelevant for non-clustered setups. i'm in for moving clustered deps to subpackages. if it's doable. Already done. Theoretically this could break a cluster on upgrade, but I don't think it would be a mass problem among PLD users ;) And production clusters are not a thing one upgrades without testing. Greets, Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
