Why are We Moving Away from Maintain?
This presentation is the property of its rightful owner.
Sponsored Links
1 / 25

Why are We Moving Away from Maintain? Jason Gorrie PowerPoint PPT Presentation


  • 75 Views
  • Uploaded on
  • Presentation posted in: General

Why are We Moving Away from Maintain? Jason Gorrie. Agenda. Why Change Selection Process Selection Outcome Implementation Timeline Questions. Definitions. IPAM: IP Address Management DHCP: Dynamic Host Configuration Protocol DNS: Domain Name System DDI: DHCP, DNS, IPAM. Why Change.

Download Presentation

Why are We Moving Away from Maintain? Jason Gorrie

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Why are we moving away from maintain jason gorrie

Why are We Moving Away from Maintain?

Jason Gorrie


Agenda

Agenda

Why Change

Selection Process

Selection Outcome

Implementation Timeline

Questions


Definitions

Definitions

IPAM: IP Address Management

DHCP: Dynamic Host Configuration Protocol

DNS: Domain Name System

DDI: DHCP, DNS, IPAM


Why change

Why Change

Oregon State Univ cease funding

Missing

IPv6 eg:fe80::224:1dff:feab:e78a/64

DNSSEC

Simple disaster recovery


Selection process

Selection Process

Spring 2011: Invite vendors for RFI

Summer 2011: RFP

Fall 2011: RFP technical evaluation

Nov 16, 2011: RFP completed

Dec 01, 2011: PO issued


Selection outcome

Selection Outcome


Infoblox in the industry

Infoblox in the Industry

Carleton University

Université de Montréal

Harvard University

Arizona State University

Tivo


Hardware options

Hardware Options

Infoblox-1050-A

24K DNS req/sec

Infoblox-1550-A

36K DNS req/sec


Hardware ib units

Hardware IB units


Web interface

Web Interface


Lab environment

Lab Environment

Lab: two IB 550-A & one IB 250-A

Setup to allow

Training

Advanced scripting changes

Testing of updates, new features

Setup completed no later: Jan 15, 2012


Preliminary layout

Preliminary Layout


Layout management

Layout - Management


Layout hidden master

Layout – Hidden Master


Layout dhcp campus

Layout - DHCP Campus


Layout dhcp resnet

Layout – DHCP Resnet


Layout unicast anycast

Layout – Unicast & Anycast


Layout insight

Layout - Insight


Layout anycast

Layout – Anycast

A1U: MC – IST machine room

A2:EV2/3 – Environment machine room

A3:E6 - Engineering machine room

A4: Unknown

A5: Unknown

A6U: PHY/? - IST machine room

Aggregate Capacity: ~ 150K DNS requests/sec

Max Observed Typical Load: 4K DNS requests/sec


Implementation timeline

Implementation Timeline


Deliverable timeline

Deliverable Timeline


Important changes

Important Changes

Policy 8 classification of A,AAAA record

Host HW/location data no longer in TXT records, available through API

Less free form data inputs

* No /etc/hosts

* No /etc/networks

Changes to bulk import TBD


Why are we moving away from maintain jason gorrie

API

Written in Perl

Reference manual ~ 1300 pages, functions well documented, sample code

Bloxtools: www.bloxtools.com

my $bind_a = Infoblox::DNS::Record::A->new (

ipv4addr => "1.1.1.1",

name => "bind_a.domain.com",

comment => "this is a demo bind_a record",

disable => "true", ttl => "33",

mac_address => "1:1:1:1:1:1",

views => [$view1] ); # Submit for addition


Question and answer

Question and Answer

Concerns?

What training do you want and how delivered?

/etc/hosts, /etc/networks are there others?

Workflows

MS DNS Integration


Links

Links


  • Login