Opened 6 years ago

Closed 6 years ago

#2850 closed task (fixed)

Host "real" metabuildbot on bb infra

Reported by: dustin Owned by: sa2ajj
Priority: minor Milestone: sys - on-bb-infra
Version: Keywords: ansible, flosoft
Cc:

Description

buildbot.buildbot.net is currently hosted on the flosoft server, and needs to be moved to Buildbot infrastructure.

This is the "real" buildbot master that we depend on for real test results, updates to docs and packages of the latest versions of Buildbot.

Change History (17)

comment:2 Changed 6 years ago by sa2ajj

  • Keywords ansible added
  • Owner set to sa2ajj
  • Status changed from new to accepted
  • Version 0.8.9 deleted

After the PR from #2851 is accepted, this should be pretty easy.

comment:3 Changed 6 years ago by sa2ajj

Should we run the latest 'eight' there or the latest release? (I'm inclined toward the latter, though the fix for #3107 seems to be important in the current eight.)

comment:4 Changed 6 years ago by sa2ajj

PR in works #40.

comment:5 Changed 6 years ago by sa2ajj

For the record:

  • according to network.txt this belongs to service3.bb.net
  • the latter has one jail configured
  • I see no trace of jail configuration in /etc/rc.conf

I'll work on adapting the jail role in this PR.

comment:6 Changed 6 years ago by dustin

Since we have the capacity to do so already, let's run the latest of the eight branch.

comment:7 Changed 6 years ago by sa2ajj

  • Keywords flosoft added

comment:8 Changed 6 years ago by sa2ajj

It's coming as part of PR#47. (Maybe I should actually split it somehow...)

comment:9 Changed 6 years ago by sa2ajj

Actually, PR#40 got the corresponding changes.

It's now merged.

Things to do:

  • get a copy of the old database
  • change DNS
  • make sure that existing build slaves successfully connect to it

Dustin, anything I should do with the database after it's copied to the new server?

comment:10 Changed 6 years ago by dustin

I don't think so.

We had discussed modifying the 'masters' table during the move, but there is no such table in 0.8.x.

comment:11 Changed 6 years ago by sa2ajj

Dustin, do we need to keep all those pickles for slaves/builders?

comment:12 Changed 6 years ago by dustin

Nope

comment:13 Changed 6 years ago by sa2ajj

so we loose all history then

comment:14 Changed 6 years ago by sa2ajj

I stopped master @ flosoft, copied database over and started the new master. It's now visible at http://140.211.10.239

I tried to manually update DNS, but the changes are not visible even on the DNS slaves. Right, I forgot to say 'rndc reload' first. Now checking the situation...

comment:15 Changed 6 years ago by sa2ajj

The situation seems to be OK, we just need for the DNS changes to propagate to users.

comment:16 Changed 6 years ago by sa2ajj

The PR for changing DNS -- GHBI:57

comment:17 Changed 6 years ago by sa2ajj

  • Resolution set to fixed
  • Status changed from accepted to closed

All the bits are merged!

Note: See TracTickets for help on using tickets.