----- Original Message -----
From: "Kiril Nesenko" <kiril@redhat.com> To: "infra" <infra@ovirt.org> Sent: Sunday, June 9, 2013 9:40:02 AM Subject: Proposing a new infra design
Hello,
I would like to propose a new design for our infrastructure. Today we have some bare metal hosts:
USA rackspace01.ovirt.org - f18 clean rackspace02.ovirt.org - f18 clean
France alterway01.ovirt.org - jenkins.ovirt.org alterway02.ovirt.org - all-in-one (that run few our services like puppet,foreman etc.)
I think that it make no sense to install all-in-one setups with local storage domains on our bare metal hosts. It will be better to install NFS or ISCSI DCs per location. For example we can use amazon VMs as engines and bare metal hosts as hypervisors.
This is the design that I propose:
amazon vm1(engine) USA - | |- rackspace01.ovirt.org |- rackspace02.ovirt.org
amazon vm2(engine) France - | |- alterway01.ovirt.org |- alterway02.ovirt.org
- Storage * For this design we need storage services that will be located in the same DCs as our bare metal hosts. * Also we will need a storage for our backups - today we don't have a defined location for our backups. * Storage for resources.ovirt.org - make no sense that VM stores RPMs on it. Much better to use a VM with a small HD and use external storage for storing RPMs.
All services/Vms from alterway02 will be exported to USA DC using NFS export domain. USA DC will be used for production machines. France DC will be used for jenkins slaves.
Guys, this is the first design I am proposing - so fill free to reply ! After we will decide which design we will go with, I will prepare a steps for migrating our services.
Thoughts ?
I like the idea, we need to see how we will get external storages for both sites, what is the alternative if we don't get it (at least for starts)? - using one bare-metal server as NFS server? - if we'll use it for starts, how complex it will be to migrate it to external storage later? also, i think keeping jenkins.ovirt.org as a VM on france will be better than hosting the master on US, since all it's slaves will be on-site and much faster communication. (i.e we'll migrate current jenkins.ovirt.org to a VM on the new system).
- Kiril _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra