1452001 - Figure out pulse/rabbitmq story for redeployed clusters

Status: RESOLVED FIXED

(Taskcluster :: Services, enhancement)

Description

[Brian Stack [:bstack]]

At the current moment this probably involves wrapping up work on taskcluster-pulse and possibly having optional support for automagically launching rabbitmq into your k8s cluster when you install tc. We should create a separate bug for the latter task if we decide to do it.

Comment 1

[Brian Stack [:bstack]]

For our internal clusters, if we want to deploy before finishing tc-pulse, we may just have to make a little script to automate things with pulseguardian.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Jonas, I think you were signed up for this in our Berlin meeting.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Per bug 1451805, tc-pulse is how we will manage using different namespaces for different clusters in the same AMQP server.  So we will need this even for the staging deployment.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

We're going to require explicit configuration of a pulse account for each pulse-using service.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

I have some patches for that work.  We still need to fix schemas + references for pulse, but that will wait until we've converted a service that uses pulse to the new world order.

Comment 6

[[github robot]]

Commit pushed to master at https://github.com/taskcluster/taskcluster-client

https://github.com/taskcluster/taskcluster-client/commit/cf127658f9f52be671a286838dad540fe821a027
Redeployability Great Library Update - 10.0 (#94)

* Bug 1452001 - pulsepublisher: require hostname, vhost

Always require the hostname (no default) and a vhost.

* Bug 1452001 - de-bablify and fix tests depending on other upgraded libraries

* upgrade tc-lib-* dependencies

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

Ah, bug 1451805 is the remainder of this work.