On Wed, May 27, 2009 at 7:57 PM, Uri Lublin <uril@xxxxxxxxxx> wrote: > sudhir kumar wrote: >> >> Michael, >> any updates on this patch? Are you going to commit this or you have >> any other plans/patch ? >> > > I'm not sure having the inter-host migration is best implemented on the > autotest-client side. Actually this is one of the few tests I think belong > to the autotest-server side. This one was a minimal and the first point implementation. I am not much expert in the server side. I will look into the code and design of the server. > > On the other hand it is pretty simple to implement it here. So I think we'd > better try first implementing it as a server test, and apply it to the > client side only as a second choice. > > A few (minor) problems with it running on the client side: > 1. We do not know what the other host is running (what version?, kvm-modules > loaded? etc.) > 2. There may be a conflict between a running local guest running on the > remote (if it allowed to run tests while being a migration destination), and > the remote guest. Yes, especially in case of parallel job execution. This is imp to be handeled. > 3. There may be a conflict between two remote guests running a migration > test on two different hosts. So you mean the server will enquire about this event if implemented using autotest server? > 3. get_free_ports run on the local machine, but expected/assumed to be free > on the remote machine too. > 4. For a migration to be successful, the image(s) must be shared by both > hosts. On the other hand, when installing a guest OS (e.g. Fedora 8) on both > hosts (let's assume they both are running fc8_quick) we want different > images on different hosts. This may be true only when the autoserver is running multiple parallel jobs. Though less likely that one would like to run 2 instances of same installation. However still this is a case. > > These are all can be solved easily by non-trivial pretty simple > configuration on the server. One can configure the "remote" migration to run > as a separate tests to all other tests. > I feel Virtmanager also will be taking care of such scenarios. Any idea how do they handle it or they just leave it to the user? > > Regards, > Uri. > > > Thanks for your comments. -- Sudhir Kumar -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
