Migrate foreman.ovirt.org to PHX DC

Description

Migrate the foreman instance from existing all in one 3.4 instance to the new PHX DC.
We should install new foreman server on a new VM, and migrate / add hosts rather than migrate the DB, as we don't have too many hosts / vm which will allow up a clean move and reduce possible errors and also minimal downtime.

Activity

Show:

Former user May 2, 2017 at 9:44 AM

Yes, everything works fine, closing.

Eyal Edri May 1, 2017 at 9:14 AM

can we move to done?

Eyal Edri March 25, 2017 at 11:18 AM

Nice!
Glad to see this finally happening

Former user March 24, 2017 at 11:47 AM

VM moved to PHX. The DNS entry was set to the new IP and clients are successfully getting manifests.
Need to test DNS/PXE functionality as well as ability to apply puppet updates via Jenkins, then this can be closed.

Former user March 23, 2017 at 4:18 PM

I've created an empty VM to simply copy the old Foreman master to PHX for now. Need to disable DHCP on alterway VMs and move it. In parallel I'm testing installation of a full new Foreman in PHX but for now will just do a disk copy using clonezilla.

Done

Details

Assignee

Reporter

Priority

Created February 10, 2016 at 4:16 PM
Updated June 1, 2017 at 11:32 AM
Resolved May 2, 2017 at 9:44 AM