Migration for the rackspace servers
Hello, Please review the plan I've wrote for the migration. MUST REQUIREMENTS * Gluster data domain * Export domain * Open a ticket to rackspace regarding static MAC address mapping STEPS 1. Install rackspace03.ovirt.org 2. Create gluster based DC and add gluser storage as data domain. 3. Add rackspace03.ovirt.org into the DC. 4. Create export domain. 5. Attach export domain into rackspace[01/02].ovirt.org. 6. Poweoff all VMs on rackspace[01/02].ovirt.org and export them. 7. Attach export domain to the gluster based dc 8. Import all vms 9. Poweroff vms and check their statuses/connectivity. In jenkins as well. 10. Add rackspace[01/02].ovirt.org to the gluster based dc 11. Do steps 5-10 for rackspace02 Will remove the local DCs a week after migration after we will be sure that everything is ok. - Kiril
On Mon, Oct 14, 2013 at 09:23:06AM -0400, Kiril Nesenko wrote:
Hello,
Please review the plan I've wrote for the migration.
MUST REQUIREMENTS * Gluster data domain * Export domain * Open a ticket to rackspace regarding static MAC address mapping
This was expanded on in the latest meeting. I think you said every mac address at rackspace can only originate from a certain other mac address. Isn't this network port in the switch because we have a layer 2 bridged network.
STEPS 1. Install rackspace03.ovirt.org 2. Create gluster based DC and add gluser storage as data domain. 3. Add rackspace03.ovirt.org into the DC. 4. Create export domain. 5. Attach export domain into rackspace[01/02].ovirt.org. 6. Poweoff all VMs on rackspace[01/02].ovirt.org and export them. 7. Attach export domain to the gluster based dc 8. Import all vms 9. Poweroff vms and check their statuses/connectivity. In jenkins as well.
Shouldn't this be power on?
10. Add rackspace[01/02].ovirt.org to the gluster based dc 11. Do steps 5-10 for rackspace02
Will remove the local DCs a week after migration after we will be sure that everything is ok.
Can we also update to fedora 19? rackspace03 already is f19.
----- Original Message -----
From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt@kohlvanwijngaarden.nl> To: infra@ovirt.org Sent: Wednesday, October 16, 2013 6:15:38 PM Subject: Re: Migration for the rackspace servers
On Mon, Oct 14, 2013 at 09:23:06AM -0400, Kiril Nesenko wrote:
Hello,
Please review the plan I've wrote for the migration.
MUST REQUIREMENTS * Gluster data domain * Export domain * Open a ticket to rackspace regarding static MAC address mapping
This was expanded on in the latest meeting. I think you said every mac address at rackspace can only originate from a certain other mac address. Isn't this network port in the switch because we have a layer 2 bridged network.
I asked rackspace guys and they told that this is not relevant and we can run our VMs on rackspace* servers without any problem.
STEPS 1. Install rackspace03.ovirt.org 2. Create gluster based DC and add gluser storage as data domain. 3. Add rackspace03.ovirt.org into the DC. 4. Create export domain. 5. Attach export domain into rackspace[01/02].ovirt.org. 6. Poweoff all VMs on rackspace[01/02].ovirt.org and export them. 7. Attach export domain to the gluster based dc 8. Import all vms 9. Poweroff vms and check their statuses/connectivity. In jenkins as well.
Shouldn't this be power on?
Yes
10. Add rackspace[01/02].ovirt.org to the gluster based dc 11. Do steps 5-10 for rackspace02
Will remove the local DCs a week after migration after we will be sure that everything is ok.
Can we also update to fedora 19? rackspace03 already is f19.
Right, will do. - Kiril
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 10/14/2013 09:23 AM, Kiril Nesenko wrote:
Hello,
Please review the plan I've wrote for the migration.
MUST REQUIREMENTS * Gluster data domain
there are issues with snapshots/thin provisioning on gluster storage domain currently. so consider posix. also, are the nodes both gluster and virt or separate? if the same, there is an issue with gluster replication and libvirt live migration ports.
* Export domain * Open a ticket to rackspace regarding static MAC address mapping
STEPS 1. Install rackspace03.ovirt.org 2. Create gluster based DC and add gluser storage as data domain. 3. Add rackspace03.ovirt.org into the DC. 4. Create export domain. 5. Attach export domain into rackspace[01/02].ovirt.org. 6. Poweoff all VMs on rackspace[01/02].ovirt.org and export them. 7. Attach export domain to the gluster based dc 8. Import all vms 9. Poweroff vms and check their statuses/connectivity. In jenkins as well. 10. Add rackspace[01/02].ovirt.org to the gluster based dc 11. Do steps 5-10 for rackspace02
Will remove the local DCs a week after migration after we will be sure that everything is ok.
- Kiril _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Kiril Nesenko" <kiril@redhat.com> Cc: "infra" <infra@ovirt.org> Sent: Thursday, October 17, 2013 7:54:32 PM Subject: Re: Migration for the rackspace servers
On 10/14/2013 09:23 AM, Kiril Nesenko wrote:
Hello,
Please review the plan I've wrote for the migration.
MUST REQUIREMENTS * Gluster data domain
there are issues with snapshots/thin provisioning on gluster storage domain currently. so consider posix.
Currently we just want to run jenkins slaves on that setup. So I don't think we will use snapshots.
also, are the nodes both gluster and virt or separate?
Yes, nodes are both gluster and virt.
if the same, there is an issue with gluster replication and libvirt live migration ports.
That's a problem. As a workaround, we can pin to host all vms and disable it when the issue will be fixed. - Kiril
* Export domain * Open a ticket to rackspace regarding static MAC address mapping
STEPS 1. Install rackspace03.ovirt.org 2. Create gluster based DC and add gluser storage as data domain. 3. Add rackspace03.ovirt.org into the DC. 4. Create export domain. 5. Attach export domain into rackspace[01/02].ovirt.org. 6. Poweoff all VMs on rackspace[01/02].ovirt.org and export them. 7. Attach export domain to the gluster based dc 8. Import all vms 9. Poweroff vms and check their statuses/connectivity. In jenkins as well. 10. Add rackspace[01/02].ovirt.org to the gluster based dc 11. Do steps 5-10 for rackspace02
Will remove the local DCs a week after migration after we will be sure that everything is ok.
- Kiril _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
participants (3)
-
Ewoud Kohl van Wijngaarden -
Itamar Heim -
Kiril Nesenko