Comments

• 

  almost 9 years ago by oholecek | Reply

  Time for some results!
  

  First day I spent with packaging all the requirements (first time that I packaged python modules, so it took a little longer) and fedmsg itself. Everything needed is for now in home:oholecek:fedmsg.
  Setup of fedmsg and openQA plugin was done quite easily (openQA plugin depends on not yet merged PR#476) and by the end of the next day I have had openQA publishing its events on fedmsg!
  Trouble started when I tried to attach IRCbot plugin provided by fedmsg which apparently wasn't as straightforward as I thought. Trying to solve this hiccup took me next day, but at least I understood 0mq and Moksha a little better. To add insult to injury, at the end the problem was that I used too long IRCbot nick! facepalm
  

  OBS Time!
  

  After openQA<->fedmsg part basically done, I started my venture into OBSland. Since I had no previous experience with code of OBS I merely deployed personal test instance into container, cloned git repo and tried to poke it to see what happens.
  Long story short, I don't have OBS plugin for fedmsg, yet.
  
  

  Conclusion:
  

  Throughout this exercise I ask myself multiple times (especially when I was hunting down that damned IRC bot) what fedmsg has that plain 0mq doesn't. Whether it would be feasible to come with something similar but, let's say, more suited for our infra:

  • if I disregard my error and pain with the IRC, fedmsg deployment is rather simple and comes with plenty tools. I didn't deploy 0mq so far so I can't comment of it's complexity, but I couldn't find any readily available CLI tools for debugging (at least at TW repository).
  • one config change topic_prefix='org.opensuse' and we have .. osmsg?
  • open question is if static and distributed endpoints configuration is ok for us or would prefer either automated or static and centralized configuration. My test setup is only two hosts wide, but I took look at fedora's configuration and what they have looks daunting.

×
Edit Comment 1682
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
####Time for some results!<br /> First day I spent with packaging all the requirements (first time that I packaged python modules, so it took a little longer) and fedmsg itself. Everything needed is for now in [home:oholecek:fedmsg](https://build.opensuse.org/project/show/home:oholecek:fedmsg).<br /> Setup of **fedmsg** and **openQA** plugin was done quite easily (**openQA** plugin depends on not yet merged [PR#476](https://github.com/os-autoinst/openQA/pull/476)) and by the end of the next day I have had **openQA** publishing its events on **fedmsg**!<br /> Trouble started when I tried to attach IRCbot plugin provided by **fedmsg** which apparently wasn't as straightforward as I thought. Trying to solve this hiccup took me next day, but at least I understood [0mq](http://zguide.zeromq.org/page:all) and [Moksha](http://mokshaproject.net/) a little better. To add insult to injury, at the end the problem was that I used too long IRCbot nick! *facepalm*<br /> ####OBS Time!<br /> After **openQA**<->**fedmsg** part basically done, I started my venture into *OBSland*. Since I had no previous experience with code of **OBS** I merely deployed personal test instance into container, cloned git repo and tried to poke it to see what happens.<br /> Long story short, I don't have **OBS** plugin for fedmsg, yet.<br /> <br /> ####Conclusion:<br /> Throughout this exercise I ask myself multiple times (especially when I was hunting down that damned IRC bot) what **fedmsg** has that plain *0mq* doesn't. Whether it would be feasible to come with something similar but, let's say, more suited for our infra: * if I disregard my error and pain with the IRC, **fedmsg** deployment is rather simple and comes with plenty tools. I didn't deploy **0mq** so far so I can't comment of it's complexity, but I couldn't find any readily available CLI tools for debugging (at least at **TW** repository). * one config change `topic_prefix='org.opensuse'` and we have .. *osmsg*? * open question is if static and distributed endpoints configuration is ok for us or would prefer either automated or static and centralized configuration. My test setup is only two hosts wide, but I took look at fedora's configuration and what they have looks daunting.
 
×
Reply to oholecek
Time for some results!

First day I spent with packaging all the requirements (first time that I packaged python modules, so it took a little longer) and fedmsg itself. Everything needed is for now in home:oholecek:fedmsg.
Setup of fedmsg and openQA plugin was done quite easily (openQA plugin depends on not yet merged PR#476) and by the end of the next day I have had openQA publishing its events on fedmsg!
Trouble started when I tried to attach IRCbot plugin provided by fedmsg which apparently wasn't as straightforward as I thought. Trying to solve this hiccup took me next day, but at least I understood 0mq and Moksha a little better. To add insult to injury, at the end the problem was that I used too long IRCbot nick! facepalm

OBS Time!

After openQA<->fedmsg part basically done, I started my venture into OBSland. Since I had no previous experience with code of OBS I merely deployed personal test instance into container, cloned git repo and tried to poke it to see what happens.
Long story short, I don't have OBS plugin for fedmsg, yet.


Conclusion:

Throughout this exercise I ask myself multiple times (especially when I was hunting down that damned IRC bot) what fedmsg has that plain 0mq doesn't. Whether it would be feasible to come with something similar but, let's say, more suited for our infra:
• if I disregard my error and pain with the IRC, fedmsg deployment is rather simple and comes with plenty tools. I didn't deploy 0mq so far so I can't comment of it's complexity, but I couldn't find any readily available CLI tools for debugging (at least at TW repository).
• one config change topic_prefix='org.opensuse' and we have .. osmsg?
• open question is if static and distributed endpoints configuration is ok for us or would prefer either automated or static and centralized configuration. My test setup is only two hosts wide, but I took look at fedora's configuration and what they have looks daunting.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview