From: Francois Prowse via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Francois Prowse <fp@prowsehouse.com>
Subject: [pve-devel] SDN Orchestration - Proof of Concept code/video
Date: Fri, 15 Aug 2025 23:13:28 +0000 [thread overview]
Message-ID: <mailman.108.1755299652.385.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 10686 bytes --]
From: Francois Prowse <fp@prowsehouse.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: SDN Orchestration - Proof of Concept code/video
Date: Fri, 15 Aug 2025 23:13:28 +0000
Message-ID: <SYBP282MB2898DA2BED7108E3D0C37E2FCB34A@SYBP282MB2898.AUSP282.PROD.OUTLOOK.COM>
Hello dev team,
I've been working on a concept to add the ability for Proxmox to provide information to external orchestration platforms, specifically focused on extracting zones, vnets and workload level information. The goal here would be to have these external platforms consume this information for their own use, network configuration, security policy creation, enrichment of log data etc. The code has been written in such a way (I believe) to allow the quick adoption of additional platforms.
I've made a quick overview video and happy to discuss and contribute the code for this.
https://youtu.be/xiRh4ZyEoCQ
Thoughts?
Have a great weekend.
re
Francois
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-08-15 23:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.108.1755299652.385.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=fp@prowsehouse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.