Re: [pve-devel] Roadmap - improved SDN support
Hi, thanks for sharing the links... -- Thomas Naumann Abteilung Netze und Kommunikation Otto-von-Guericke Universität Magdeburg Universitätsrechenzentrum Universitätsplatz 2 39106 Magdeburg fon: +49 391 67-58563 email: thomas.naum...@ovgu.de On Thu, 2019-07-11 at 10:25 +0200, Thomas Lamprecht wrote: > Hi, > > On 7/11/19 6:11 AM, Naumann, Thomas wrote: > > Hi, > > > > at datacenter of university we are working on a saas-platform to > > automaticly deploy VMs, container, networks, services via web-gui > > for > > students and employies. So, we are searching for a technicly basis > > for > > this project. > > Because "Proxmox" runs several Clusters in our datacenter and does > > a > > great jobs we wonder if it could be a basis for this project. We > > known > > there is also "Openstack" but I think it might be some kind of > > overkill. > > What do you think about that? > > > > proxmox.com has some testimonials from universities using Proxmox VE > in a lab course or similar, see (especially the first two, I'd > guess): > > https://www.proxmox.com/en/proxmox-ve/testimonials/category/edu-gov > > Also, as Proxmox VE has a REST api which allows nowadays build a > cluster, > create & manage VMs and CTs, you should not have big problems in > integrating > and adapting it into your own platform. > > https://pve.proxmox.com/pve-docs/api-viewer/index.html > > cheers, > Thomas > ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Roadmap - improved SDN support
Hi, On 7/11/19 6:11 AM, Naumann, Thomas wrote: > Hi, > > at datacenter of university we are working on a saas-platform to > automaticly deploy VMs, container, networks, services via web-gui for > students and employies. So, we are searching for a technicly basis for > this project. > Because "Proxmox" runs several Clusters in our datacenter and does a > great jobs we wonder if it could be a basis for this project. We known > there is also "Openstack" but I think it might be some kind of > overkill. > What do you think about that? > proxmox.com has some testimonials from universities using Proxmox VE in a lab course or similar, see (especially the first two, I'd guess): https://www.proxmox.com/en/proxmox-ve/testimonials/category/edu-gov Also, as Proxmox VE has a REST api which allows nowadays build a cluster, create & manage VMs and CTs, you should not have big problems in integrating and adapting it into your own platform. https://pve.proxmox.com/pve-docs/api-viewer/index.html cheers, Thomas ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Roadmap - improved SDN support
Hi, at datacenter of university we are working on a saas-platform to automaticly deploy VMs, container, networks, services via web-gui for students and employies. So, we are searching for a technicly basis for this project. Because "Proxmox" runs several Clusters in our datacenter and does a great jobs we wonder if it could be a basis for this project. We known there is also "Openstack" but I think it might be some kind of overkill. What do you think about that? -- Thomas Naumann Abteilung Netze und Kommunikation Otto-von-Guericke Universität Magdeburg Universitätsrechenzentrum Universitätsplatz 2 39106 Magdeburg fon: +49 391 67-58563 email: thomas.naum...@ovgu.de On Wed, 2019-05-22 at 18:25 +0200, Alexandre DERUMIER wrote: > Hi, > > I'm working on it. > > The main idea is to be able to define bridge/network at datacenter > level, > then deploy them to hosts and manage dynamic network reloading. > > Theses bridge network will support vlan but also vxlan. > (I'll try to finish this for proxmox6) > > Then I'm working to implement vxlan with bgp evpn too (with anycast > routing, full layer3 distributed vm network), to have a full sdn, > with routing through frr. > > When it'll be done, I think it'll be possible to add more services on > top on > theses networks (dhcp server, nat,). > > > Do you have a special need with sdn? > > > - Mail original - > De: "Naumann, Thomas" > À: "pve-devel" > Envoyé: Mardi 21 Mai 2019 08:46:51 > Objet: [pve-devel] Roadmap - improved SDN support > > Hi, > > there is an extra point "improved SDN support" under roadmap in > official proxmox-wiki. Who can give a hint what this means in > detail? ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Roadmap - improved SDN support
Hi, I'm working on it. The main idea is to be able to define bridge/network at datacenter level, then deploy them to hosts and manage dynamic network reloading. Theses bridge network will support vlan but also vxlan. (I'll try to finish this for proxmox6) Then I'm working to implement vxlan with bgp evpn too (with anycast routing, full layer3 distributed vm network), to have a full sdn, with routing through frr. When it'll be done, I think it'll be possible to add more services on top on theses networks (dhcp server, nat,). Do you have a special need with sdn? - Mail original - De: "Naumann, Thomas" À: "pve-devel" Envoyé: Mardi 21 Mai 2019 08:46:51 Objet: [pve-devel] Roadmap - improved SDN support Hi, there is an extra point "improved SDN support" under roadmap in official proxmox-wiki. Who can give a hint what this means in detail? -- Thomas Naumann Abteilung Netze und Kommunikation Otto-von-Guericke Universität Magdeburg Universitätsrechenzentrum Universitätsplatz 2 39106 Magdeburg fon: +49 391 67-58563 email: thomas.naum...@ovgu.de ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] Roadmap - improved SDN support
Hi, there is an extra point "improved SDN support" under roadmap in official proxmox-wiki. Who can give a hint what this means in detail? -- Thomas Naumann Abteilung Netze und Kommunikation Otto-von-Guericke Universität Magdeburg Universitätsrechenzentrum Universitätsplatz 2 39106 Magdeburg fon: +49 391 67-58563 email: thomas.naum...@ovgu.de ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 6 ?
>>besides a cleaner interface, do you know some other improvements blockdev >>provides? I known it's improve mirroring, when we can pass argument to target storage. mirroring preserving sparseness (mainly for nbd) https://bugzilla.redhat.com/show_bug.cgi?id=1232914 luks support (If we wanted to add luks encryption at rest in qemu-server) https://bugzilla.redhat.com/show_bug.cgi?id=1371022 should improve disk unplug too. Maybe it'll help too later with multithread iothreads blockdev. And it'll be needed by COLO (if one day it'll be ready ;) I had done some code 1 or 2 years ago, but throttling was missing at this time.(it's ok now) I don't known when qemu will deprecated to old interface. (but I think we have time) It's not difficult to implement, but this almost need to change all drive qmp command related, some command line options are on devices and not drive anymore, ... So this need a lot of tests. - Mail original - De: "Thomas Lamprecht" À: "pve-devel" , "Alexandre Derumier" Envoyé: Mardi 5 Février 2019 17:38:16 Objet: Re: [pve-devel] roadmap for proxmox 6 ? Hi! Am 2/5/19 um 2:47 PM schrieb Alexandre DERUMIER:> Hi, > > as debian buster is coming, do you have already a roadmap for proxmox6 ? > nothing fully fleshed out/set in stone so below is nothing fixed :) > > Here some features I have in mind: > > - corosync 3 yes, as talked off-list this will probably come, but needs a bit of adaption... But as I do not want to maintain the current 2.x needle branch for PVE 6 for until ~2022 I'd rather do some work now. > - qemu 3.x We wait on a bugfix release (or do one with the stable patches ourself), but yes in general we'd like to ship a newer one backporting (security) fixes normally does not gets easier the longer the interval between upstream current and used version, and some new features are great too.. > - ifupdown2 by default ? (need to test openvswitch) I think this is a bit longer on the roadmap, but one needs to do the work :D > - I'll try to work on vxlan (+frr) /vlan, /etc/pve/networks.cfg. I'll try to > send prelimaries patches this month. great! > - qemu-server : implement blockdev (I think it's now 100% feature complete, > but they are a lot of thing to change/adapt/ > (param,hotplug,mirror,throttling,snapshot,..). > not sure if proxmox backup will work without change. besides a cleaner interface, do you know some other improvements blockdev provides? cheers, Thomas ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 6 ?
Hi! Am 2/5/19 um 2:47 PM schrieb Alexandre DERUMIER:> Hi, > > as debian buster is coming, do you have already a roadmap for proxmox6 ? > nothing fully fleshed out/set in stone so below is nothing fixed :) > > Here some features I have in mind: > > - corosync 3 yes, as talked off-list this will probably come, but needs a bit of adaption... But as I do not want to maintain the current 2.x needle branch for PVE 6 for until ~2022 I'd rather do some work now. > - qemu 3.x We wait on a bugfix release (or do one with the stable patches ourself), but yes in general we'd like to ship a newer one backporting (security) fixes normally does not gets easier the longer the interval between upstream current and used version, and some new features are great too.. > - ifupdown2 by default ? (need to test openvswitch) I think this is a bit longer on the roadmap, but one needs to do the work :D > - I'll try to work on vxlan (+frr) /vlan, /etc/pve/networks.cfg. I'll try to > send prelimaries patches this month. great! > - qemu-server : implement blockdev (I think it's now 100% feature complete, > but they are a lot of thing to change/adapt/ > (param,hotplug,mirror,throttling,snapshot,..). > not sure if proxmox backup will work without change. besides a cleaner interface, do you know some other improvements blockdev provides? cheers, Thomas ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] roadmap for proxmox 6 ?
Hi, as debian buster is coming, do you have already a roadmap for proxmox6 ? Here some features I have in mind: - corosync 3 - qemu 3.x - ifupdown2 by default ? (need to test openvswitch) - I'll try to work on vxlan (+frr) /vlan, /etc/pve/networks.cfg. I'll try to send prelimaries patches this month. - qemu-server : implement blockdev (I think it's now 100% feature complete, but they are a lot of thing to change/adapt/ (param,hotplug,mirror,throttling,snapshot,..). not sure if proxmox backup will work without change. Regards, Alexandre ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] Roadmap
Hi all, I would also suggest adding ploop support to openvz as part of the roadmap since ploop will give real live migration to CT's, improve backup performance, add snapshot feature, and add support for thin provisioned CT's. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: Of course power tools and alcohol don't mix. Everyone knows power tools aren't soluble in alcohol... -- Crazy Nigel pgpTUFSe8bpJC.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Roadmap
I would also suggest adding ploop support to openvz as part of the roadmap since ploop will give real live migration to CT's, improve backup performance, add snapshot feature, and add support for thin provisioned CT's. I will not add that until it is 100% sure that OpenVZ team will support that for newer 3.X kernels. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Roadmap
I will not add that until it is 100% sure that OpenVZ team will support that for newer 3.X kernels. Where do you get this information? I have not seeing anything on openvz.org indicating ploop should not be supported on 3.1x kernels. There is no information so far (that is why I do not touch ploop). ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
- basic virtio dataplane support (seem that only block jobs are missing now, hotplug,resize,throttling,migration are working fine) 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) - 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 for proxmox 3.4 ? - basic virtio dataplane support (seem that only block jobs are missing now, hotplug,resize,throttling,migration are working fine) is that already stable? And is it really faster? yes, the command line is stable now. (no more x-dataplane, it's use -object iothread,id=iothread0 -device virtio-blk-pci,iothread=iothread0,...). I'm going to do some tests next month. Performance are faster, but you need a really fast storage. ( 100.000 iops ;). Maybe it's use less cpu too. So usage is really specific. (for big database for example) - some kind of task scheduler, to automate config changes at specific time (like cpu hotplug,memory hotplug) Mind to elaborate on that a bit more? 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) This could be done with cronjobs and qm set ..., but they would like something more integrated. (so, I thinked about something more generic, like a target config which could be applied 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 in mind (no priority order) : - ipv6 support (firewall and also pveproxy (maybe other daemons too)) +1 - config pending changes. (and improve hotplug) +1 - memory hotplug support (I have already working patches, I'll send them soon) great - basic virtio dataplane support (seem that only block jobs are missing now, hotplug,resize,throttling,migration are working fine) is that already stable? And is it really faster? During my training last week, I have add some features request from Sisteer company - vm auto balancing scheduler (I also need this feature) - allow network change through gui without reboot (I think it could be easy for bridge without any tap plugged) IMHO this one is really hard to do it right... - some kind of task scheduler, to automate config changes at specific time (like cpu hotplug,memory hotplug) Mind to elaborate on that a bit more? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
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 GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- /usr/games/fortune -es says: There's no use in having a dog and doing your own barking. pgpr1y6QvuO6Y.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
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. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
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 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. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel -- Kamil Trzciński ayu...@ayufan.eu www.ayufan.eu ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
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 GMT-03:00 Kamil Trzciński ayu...@ayufan.eu: 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 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. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel -- Kamil Trzciński ayu...@ayufan.eu www.ayufan.eu ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel -- -- Gilberto Ferreira -- Kamil Trzciński ayu...@ayufan.eu www.ayufan.eu ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
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 support manual migrations to/from local storages. On Oct 3, 2014 2:54 PM, Gilberto Nunes gilberto.nune...@gmail.com wrote: Nice... Over DRBD, I suppose... That is clearly possible... Even over glusterfs ou DRBD+OCFS 2014-10-03 17:47 GMT-03:00 Kamil Trzciński ayu...@ayufan.eu: 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 GMT-03:00 Kamil Trzciński ayu...@ayufan.eu: 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 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. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel -- Kamil Trzciński ayu...@ayufan.eu www.ayufan.eu ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel -- -- Gilberto Ferreira -- Kamil Trzciński ayu...@ayufan.eu www.ayufan.eu -- -- Gilberto Ferreira ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] roadmap for proxmox 3.4 ?
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 already working patches, I'll send them soon) - basic virtio dataplane support (seem that only block jobs are missing now, hotplug,resize,throttling,migration are working fine) During my training last week, I have add some features request from Sisteer company - vm auto balancing scheduler (I also need this feature) - allow network change through gui without reboot (I think it could be easy for bridge without any tap plugged) - some kind of task scheduler, to automate config changes at specific time (like cpu hotplug,memory hotplug) ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
- basic virtio dataplane support (seem that only block jobs are missing now, hotplug,resize,throttling,migration are working fine) is that already stable? And is it really faster? yes, the command line is stable now. (no more x-dataplane, it's use -object iothread,id=iothread0 -device virtio-blk-pci,iothread=iothread0,...). I'm going to do some tests next month. Performance are faster, but you need a really fast storage. ( 100.000 iops ;). Maybe it's use less cpu too. So usage is really specific. (for big database for example) - some kind of task scheduler, to automate config changes at specific time (like cpu hotplug,memory hotplug) Mind to elaborate on that a bit more? 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) This could be done with cronjobs and qm set ..., but they would like something more integrated. (so, I thinked about something more generic, like a target config which could be applied 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 in mind (no priority order) : - ipv6 support (firewall and also pveproxy (maybe other daemons too)) +1 - config pending changes. (and improve hotplug) +1 - memory hotplug support (I have already working patches, I'll send them soon) great - basic virtio dataplane support (seem that only block jobs are missing now, hotplug,resize,throttling,migration are working fine) is that already stable? And is it really faster? During my training last week, I have add some features request from Sisteer company - vm auto balancing scheduler (I also need this feature) - allow network change through gui without reboot (I think it could be easy for bridge without any tap plugged) IMHO this one is really hard to do it right... - some kind of task scheduler, to automate config changes at specific time (like cpu hotplug,memory hotplug) Mind to elaborate on that a bit more? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
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 3.4 ? Continue with DHCP integration. On September 30, 2014 9:55:26 AM CEST, Dietmar Maurer diet...@proxmox.com wrote: blockquote What I have in mind (no priority order) : - ipv6 support (firewall and also pveproxy (maybe other daemons too)) +1 blockquote - config pending changes. (and improve hotplug) /blockquote +1 blockquote - memory hotplug support (I have already working patches, I'll send them soon) /blockquote great blockquote - basic virtio dataplane support (seem that only block jobs are missing now, hotplug,resize,throttling,migration are working fine) /blockquote is that already stable? And is it really faster? blockquote During my training last week, I have add some features request from Sisteer company - vm auto balancing scheduler (I also need this feature) - allow network change through gui without reboot (I think it could be easy for bridge without any tap plugged) /blockquote IMHO this one is really hard to do it right... blockquote - some kind of task scheduler, to automate config changes at specific time (like cpu hotplug,memory hotplug) /blockquote Mind to elaborate on that a bit more? pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel /blockquote -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. This mail was virus scanned and spam checked before delivery. This mail is also DKIM signed. See header dkim-signature. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
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 to compute billing which take a lot of cpu for 2 days) This could be done with cronjobs and qm set ..., but they would like something more integrated. (so, I thinked about something more generic, like a target config which could be applied at a specific date (online hotplug,or offline with vm stop/start). I think using a script/API is a perfect fit for such things. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
I think using a script/API is a perfect fit for such things. Yes, I think it could be done with api indeed. - Mail original - De: Dietmar Maurer diet...@proxmox.com À: 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 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) This could be done with cronjobs and qm set ..., but they would like something more integrated. (so, I thinked about something more generic, like a target config which could be applied at a specific date (online hotplug,or offline with vm stop/start). I think using a script/API is a perfect fit for such things. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.4 ?
Hi... I am not a programmers... Perhaps someone more like a betatester I subscribe this like. just to stay tunned about last Proxmox news... But, I have some suggestions too: 1 - Build cluster over GUI 2 - Improve VDI, perhaps... I would like to see something like Xen Desktop, the hability to create shortchuts on desktop, linked to remote apps 3 - Improve User Manager... I would like to see more granular permissions... 4 - Qemu MicroCheckPoint (http://wiki.qemu.org/Features/MicroCheckpointing) Sorry if I am out of place here... And forgive me if some this suggestions make nosense or if some one of thens is already on plan... Cheers... 2014-09-30 6:46 GMT-03:00 Alexandre DERUMIER aderum...@odiso.com: I think using a script/API is a perfect fit for such things. Yes, I think it could be done with api indeed. - Mail original - De: Dietmar Maurer diet...@proxmox.com À: 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 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) This could be done with cronjobs and qm set ..., but they would like something more integrated. (so, I thinked about something more generic, like a target config which could be applied at a specific date (online hotplug,or offline with vm stop/start). I think using a script/API is a perfect fit for such things. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel Gilberto Ferreira ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
Ok, I just started the upgrade, and pushed a few patches so that we can compile pve-qemu-kvm with qemu-1.7rc2 I disabled the backup and snapshot patches for now. Next I will update the backup patches for qemu 1.7 Would be great if someone can update the following patches for 1.7 ;-) move-bdrv-snapshot-find.patch internal-snapshot-async.patch I plan to start working on that now - do you already have some patches? No, sorry, I was too busy, tryng to finish zfs nexenta patch and also local storage migration. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
move-bdrv-snapshot-find.patch internal-snapshot-async.patch I'll try to have a look at it. do we want to use new transaction feature ? http://wiki.qemu.org/Features/SnapshotsMultipleDevices - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel pve-devel@pve.proxmox.com Envoyé: Mercredi 27 Novembre 2013 12:41:05 Objet: RE: [pve-devel] roadmap for qemu upgrade ? Ok, I just started the upgrade, and pushed a few patches so that we can compile pve-qemu-kvm with qemu-1.7rc2 I disabled the backup and snapshot patches for now. Next I will update the backup patches for qemu 1.7 Would be great if someone can update the following patches for 1.7 ;-) move-bdrv-snapshot-find.patch internal-snapshot-async.patch I plan to start working on that now - do you already have some patches? No, sorry, I was too busy, tryng to finish zfs nexenta patch and also local storage migration. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
move-bdrv-snapshot-find.patch internal-snapshot-async.patch I'll try to have a look at it. do we want to use new transaction feature ? http://wiki.qemu.org/Features/SnapshotsMultipleDevices Yes (if possible). ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
Yes (if possible). Ok, I'll try to port save-async.c in a first time , then I'll look for new snasphot code. (move-bdrv-snapshot-find.patch can be dropped, as bdrv_snapshot_find have move to block/snapshot.c) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel pve-devel@pve.proxmox.com Envoyé: Mercredi 27 Novembre 2013 15:19:12 Objet: RE: [pve-devel] roadmap for qemu upgrade ? move-bdrv-snapshot-find.patch internal-snapshot-async.patch I'll try to have a look at it. do we want to use new transaction feature ? http://wiki.qemu.org/Features/SnapshotsMultipleDevices Yes (if possible). ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
I plan to start working on that now - do you already have some patches? No, sorry, I was too busy, tryng to finish zfs nexenta patch and also local storage migration. (I also try to test your ceph pve-manager patch this week) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel pve-devel@pve.proxmox.com Envoyé: Mardi 26 Novembre 2013 08:23:31 Objet: RE: [pve-devel] roadmap for qemu upgrade ? Ok,I'll try to look at it next week. (we can remove my qemu-img-convert-skipcreate-option.patch, now in qemu git :) http://git.qemu.org/?p=qemu.git;a=commit;h=b2e10493c71160d88bb823cae9a 92e806a79b9d6 ) I'll begin to work on simple patches I plan to start working on that now - do you already have some patches? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
Ok,I'll try to look at it next week. (we can remove my qemu-img-convert-skipcreate-option.patch, now in qemu git :) http://git.qemu.org/?p=qemu.git;a=commit;h=b2e10493c71160d88bb823cae9a 92e806a79b9d6 ) I'll begin to work on simple patches I plan to start working on that now - do you already have some patches? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
We need to update/test all patches for 1.7. So any help in that direction is highly appreciated. Ok,I'll try to look at it next week. (we can remove my qemu-img-convert-skipcreate-option.patch, now in qemu git :) http://git.qemu.org/?p=qemu.git;a=commit;h=b2e10493c71160d88bb823cae9a92e806a79b9d6 ) I'll begin to work on simple patches fr-ca-keymap-corrections.diff adjust-path.diff fairsched.diff keymap.diff pve-auth.patch vencrypt-auth-plain.patch virtio-balloon-fix-query.patch set-cpu-model-to-kvm64.patch modify-query-machines.patch modify-query-spice.patch spice-use-pve-certs.patch enable-kvm-by-default.patch maybe snapshot patches too fix-qemu-img-snapshot-removal.patch move-bdrv-snapshot-find.patch internal-snapshot-async.patch (I see that we can use transactions now for snapshot,I'll try to look a it) For backup patches, I think you the best to do it ;) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com Envoyé: Lundi 18 Novembre 2013 06:40:00 Objet: RE: [pve-devel] roadmap for qemu upgrade ? qemu 1.7 should come soon, any plan to upgrade current qemu 1.4 to 1.7 ? I just do not have enough time. But yes, it is on the TODO list. (I known they are a lot of work for backup, maybe snapshots too) Maybe can we help ? We need to update/test all patches for 1.7. So any help in that direction is highly appreciated. - Dietmar ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] roadmap for qemu upgrade ?
Hi, qemu 1.7 should come soon, any plan to upgrade current qemu 1.4 to 1.7 ? (I known they are a lot of work for backup, maybe snapshots too) Maybe can we help ? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for qemu upgrade ?
qemu 1.7 should come soon, any plan to upgrade current qemu 1.4 to 1.7 ? I just do not have enough time. But yes, it is on the TODO list. (I known they are a lot of work for backup, maybe snapshots too) Maybe can we help ? We need to update/test all patches for 1.7. So any help in that direction is highly appreciated. - Dietmar ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.1 ?
- live storage migration. (should be easy, we have already the drive-mirror code) - spice ??? These and pool concept improvement: - add RAM, vCPUs and bridges to pool (ability to allocate only part of certain storage would be nice) ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.1 ?
On 05-27-2013 08:38, Alexandre DERUMIER wrote: Omnios: http://omnios.omniti.com/ but OpenIndiana and Oracle Solaris (and express + pkg install solaris/storage-server) should work also. Do you known if I can install omnios on a kvm machine ? (My servers are on a remote site and I don't have too much time this week to go to the datacenter ;) Yes, this is possible but you can only choose between IDE and SATA disks (omnios does not support virtio-block, and seabios does not support boot from scsi). Also if you want to be able to migrate the VM you cannot use SATA disk since Qemu does not support migrating SATA disks (a hardcoded error message is displayed). So this kind of narrows the choices down:-) Choose Qemu64 as CPU. KVM64 cannot be used since Omnios (and Solaris for that matter refused to boot with kvm64). For net device choose E1000 since omnios does not support virtio-net. I have only been testing with bloody (unstable) so I don't know if it works with stable. -- Hilsen/regards Michael Rasmussenattachment: vcard.vcf___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] roadmap for proxmox 3.1 ?
Hi, now that proxmox 3.0 has been released (Congrats Dietmar Martin) :), maybe can we post some ideas for new features for proxmox 3.1 ? I don't known the target date for next release ? (3month ? 6 month ?) Somes ideas here : (by priority for my own usage) - live storage migration. (should be easy, we have already the drive-mirror code) - cpu-add qmp command - add hyper-v option (cpu flags) for windows vm. (this need next openvz-kernel, currently in testing) - dhcp server implementation + nat + routing - qemu-ga - spice ??? - glusterfs storage driver ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.1 ?
maybe can we post some ideas for new features for proxmox 3.1 ? Yes. Maybe we can use pve-manager/README to track all those ideas? That way we have the list in git. What do you think? I don't known the target date for next release ? (3month ? 6 month ?) I guess something in between ;-) Depends on features, and that is not decided so far. Somes ideas here : (by priority for my own usage) - live storage migration. (should be easy, we have already the drive-mirror code) - cpu-add qmp command - add hyper-v option (cpu flags) for windows vm. (this need next openvz- kernel, currently in testing) - dhcp server implementation + nat + routing - qemu-ga - spice ??? - glusterfs storage driver ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.1 ?
Yes. Maybe we can use pve-manager/README to track all those ideas? That way we have the list in git. What do you think? Yes sure, good idea, I'll send a patch :) (I also forgot update to extjs 4.2, but I can't help for this, sorry) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com, pve-devel@pve.proxmox.com Envoyé: Vendredi 24 Mai 2013 15:04:03 Objet: RE: [pve-devel] roadmap for proxmox 3.1 ? maybe can we post some ideas for new features for proxmox 3.1 ? Yes. Maybe we can use pve-manager/README to track all those ideas? That way we have the list in git. What do you think? I don't known the target date for next release ? (3month ? 6 month ?) I guess something in between ;-) Depends on features, and that is not decided so far. Somes ideas here : (by priority for my own usage) - live storage migration. (should be easy, we have already the drive-mirror code) - cpu-add qmp command - add hyper-v option (cpu flags) for windows vm. (this need next openvz- kernel, currently in testing) - dhcp server implementation + nat + routing - qemu-ga - spice ??? - glusterfs storage driver ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.1 ?
On 05-24-2013 14:41, Alexandre DERUMIER wrote: - live storage migration. (should be easy, we have already the drive-mirror code) - cpu-add qmp command - add hyper-v option (cpu flags) for windows vm. (this need next openvz-kernel, currently in testing) - dhcp server implementation + nat + routing - qemu-ga - spice ??? - glusterfs storage driver Add this to list just after live storage migration: - Activate currently deactivated storage plugins in gui which is considered stable - Add my zfs plugin ;-) Regarding my zfs plugin. It is completed and seems to function well. I will post a patch to this list later this evening. I would be nice if someone would take some time testing it. -- Hilsen/regards Michael Rasmussenattachment: vcard.vcf___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] roadmap for proxmox 3.1 ?
On Fri, 24 May 2013 15:30:09 +0200 (CEST) Alexandre DERUMIER aderum...@odiso.com wrote: I would be nice if someone would take some time testing it. I'll try to build an test server next week to test. which solaris distrib do you use? Omnios: http://omnios.omniti.com/ but OpenIndiana and Oracle Solaris (and express + pkg install solaris/storage-server) should work also. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael at rasmussen dot cc http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD3C9A00E mir at datanom dot net http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE501F51C mir at miras dot org http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xE3E80917 -- You are here: *** *** * *** * *** * But you're not all there. signature.asc Description: PGP signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
