RIPE Database Release 1.73.1 Available in the Release Candidate Environment
Dear colleagues, Based on feedback from users testing RIPE Database release 1.73 in the Release Candidate (RC) environment, the RIPE NCC Database Group have made some software improvements that we’ve decided to incorporate into the next deployment. We will not deploy version 1.73 to production. Instead, we will deploy the improved version, 1.73.1, to the RC environment today, 19 May, and to production on 27 May 2014. The main concern with RIPE Database release 1.73 was related to user-automated assignment generation in the RIPE Database for legacy address space. With release 1.73, if a legacy object was updated with an incorrect "status:" attribute value, then the update would fail. With version 1.73.1, the database software will accept the update, regardless of any value supplied by the user, but will show a warning if the “status:” attribute value is incorrect. For more information about this release and how it might affect your operations, please see the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.73.... We look forward to any questions or comments you might have. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC
Dear colleagues, RIPE Database software release 1.73.1 has now been deployed into production. The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:" attribute. We have also modified all legacy INETNUM objects and set the "status:" to 'LEGACY'. Regards Denis Walker Business Analyst RIPE NCC Database Team On 19/05/2014 16:32, Johan Åhlén wrote:
Dear colleagues,
Based on feedback from users testing RIPE Database release 1.73 in the Release Candidate (RC) environment, the RIPE NCC Database Group have made some software improvements that we’ve decided to incorporate into the next deployment. We will not deploy version 1.73 to production. Instead, we will deploy the improved version, 1.73.1, to the RC environment today, 19 May, and to production on 27 May 2014.
The main concern with RIPE Database release 1.73 was related to user-automated assignment generation in the RIPE Database for legacy address space. With release 1.73, if a legacy object was updated with an incorrect "status:" attribute value, then the update would fail. With version 1.73.1, the database software will accept the update, regardless of any value supplied by the user, but will show a warning if the “status:” attribute value is incorrect.
For more information about this release and how it might affect your operations, please see the release notes: https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.73....
We look forward to any questions or comments you might have.
Kind regards,
Johan Åhlén Assistant Manager Database RIPE NCC
Hi Denis,
RIPE Database software release 1.73.1 has now been deployed into production.
The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:" attribute. We have also modified all legacy INETNUM objects and set the "status:" to 'LEGACY'.
And all the others to "status: ASSIGNED" it seems :) Thanks! Sander
The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:" attribute. We have also modified all legacy INETNUM objects and set the "status:" to 'LEGACY'.
And all the others to "status: ASSIGNED" it seems :)
...with the odd 'status: OTHER' for objects that are neither legacy nor assigned by the NCC. Cheers, Rob
On Tue, May 27, 2014 at 04:24:45PM +0200, Denis Walker wrote:
RIPE Database software release 1.73.1 has now been deployed into production.
The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:" attribute. We have also modified all legacy INETNUM objects and set the "status:" to 'LEGACY'.
Is it possible to stop forcefully inserting this line: remarks: For information on "status:" attribute read <snip> in one of the next releases? To be more specific: disable enforceRemarksRightBeforeStatus() for remarks about the 'status' attribute. As a method to inform resource-holders that something has changed I think that one-shot inserting of remarks is a good method (next to informing mailing-lists, twitter, etc), but these messages should not be enforced too long. I'm fine with leaving the existing remarks in the DB, just don't enforce on new updates after four weeks or so. Kind regards, Job
Dear Job This was only a short term action and the persistence of this remarks attribute will be dropped in the next release 1.74. We wanted to persist it for a short while otherwise the first auto-generated update would have removed it with little chance of it being noticed. Regards Denis Walker Business Analyst RIPE NCC Database Team On 13/06/2014 11:50, Job Snijders wrote:
On Tue, May 27, 2014 at 04:24:45PM +0200, Denis Walker wrote:
RIPE Database software release 1.73.1 has now been deployed into production.
The RIPE NCC has modified all AUT-NUM objects to add the mandatory "status:" attribute. We have also modified all legacy INETNUM objects and set the "status:" to 'LEGACY'. Is it possible to stop forcefully inserting this line:
remarks: For information on "status:" attribute read <snip>
in one of the next releases? To be more specific: disable enforceRemarksRightBeforeStatus() for remarks about the 'status' attribute.
As a method to inform resource-holders that something has changed I think that one-shot inserting of remarks is a good method (next to informing mailing-lists, twitter, etc), but these messages should not be enforced too long. I'm fine with leaving the existing remarks in the DB, just don't enforce on new updates after four weeks or so.
Kind regards,
Job
On Fri, Jun 13, 2014 at 11:57:42AM +0200, Denis Walker wrote:
This was only a short term action and the persistence of this remarks attribute will be dropped in the next release 1.74. We wanted to persist it for a short while otherwise the first auto-generated update would have removed it with little chance of it being noticed.
Yes, makes absolute sense. Thanks for your confirmation! Kind regards, Job
participants (5)
-
Denis Walker -
Job Snijders -
Johan Åhlén -
Rob Evans -
Sander Steffann