Skip to Content.
Sympa Menu

rare-dev - Re: [rare-dev] Integration of the release manager

Subject: Rare project developers

List archive

Re: [rare-dev] Integration of the release manager


Chronological Thread 
  • From: Alexander Gall <>
  • To: <>
  • Cc: <>
  • Subject: Re: [rare-dev] Integration of the release manager
  • Date: Tue, 12 Apr 2022 09:18:18 +0200

Hi

On Fri, 8 Apr 2022 09:38:41 +0200, mc36 <> said:

> On 4/7/22 09:24, Alexander Gall wrote:
>> Thanks, works as expected.

> i just upgraded the testbed to the latest from git, and played a bit with
> the stuff...
> one thing i noticed is that the boxes does not boot cleanly because the
> sticky param:

> POZ0001#show logging
> 2022-04-08 07:25:04 info cfgInit.doInit:cfgInit.java:762 booting
> 2022-04-08 07:25:04 info cfgInit.doInit:cfgInit.java:921 initializing
> hardware
> 2022-04-08 07:25:04 info cfgInit.doInit:cfgInit.java:927 applying defaults
> 2022-04-08 07:25:06 info cfgInit.doInit:cfgInit.java:948 applying
> configuration
> 2022-04-08 07:25:10 info cfgInit.executeSWcommands:cfgInit.java:750 line
> 797: "alias exec tna-set-profile sticky-param GEANT_TESTBED" : child 124379
> created on 3 child started
> GEANT_TESTBED is already the current profile process exited with 256
> code % returned 1
> 2022-04-08 09:25:10 error cfgInit.doInit:cfgInit.java:956 1 errors found
> 2022-04-08 09:25:10 info cfgInit.doInit:cfgInit.java:983 boot completed

> i'm writing you that my idea here is a new knob: "alias exec asdf
> sticky-onlychanged"
> then it'll be executed only if the parameter changed...
> it's a redundant check because you already implemented it but imho it's the
> way to go....
> and imho we'll need an other knob, "alias exec asdf sticky-onlysuccess"
> which will remember the last choice only if the execution went well...

Ok, in that case I'll remove the check from the script. I'll also add
a new alias that shows a list of available profiles. This was also
part of the script when the user didn't provide a profile, but I'll
remove that, too.

> an other notice that you really ask the user in the aliases, but please
> dont...
> freeroutecr have at least 2 places where it wont work because there is no
> controlling terminal so noone can answer causing the stuff to hang for a
> minute:

> 1) "config revert" executed by the admin to revert the config changes
> immediately (available in xr)
> 2) "config rollback" which auto-reverts if the admin fails to cleanly exit
> config mode (available in xe)

This only concerns the aliases that have a sticky parameter, right? In
other words: are non-sticky aliases only ever executed from the CLI?

--
Alex



Archive powered by MHonArc 2.6.19.

Top of Page