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: Tue, 21 Nov 2023 11:50:39 +0100	[thread overview]
Message-ID: <5fec72d4-28b0-4bd8-a23f-50e6c090cf35@proxmox.com> (raw)
In-Reply-To: <23f0b3562f6433ef80d2605e594a9bd481eb197a.camel@groupe-cyllene.com>

Am 21/11/2023 um 09:54 schrieb DERUMIER, Alexandre:
>>
>>>> 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.
> 
> I think that we could broadcast the state of the service with pvestatd,
> 
> like for ceph services ?
> 

Yes, but IMO it'd be better to rework that into a more general mechanism
that allows to check if a feature is supported supported. We could also
hook into apt/dpkg there and only update this state on actual changes
to the installed packages.

But IMO something for the future, for now warning on apply is fine enough
IMO, if we switch those warnings to using PVE::RESTEnvironment::log_warn
the task will also be marked orange in the UI task list, so it would be
quite visible for the admin.




      reply	other threads:[~2023-11-21 10:50 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
2023-11-21  8:54     ` DERUMIER, Alexandre
2023-11-21 10:50       ` Thomas Lamprecht [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=5fec72d4-28b0-4bd8-a23f-50e6c090cf35@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