public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gabriel Goller <g.goller@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-ve-rs 5/9] frr: add template serializer and serialize fabrics using templates
Date: Wed, 25 Feb 2026 18:03:34 +0100	[thread overview]
Message-ID: <c3f23yet4o4tjnywyvyaoyyizdafmnx7glwwuu3zbwwfnnxva7@q2qfleshzw2l> (raw)
In-Reply-To: <yac7x5njtjzp2vkn726v54y2kjft6u6mt6hpirzbv6f2okbe74@f4w33nhbhtuq>

> [snip]
> > > @@ -166,76 +73,128 @@ pub enum CommonInterfaceNameError {
> > >  ///
> > >  /// FRR itself doesn't enforce any limits, but the kernel does. Linux only allows interface names
> > >  /// to be a maximum of 16 bytes. This is enforced by this struct.
> > > -#[derive(Clone, Debug, PartialEq, Eq, Hash, PartialOrd, Ord)]
> > > -pub struct CommonInterfaceName(String);
> > > +#[derive(Clone, Debug, PartialEq, Eq, Hash, PartialOrd, Ord, Serialize, Deserialize)]
> > > +pub struct InterfaceName(String);
> > >  
> > > -impl TryFrom<&str> for CommonInterfaceName {
> > > -    type Error = CommonInterfaceNameError;
> > > +impl TryFrom<&str> for InterfaceName {
> > > +    type Error = InterfaceNameError;
> > >  
> > >      fn try_from(value: &str) -> Result<Self, Self::Error> {
> > >          Self::new(value)
> > >      }
> > >  }
> > >  
> > > -impl TryFrom<String> for CommonInterfaceName {
> > > -    type Error = CommonInterfaceNameError;
> > > +impl TryFrom<String> for InterfaceName {
> > > +    type Error = InterfaceNameError;
> > >  
> > >      fn try_from(value: String) -> Result<Self, Self::Error> {
> > >          Self::new(value)
> > >      }
> > >  }
> > >  
> > > -impl CommonInterfaceName {
> > > -    pub fn new<T: AsRef<str> + Into<String>>(s: T) -> Result<Self, CommonInterfaceNameError> {
> > > +impl InterfaceName {
> > > +    pub fn new<T: AsRef<str> + Into<String>>(s: T) -> Result<Self, InterfaceNameError> {
> > 
> > Is Into<String> as bound necessary here? Anything we can access as str
> > reference can be converted into a string anyway?
> 
> Umm I think so because we need a owned String? This way we don't need to force a
> clone.

I now have this overengineered api type :) :

   /// Name of a interface, which is common between all protocols.
   ///
   /// FRR itself doesn't enforce any limits, but the kernel does. Linux only allows interface names
   /// to be a maximum of 16 bytes. This is enforced by this struct.
   #[derive(Clone, Debug, PartialEq, Eq, Hash, PartialOrd, Ord, Serialize, Deserialize)]
   pub struct InterfaceName(String);

   impl TryFrom<&str> for InterfaceName {
       type Error = InterfaceNameError;

       fn try_from(s: &str) -> Result<Self, Self::Error> {
           Self::validate(s).map(Self::from_str_unchecked)
       }
   }

   impl TryFrom<String> for InterfaceName {
       type Error = InterfaceNameError;

       fn try_from(value: String) -> Result<Self, Self::Error> {
           if Self::validate(&value).is_ok() {
               Ok(Self::from_string_unchecked(value))
           } else {
               Err(InterfaceNameError::TooLong)
           }
       }
   }

   impl InterfaceName {
       fn validate(s: &str) -> Result<&str, InterfaceNameError> {
           if s.len() <= 15 {
               Ok(s)
           } else {
               Err(InterfaceNameError::TooLong)
           }
       }
       fn from_string_unchecked(s: String) -> InterfaceName {
           Self(s)
       }

       fn from_str_unchecked(s: &str) -> InterfaceName {
           Self::from_string_unchecked(s.to_string())
       }
   }



> 
> [snip]




  reply	other threads:[~2026-02-25 17:02 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 16:01 [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} 00/23] Generate frr config using jinja templates and rust types Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 1/9] ve-config: firewall: cargo fmt Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 2/9] frr: add proxmox-frr-templates package that contains templates Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 3/9] ve-config: remove FrrConfigBuilder struct Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 4/9] sdn-types: support variable-length NET identifier Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 5/9] frr: add template serializer and serialize fabrics using templates Gabriel Goller
2026-02-25 13:43   ` Stefan Hanreich
2026-02-25 16:29     ` Gabriel Goller
2026-02-25 17:03       ` Gabriel Goller [this message]
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 6/9] frr: add isis configuration and templates Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 7/9] frr: support custom frr configuration lines Gabriel Goller
2026-02-19 12:17   ` Hannes Laimer
2026-02-19 15:01     ` Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 8/9] frr: add bgp support with templates and serialization Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 9/9] frr: store frr template content as a const map Gabriel Goller
2026-02-25  9:23   ` Stefan Hanreich
2026-02-25 10:08     ` Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-perl-rs 1/2] sdn: add function to generate the frr config for all daemons Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-perl-rs 2/2] sdn: add method to get a frr template Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 01/10] sdn: remove duplicate comment line '!' in frr config Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 02/10] sdn: tests: add missing comment " Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 03/10] tests: use Test::Differences to make test assertions Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 04/10] sdn: write structured frr config that can be rendered using templates Gabriel Goller
2026-02-19 13:52   ` Hannes Laimer
2026-02-19 15:36     ` Gabriel Goller
2026-02-19 15:44       ` Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 05/10] tests: rearrange some statements in the frr config Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 06/10] sdn: adjust frr.conf.local merging to rust template types Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 07/10] cli: add pvesdn cli tool for managing frr template overrides Gabriel Goller
2026-02-19 12:39   ` Hannes Laimer
2026-02-19 15:49     ` Gabriel Goller
2026-02-24 14:05   ` Stefan Hanreich
2026-02-03 16:01 ` [PATCH pve-network 08/10] debian: handle user modifications to FRR templates via ucf Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 09/10] api: add dry-run endpoint for sdn apply to preview changes Gabriel Goller
2026-02-24 13:53   ` Stefan Hanreich
2026-02-03 16:01 ` [PATCH pve-network 10/10] test: add test for frr.conf.local merging Gabriel Goller
2026-02-24 13:27   ` Stefan Hanreich
2026-02-25 15:52     ` Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-manager 1/1] sdn: add dry-run view for sdn apply Gabriel Goller
2026-02-24 12:49   ` Stefan Hanreich
2026-02-03 16:01 ` [PATCH pve-docs 1/1] docs: add man page for the `pvesdn` cli Gabriel Goller
2026-02-23 16:09 ` [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} 00/23] Generate frr config using jinja templates and rust types Hannes Laimer
2026-02-24 11:09   ` Stefan Hanreich

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=c3f23yet4o4tjnywyvyaoyyizdafmnx7glwwuu3zbwwfnnxva7@q2qfleshzw2l \
    --to=g.goller@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.hanreich@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