From: alexandre derumier <aderumier@odiso.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH v12 pve-manager 0/4] sdn: add subnet/ipam/sdn management
Date: Wed, 28 Apr 2021 04:36:13 +0200 [thread overview]
Message-ID: <5a2fd8f3-0ab8-6a7a-eda6-6a04cbaecd66@odiso.com> (raw)
In-Reply-To: <96e121b1-0731-7ec9-34a0-335336347563@proxmox.com>
>>applied, thanks! The gui looks now quite clean, I like it this way!
Thanks Thomas for the cleanup too !
I'll check the doc too, as I have moved some options.
and I'll try to see if I can add some graphviz schema for complex setup + some examples for setup like heztner.
On 26/04/2021 20:08, Thomas Lamprecht wrote:
> On 21.04.21 23:53, Alexandre Derumier wrote:
>> changelog v11:
>> No code changes since v10, only identation cleanup.
>>
>> rebased on last master and patches merged together
>>
>> changelog v12:
>> add last pve-network changes
>>
>>
>> Small reminder of other related patches:
>>
>> pve-network:
>> [pve-devel] [PATCH v3 pve-network 0/6] evpn && bgp improvements
>> https://lists.proxmox.com/pipermail/pve-devel/2021-April/047800.html
>>
>>
>> pve-cluster:
>>
>> [PATCH V5 pve-cluster 0/5] sdn : add subnets management
>>
>> https://lists.proxmox.com/pipermail/pve-devel/2020-September/045284.html
>>
>>
>> pve-common:
>>
>> INotify: add support for dummy interfaces type
>>
>> (this is a small patch for ebgp loopback/dummy interface support)
>>
>> https://www.mail-archive.com/pve-devel@lists.proxmox.com/msg01755.html
>>
>>
>> pve-container: (maybe we could wait a little bit to finish qemu support too)
>>
>> [PATCH pve-container] add ipam support
>> https://lists.proxmox.com/pipermail/pve-devel/2021-January/046609.html
>>
>>
>> Alexandre Derumier (4):
>> sdn: add subnet/ipam/sdn management
>> sdn: move mac option from vnet to evpn zone plugin
>> sdn: controller: bgp: add ebgp-multihop option
>> sdn: controllers: bgp: use node as controllerid
>>
>
> applied, thanks! The gui looks now quite clean, I like it this way!
>
prev parent reply other threads:[~2021-04-28 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 21:53 [pve-devel] " Alexandre Derumier
2021-04-21 21:53 ` [pve-devel] [PATCH v12 pve-manager 1/4] " Alexandre Derumier
2021-04-21 21:53 ` [pve-devel] [PATCH v12 pve-manager 2/4] sdn: move mac option from vnet to evpn zone plugin Alexandre Derumier
2021-04-21 21:53 ` [pve-devel] [PATCH v12 pve-manager 3/4] sdn: controller: bgp: add ebgp-multihop option Alexandre Derumier
2021-04-21 21:53 ` [pve-devel] [PATCH v12 pve-manager 4/4] sdn: controllers: bgp: use node as controllerid Alexandre Derumier
2021-04-26 18:08 ` [pve-devel] applied: [PATCH v12 pve-manager 0/4] sdn: add subnet/ipam/sdn management Thomas Lamprecht
2021-04-28 2:36 ` alexandre derumier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a2fd8f3-0ab8-6a7a-eda6-6a04cbaecd66@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox