1 / 10

Frederico A C Neves <fneves@lacnic>

Frederico A C Neves <fneves@lacnic.net>. Data Input. Flat file in RPSL format 3 object types (ARIN old DB) Aut-num Inetnum Person Entity is an attribute of the 2 services objects No strong “ownership” relation between service objects. LacNIC Objects. Entity Block (inetnum)

rainer
Download Presentation

Frederico A C Neves <fneves@lacnic>

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Frederico A C Neves <fneves@lacnic.net> Mexico City, 11/12 Nov 2002

  2. Data Input • Flat file in RPSL format • 3 object types (ARIN old DB) • Aut-num • Inetnum • Person • Entity is an attribute of the 2 services objects • No strong “ownership” relation between service objects Mexico City, 11/12 Nov 2002

  3. LacNIC Objects • Entity • Block (inetnum) • ASN (aut-num) • Person Mexico City, 11/12 Nov 2002

  4. Objects relation Entity 1 Person 1 2 N N Block ASN 1 1 Mexico City, 11/12 Nov 2002

  5. Data Manipulation • Two temporary object (OldEnt and OldId) were created to import the data • During the import an algorithm cleaned up the “owner” name and compared them between the 2 services objects. The cross relation was got from these information. Name clashes were treated by manual processing. • The adopted transition schema provides only full whois and reverse publication services until the update of the information is made. • Block boundaries were adjusted to prefixes. • Represented reverse delegation on the Whois were adjusted to prefixes and represent exactly the requested reverse delegation. Mexico City, 11/12 Nov 2002

  6. Migration / Verification • The process took 2 weeks between the arrival of the first dump and the take over of the reverse zone file generation and publication • After the final import the data was verified by independent reverse publication(ARIN and LacNIC) and objects count. Mexico City, 11/12 Nov 2002

  7. Transition Schema • To update the data the customer need to contact RSG. • The customer receives a password and could update the information directly on the system. • During the update the “owner” data is imported in a final object and the customer receives full services directly on the system interface. • The adopted policy to provide smooth transition is: • Customer is allowed to update the data on request • Customer is obligated to update the information during new allocation. • So far we have 10% of the database updated. Mexico City, 11/12 Nov 2002

  8. Data Protection • Database replicated online. • Read load separated from master database • Two full flat file backups during the day • One daily copy on tape to a safe • External online replication Mexico City, 11/12 Nov 2002

  9. Database Replication / Flow Schema RSG Applications User Admin Applications Whois Zone File Generation Master DB Application Data Flow Read Load DB Online Replication Data Flow Backup DB Ext.BackupDB Mexico City, 11/12 Nov 2002

  10. Questions ? Mexico City, 11/12 Nov 2002

More Related