<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Having a "Maintenance" mode would be
good.<br>
<br>
Being able to mark a node as being under "Maintenance" and having
all VM's migrate off it, and it disappear from the target list in
migrations.<br>
<br>
Also being able to select Multiple guests and migrate them in one
action would also be VERY useful.<br>
<br>
<br>
<br>
<br>
Regards,<br>
<br>
<br>
<br>
<br>
Andrew<br>
<br>
<br>
<br>
<br>
<br>
On 3/13/2013 8:21 AM, James Devine wrote:<br>
</div>
<blockquote
cite="mid:CAPmoJaOe7Ob+_r-GdkKSCHo=7rDXqvv6OzhqqWY=qPckV=RzEw@mail.gmail.com"
type="cite">
<div dir="ltr">Perhaps some type of update mode which would pull a
host server out of the cluster and migrate machines off of it.
<div><br>
<div>Auto-migrate VMs to do resource balancing. I've heard
resistance to this with the argument that the migration
would cause an even higher load but I think it is still a
valid option. If the high load ends up being a long term
situation it may be beneficial to migrate and cause a high
load for a brief period of time. Also if things are kept
balanced early enough the problem may be prevented all
together. There could be tuning options such as when to
balance and delay to prevent short periods of high load from
causing a migration. This would also be useful for
rebalancing the cluster if new hosts are added or if the
above option is implemented and a host is re-added to the
cluster.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Mar 6, 2013 at 3:18 AM, James
A. Coyle <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:james.coyle@jamescoyle.net" target="_blank">james.coyle@jamescoyle.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I would
+1 the backups, it's the one part of Proxmox which drives
me mad! I tend to SSH in and rename them manually for
major backups.<br>
<br>
I'd like to see some small UI changes:<br>
- Add a search box under Storage > Content so that we
can start to type and the content is filtered.<br>
- On Create Backup Job - allow a name or comment to
describe the backup.<br>
- As discussed - backups are tricky to manage on VMID
alone.<br>
<br>
Overall though, it's a great product! I use 2 x 3 node
clusters and use about a 50:50 split between QEMU and
OpenVZ. Thanks for your efforts!<br>
<br>
<br>
James Coyle<br>
<br>
M:<a moz-do-not-send="true"
href="tel:%2B44%20%280%29%207809%20895%20392"
value="+447809895392" target="_blank">+44 (0) 7809 895
392</a><br>
E: <a moz-do-not-send="true"
href="mailto:james.coyle@jamescoyle.net" target="_blank">james.coyle@jamescoyle.net</a><br>
Skype: jac2703<br>
Gtalk: <a moz-do-not-send="true"
href="mailto:jac2703@gmail.com" target="_blank">jac2703@gmail.com</a><br>
www: <a moz-do-not-send="true"
href="http://www.jamescoyle.net" target="_blank">www.jamescoyle.net</a><br>
<div>
<div><br>
----- Original Message -----<br>
From: "FinnTux" <<a moz-do-not-send="true"
href="mailto:finntux@gmail.com" target="_blank">finntux@gmail.com</a>><br>
To: "Alexandre DERUMIER" <<a moz-do-not-send="true"
href="mailto:aderumier@odiso.com" target="_blank">aderumier@odiso.com</a>><br>
Cc: <a moz-do-not-send="true"
href="mailto:pve-devel@pve.proxmox.com"
target="_blank">pve-devel@pve.proxmox.com</a><br>
Sent: Wednesday, 6 March, 2013 7:52:56 AM<br>
Subject: Re: [pve-devel] features ideas for 3.0
roadmap<br>
<br>
> - finish vm/templates copy/clone<br>
> - storage migration<br>
> - storage migration + live migration for local
disks<br>
> - add hyperv cpu features for windows > 2008<br>
> - add spice console support (openstack has added
spice-html5 console, so it should work now)<br>
> - add support for qemu guest agent<br>
> - finish cleanup of hotplug/unplug with
cooperation of guest agent<br>
> - add dynamic nic vlan change<br>
> - add dynamic nic rate limit change<br>
><br>
> What do you think about this ? Other ideas are
welcome :)<br>
<br>
Sounds great.<br>
<br>
- Add vCPU, vRAM and bridges (networks) to pools<br>
- Improve backup handling. Like mentioned before on
the forums backup<br>
name based solely on VMID is confusing. Needs somekind
of notes<br>
included in the backup<br>
_______________________________________________<br>
pve-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:pve-devel@pve.proxmox.com"
target="_blank">pve-devel@pve.proxmox.com</a><br>
<a moz-do-not-send="true"
href="http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel"
target="_blank">http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel</a><br>
_______________________________________________<br>
pve-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:pve-devel@pve.proxmox.com"
target="_blank">pve-devel@pve.proxmox.com</a><br>
<a moz-do-not-send="true"
href="http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel"
target="_blank">http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pve-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pve-devel@pve.proxmox.com">pve-devel@pve.proxmox.com</a>
<a class="moz-txt-link-freetext" href="http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel">http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>