Re: fedora-messaging for Copr - what do you need?
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. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/message/DFDYXMSQ55CS6MFUNQOYQ47LJZE7VJMH/
Re: fedora-messaging for Copr - what do you need?
On Sat, Aug 11, 2018 at 10:33 AM Miroslav Suchý 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 . I would use this
> information for .
>
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-le...@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/message/OMIVYTJ27O5Z2QPZFSUXHBYLAZ7VPAZX/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/message/MBGDSJBGNGIKNONMOUCANQAWLX4APS4G/
Re: fedora-messaging for Copr - what do you need?
On Mon, Aug 13, 2018 at 12:52 AM Jeff Johnson 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-le...@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/message/KSAKHYHPVQVHWJFMEBSL6IF3W2JX6MDM/ > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/message/SAA6EVCS2W43Y5ZPA7NHETNMFE3VPCLF/
Re: fedora-messaging for Copr - what do you need?
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? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/message/KSAKHYHPVQVHWJFMEBSL6IF3W2JX6MDM/
