[db-wg] cmd line asused and webasused

On 17/01/2012 16:21, Nick Hilliard wrote:
> Hi Alex,
> Problem is, we don't yet have a replacement command-line tool for dealing
> with quick-n-easy LIR resource usage summarisation.  This has meant that
> the people who depended on this tool were left hanging for the last 8
> years, because the code slowly rotted as interfaces subtly changed over
> time.  This is not a criticism of changing the DB interface or anything,
> btw - progress needs to happen.
>
> In terms of being platform specific, it was limited to any platform which
> could run perl - perhaps with minor modifications.  There are lots of
> complaints that people make about perl, (some legitimate) but platform
> portability is not one of them.
>
> OTOH, webasused can be very slow.  E.g. I submitted a request for a LIR at
> 15:28 GMT today, and got a reply at 15:39.  This makes it unusable for a
> typical workflow process (e.g. run asused, check output against internal
> records, submit a couple of updates, run asused again, check again, repeat
> until satisfied).
>
> The web version is also unauthenticated which means that it's open to third
> parties submitting requests for arbitrary LIRs.  And it doesn't support
> ipv6, which means that it's still difficult to do resource reconciliation
> for v6 assignments.
>
> I'll admit that not everyone likes command line tools, but for those of us
> who continue to us asused, it's a real pity that it wasn't maintained and
> further developed to support ipv6.
>

Nick, Alex et al

At the Board meeting on the 8th December the board gave Axel an action 
"to reinstate/redevelop the stand-alone version of the RIPE NCC ASused tool"

I doubt that this action would be satisfied merely by the provision of 
an API into the webasused tool.

Alex, you may like to check this with Axel. It is possible that it was 
misunderstood by him, but it is very clearly minuted.

And I'd agree with Nick that lack of platform portability is one of the 
few brickbats that cannot be aimed atperl.

Nigel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20120117/2e140469/attachment.html>