[ClusterLabs Developers] new booth maintainer
Hi, I would like to propose a new maintainer for the booth project: Jan Friesse. He knows the booth code inside out and I have been for a long while in the reactive mode when it comes to booth. If anyone has objections please voice them here. Thank you for your attention! Cheers, Dejan ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs Developers] moving cluster-glue to github
On Wed, Oct 19, 2016 at 12:03:38PM +0200, Lars Ellenberg wrote: > On Tue, Oct 11, 2016 at 08:59:45AM +0200, Kristoffer Grönlund wrote: > > Andrew Beekhofwrites: > > > > >> On 10 Oct 2016, at 8:45 PM, Adam Spiers wrote: > > >> > > >> Kristoffer Gronlund wrote: > > >>> We've discussed moving cluster-glue to github.com and the ClusterLabs > > >>> organization, but no one has actually done it yet. ;) > > > > > > I’m not sure I realised that. > > > I’ve created a blank repo, just: > > > > > > git remote add origin g...@github.com:ClusterLabs/cluster-glue.git > > > git push -u origin master > > > > > > I cheated and used the same team as crmsh, let me know if you’d prefer a > > > separate one. > > > > > > > Thanks! > > > > I have imported the cluster-glue repository, so it should now be in the > > same state as the mercurial repository. I also updated the README to > > actually contain a brief description of the project (stolen from the > > linux-ha.org wiki). > > > > https://github.com/ClusterLabs/cluster-glue > > The import-by-github of the mercurial resulted in a usable tree, > but in a very bogus history. > bogus as in needless merges, number of commits without parents > just popping into existence out of nowhere, other similar crap. Hrm. Never trust the tools! ;-) > Just compare the resulting commit history using gitk, qgit, > git log --graph or whatever you like, and also compare that > to the original mercurial using hg log -G or similar. > > I re-imported using git-remote-hg > (git remote add lha hg::http://hg.linux-ha.org/glue) > and force-pushed that over to github ClusterLabs/cluster-glue master > > kept the old github imported master for reference for now as > master-as-originally-imported-by-github-hg-importer > 08bec629045c285746046796c84ae71f2ef34016 > > But I intend to delete that branch eventually. > > Every interested party: > please re-clone, or hard reset, > and rebase anything you may have against that new clusterlabs master. > > This also should make it "easy" to keep the hg repo in sync, > as long as we may want to do that. Before we finally close it down > completely. Not sure what's the benefit of keeping the old hg repository. I know that the resource agents are still at linux-ha.org too, but cannot anymore recall why. Well, I guess that either way is fine. Many thanks for looking into this! Cheers, Dejan P.S. Move the heartbeat too? ;-) > > What remains is to update the mercurial repository and the linux-ha.org > > wiki to point to the github repository instead of the hg one. Dejan or > > Lars, could you take care of this part? > > I'll look into that "later". > Feel free to poke me in case it falls through... > > Thanks, > > -- > : Lars Ellenberg > : LINBIT | Keeping the Digital World Running > : DRBD -- Heartbeat -- Corosync -- Pacemaker > : R, Integration, Ops, Consulting, Support > > DRBD® and LINBIT® are registered trademarks of LINBIT > > ___ > Developers mailing list > Developers@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/developers ___ Developers mailing list Developers@clusterlabs.org http://clusterlabs.org/mailman/listinfo/developers
Re: [ClusterLabs Developers] moving cluster-glue to github
On Mon, Oct 10, 2016 at 12:31:36PM +0200, Klaus Wenninger wrote: > On 10/10/2016 12:07 PM, Kristoffer Grönlund wrote: > > Adam Spierswrites: > > > >> Kristoffer Gronlund wrote: > >>> We've discussed moving cluster-glue to github.com and the ClusterLabs > >>> organization, but no one has actually done it yet. ;) > >> Out of curiosity what needs to be done for this, other than the > >> obvious "git push" to github, and maybe updating a README / wiki page > >> or two? > >> > > The main thing would be to ensure that everyone who maintains it agrees > > to the move. AFAIK at least Lars Ellenberg and Dejan are both in favor, > > but I am not sure who else might be considered an owner of > > cluster-glue. > > > > Cc:ing the Linux HA development list as well. > > > Of course it doesn't solve the asking around for OK issue but > > are there experiences with: > > https://help.github.com/articles/about-github-importer/ No, but I assume it wouldn't be too difficult to give it a try. I'm not sure if I've ever converted a mercurial repository to git, but I think that there are a number of tools for that. Kristoffer has some experience as he moved crmsh to github. Cheers, Dejan > > > ___ > Developers mailing list > Developers@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/developers ___ Developers mailing list Developers@clusterlabs.org http://clusterlabs.org/mailman/listinfo/developers
Re: [ClusterLabs Developers] moving cluster-glue to github
Hi, On Mon, Oct 10, 2016 at 12:07:48PM +0200, Kristoffer Grönlund wrote: > Adam Spierswrites: > > > Kristoffer Gronlund wrote: > >> We've discussed moving cluster-glue to github.com and the ClusterLabs > >> organization, but no one has actually done it yet. ;) > > > > Out of curiosity what needs to be done for this, other than the > > obvious "git push" to github, and maybe updating a README / wiki page > > or two? > > > > The main thing would be to ensure that everyone who maintains it agrees > to the move. AFAIK at least Lars Ellenberg and Dejan are both in favor, > but I am not sure who else might be considered an owner of > cluster-glue. > > Cc:ing the Linux HA development list as well. Lars (aka lge), if you don't see any obstacles, shall we do this? Cheers, Dejan > -- > // Kristoffer Grönlund > // kgronl...@suse.com > > ___ > Developers mailing list > Developers@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/developers ___ Developers mailing list Developers@clusterlabs.org http://clusterlabs.org/mailman/listinfo/developers
Re: [ClusterLabs Developers] RFC: New stonith agent for pacemaker clusters running on virtual machines which are managed by ganeti
Hi Dominik, On Fri, Oct 07, 2016 at 02:50:10PM +0200, Dominik Klein wrote: > Hi there > > I wrote an agent that should be (_is_ in my environment) able to > implement stonith in a pacemaker cluster running on ganeti-powered > virtual machines. It talks to the ganeti api. > > I did not do this with the xvm agent since it would (from what I > understand) require a second control instance on the physical machines > which might interfere with ganeti (expected machine states will likely > be different in a shooting scenario). > > Any feedback is appreciated. > > Example configuration: > > Place the script in /usr/lib/stonith/plugins/external/ganeti and > configure this fencing resource: > > primitive fencing stonith:external/ganeti \ > params \ > ganeti_api_port=5080 \ > ganeti_api_transport=https \ > ganeti_auth_password=sCret \ > ganeti_auth_user=overlord \ > ganeti_cluster=ganeti.example.com \ > ganeti_curl_ignore_ssl_errors=true \ > op monitor interval=120s Why the "ganeti" prefix for parameters? It is anyway within the ganeti plugin's scope. I'll take a look at the code too. Cheers, Dejan > > Thanks > Dominik > ___ > Developers mailing list > Developers@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/developers ___ Developers mailing list Developers@clusterlabs.org http://clusterlabs.org/mailman/listinfo/developers
Re: [ClusterLabs Developers] [booth][sbd] GPLv2.1+ clarification request
On Thu, May 05, 2016 at 04:53:57PM +0200, Jan Pokorný wrote: > On 05/04/16 12:33 +0200, Dejan Muhamedagic wrote: > > On Wed, Mar 30, 2016 at 05:27:20PM +0200, Jan Pokorný wrote: > >> On 24/03/16 17:18 +0100, Jan Pokorný wrote: > >>> On 22/03/16 19:18 +0100, Dejan Muhamedagic wrote: > >>>> On Mon, Mar 21, 2016 at 10:03:12PM +0100, Jan Pokorný wrote: > >>>>> On 18/03/16 16:16 +0100, Lars Ellenberg wrote: > >>>>>> So I move to change it to GPLv2+, for everything that is a "program", > >>>>>> and LGPLv2.1 for everything that may be viewed as a library. > >>>>>> > >>>>>> At least that's how I will correct the wording in the > >>>>>> affected files in the heartbeat mercurial. > >>>>> > >>>>> In the light of the presented historic excursion, that feels natural. > >>>>> > >>>>> Assuming no licensors want to speak up, the question now stands: > >>>>> Is it the same conclusion that has been reached by booth and sbd > >>>>> package maintainers (Dejan and Andrew respectively, if I follow what's > >>>>> authoritative nowadays properly) and are these willing to act on it to > >>>>> prevent the mentioned ambiguous interpretation once forever? > >>>> > >>>> Yes, that's all fine with me. > >>>> > >>>>> I will be happy to provide actual patches, > >>>> > >>>> Even better :) > >>> > >>> Added the "maint: clarify GPLv2.1+ -> GPLv2+ in the license notices" > >>> (e294fa2) commit into https://github.com/ClusterLabs/booth/pull/23 > >>> if that's OK with you, Dejan. > >> > >> I hope we are all on the same page as Andrew went ahead there (thanks). > >> Alas, I've noticed there were some subtleties neglected in there so, > >> with regrets, a separate (and hopefully final) pull request: > >> > >> https://github.com/ClusterLabs/booth/pull/24 > > > > This got merged too. Thanks! > > Neverending story, it seems. Regrettably, please accept also > https://github.com/ClusterLabs/booth/pull/33 to call this license > clarification effort complete, Dejan. Will take a look. Cheers, Dejan > -- > Jan (Poki) > ___ > Developers mailing list > Developers@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/developers ___ Developers mailing list Developers@clusterlabs.org http://clusterlabs.org/mailman/listinfo/developers