On Wed, Oct 7, 2009 at 7:29 AM, Bill Nottingham <notting@xxxxxxxxxx> wrote: > Surely the way to do this is to know what your workload is doing, > and not do live migration to random hardware? I think random hardware is going to be exactly what you will see a lot of scientific research appliances being thrown at. There are groups interested in offering off the shelf appliances for some complex computational codes meant to be run on private/academic/national lab infrastructure to make it easier for scientific users to run the codes correctly. It's pretty pedantic stuff, and you can really screw up the build configuration when you are trying to build your own instances (DYI kernel compiles can be refreshingly less complicated sometimes) Live migrating appliances across those boundaries will undoubtedly be desired. National Lab run "clouds" are going to be well defined hardware targets.... but academic clouds are going to be all over the place. -jef -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
