Sent from phone, thus brief. Am 09.06.2015 19:01 schrieb "Brian Knox" <[email protected]>: > > Coordinating on the mailing list is fine with me. My employer > (DigitalOcean) has given the rsyslog project a fairly sizeable free hosting > budget so I'd be remiss to not advocate for us ;).
I just realize that I slipped something (the Digital Ocean sponsoring) that I wanted to announce more formally ... Well that will follow but let me say now that it is very useful and appreciated :) Rainer > If another option works > out to be better I certainly understand! > > I totally agree that converging on an agreed upon problem statement is the > right place to start. > > Cheers, > Brian > > On Tue, Jun 9, 2015 at 12:53 PM, David Lang <[email protected]> wrote: > > > On Tue, 9 Jun 2015, Rainer Gerhards wrote: > > > > Hi all, > >> > >> chances are extremely well to get to better packaging projects. We had > >> some discussions internally in Adiscon, and I was able to secure the > >> help of Florian Riedl for getting this in the best possible shape. > >> > >> Our goal is to get > >> > >> - better packages > >> - more timely support for new distro releases > >> - support for a broader set of distros (e.g. Fedora, often requested) > >> - more ability for the community to steer this previous all-Adiscon > >> project > >> > >> The 0mq discussion that started this thread is a good example of what > >> this means. > >> > >> With the help of more community involvment we can reach the goals. And > >> in order to make it easier to contribute, we need to streamline the > >> process of how we build, release, test, and announce packages. > >> > >> Thankfully, Brian has offered to become an active team member. It > >> would be great if others would also join in. > >> > >> I currently think that the right path to success is to start with > >> small but sufficiently large project part. So I would propose that we > >> focus on Ubuntu initially, get that part organized, learn a couple of > >> things and apply the gained experience later to a "final" project that > >> covers other distros as well (as mentioned by darix, the use of OBS > >> sounds very appealing to me). > >> > >> In order to get going, I would like to see some ideas float on: > >> > >> - how should we communicate? > >> (rsyslog mailing list, dedicated mailing list, github issue > >> trackers, IRC, ...) > >> > > > > I'd say the rsyslog mailing list, failing that a dedicated mailing list. > > But I think that the issues we will be working through are useful to people > > who need to roll their own version (to test something from git, or to > > enable specific features). > > > > - where do we track issues? > >> (I have a strong preferrence for the github issue trackers) > >> - what about doc? > >> - where should we place the build platform > >> (cloud I would guess, could we use Digital Ocean sponsorship for this)? > >> > > > > I don't know the details of using it, but the Suse Open Build Platform is > > already setup to support a whole bunch of target distros. How close does it > > come to covering everything we need? > > > > Can it be used for all the different uses we want from this (distro > > release builds, nightly builds, other) > > > > If we have to roll our own infrastructure, some sort of cloud system is > > right. Google donates time on their cloud system to opensource projects, I > > don't know if it would be enough or not. Sponsorship from whoever is good > > :-) > > > > - when do we start ;) > >> > > > > Clarification of the problem statement and where we are starting from :-) > > > > right now there is the rsyslog-pkg-* repos on github that have the scripts > > that adiscon uses internally. As I found when I went to use them, there are > > a few oddities and too much hard-coded for adiscon internal use. But there > > is also a lot of useful stuff there as well. > > > > As we look at the build options, let's see how much of the existing stuff > > we can re-use. > > > > Also, let's try to make this be something that people can use when > > building from git. > > > > David Lang > > > > > > - ... whatever else I haven't yet thought about. > >> > >> Please take a moment to voice your preferrences! > >> > >> Thanks, > >> Rainer > >> > >> > >> 2015-06-03 21:08 GMT+02:00 David Lang <[email protected]>: > >> > >>> take a look at > >>> > >>> https://github.com/rsyslog/rsyslog-pkg-ubuntu > >>> > >>> to build locally without using the PPA infrastructure I apply the > >>> attached > >>> patch (remove the sections for disabling usertools, that's a debugging > >>> thing > >>> I have in place at the moment) > >>> > >>> do pbuilder --create to create the compile environment, then I use the > >>> following script to pull the latest updates and compile test packages > >>> > >>> find . -name .git |sed s/.git// |while read file > >>> do > >>> echo "$file" > >>> cd $file > >>> /usr/bin/git fetch > >>> /usr/bin/git pull > >>> /usr/bin/git fetch --tags > >>> # /usr/bin/git gc -q --aggressive > >>> autoreconf -fi > >>> ./configure -q > >>> rm *master* > >>> make dist --quiet > >>> cd - > >>> done > >>> echo "finished making source packages" > >>> cd rsyslog-pkg-ubuntu > >>> rm */LAST_VERSION.* > >>> for i in libestr liblogging liblognorm librelp rsyslog > >>> do > >>> cd $i > >>> rm ${i}_* > >>> cp ../../$i/*master* . > >>> ../scripts/auto_daily_project.sh trusty v8-devel master > >>> ( > >>> echo '1' > >>> echo '1' > >>> echo '1' > >>> echo '1' > >>> ) |../scripts/build.sh > >>> echo "finished making $i" > >>> cd - > >>> done > >>> > >>> This should help get you started :-) > >>> > >>> David Lang > >>> > >>> On Wed, 3 Jun 2015, Brian Knox wrote: > >>> > >>> Date: Wed, 3 Jun 2015 11:48:20 -0400 > >>>> From: Brian Knox <[email protected]> > >>>> Reply-To: rsyslog-users <[email protected]> > >>>> To: rsyslog-users <[email protected]> > >>>> Subject: Re: [rsyslog] rsyslog adiscon packages > >>>> > >>>> > >>>> Ubuntu LTS is currently what I'm using so that's advantageous. In > >>>> addition, I've built a custom rsyslog package for Ubuntu that includes > >>>> omczmq / imczmq along with debs for the dependencies. However, my > >>>> rsyslog > >>>> package is monolithic and I'm using brew2deb, which is kind of a strange > >>>> wrapper around fpm and homebrew that probably isn't the best way to do > >>>> things. > >>>> > >>>> Ubuntu and Debian pacakge libzmq (but not czmq). Their packages are > >>>> behind > >>>> current, but maybe their packages would be a good and hopefully easy > >>>> place > >>>> to start, depending on how packages are being built currently for the > >>>> ubuntu repo. > >>>> > >>>> If there's build scripts for the current repo now, I'd be happy to work > >>>> through them and do the work. > >>>> > >>>> Brian > >>>> > >>>> > >>>> On Wed, Jun 3, 2015 at 11:38 AM, Rainer Gerhards > >>>> <[email protected]> > >>>> wrote: > >>>> > >>>> Would it be a good idea to start with Ubuntu? > >>>>> > >>>>> Sent from phone, thus brief. > >>>>> Am 03.06.2015 16:23 schrieb "Brian Knox" <[email protected]>: > >>>>> > >>>>> I'm on board! > >>>>>> > >>>>>> Cheers, > >>>>>> Brian > >>>>>> > >>>>>> On Wed, Jun 3, 2015 at 10:07 AM, Rainer Gerhards < > >>>>>> > >>>>> > >>>>> [email protected] > >>>>> > >>>>>> > >>>>>>> > >>>>>>> wrote: > >>>>>> > >>>>>> Sent from phone, thus brief. > >>>>>>> Am 03.06.2015 15:58 schrieb "Brian Knox" <[email protected]>: > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> I'm a member of the zeromq team :) > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> I know ;) > >>>>>>> > >>>>>>> What would I need to do? > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Join the rsyslog release team and keep an eye especially on zmq. As I > >>>>>>> > >>>>>> > >>>>>> wrote > >>>>>> > >>>>>>> > >>>>>>> is just something we need to newly setup. > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> Brian > >>>>>>>> > >>>>>>>> On Wed, Jun 3, 2015 at 9:56 AM, Rainer Gerhards < > >>>>>>>> > >>>>>>> > >>>>>>> [email protected]> > >>>>>>> > >>>>>>>> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>> 2015-06-03 14:50 GMT+02:00 Brian Knox <[email protected]>: > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> I've been working on the new zeromq plugins ( contrib/omczmq and > >>>>>>>>>> contrib/imczmq) for a bit, and have been using them in production > >>>>>>>>>> > >>>>>>>>> > >>>>>>> myself > >>>>>>> > >>>>>>>> > >>>>>>>>>> for quite awhile. > >>>>>>>>>> > >>>>>>>>>> Yesterday, the zeromq organization released zeromq 4.1 ( > >>>>>>>>>> http://zeromq.org/intro:get-the-software ) and czmq 3.0 ( > >>>>>>>>>> http://czmq.zeromq.org/page:get-the-software ) stable releases, > >>>>>>>>>> > >>>>>>>>> > >>>>>>> which > >>>>>>> > >>>>>>>> > >>>>>>>>> are > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> the versions of zeromq and czmq ( a nice C api on top of libzmq ) > >>>>>>>>>> > >>>>>>>>> > >>>>>>> that > >>>>>>> > >>>>>>>> > >>>>>>>>>> om/imczmq depend on. > >>>>>>>>>> > >>>>>>>>>> I was wondering if it would be possible to get these added to the > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> packages > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> now the same way librdkafka / omkafka is set up. > >>>>>>>>>> > >>>>>>>>>> The dependencies are: > >>>>>>>>>> > >>>>>>>>>> * libsodium ( included in most distros now afaik, but latest > >>>>>>>>>> > >>>>>>>>> > >>>>> stable > >>>>> > >>>>>> > >>>>>>>>> source > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> is also at > >>>>>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>> https://download.libsodium.org/libsodium/releases/libsodium-1.0.3.tar.gz > >>>>> > >>>>>> > >>>>>>>>> ) > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> * zeromq 4.1 ( http://download.zeromq.org/zeromq-4.1.1.tar.gz ) > >>>>>>>>>> * czmq 3.0 ( http://download.zeromq.org/czmq-3.0.1.tar.gz ) > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> The main "problem" is that we do not want to be responsible to > >>>>>>>>> maintain 0mq in regard to checking for patches etc... However, if a > >>>>>>>>> member of the 0mq team is also a member of our release team and > >>>>>>>>> > >>>>>>>> > >>>>> looks > >>>>> > >>>>>> > >>>>>>>>> after that, this problem can be solved ;) > >>>>>>>>> > >>>>>>>>> Maybe we could use a DigitalOcean droplet to run the package > >>>>>>>>> > >>>>>>>> > >>>>> creation > >>>>> > >>>>>> > >>>>>>>>> scripts in the future, this would also solve a bit on the > >>>>>>>>> collaboration front. What do you think? > >>>>>>>>> > >>>>>>>>> If that's a way to go, it's probably not done immediately, as "a > >>>>>>>>> little bit of setup and redesign work" is involved, but we could > >>>>>>>>> > >>>>>>>> > >>>>> work > >>>>> > >>>>>> > >>>>>>>>> towards that goal... > >>>>>>>>> > >>>>>>>>> Rainer > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> The only option flag needed is --enable-libsodium on the zeromq > >>>>>>>>>> > >>>>>>>>> > >>>>> 4.1 > >>>>> > >>>>>> > >>>>>>>>> build. > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> I'd be happy to work with whoever works on the packages. Getting > >>>>>>>>>> > >>>>>>>>> > >>>>>>> this > >>>>>>> > >>>>>>>> > >>>>>>>>> easy > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> to install would be helpful, and the more people attempting to > >>>>>>>>>> > >>>>>>>>> > >>>>> use > >>>>> > >>>>>> > >>>>>>> the > >>>>>>> > >>>>>>>> > >>>>>>>>>> plugins the more feedback I can get. > >>>>>>>>>> > >>>>>>>>>> Cheers, > >>>>>>>>>> Brian > >>>>>>>>>> _______________________________________________ > >>>>>>>>>> rsyslog mailing list > >>>>>>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>>>>>>>>> http://www.rsyslog.com/professional-services/ > >>>>>>>>>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>>>>>>>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >>>>>>>>>> > >>>>>>>>> > >>>>>>> myriad > >>>>>>> > >>>>>>>> > >>>>>>>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if > >>>>>>>>> > >>>>>>>> > >>>>>> you > >>>>>> > >>>>>>> > >>>>>>>>> DON'T LIKE THAT. > >>>>>>>>> _______________________________________________ > >>>>>>>>> rsyslog mailing list > >>>>>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>>>>>>>> http://www.rsyslog.com/professional-services/ > >>>>>>>>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>>>>>>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >>>>>>>>> > >>>>>>>> > >>>>>>> myriad > >>>>>>> > >>>>>>>> > >>>>>>>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if > >>>>>>>>> > >>>>>>>> > >>>>>> you > >>>>>> > >>>>>>> > >>>>>>>>> DON'T LIKE THAT. > >>>>>>>>> > >>>>>>>>> _______________________________________________ > >>>>>>>> rsyslog mailing list > >>>>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>>>>>>> http://www.rsyslog.com/professional-services/ > >>>>>>>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>>>>>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >>>>>>>> > >>>>>>> > >>>>>> myriad > >>>>>> > >>>>>>> > >>>>>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if > >>>>>>> you > >>>>>>> DON'T LIKE THAT. > >>>>>>> _______________________________________________ > >>>>>>> rsyslog mailing list > >>>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>>>>>> http://www.rsyslog.com/professional-services/ > >>>>>>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>>>>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >>>>>>> > >>>>>> > >>>>> myriad > >>>>> > >>>>>> > >>>>>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if > >>>>>>> you > >>>>>>> DON'T LIKE THAT. > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>> rsyslog mailing list > >>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>>>>> http://www.rsyslog.com/professional-services/ > >>>>>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>>>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >>>>>> myriad > >>>>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > >>>>>> DON'T LIKE THAT. > >>>>>> > >>>>>> _______________________________________________ > >>>>> rsyslog mailing list > >>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>>>> http://www.rsyslog.com/professional-services/ > >>>>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a > >>>>> myriad > >>>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > >>>>> DON'T LIKE THAT. > >>>>> > >>>>> _______________________________________________ > >>>> rsyslog mailing list > >>>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>>> http://www.rsyslog.com/professional-services/ > >>>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > >>>> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > >>>> DON'T > >>>> LIKE THAT. > >>>> > >>> > >>> > >>> _______________________________________________ > >>> rsyslog mailing list > >>> http://lists.adiscon.net/mailman/listinfo/rsyslog > >>> http://www.rsyslog.com/professional-services/ > >>> What's up with rsyslog? Follow https://twitter.com/rgerhards > >>> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > >>> of > >>> sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T > >>> LIKE THAT. > >>> > >> _______________________________________________ > >> rsyslog mailing list > >> http://lists.adiscon.net/mailman/listinfo/rsyslog > >> http://www.rsyslog.com/professional-services/ > >> What's up with rsyslog? Follow https://twitter.com/rgerhards > >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > >> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > >> DON'T LIKE THAT. > >> > >> _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com/professional-services/ > > What's up with rsyslog? Follow https://twitter.com/rgerhards > > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > > DON'T LIKE THAT. > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
