899766 - Install testdaybot (including node.js) on mozqa.com

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: Infrastructure, defect)

Description

[u279076]

I'd like to install the TestdayBot IRC bot to run on mozqa.com instead of David Burns' personal server. One of the requirements is to have a node.js instance running. 

Do we already have node.js running on mozqa.com?
If not, can we get it set up?

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Anthony, can you please give us the instructions how to setup the testday bot? Once we have those someone can set it up.

Comment 2

[u279076]

https://github.com/AutomatedTester/testdaybot is all the info I have. David Burns should be able to give you more information beyond that.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Ah, thanks Anthony. So I think we can easily get IT to get node.js to be installed. Beside that package we would also need the PIPy irc package (https://pypi.python.org/pypi/irc/).

The question which remains here is, who will maintain the bot instance? It looks like it has to be restarted for each testday with the actual etherpad. As long as it cannot be set via an IRC command we need someone to volunteer for that and who will always be present.

David, is there a way to get this above mentioned feature implemented?

Comment 4

[David Burns :automatedtester]

(In reply to Henrik Skupin (:whimboo) from comment #3)
> Ah, thanks Anthony. So I think we can easily get IT to get node.js to be
> installed. Beside that package we would also need the PIPy irc package
> (https://pypi.python.org/pypi/irc/).

we shouldnt need that since that is python and the bot is written in node.js

> 
> The question which remains here is, who will maintain the bot instance? It
> looks like it has to be restarted for each testday with the actual etherpad.
> As long as it cannot be set via an IRC command we need someone to volunteer
> for that and who will always be present.
> 
> David, is there a way to get this above mentioned feature implemented?

I don't have the bandwidth currently to get that feature added but hopefully we can delegate this to a trusted person at SV to do this.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Brandon, a quick question here because I think that the puppet script will have to be updated too. What's necessary to do here from the IT side? Would it be possible for you to prepare that? Thanks.

Comment 6

[Brandon Burton [:solarce]]

(In reply to Henrik Skupin (:whimboo) from comment #5)
> Brandon, a quick question here because I think that the puppet script will
> have to be updated too. What's necessary to do here from the IT side? Would
> it be possible for you to prepare that? Thanks.

WebOps can help with installing packages on the system through Puppet, which ensures they'll get reinstalled in the event of a system rebuild.

In general we try to stick with what's available as RPMs in the repositories we mirror, which you can get a sense of by doing a 'sudo yum search $packagename$' on the server, but in this case the only dependency of the irc bot is an npm package we don't have an RPM for, so we'll need to build one and put it in our internal Yum repository

Please open a bug in https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=WebOps%3A%20IT-Managed%20Tools about getting the dependencies for the IRC bot packaged and installed on the server and we'll get it assigned

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

David, can you please give feedback which specific node.js package we would need? Thanks.

Comment 8

[David Burns :automatedtester]

(In reply to Henrik Skupin (:whimboo) from comment #7)
> David, can you please give feedback which specific node.js package we would
> need? Thanks.

None, I have committed all the relevant packages to the repo so just need to clone

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Great. So I filed bug 918266 to get mozqa setup.

Comment 10

[Henrik Skupin [:whimboo][⌚️UTC+2]]

I had to reopen bug 919829 given that port 6667 hasn't been opened yet. For using SSL we would have to modify the source of the bot. Sadly its code is not under the official Mozilla account yet. To make it easier for us to maintain, it would be great to get it moved over. David, I have created issue: https://github.com/AutomatedTester/testdaybot/issues/12.

Comment 11

[David Burns :automatedtester]

I will move over in a bit but just so we know github has a pull request system for submitting changes if you want

Comment 12

[David Burns :automatedtester]

moved over and automation added as a team

Comment 13

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Thanks David. A first try on mozqa.com showed me that there are some bugs we have to get fixed first, before we can get it running. I will submit some PR soon.

Comment 14

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Ok, so testdaybot ran last Friday but it failed to quit after 20h and hasn't send the stats to Anthony and David. Looks like some work has to be done here additionally to get it running successfully. I will file issues on the github issue tracker, and work on fixes when I find the time over the next weekend.

Comment 15

[u279076]

What if we just set it to always be running and enable me (or any channel op) the ability to issue it a command to send stats between two timestamps to a given email? Something like:

/msg TestdayBot SENDSTATS 20131010000000 20131010235959 [e-mail]

Comment 16

[u279076]

(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #15)
> What if we just set it to always be running and enable me (or any channel
> op) the ability to issue it a command to send stats between two timestamps
> to a given email? Something like:
> 
> /msg TestdayBot SENDSTATS 20131010000000 20131010235959 [e-mail]

In this way we wouldn't have to worry about turning on/off the bot and we could query for stats when we wanted them.

Comment 17

[Henrik Skupin [:whimboo][⌚️UTC+2]]

That's my idea similar to dynamically setting the etherpad URL. Lets see when I have the time to continue on the bot.

Comment 18

[Henrik Skupin [:whimboo][⌚️UTC+2]]

I have updated the code on mozqa.com to the latest changes in the testdaybot repository. That means that the service for testdaybot on this host is now running via init.d. So all is done here.