public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
	"pve-devel@pve.proxmox.com" <pve-devel@pve.proxmox.com>
Subject: Re: [pve-devel] pve-network : downgrading frr dependency to suggested
Date: Mon, 20 Nov 2023 18:34:45 +0100	[thread overview]
Message-ID: <07d95b72-1a02-4148-bf51-4327c899d839@proxmox.com> (raw)
In-Reply-To: <7cce062d7d30216f474b12b3a7fae826c940c43e.camel@groupe-cyllene.com>

Am 20/11/2023 um 18:20 schrieb DERUMIER, Alexandre:
> It's needed for transparent reload (usr/lib/frr/frr-reload.py).
> 
> so you can be 100% sure It'll break if it's not installed ^_^

Ah, we already got a check in EVPN's reload_controller:

    my $bin_path = "/usr/lib/frr/frr-reload.py";

    if (!-e $bin_path) {
        warn "missing $bin_path. Please install frr-pythontools package";
        return;
    }


> 
>>> For the code it would be nice to add a helper that asserts that frr
>>> is installed
>>> for all API endpoints that need it, that way user get informed
>>> upfront, similar
>>> to how we do it for ceph (but no full web installer for now ^^)
> 
> Yes good idea. 
> 
> I don't known if it's easy to check, as the frr is local to each node,
> and the sdn api is global at datacenter level. ?

hmm true, one would only see if the current node one is connect
through supports it, a warning (or error) on apply could be better
then, should ideally happen as early as possible though, to not roll
out a partial state.




  reply	other threads:[~2023-11-20 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 16:55 Thomas Lamprecht
2023-11-20 17:20 ` DERUMIER, Alexandre
2023-11-20 17:34   ` Thomas Lamprecht [this message]
2023-11-21  8:54     ` DERUMIER, Alexandre
2023-11-21 10:50       ` Thomas Lamprecht

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=07d95b72-1a02-4148-bf51-4327c899d839@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=alexandre.derumier@groupe-cyllene.com \
    --cc=pve-devel@pve.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal