863836 - please create a new database for servo buildbot master

Status: VERIFIED FIXED

(Data & BI Services Team :: DB: MySQL, task)

Description

[[e-mail] (:bhearsum)]

We're going to be creating a new buildbot master for the Servo project - one that won't be related to our existing buildbot db.

Let me know what other details you need.

Comment 1

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

Should this go on the buildbot cluster?  Other options are the generic and devtools clusters, and the not-yet-built releng cluster.  I'm not sure who I'm asking, here - Ben, Sheeri, Corey..

Comment 2

[[e-mail] (:bhearsum)]

I'm trying to keep servo infrastructure as close to other RelEng infra to ease consolidation later so my intuition says "buildbot cluster", but I don't know all the implications of that.

Comment 3

[Derek Moore [:dmoore]]

Fixing component!

Comment 4

[Sheeri Cabral [:sheeri]]

Well, for now, how about I make it on the staging server? The implications of having servo on the same machine as buildbot is that buildbot failing is tree-closing.

What's the db name I should put in? something like servo_allizom_org?

Comment 5

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

This isn't a staging instance, so that doesn't seem like a good choice.  Ben, do the trees close if this fails?

Comment 6

[[e-mail] (:bhearsum)]

(In reply to Dustin J. Mitchell [:dustin] from comment #5)
> This isn't a staging instance, so that doesn't seem like a good choice. 

+1

> Ben, do the trees close if this fails?

Servo's workflow is a little different, but the simple answer is "no". Servo can survive outages better than we can on the other Buildbot DB, but it's still going to be a production service...so long outages are bad, of course.

Comment 7

[Sheeri Cabral [:sheeri]]

I know it's not a staging instance, but don't you want one, to test?

Comment 8

[[e-mail] (:bhearsum)]

(In reply to Sheeri Cabral [:sheeri] from comment #7)
> I know it's not a staging instance, but don't you want one, to test?

Yeah - that's a good idea.

Comment 9

[[e-mail] (:bhearsum)]

(In reply to Sheeri Cabral [:sheeri] from comment #4)
> Well, for now, how about I make it on the staging server? The implications
> of having servo on the same machine as buildbot is that buildbot failing is
> tree-closing.
> 
> What's the db name I should put in? something like servo_allizom_org?

Oh, and let's not use servo_allizom_org...how about servo_buildbot_staging?

Comment 10

[Sheeri Cabral [:sheeri]]

How about buildbot_servo_staging that way we can do something like "show databases like "buildbot%" and see everything?

Comment 11

[Sheeri Cabral [:sheeri]]

buildbot_servo_staging db and buildbot_servo user created, password given securely to Ben.

Comment 12

[Sheeri Cabral [:sheeri]]

virtual IP for stage is:

writes: stage-rw-vip.db.scl3.mozilla.com      
reads: stage-ro-vip.db.scl3.mozilla.com

Comment 13

[[e-mail] (:bhearsum)]

Can we get the prod the db created now?

Comment 14

[Sheeri Cabral [:sheeri]]

OK, we can do either devtools or generic, pinging bhearsum in IRC about which he prefers (what might interfere or not play nicely with others).

Comment 15

[Sheeri Cabral [:sheeri]]

I have created buildbot_servo database on the devtools cluster and gave the buildbot_servo user permissions on the database. Will send password securely.

Comment 16

[Sheeri Cabral [:sheeri]]

VIPs:

 devtools-ro-vip.db.scl3.mozilla.com      	
 devtools-rw-vip.db.scl3.mozilla.com

Comment 17

[[e-mail] (:bhearsum)]

tested the rw credentials and they work fine. Thanks!