engineering status report

32
Mark Kosters Engineering Status Report

Upload: gerodi

Post on 24-Feb-2016

36 views

Category:

Documents


0 download

DESCRIPTION

Engineering Status Report. Mark Kosters. Engineering Theme. 2012 s uccess is being aided by contractors (but not as many) An age for new engineers Lots of work done, much more to do. Staffing. Operations 6 People + Manager (one slot open) Development 5 Developers + Manager - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Engineering Status Report

Mark Kosters

Engineering Status Report

Page 2: Engineering Status Report

2

Engineering Theme• 2012 success is being aided by

contractors (but not as many)• An age for new engineers• Lots of work done, much more to do

Page 3: Engineering Status Report

3

Staffing• Operations

– 6 People + Manager – (one slot open)

• Development– 5 Developers + Manager– 5 Contractors (down 2 since ARINXXVIII)

• Quality Assurance– 3 QA + Manager– 4 Contractors

• Project Management– 1 (slot open)

• Management– 1 (me)

Page 4: Engineering Status Report

4

Operations• Upgrading end-of-life equipment• Rolled out Anycast

– Running now in St Maartin, San Jose, and Ashburn– Soon in Toronto

• Maintaining the various environments we have running (Production/OT&E/Dev/QA/Staging)

• Close to running https version of Whois-RWS• IT Support• RPKI rollout

Page 5: Engineering Status Report

5

Whois-RWS Traffic Loads• Have had a pretty good run–Multiple highs in 2010 and 2011

• Today– Running “normally” now at 475 queries

per second– RESTful calls have overtaken port 43

calls• 1.8 Billion RESTful calls for March• 1.2 Billion Port 43 queries

Page 6: Engineering Status Report

6

Whois-RWS StatisticsQueries on Port 43

Months

Que

ries

Per

Sec

ond

1999-102000-102001-102002-102003-102004-102005-102006-102007-102008-102009-102010-102011-100

500

1000

1500

2000

2500

3000

3500

4000

Page 7: Engineering Status Report

Whois-RWS StatisticsQueries

Months

Que

ries

Per

Sec

ond

2010-09

2010-10

2010-11

2010-12

2011-01

2011-02

2011-03

2011-04

2011-05

2011-06

2011-07

2011-08

2011-09

2011-10

2011-11

2011-12

2012-01

2012-02

2012-03

0.00

500.00

1000.00

1500.00

2000.00

2500.00

3000.00

3500.00

4000.00

4500.00

RESTfulPort 43Total

Page 8: Engineering Status Report

8

Whois-RWS – IPv6To

tal P

er M

onth

Month

Page 9: Engineering Status Report

9

Development/QA• Improvements to existing systems• ARIN Online releases since ARIN XXVIII– Invoice reminders now in ARIN Online– Implementation of Policy 2011.3

• Huge implications on DNS zone generation• No longer creating delegations at a /20 boundary

– WhoWas– Moving to newer JAVA concepts– Various Whois-RWS improvements and ACSP

requests

Page 10: Engineering Status Report

10

Current Tasks• Moving from Red Hat JBoss to JBoss

AS7– Cost reduction measure– Lots of improvements to internal

frameworks• Home-stretch for Hosted RPKI– Working on loose ends and documentation– Embedding the CPS URL in certificates

currently break two of the three existing validators

Page 11: Engineering Status Report

11

Upcoming Tasks for 2012• Deploy hosted RPKI• Implement delegated RPKI (up/down)• Moving from Oracle to open source

database– Cost reduction measure

• Moving off Red Hat OS– Cost reduction again

• IPv4 runout changes• Integrated payments

Page 12: Engineering Status Report

12

How is ARIN Online used?• 54,196 accounts activated by Q1 of

2012 since inception

2008200920102011

2012*

Number of Accounts Activated5000 10000 15000 20000

* Through Q1 of 2012

Page 13: Engineering Status Report

13

Active Usage of ARIN Online

0 1 2 - 5 6 - 10 11 - 15 >160

500010000150002000025000

Logins

# of

Us

ers

Times Logged In

Page 14: Engineering Status Report

14

Management of POCsSince April, 2011

8933

44547

451

Create

ARIN OnlineTemplatesREST

Modify

9014

Includes POCs created via SWiPs

Page 15: Engineering Status Report

15

Management of OrgsSince April, 2011

5585

46757

259Create

ARIN Online

Templates

REST11653

9 2

Modify

Includes Orgs created via SWiPs

ARIN Online 208

Templates 12

Org Deletes

