[ https://ovirt-jira.atlassian.net/browse/OVIRT-406?page=com.atlassian.jira.pl... ] eyal edri [Administrator] reassigned OVIRT-406: ----------------------------------------------- Assignee: bkorren (was: infra) Please start planning the best route for migration, maybe its possible to keep existing foreman proxy and work with a new foreman VM as first step? to ease the dns/dhcp issues? But lets start with specifying the required steps for the install / migration. I'm guessing we can start with 1.11 and upgrade to 1.12 when its out in June.
Migrate foreman.ovirt.org to PHX DC -----------------------------------
Key: OVIRT-406 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-406 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: bkorren
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.
-- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)