Rare project developers

[mc36 <>]

hi,

On 7/12/22 10:45, Alexander Gall wrote:
> Appreciated :) What would be even better is if the config would show
> the names instead of the translated numbers, e.g. from you example
>
>   sid(cfg-server)#show running-config this
>   server p4lang p4
>     export-port sdn1 sdn1 frontpanel-1/1 10 rs off auto
>
> The way it is now, the meaning of the parameters is lost after
> configuration. I suppose you did it that way because the translation
> takes place in the parser. But how about storing both, the names and
> the values in the config? Then, for the show command you'd display the
> names but when the config is applied it reads the numbers.

so i see that such a thing could ease the single-switch operations,
but to keep flexibility and fool-proofness of the current solution,
finally here is my suggestion:

sid(cfg-server)#show running-config this
server p4lang p4
 export-vrf v2 2
 export-port sdn1 1 10 0 0 0
 export-port sdn2 2 10 0 0 0
 export-port sdn3 3 10 0 0 0
 export-port sdn4 4 10 0 0 0
 interconnect pwether0
 vrf v1
 exit
!

sid(cfg-server)#export-names
sid(cfg-server)#show running-config this
server p4lang p4
 export-names
 export-vrf v2 2
 export-port sdn1 ens5 10 0 0 0
 export-port sdn2 ens6 10 0 0 0
 export-port sdn3 ens7 10 0 0 0
 export-port sdn4 ens8 10 0 0 0
 interconnect pwether0
 vrf v1
 exit
!

sid(cfg-server)#

the drawback of the delayed validation is that for now, everything is 
accepted and stored if the dataplane is not connected...
i could remove these stale ones when the dataplane connects back but hey, 
removing things automagically from the running is not
we supposed to do so.... all in all, it can easily pollute this section, if 
configured, because everything goes to a shadow
list until these entries could be validated properly... for this problem, 
turning off the feature clears the shadow buffer,
if the dataplane is connected... that is, no export-names, export-names, do 
wr will overcome this...

br,
cs