[db-wg] Proposal for Test Database Cleanup

Dear Colleagues,

As described in the 'Proposal for Periodic Clean-up for the TEST RIPE 
Database', the test database has been reset to a default set of 
objects.

The Proposal for Periodic Clean-up for the TEST RIPE Database is 
available at:

http://www.ripe.net/ripe/maillists/archives/db-wg/2005/msg01181.html

The next periodic clean up will take place on the first Tuesday of next 
month (6 December, 2005). In the initial state, the following objects 
are loaded:

mntner:         TEST-ROOT-MNT
mntner:         TEST-DBM-MNT
aut-num:        AS1
person:         Test Person
role:           TEST ROLE
organisation:   ORG-TT1-TEST
inetnum:        0.0.0.0 - 255.255.255.255
inet6num:       0::/0
route:          0.0.0.0/0
route6:         0::/0
as-block:       AS0 - AS65535
domain:         in-addr.arpa
domain:         ip6.arpa
domain:         e164.arpa

For generating objects you may need the password of TEST-DBM-MNT. It is 
written in the 'remarks:' attributes of the object itself.

Please direct all comments and suggestions to ripe-dbm at ripe.net

Regards,

On Tuesday 25 October 2005 17:26, Can Bican wrote:
> Proposal for Periodic Clean-up for the TEST RIPE Database
>
> Motivation
> ----------
>
> The RIPE NCC provides a TEST RIPE Database for users to learn how to
> use the software and try out new updates without the risk of damaging
> data in the real database. This database uses the same software as
> the production version of the RIPE Database.
>
> The data in the TEST database is NOT a copy of that in the RIPE
> Database, it is not authoritative data. Therefore no value should be
> put on it.
>
> The RIPE NCC only carries out maintenance operations in the RIPE
> Database and not in the TEST database. Over time, however, outdated
> features in the database software may make some parts of the TEST
> database unusable.
>
> To ensure a clean functioning test environment, we propose a periodic
> clean-up of the TEST database.
>
> Objectives
> ----------
>
> - To increase the availability of the TEST database with a minimum of
> administrator interference.
>
> - To clean up unneeded items from the TEST database.
>
> - To provide a consistent starting point for the TEST database.
>
> Implementation
> --------------
>
> - Every first Tuesday of each month, the TEST database will be
> reloaded with a set of database objects. Downtime will be brief, and
> is estimated to be at most half an hour.
>
> - After the reinitialisation, the database will contain:
>
>    * One PERSON, one ROLE, one ORGANISATION and one MAINTAINER object
> for test purposes.
>    * One MAINTAINER object to maintain the test MAINTAINER object.
>    * 0/0 network ranges for IPv4 and IPv6.
>    * 0/0 ROUTE and ROUT6 objects.
>    * One as-block containing as0 - as65535.
>    * Three DOMAIN objects for 'in-addr.arpa', 'ip6.arpa' and
> 'e164.arpa'.

-- 
Can Bican
Software Engineering Department