Closed
Bug 1078522
Opened 11 years ago
Closed 10 years ago
Update BuildBot Pulse publisher to use mozillapulse 1.0
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcote, Assigned: catlee)
Details
Attachments
(2 files, 1 obsolete file)
|
1.32 KB,
patch
|
rail
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
|
2.11 KB,
patch
|
rail
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
As part of the Pulse security update, the BuildBot Pulse publisher should be updated to use mozillapulse 1.0. BuildBot already uses its own Pulse account, but it should be updated to start publishing to the new exchange format (exchange/build/ instead of org.mozilla.exchange.build). The timing isn't critical, since we have already bound the old exchange to the new one, but it should be no earlier than Tuesday, Oct 14, since we need to give consumers a chance to upgrade.
BuildBot is still using a very old version of mozillapulse (.4). There have been a few significant changes since then, particularly switching to kombu and enabling ssl. To avoid breaking too many things at once, we should probably upgrade in steps.
Kombu was introduced in mozillapulse 0.80, though 0.90 just has a small fix so we could upgrade to that first. Latest kombu is 3.0.23 which in turn requires amqp (not, apparently, amqplib), the latest of which is 1.4.5.
SSL support by default was introduced in mozillapulse 0.93. After applying that version and restarting, if you don't add any extra config parameters to your publisher code, you'll connect automatically via ssl on the ssl port (5671 for Pulse).
Finally, 1.0 was released today, with the main new feature being the updated exchange names.
Upgrading to 0.90 and 0.93 can be done at any time.
| Assignee | ||
Comment 1•11 years ago
|
||
I think I'd rather set 1.0 as the goal than doing this in steps. We're going to have to get all the python packages mirrored locally first, and jumping to our desired end state means less churn with package mirroring.
| Reporter | ||
Comment 2•11 years ago
|
||
Sure, completely up to you. :)
| Reporter | ||
Comment 3•10 years ago
|
||
A pip freeze of a fresh install of MozillaPulse 1.2.1 gives me this:
amqp==1.4.6
anyjson==0.3.3
kombu==3.0.26
MozillaPulse==1.2.1
pytz==2015.6
wheel==0.24.0
Although wheel isn't required; it's just installed by default in virtualenvs now.
| Reporter | ||
Comment 4•10 years ago
|
||
It would be very good to do this before we move to Pulse in the cloud next week, if there's any way to make that happen.
| Assignee | ||
Comment 5•10 years ago
|
||
Ok, need to make sure all those packages are in our internal pypi first.
| Assignee | ||
Comment 6•10 years ago
|
||
From what I can tell, the only changes to our existing virtualenvs would be:
- MozillaPulse 0.80 -> 1.2.1
- anyjson 0.3 -> 0.3.3
- argparse 1.1 -> 1.2.1
- pytz 2011d -> 2015.6
carrot, and amqplib are no longer required.
the only change there that could have possible impact to other code is the argparse update. I'll dig into that a bit more today.
| Assignee | ||
Comment 7•10 years ago
|
||
published MozillaPulse 1.2.1, argparse 1.2.1 and pytz 2015.6 on our pypi.
| Assignee | ||
Comment 8•10 years ago
|
||
Ran a test of pulse_publisher with the updated libraries, and everything worked fine.
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → catlee
| Assignee | ||
Comment 9•10 years ago
|
||
Attachment #8669935 -
Flags: review?(rail)
| Assignee | ||
Comment 10•10 years ago
|
||
Attachment #8669951 -
Flags: review?(rail)
Updated•10 years ago
|
Attachment #8669935 -
Flags: review?(rail) → review+
Comment 11•10 years ago
|
||
Comment on attachment 8669951 [details] [diff] [review]
Update MozillaPulse for buildbot masters
SSL is the new default now https://hg.mozilla.org/automation/mozillapulse/file/e6d10b16c666/mozillapulse/config.py#l17
The flows look ok:
[cltbld@buildbot-master81.bb.releng.scl3.mozilla.com ~]$ nc -vz pulse.mozilla.org 5671
Connection to pulse.mozilla.org 5671 port [tcp/amqps] succeeded!
Attachment #8669951 -
Flags: review?(rail) → review+
| Assignee | ||
Comment 12•10 years ago
|
||
found a small typo in the puppet patch: anyjson==1.3.3 should be 0.3.3.
also, our puppet manifests don't restart the queue services when updating the virtualenv.
| Assignee | ||
Comment 13•10 years ago
|
||
fixes typo, and ensures queue processors are restarted after the virtualenv changes
Attachment #8669935 -
Attachment is obsolete: true
Attachment #8670337 -
Flags: review?(rail)
Updated•10 years ago
|
Attachment #8670337 -
Flags: review?(rail) → review+
| Assignee | ||
Updated•10 years ago
|
Attachment #8670337 -
Flags: checked-in+
| Assignee | ||
Updated•10 years ago
|
Attachment #8669951 -
Flags: checked-in+
| Assignee | ||
Comment 14•10 years ago
|
||
all pulse publishers have been upgraded
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 15•10 years ago
|
||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•