Re: Status report, week 9 (and 10): FedMsg for Debian
by Simon Chopin
Hi,
Sorry to be late for my reports of the last 2 weeks :/
Also, I apologize if this mail is ill-formed, unfortunate
circumstances force me to
use GMail instead of my usual MUA.
The week 9 of my GSoC was at DebConf, where I haven't done much directly
related to FedMsg. The main highlight is that python-fedmsg is finally
available in
Debian unstable, many thanks to algernon, paultag and olasd. I've also
chatted with
many people about Fedmsg and the infrastructure in general, and
collected -- and hopefully
addressed some of the concerns people have about the project.
I'd especially like to thank Asheesh for doubling the size of my TODO
list in an hour or so :-).
(I might have forgotten some stuff I've done related to the project
during the week,
but I'm sure Nicolas will be happy to fill in the blanks)
The week 10 has been mainly about travelling back to Rennes. I had
planned to hitchhike
my way back, making a detour in Bordeaux. Initially, I should have been able
to get back to work on Wednesday, but since things never go as planned
I eventually
managed to arrive on Friday, to move into my new flat in Rennes on Saturday.
Because life would have been to easy, of course I still don't have
Internet over there,
which means that I wasn't able to push out my GPG backend, which is
finally done.
My plans for the next week are:
* Help upstream get 0.7.0 out the doors, which means amongst other
things upstream the GPG backend.
* Document the data schema used by the Debian endpoints and provide
an easy way to use
those schemas to easily validate a message format.
* Patch fedmsg-relay (or write another one) to be able to deal with
replay requests, either by storing itself the messages or proxying the
request back to the emitter (in case of a single one)
10 years, 7 months
Status report, week 8: FedMsg for Debian
by Simon Chopin
Hello,
Late 8th report for the "FedMsg for Debian" project, the tardiness (and
the fact that I haven't done computer-related for that matter) on Friday
is because I had to take an sudden personal day for family reasons.
I am currently writing this report on my way to DebConf, so forgive me
if I don't provide much links :-).
First of all, I'm pleased to announce that all of my patches so far have
been integrated upstream, thanks to the work of Ralph Bean. This
includes the replay feature server and client side (with a bit of
documentation, although I could have done better on that front), and the
ability to fetch endpoints using SRV records.
I've also worked a bit on debmessenger and fedmsg-meta-debian to improve
the human readability. Whilst doing this I have noticed that there was a
type of mails from the BTS that debmessenger didn't like at all, namely
the "transcript" type, which is the answer to mails at control(a)bugs.d.o.
The solution will be to parse the mail to get the most informations out
of it, and dispatch it in several messages on the bus depending on how
many packages are dealt with in the mail.
I've also been able to assess how shitty the situation is regarding GPG
bindings for Python. There are several implementations available, with
apparently a preference for pygpgme, except that this package is totally
undocumented and isn't pure Python but an extension. Combine the two and
throw a FTBFS on top of that and you can understand why I'm actually
wondering if it wouldn't be best to write my own set of bindings!
I can't say I have plans for next week except attending DebConf. We'll
probably assess the situation with Nicolas, which means I will be
posting a followup to this report soon-ish.
Cheers,
Simon
10 years, 8 months
Status report, week 4: FedMsg for Debian
by Simon Chopin
Hi,
As part of my GSoC project this week, I've done the following:
— Hacked up some -bugs-dist support in debmessenger[1].
— Thought up a preliminary implementation of a replay protocol for
fedmsg in case of dropped messages[2][3].
— Deployed fedmsg on mentors.debian.net (well, most of the work has
been accomplished by Nicolas Dandrimont, kudos for that BTW).
For the curious amongst the readers, you can listen to the chatter
by adding tcp://mentors.debian.net:300[0-4] to the list of
endpoints.
— Implemented service discovery through SRV records in fedmsg
(untested as of today)[4]
For next week, I plan to:
— Rewrite the replay mechanism as the more I think about the current
implementation the less I'm happy with it.
— Deploy a fedmsg gateway that will consume all debian-produced
messages and resend them on a single endpoint, much like [5].
— Work out the last kinks in my packaging (I know, I say that every
week, but try to deal with an overcommitted sponsor ;-) )
— Maybe, deploy an instance of debmessenger somewhere.
Have a nice week-end all!
Cheers,
Simon
[1] https://github.com/laarmen/debmessenger/commit/dde1454cf362f4f4755d6c9b2a...
[2] https://lists.fedoraproject.org/pipermail/messaging-sig/2013-July/000008....
[3] https://github.com/laarmen/fedmsg/tree/feature/replay
[4] https://github.com/laarmen/fedmsg/tree/feature/srv-records
[5] tcp://hub.fedoraproject.org:9940
10 years, 8 months