Page 16: Engineering Status Report

16

Net Record ManagementSince April, 2011

Modify335

394

781

507

Requests

v6 ISPv6 End Userv4 ISPv4 End User

Similar toOrg Modify

All requests made via ARIN Online

2844

20

Page 17: Engineering Status Report

17

Reg-RWS (RESTful Provisioning)

Since April, 2011

REST

Templates

0 100000200000300000400000500000600000700000

Transactions

April Jun

eAu

gust

Octobe

r

Decembe

r

Febru

ary0

100020003000400050006000

POC CreateOrg CreateCustomer Createv6 Simple Createv6 Simple Removev4 Simple Createv4 Simple Remove

Page 18: Engineering Status Report

18

Evolution/Development of Services• Briefly look at three services– How introduced– Participation– Feedback

• WhoWas• RPKI• Whois -> Whois-RWS

Page 19: Engineering Status Report

19

WhoWas Requests• Demo Period– 9 inquiries– 1 actually used the system

• Production– 45 authorized users– 125 requests–Most active user: 66 requests

Page 20: Engineering Status Report

20

RPKI Pilot• Pilot period– Operational since 7/2009– 63 users– 76 ROAs in the pilot

• Instructions on how to use– https://www.arin.net/resources/rpki.html– Includes the TAL!

• Services are hooked into the pilot– RIPE validator

Page 21: Engineering Status Report

21

RPKI Progress on Production Services• Huge challenge developing against IBM HSM has been

overcome– Working with a secured embedded device– The attached host is a RPKI generator– The HSM is a RPKI validator

• Estimated to have first part in production in 2012– Will require RSA or LRSA to participate

• Protocol is mature – kind of – Validators do not allow for extension that we require

(certificate policies extension)– Rsync may not be the best protocol to retrieve data from

repositories

Page 22: Engineering Status Report

22

RPKI Challenges• Delegated is up next• Distribution protocol changes (Rsync verses http or ?)• Publication Protocol• ERX and Inter-RIR transfers• Merging with the Global Trust Anchor• Simultaneous Operation of RIR Trust Anchor and Global

Trust Anchor

Page 23: Engineering Status Report

23

Whois circa 2007• Whois was at the end of life– Extremely expensive to run and

maintain– No real-time updates

• Need a replacement• Need to add CIDR query support• Need a way to handle change

Page 24: Engineering Status Report

24

Whois-RWS• Andy came up with a RESTful

interface• Added real-time updates• Added way to evolve features via

REST• Other RIRs are following along

Page 25: Engineering Status Report

25

Whois-RWS Today• A working Group is chartered for both

names and numbers (WEIRDS)• Security and other committees within

ICANN is pushing for a replacement to WHOIS - SSAC, Whois review team, Internationalized Whois WG, etc.

• ICANN sees this work as a way to move away from Whois

Page 26: Engineering Status Report

26

Retrospective• ARIN has matured and come a long

way since fall of 2007– Lots of core stuff ignored for too long– Example database was Oracle 8 on Solaris

8 • Solaris 8 released in 2000• Oracle 8 end of life was 2004/6

– Software deployments were impossibly hard

– No real interactive website

Page 27: Engineering Status Report

27

ARIN Today• Almost complete rewrite• Additional functionality– Reg-RWS–Whois-RWS– DNSSEC– Security (API-Keys)

• IRR feature set– Now at par with other IRR’s for

functionality (using templates)

Page 28: Engineering Status Report

28

Where this puts us• With the core completed…– Items modified, documented, tested,

and deployed with confidence – Bolt on things faster (WhoWas took 3

months)

Page 29: Engineering Status Report

29

Schedule Challenges• Planned Functionality for 2011– Hosted RPKI– Delegated RPKI–Managing unmet IPv4 requests– Payment integration– SWIP Easy–Migration off of Red Hat and Oracle

Page 30: Engineering Status Report

30

Schedule Challenges• Unplanned Functionality– Extended stats for NRO– DNSSEC improvements– Streamlined Transfer Service– CMSD membership/voter functionality– Integration of IRR within ARIN Online– Lame delegation reporting– Additional OT&E services– Alternative RPKI-like services– Retrievable meeting registration data

Page 31: Engineering Status Report

31

Schedule Challenges• Community Needs/Policy

– Ways to better vet/implement community needs – Need to hear from you

• Technical and Operational Debt– Many existing internal processes are inefficient and labor intensive– Software changes

• Thought Leadership– Whois-RWS– RPKI– Research

Page 32: Engineering Status Report

32

Comments?