Project

General

Profile

Task #1465

migration of website VM host

Added by Florian Effenberger about 2 years ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Category:
Virtualization
Target version:
Team - Q2/2017
Start date:
Due date:
% Done:

100%

Estimated time:
Tags:
URL:

Description

Our current website VM host is on a regular root server, with less redundancy than our big boxes.
The scope of this ticket is to migrate the website VM back to our main hardware.


Related issues

Related to Infrastructure - Task #1835: migration to own rackClosed2016-04-27

Related to Infrastructure - Task #1863: Remove vm138 from dauntlessNew

History

#1 Updated by Dennis Roczek about 2 years ago

  • Category set to Virtualization

#2 Updated by Florian Effenberger about 2 years ago

  • Target version changed from Q4/2015 to Q1/2016

Deferred due to new backup server taking higher priority, and we run out of maintenance windows this years

#3 Updated by Florian Effenberger almost 2 years ago

Have any efforts been taken in this already? I really would love to get rid of the additional box...

#4 Updated by Alexander Werner almost 2 years ago

  • Related to Task #1835: migration to own rack added

#5 Updated by Alexander Werner almost 2 years ago

  • Target version changed from Q1/2016 to Q2/2016

This is blocked by the migration #1835, so very improbable to happen in Q1.

#6 Updated by Alexander Werner almost 2 years ago

  • Related to Task #1863: Remove vm138 from dauntless added

#7 Updated by Florian Effenberger over 1 year ago

  • Due date set to 2016-07-31
  • Target version changed from Q2/2016 to Q3/2016

A possible topic for our in-person infra meeting

#8 Updated by Florian Effenberger over 1 year ago

  • Due date deleted (2016-07-31)
  • Priority changed from Normal to High
  • Target version changed from Q3/2016 to Q4/2016

#9 Updated by Florian Effenberger over 1 year ago

  • Target version changed from Q4/2016 to Qlater

#10 Updated by Florian Effenberger over 1 year ago

  • Assignee changed from Alexander Werner to Christian Lohmaier
  • Priority changed from High to Normal
  • Target version changed from Qlater to Q3/2016

Re-assigning to Cloph

#11 Updated by Christian Lohmaier over 1 year ago

actually it runs in a VM on the separate server, so we should be able to migrate that over with minimal downtime. (at least live-migration within hypervisors did work OK so far...)

#12 Updated by Florian Effenberger over 1 year ago

The Document Foundation Redmine wrote on 2016-08-08 at 15:01:

actually it runs in a VM on the separate server, so we should be able to
migrate that over with minimal downtime. (at least live-migration within
hypervisors did work OK so far...)

I assume the bandwith problem is a blocker for that, and then we can
migrate?

#13 Updated by Florian Effenberger about 1 year ago

  • Assignee changed from Christian Lohmaier to Guilhem Moulin
  • Target version changed from Q3/2016 to Qlater

re-assigning to Guilhem in order to clean up Redmine queues
nothing concrete to do at the moment

#14 Updated by Florian Effenberger about 1 year ago

  • Target version changed from Qlater to Q1/2017

As things in infra have now settled, I'd like to aim for Q1 to get this

#15 Updated by Florian Effenberger 8 months ago

  • Target version changed from Q1/2017 to Q2/2017

#16 Updated by Guilhem Moulin 6 months ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Redeployed to our infra on a fresh Debian 8 VM. Since vm185 was migrated ~ 2 months ago there is nothing on said root server anymore.

#17 Updated by Florian Effenberger 6 months ago

Redeployed to our infra on a fresh Debian 8 VM. Since vm185 was migrated
~ 2 months ago there is nothing on said root server anymore.

Sounds great!

I propose shutting down the web server to see if there are any sites/DNS
records still pointing to that box.

That being said, is there anything noteworthy on the box or can we wipe
and cancel it soon? I'll then chat with manitu about cancellation. I
don't think we have other use for it, right? :)

#18 Updated by Guilhem Moulin 6 months ago

Florian Effenberger wrote:

I propose shutting down the web server to see if there are any sites/DNS
records still pointing to that box.

The old webserver is already offline as I reused its IPs for the new VM :-)

That being said, is there anything noteworthy on the box or can we wipe
and cancel it soon? I'll then chat with manitu about cancellation. I
don't think we have other use for it, right? :)

The old vm168 also used to serve libreofficebox (now a static site), but I migrated it as well. I didn't check the homedirs but I don't think there is anything of interest anymore (copied the logs over, too ;-)

#19 Updated by Florian Effenberger 6 months ago

The old vm168 also used to serve libreofficebox (now a static site), but
I migrated it as well. I didn't check the homedirs but I don't think
there is anything of interest anymore (copied the logs over, too ;-)

Great! I'll check the cancellation period and get back to you then. :)

#20 Updated by Florian Effenberger 6 months ago

Great! I'll check the cancellation period and get back to you then. :)

Can you quickly confirm it's this host we're talking about?

host-20150218.documentfoundation.org
89.238.68.241

#21 Updated by Guilhem Moulin 6 months ago

Correct

Also available in: Atom PDF