On Thu, 2015-03-26 at 11:10 +0100, Martin Gerhard Loschwitz wrote: > Richard, > > I added you to the HA group on alioth. Let me know if you need something to > be sponsored. Feel free to do whatever you need with the packages as long > as you manage to keep them working or make them work again :) > > Best regards > Martin Hi Martin, Thank you so much for your reply. I do want to help out, though I do not want to step all over your work either :) I'm very glad to see you are still around and active and willing to sponsor updates to the packages. I'll work with Feri and contribute all I can to help keep debian-ha alive and our cluster stack in pristine condition. I've been communicating with upstream (beekhof, krig, feist), have contributed to upstream as well -> and have gotten the hang of the Pacemaker/Corosync stack utilizing crmsh or pcs/pcsd (pcs/pcsd is my personal favorite cli tool). I honestly didn't see a crmsh package so I started there - so very sorry for how aggressive that ended up looking (I retracted ITP there ofc) :\ --- I'll take some time digging around Alioth, Package Tracker, and reviewing any docs/links you guys provide for contributing. --- I mentioned keeping corosync related libraries within the corosync package - but Feri made a good point by stating we should ask why you decided to break them up; since you likely had a good reason. What's your take on this? --- http://mentors.debian.net/package/crmsh That's what I've done with crmsh. Notice what I did with the rules file (rather than patching the source). I had contributed a hack upstream for making upstream source build work on Debian as well. I'll take a look through the existing package -> to see how you tackled certain aspects. I'm sure also that depends needs to be updated. I can just apply updated source to the old package and bring it up to date with modifications - or is a properly built and tested new package able to be dropped 'on-top'? I rushed it a little bit so krig could look into potentially auto generating debs for the public via OBS -> though the Build-Depends caused him errors testing that out with OBS (SUSE build system). pcs/pcsd is also an interesting subject, due to the ruby gem installation for pcsd. I've been working on the init script (which upstreams provided version doesn't seem to work on Debian), but have tackled a majority of that package already as well. --- Feri, I recall you saying you would like to work on updating corosync -> I can target pacemaker or pcs next, or we can work together on each piece? What would you prefer? Are there any others still active? Looking forward to meeting any of you and working together in the future! --- Alright, sorry for the massive brain picking. I'm rather excited now - I'll get moving :) Best, -- Rik
Attachment:
signature.asc
Description: This is a digitally signed message part