As part of migration of fedmsg from ZMQ to AMQP, I would like to revisit what is Copr sending to fedmsg.
Right now we are sending:
'build.start': { 'what': "build start: user:{user} copr:{copr}" \ " pkg:{pkg} build:{build} ip:{ip} pid:{pid}", }, 'chroot.start': { 'what': "chroot start: chroot:{chroot} user:{user}" \ " copr:{copr} pkg:{pkg} build:{build} ip:{ip} pid:{pid}", }, 'build.end': { 'what': "build end: user:{user} copr:{copr} build:{build}" \ " pkg:{pkg} version:{version} ip:{ip} pid:{pid} status:{status}", },
I have several ideas what we *should* send. Thou, I'd like to hear *your* use case. You do not need to be technically detailed. Something like:
I can utilize if you send message and the end/start of XXX and you will put there information YYYY. I would use this information for ZZZZ.
Miroslav
Changing Fedora infrastructure to use AMQP brings up a different usage case.
Build systems tend to eventually invoke rpmbuild to do the actual build.
Would you like rpmbuild to, say, send time stamped progress messages directly through AMQP?
The usage case for AMQP messages in rpmbuild starts with the start/end times to collect statistics on package builds, but could also include other resource usages needed by rpmbuild.
With RPM+AMQP, there is additional detailed information about installations that can be sent directly as well.
Any interest in receiving AMQP messages directly from RPM?
On Mon, Aug 13, 2018 at 12:52 AM Jeff Johnson n3npq.jbj@gmail.com wrote:
Changing Fedora infrastructure to use AMQP brings up a different usage case.
Build systems tend to eventually invoke rpmbuild to do the actual build.
Would you like rpmbuild to, say, send time stamped progress messages directly through AMQP?
The usage case for AMQP messages in rpmbuild starts with the start/end times to collect statistics on package builds, but could also include other resource usages needed by rpmbuild.
With RPM+AMQP, there is additional detailed information about installations that can be sent directly as well.
Any interest in receiving AMQP messages directly from RPM?
Jeff, as far as building goes, note that most build system (includding Copr with default project settings) invoke rpmbuild inside a chroot with network disabled. It's probably easier to implement the messaging on higher level.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
There is no reason why a connection to an AMQP broker cannot be opened and carried into a chroot that has networking disabled: rpm installs already perform chroot's carrying multiple open Berkeley DB fdnos into the chroot.
On Sat, Aug 11, 2018 at 10:33 AM Miroslav Suchý msuchy@redhat.com wrote:
As part of migration of fedmsg from ZMQ to AMQP, I would like to revisit what is Copr sending to fedmsg.
Right now we are sending:
'build.start': { 'what': "build start: user:{user} copr:{copr}" \ " pkg:{pkg} build:{build} ip:{ip} pid:{pid}", }, 'chroot.start': { 'what': "chroot start: chroot:{chroot} user:{user}" \ " copr:{copr} pkg:{pkg} build:{build} ip:{ip}pid:{pid}", }, 'build.end': { 'what': "build end: user:{user} copr:{copr} build:{build}" \ " pkg:{pkg} version:{version} ip:{ip} pid:{pid} status:{status}", },
I have several ideas what we *should* send. Thou, I'd like to hear *your* use case. You do not need to be technically detailed. Something like:
I can utilize if you send message and the end/start of XXX and you will put there information YYYY. I would use this information for ZZZZ.
If there is nobody listening to current Copr messages, maybe we could invest into making their format more easier to parse? I.e. instead of the 'what' fields, actually output some better structured information that does not necessitate string splitting on whitespaces. I think with the introduction of the new messaging system, this could be a good time to do this.
clime
Miroslav _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
-
Jeff Johnson -
Michal Novotny -
Miroslav Suchý