On Sat, Jan 15, 2011 at 05:39:54PM +0530, Gautam wrote:
>    Hi Pasi,
>    i am targeting xen hypervisor.
>
Ok.
>    i have already written one script which manage the work load.
>    my script uses xentop command.
>
Feel free to post your script to xen-devel for comments.
>    but i wanted to add this features in xen code rather than running an
>    outside script.
>
New features should be developed against xen-unstable, ie. Xen 4.1 at this point.
Xen 4.1 uses the xl/libxl toolstack as the primary toolstack, so you should
make sure your script works with xl/libxl.
Other than that.. post your script as RFC (Request For Comments),
and we'll see how it looks like.
-- Pasi
>    On Sat, Jan 15, 2011 at 5:24 PM, Pasi Kärkkäinen <[1]
pasik@xxxxxx> wrote:
>
>      On Sat, Jan 15, 2011 at 04:59:28PM +0530, Gautam wrote:
>      >    Automatic live migration means XEN should monitor the workload of
>      the
>      >    machine and user will define the threshold of
>      >    any parameter say(CPU usage) then if workload cross the threshold
>       value
>      >    then XEN should migrate a virtual machine
>      >    to the other machine automatically without any user interruption.
>      >
>      >    let me know if you need any further info.
>      >
>
>      This kind of functionality does not belong to Xen *hypervisor*,
>      it should be done from the management toolstack.
>
 >      If we're talking about traditional [2]xen.org hypervisor then the first
>      implementation
>      could be a script that monitors the resource usage on all physical
>      hosts,
>      and executes live migration commands based on the resource usage to
>      balance the workloads.
>
>      I'm not sure if there's something like this already available for Xen ..
>      Remember Xen 4.0 and older versions use the xm/xend toolstack,
>      and the upcoming Xen 4.1 will use the xl/libxl toolstack as the primary
>      toolstack.
>
>      Both xm/xend and xl/libxl toolstack are more focused on single host
>      management,
>      while the XAPI toolstack in XenServer and XCP (Xen Cloud Platform) has
>      multi-host pools.
>
>      Which one are you targeting? [3]xen.org hypervisor or XAPI/XCP ?
>
>      XAPI toolstack in XenServer/XCP has the concept of "Workload Balancing"
>      (WLB),
>      which is meant for exactly what you described.
>
>      Citrix XenServer includes WLB service, but XCP doesn't, afaik.
>
>      See:
>      - "XenServer Workload Balancing Administration Tool":
>      [4]http://support.citrix.com/article/CTX125365
>      - "Configuring XenServer Workload Balancing Settings Using XE Commands":
>      [5]http://support.citrix.com/article/CTX125186
>
>      There are some thirdparty WLB services available for XCP,
>      see for example [6]http://www.xencloudcontrol.com/ and
>      [7]http://www.xencloudcontrol.com/DOCS/load-balancer.txt
>
>      Are you thinking of writing your own WLB service?
>      Hopefully that helps.
>
>      -- Pasi
>
>      >    On Sat, Jan 15, 2011 at 4:54 PM, Pasi Kärkkäinen
>      <[1][8]
pasik@xxxxxx> wrote:
>      >
>      >      On Sat, Jan 15, 2011 at 02:02:40PM +0530, Gautam wrote:
>      >      >    i am trying to add auto migration feature in XEN.
>      >      >    so is anyone has worked related to migration part.
>      >      >    i need help regarding files related to migration.
>      >      >
>      >
>      >      Hello,
>      >
>      >      First of all, what do you exactly mean with "automatic live
>      migration" ?
>      >      -- Pasi
>      >
>      >    --
>      >    Regards
>      >    Gautam
>      >
>      >
>      >
>      > References
>      >
>      >    Visible links
 >      >    1. mailto:[9]pasik@xxxxxx
>
>    --
>    Regards
>    Gautam
>
>
>
> References
>
>    Visible links
>    1. mailto:
pasik@xxxxxx
 >    2. http://xen.org/
>    3. http://xen.org/
>    4. http://support.citrix.com/article/CTX125365
>    5. http://support.citrix.com/article/CTX125186
>    6. http://www.xencloudcontrol.com/
>    7. http://www.xencloudcontrol.com/DOCS/load-balancer.txt
>    8. mailto:pasik@xxxxxx
>    9. mailto:pasik@xxxxxx