Project

General

Profile

Actions
Copy link

Feature #762

closed

Feature #751: BugZilla migration

define criteria of successful migration

Added by Florian Effenberger about 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Robinson Tryon
Category:
-
Target version:
-
Start date:
Due date:
% Done:

100%

Tags:
URL:

Description

The window of decision when the switch is plugged is rather short - ~15 minutes. It is crucial to define a criteria for successful migration so we don't waste time when "things are hot"

Subtasks 1 (0 open — 1 closed)

Bug #829: Verify that the Bugzilla-test install works with known consumers of LibreOffice bug data from bugs.freedesktop.orgClosedRobinson Tryon

Actions
Actions
Copy link
 #1

Updated by Robinson Tryon about 10 years ago

Florian Effenberger wrote:

The window of decision when the switch is plugged is rather short - ~15 minutes. It is crucial to define a criteria for successful migration so we don't waste time when "things are hot"

There's a certain amount we'll be able to test in 15 minutes, and a certain amount we won't be able to test. We'll have to do our best :-)

Here's a quick list of some of the most common Bugzilla activities that we'll want to make sure work:

Putting a bit of a load on the server would also be helpful, as it would ensure that there's nothing insanely brittle with the database such that it will collapse with just a handful of users.

Actions
Copy link
 #2

Updated by Robinson Tryon about 10 years ago

  • Status changed from New to In Progress

There are tests outside of the Bugzilla web front-end as well:

  • Making sure that the BSA can talk to Bugzilla (Cloph & Rob Snelders are most knowledgeable here) (#754)
  • Making sure that bots and other tools can talk to Bugzilla (should transition over fluidly if they already point at bugs.libreoffice.org)

There are multiple systems that consume data from FDO Bugzilla (https://wiki.documentfoundation.org/QA/Bugzilla/TDF_Bugzilla_Proposal#Identify_systems_dependent_upon_Freedesktop.org), but we don't have to migrate and test all of those services in our 15minute test window. It would be clever for us to do a dry run of those systems against our test install well before the migration date, just to make sure that all the pieces can talk to Bugzilla + a migrated database, all running in one of our TDF VMs.

Actions
Copy link
 #3

Updated by Florian Effenberger about 10 years ago

As for the bots, the wiki, etc., this is something that can be tested well in advance with the existing VM and database dump - please do so
Testing again when the migration actually took place is fine, but let's test ahead of the migration whatever we can to limit the risks

Actions
Copy link
 #4

Updated by Robinson Tryon about 10 years ago

  • Status changed from In Progress to Resolved

Florian Effenberger wrote:

As for the bots, the wiki, etc., this is something that can be tested well in advance with the existing VM and database dump - please do so

Yes, see new bug #829 ("Verify that the Bugzilla-test install works with known consumers of LibreOffice bug data from bugs.freedesktop.org") created for this pre-migration testing purpose.

Actions
Copy link
 #5

Updated by Florian Effenberger almost 10 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF