From: aderumier@odiso.com
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-devel <pve-devel@pve.proxmox.com>
Subject: [pve-devel] sdn: looking to unify .cfg files, need opinions about config format
Date: Tue, 12 Jan 2021 10:19:31 +0100 [thread overview]
Message-ID: <ee2f7206124fc8adb6d6e9b6691b8388f8622aeb.camel@odiso.com> (raw)
Hi,
I'm looking to unify sdn .cfg files with only 1 file,
with something different than section config format.
We have relationship like zones->vnets->subnets,
so I was thinking about something like this:
[zone myzone]
type: vxlan
option1: xxx
option2: xxx
[[vnet myvnet]]
option1: xxx
option2: xxx
[[[subnet 10.0.0.0/8]]]
option1: xxx
option2: xxx
[controller mycontroller]
type: evpn
option1: xxx
option2: xxx
[dns mydns]
type: powerdns
option1: xxx
option2: xxx
What do you think about this ?
Another way could be a simple yaml config file. (but I think it's not
really matching currents proxmox configs formats)
Alexandre
next reply other threads:[~2021-01-12 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 9:19 aderumier [this message]
2021-04-18 17:01 ` Thomas Lamprecht
2021-04-20 7:51 ` alexandre derumier
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=ee2f7206124fc8adb6d6e9b6691b8388f8622aeb.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@pve.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