to implement all features to
dataplane.
(and make it the default in the future)
- Mail original -
De: Alexandre DERUMIER aderum...@odiso.com
À: Dietmar Maurer diet...@proxmox.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Mardi 30 Septembre 2014 11:20:04
Objet: Re: [pve-devel] roadmap
On Tue, 30 Sep 2014 08:22:04 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
Now that proxmox 3.3 , maybe could it be a good time to send features ideas
for proxmox 3.4 ?
Will there be a prioritiesed list published somewhere?
--
Hilsen/Regards
Michael Rasmussen
Get my public
about dataplane, blockjobs are coming for qemu 2.2. (first patches already
sent
to the mailing some days ago)
I have talked with paolo, and the roadmap seem to implement all features to
dataplane.
(and make it the default in the future)
Great! Thanks for the update.
I would like to see migration between non-shared storage. I can even
prepare patches if anyone will help me with where to start.
On Fri, Oct 3, 2014 at 6:50 PM, Dietmar Maurer diet...@proxmox.com wrote:
about dataplane, blockjobs are coming for qemu 2.2. (first patches already
sent
to the
It's possible, because I were doing it already, but only from command
line. Qemu basically transfers all disks and memory state over
network.
On Fri, Oct 3, 2014 at 8:47 PM, Gilberto Nunes
gilberto.nune...@gmail.com wrote:
I think that is not possible... Or may I wrong?
2014-10-03 15:12
In a pinch, even rsync would work, though it would take a while.
The trouble is with HA migrations. There's a decent chance your VM is down
because your node is, and you can't migrate from a storage which is offline.
Still, HA is handled separately, so it shouldn't cause too many issues to
Hi,
Now that proxmox 3.3 , maybe could it be a good time to send features ideas for
proxmox 3.4 ?
What I have in mind (no priority order) :
- ipv6 support (firewall and also pveproxy (maybe other daemons too))
- config pending changes. (and improve hotplug)
- memory hotplug support (I have
at a specific date (online hotplug,or offline with vm stop/start).
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com, pve-devel@pve.proxmox.com
Envoyé: Mardi 30 Septembre 2014 09:55:26
Objet: RE: [pve-devel] roadmap for proxmox 3.4 ?
What I have
Continue with DHCP integration.
+1 !
- Mail original -
De: Michael Rasmussen m...@datanom.net
À: Dietmar Maurer diet...@proxmox.com, Alexandre DERUMIER
aderum...@odiso.com, pve-devel@pve.proxmox.com
Envoyé: Mardi 30 Septembre 2014 10:36:11
Objet: Re: [pve-devel] roadmap for proxmox
For their activity, they now that at a specific date, they need a lot more
cpu/ram
for a specific vm, so they would like to be able to plan auto upgrade
memory,cpu at a specific date.
(for example, at the begin of the month, they need to compute billing which
take a lot of cpu for 2 days)
Objet: RE: [pve-devel] roadmap for proxmox 3.4 ?
For their activity, they now that at a specific date, they need a lot more
cpu/ram
for a specific vm, so they would like to be able to plan auto upgrade
memory,cpu at a specific date.
(for example, at the begin of the month, they need
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Mardi 30 Septembre 2014 11:32:39
Objet: RE: [pve-devel] roadmap for proxmox 3.4 ?
For their activity, they now that at a specific date, they need a lot
more cpu/ram
for a specific vm, so they would like
12 matches
Mail list logo
