Release 1.86 deployed to RC
Dear working group, We have deployed release 1.86 to the Release Candidate environment. With this release we will: = Make "descr:" tribute optional for all object types as discussed in the Database WG. = Prevent RIPE-NCC-RPSL-MNT to be used as mnt-by We encourage all users of the database to test their tools. Kind regards, Thiago da Cruz Software Engineer - RIPE NCC Database Team
Dear working group, We have now deployed release 1.86 to production. As mentioned this release: = Makes "descr:" tribute optional for all object types as discussed in the Database WG. = Prevents RIPE-NCC-RPSL-MNT to be used as mnt-by Please note that we were also planning to perform the following clean-up actions: = 11 April, clean-up existing "descr:" attributes where the RIPE NCC enforced organisation names = 11 April, warn users of objects with RIPE-NCC-RPSL-MNT on "mnt-by:" = 25 April, remove RIPE-NCC-RPSL-MNT from "mnt-by:" on all objects Unfortunately we cannot do this work earlier, because our Customer Service department is currently very busy with invoicing, and we want to be sure that we have enough staff available for any questions this might raise. Also note that the "descr:" is currently still not editable in the LIR Portal allocation object editor. However, rather than adding this to the object editors, we are working out an implementation plan to phase out object editors and allow LIRs to use their own maintainer on their organisation and allocation objects. You can expect an update on this, to this list shortly. In the meantime you can modify the "descr:" attribute on assignments. Please let us know if you have any more questions or comments. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE Database Group
On 07 Mar 2016, at 12:02, Thiago da Cruz Pereira <tdacruzper@ripe.net> wrote:
Dear working group,
We have deployed release 1.86 to the Release Candidate environment.
With this release we will:
= Make "descr:" tribute optional for all object types as discussed in the Database WG. = Prevent RIPE-NCC-RPSL-MNT to be used as mnt-by
We encourage all users of the database to test their tools.
Kind regards, Thiago da Cruz Software Engineer - RIPE NCC Database Team
Dear working group, As announced earlier, we have now finished the clean-up of "descr:" attributes, and sent out warnings to users of objects with the RIPE-NCC-RPSL-MNT. Kind regards, Tim Bruijnzeels
On 21 Mar 2016, at 17:32, Tim Bruijnzeels <tim@ripe.net> wrote:
Dear working group,
We have now deployed release 1.86 to production. As mentioned this release:
= Makes "descr:" tribute optional for all object types as discussed in the Database WG. = Prevents RIPE-NCC-RPSL-MNT to be used as mnt-by
Please note that we were also planning to perform the following clean-up actions:
= 11 April, clean-up existing "descr:" attributes where the RIPE NCC enforced organisation names = 11 April, warn users of objects with RIPE-NCC-RPSL-MNT on "mnt-by:" = 25 April, remove RIPE-NCC-RPSL-MNT from "mnt-by:" on all objects
Unfortunately we cannot do this work earlier, because our Customer Service department is currently very busy with invoicing, and we want to be sure that we have enough staff available for any questions this might raise.
Also note that the "descr:" is currently still not editable in the LIR Portal allocation object editor. However, rather than adding this to the object editors, we are working out an implementation plan to phase out object editors and allow LIRs to use their own maintainer on their organisation and allocation objects. You can expect an update on this, to this list shortly. In the meantime you can modify the "descr:" attribute on assignments.
Please let us know if you have any more questions or comments.
Kind regards
Tim Bruijnzeels
Assistant Manager Software Engineering RIPE Database Group
On 07 Mar 2016, at 12:02, Thiago da Cruz Pereira <tdacruzper@ripe.net> wrote:
Dear working group,
We have deployed release 1.86 to the Release Candidate environment.
With this release we will:
= Make "descr:" tribute optional for all object types as discussed in the Database WG. = Prevent RIPE-NCC-RPSL-MNT to be used as mnt-by
We encourage all users of the database to test their tools.
Kind regards, Thiago da Cruz Software Engineer - RIPE NCC Database Team
Dear working group, Unfortunately, we have found an issue where the clean-up of the "descr:" attribute resulted in reformatting of database objects. Specifically, multiple whitespace characters were reduced to a single space character, and if a line had multiple ‘#’ characters only the first was kept. There were no semantic changes to objects, but formatting was affected. Obviously this should not have happened and we are working on rolling back this change with the highest priority. Once this is resolved, we will revisit the clean-up script and only run it again when we're sure that this issue is fixed. We apologise for the inconvenience caused by this. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group
On 12 Apr 2016, at 13:59, Tim Bruijnzeels <tim@ripe.net> wrote:
Dear working group,
As announced earlier, we have now finished the clean-up of "descr:" attributes, and sent out warnings to users of objects with the RIPE-NCC-RPSL-MNT.
Kind regards,
Tim Bruijnzeels
On 21 Mar 2016, at 17:32, Tim Bruijnzeels <tim@ripe.net> wrote:
Dear working group,
We have now deployed release 1.86 to production. As mentioned this release:
= Makes "descr:" tribute optional for all object types as discussed in the Database WG. = Prevents RIPE-NCC-RPSL-MNT to be used as mnt-by
Please note that we were also planning to perform the following clean-up actions:
= 11 April, clean-up existing "descr:" attributes where the RIPE NCC enforced organisation names = 11 April, warn users of objects with RIPE-NCC-RPSL-MNT on "mnt-by:" = 25 April, remove RIPE-NCC-RPSL-MNT from "mnt-by:" on all objects
Unfortunately we cannot do this work earlier, because our Customer Service department is currently very busy with invoicing, and we want to be sure that we have enough staff available for any questions this might raise.
Also note that the "descr:" is currently still not editable in the LIR Portal allocation object editor. However, rather than adding this to the object editors, we are working out an implementation plan to phase out object editors and allow LIRs to use their own maintainer on their organisation and allocation objects. You can expect an update on this, to this list shortly. In the meantime you can modify the "descr:" attribute on assignments.
Please let us know if you have any more questions or comments.
Kind regards
Tim Bruijnzeels
Assistant Manager Software Engineering RIPE Database Group
On 07 Mar 2016, at 12:02, Thiago da Cruz Pereira <tdacruzper@ripe.net> wrote:
Dear working group,
We have deployed release 1.86 to the Release Candidate environment.
With this release we will:
= Make "descr:" tribute optional for all object types as discussed in the Database WG. = Prevent RIPE-NCC-RPSL-MNT to be used as mnt-by
We encourage all users of the database to test their tools.
Kind regards, Thiago da Cruz Software Engineer - RIPE NCC Database Team
participants (2)
-
Thiago da Cruz Pereira -
Tim Bruijnzeels