Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

>>Looks we simply need a flexible plugin architecture ... I think, first, we can try to implement only the virtual network, without focus on external gateway. I'm seeing 2 good candidate: for linux bridge : vxlan ebgp-vpn for ovs : ovn network

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

On 26 January 2018 at 12:12, Alexandre DERUMIER wrote: > I have talked with my network engineer, > > he's only see 2 possibility: > > > 1 use floating-ip/nat 1:1 on compute node and translate to vm private > address > (so external router see mac-adress of compute node for

Re: [pve-devel] [PATCH manager] qemu/Monitor: save the last 20 commands

On 1/26/18 3:25 PM, Dominik Csapak wrote: > and make them available with the up/down arrow key > Looks good. Reviewed-by: Thomas Lamprecht Tested-by: Thomas Lamprecht Up next: tab auto completion? ;) > Signed-off-by: Dominik Csapak

Re: [pve-devel] LizardFS support - wishlist

Hi Gilberto, I took a look at their website, but didn't find any hint about why this LizardFs would be better than currenty supported storages likes Ceph or GlusterFS. Did you find some use cases where this solution will be better than currently supported ones? Cheers El 27/01/18 a las

[pve-devel] [PATCH common] net: remove flowid in traffic limit commands

We don't use them and newer iproute2 doesn't like ':1' as abbreviation for '0:1' apparently. Signed-off-by: Wolfgang Bumiller --- src/PVE/Network.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/Network.pm b/src/PVE/Network.pm index

Re: [pve-devel] [PATCH common] net: remove flowid in traffic limit commands

Forgot to include: Fix #1637 On Mon, Jan 29, 2018 at 10:52:39AM +0100, Wolfgang Bumiller wrote: > We don't use them and newer iproute2 doesn't like ':1' as > abbreviation for '0:1' apparently. > > Signed-off-by: Wolfgang Bumiller > --- > src/PVE/Network.pm | 2 +- > 1

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

Hi, >>I would avoid the floating-ip/nat 1:1 stuff as the plague. >>We also did some research on the same thing your trying to do I think. >>Since your are also working with cumulus (IIRC you referred to it). >>We didn't implement it, but if you are interested, we could sync >>and see if we

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

On 29 January 2018 at 11:46, Alexandre DERUMIER wrote: > > It's not difficult if we can do bgp to the router. but I think Dietmar > want something > for user with a simple router/default gw. (so with some proxy-arp trick). > I would avoid proxy-arp as well. just embrace

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

On 29 January 2018 at 12:22, Dietmar Maurer wrote: > > > Looks we simply need a flexible plugin architecture ... > > You could take a look at how kubernetes does it. If somehow you can keep it compatible you can get lots of stuff for free. :-)

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

https://github.com/containernetworking ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

> It's not difficult if we can do bgp to the router. but I think Dietmar want > something > for user with a simple router/default gw. (so with some proxy-arp trick). No, I still do not know what I want - too many options ;-) Looks we simply need a flexible plugin architecture ...

Re: [pve-devel] [PATCH v2] improve serial terminal handling

On 1/26/18 11:57 AM, Dominik Csapak wrote: > this series adds the ability to show serial ports on the gui, > and disabling the xtermjs button when no serial device exists for the vm > > changes from v1: > * rebase on current master > * changed icon to thomas version, thanks :) > > qemu-server: >

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

maybe have a look at openstack network api too https://developer.openstack.org/api-ref/network/v2/ - Mail original - De: "dietmar" À: "Herman Bos" , "pve-devel" Envoyé: Lundi 29 Janvier 2018 13:35:34 Objet: Re: [pve-devel]

Re: [pve-devel] LizardFS support - wishlist

Hi Well... It's just seems that LizardFS (which is a MooseFS fork, I guess), is easier to implement, very faster than GlusterFS, have metadata all save into RAM, easier to implement compares to Ceph, there's client to Linux, Windows and MacOS... I am research with more benchmarks regard

Re: [pve-devel] LizardFS support - wishlist

> Well... It's just seems that LizardFS (which is a MooseFS fork, I guess), > is easier to implement, If I remember correctly, they run a single Master with no automatic failover? ___ pve-devel mailing list pve-devel@pve.proxmox.com

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

>>No, I still do not know what I want - too many options ;-) yes. >>Looks we simply need a flexible plugin architecture ... I think it's almost always the same on all sdn, you have a network, 1 gateway (or multiple anycast gateway if plugin support it), then you need to manage

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

>>You could take a look at how kubernetes does it. If somehow you can keep it >>compatible you can get lots of stuff for free. :-) >>https://kubernetes.io/docs/concepts/cluster-administration/network-plugins/ Personnaly, I'm currently looking at BaGPipe BGP and CNI for kubernetes

Re: [pve-devel] LizardFS support - wishlist

And just to supplement, I already had implement GlusterFS in WAN over fiber channel and the latency was painful... --- Gilberto Nunes Ferreira (47) 3025-5907 (47) 99676-7530 - Whatsapp / Telegram Skype: gilberto.nunes36 2018-01-29 9:17 GMT-02:00 Gilberto Nunes :

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

> On January 29, 2018 at 1:31 PM Herman Bos wrote: > > > On 29 January 2018 at 12:22, Dietmar Maurer wrote: > > > > > > > Looks we simply need a flexible plugin architecture ... > > > > > You could take a look at how kubernetes does it. If somehow you can

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

> I think, first, we can try to implement only the virtual network, without > focus on external gateway. > > > I'm seeing 2 good candidate: > > for linux bridge : vxlan ebgp-vpn > for ovs : ovn network > (http://openvswitch.org/support/slides/OVN_LinuxCon_Toronto.pdf) > > > Both have

Re: [pve-devel] LizardFS support - wishlist

Yes, you remember correctly. It's a paid option with their commercial version. On 29/01/18 14:29, Dietmar Maurer wrote: Well... It's just seems that LizardFS (which is a MooseFS fork, I guess), is easier to implement, If I remember correctly, they run a single Master with no automatic

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

We use sort of standard flannel with vxlan. just works. but we don't need to integrate with stuff outside k8s. On 29 January 2018 at 14:20, Alexandre DERUMIER wrote: > >>You could take a look at how kubernetes does it. If somehow you can keep > it compatible you can get

[pve-devel] [PATCH common] schema: allow ipv6 prefix lengths up to 128

There's no technical reason for *us* to limit this to 120. Signed-off-by: Wolfgang Bumiller --- src/PVE/JSONSchema.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index c09a9f4..4bc7cbb 100644 ---

[pve-devel] applied: [PATCH manager] qemu/Monitor: save the last 20 commands

applied, despite the lack of tab completion ;-) On Fri, Jan 26, 2018 at 03:25:26PM +0100, Dominik Csapak wrote: > and make them available with the up/down arrow key > > Signed-off-by: Dominik Csapak > --- > www/manager6/qemu/Monitor.js | 45 >

Re: [pve-devel] [PATCH ha-manager 0/8] simulate and cope with unavailable cfs

looks good to me, works fine Reviewed-by: Dominik Csapak Tested-by: Dominik Csapak On 11/22/2017 11:53 AM, Thomas Lamprecht wrote: This series adds functionallity to simulate and nor read/writeable or not updatable cluster file system. First add