32

OpenStack Summit Austin - Split Brain (1)

Embed Size (px)

Citation preview

Page 1: OpenStack Summit Austin - Split Brain (1)
luckybaker4
I might remove this and add it as a header on the 3 main slides. I find myself repeating a lot on here.
luckybaker4
I'm going to remove this slide and replace it with "Our OpenStack Story" slide.
Russ Starr
Thinking about deleting this slide since it doesn't focus on the core concept.
Russ Starr
It might look better not to use a transparent image for CHEF. Color clash with background. We can either adjust background image or find CHEF logo with appropriate BG color.
luckybaker4
Agreed. I'm planning on going back through soon and making things pretty. Focused on content right now.
Page 2: OpenStack Summit Austin - Split Brain (1)

AgendaIntroductions & Cerner Story Our PracticesSystem Engineer PerspectiveNetwork Engineer PerspectiveQuestions & Answers

Page 3: OpenStack Summit Austin - Split Brain (1)

Midokura IntroductionAdam JohnsonVP Business, Midokura

Background● Network Virtualization

Overlay● Plugs into Neutron● Open source base:

midonet.org● Fully distributed L2-4● It’s Linux Software

Background● Open source software

developer● Virtual worlds to virtual

machines● Tech to sales

Page 4: OpenStack Summit Austin - Split Brain (1)

Cerner Introductions

@Russ_StarrNetwork Engineer / Architect

Ryan BakerSystem Engineer / Architect

Background● Data Center

Networking● Routing & Switching● Proxy & Load

Balancing

Background● OS System

Management● Data Center

Technologies● Infrastructure

Automation

Page 5: OpenStack Summit Austin - Split Brain (1)

Who Cerner is...

$4.4BILLION

Page 6: OpenStack Summit Austin - Split Brain (1)

Cerner’s OpenStack Story2013/2014: First ExplorationsLate 2014: Official POCEarly 2015: Production PlanningMid 2015: Production Live

Page 7: OpenStack Summit Austin - Split Brain (1)
Page 8: OpenStack Summit Austin - Split Brain (1)

Our Practices - OpenStack Deployment Planning

System Engineer

OpenStack platform architecture including overlay

Deployment strategy

Network Engineer

Underlay network architecture

Responsible for external network connection architecture

50% 50%

workload balance

Page 9: OpenStack Summit Austin - Split Brain (1)

Our Practices - Initial OpenStack Deployment

System Engineer

Deploy OpenStack Install and configures

the overlay

Network Engineer

External network architecture

Observe Deployment

66%

workload balance

34%

Page 10: OpenStack Summit Austin - Split Brain (1)

Our Practices - Final Steps of OpenStack Deployment 66%

workload balance

34%

System Engineer

Continues OpenStack platform tuning

Network Engineer

Configure overlay for tenant networks

Integrate routing with external networks

Page 11: OpenStack Summit Austin - Split Brain (1)

Our Practices - OpenStack Post Go-Live50% 50%

workload balance

System Engineer

Help tenants through Neutron

Advanced overlay agent troubleshooting

Network Engineer

Overlay versionMonitoringHousekeepingAdvanced Neutron

tenant requests

Page 12: OpenStack Summit Austin - Split Brain (1)

Our Practices - Overlay Upgrade (Midonet example)

Network Engineer

Responsible for target version, release notes.

Change Control & Notification

Coordinates with Business Units accordingly

System Engineer

Standby for any help or unexpected situations

Peer ReviewerSoftware repository

updates

10% 90%

workload balance

Page 13: OpenStack Summit Austin - Split Brain (1)
Page 14: OpenStack Summit Austin - Split Brain (1)

Tips and Essential Skills for System EngineersForce yourself to become a network engineer

Start small - Learn CIDR notation!Know the common acronyms and what they mean

VLAN, VXLAN, MTU, BGPIt’s ok to be lost… keep going to those meetingsStand up a full OpenStack deployment, overlay and

all, on your own

Page 15: OpenStack Summit Austin - Split Brain (1)

Tips and Essential Skills for System EngineersCommunication is key!

“It is a network problem” is now “It is OUR problem”

Seemingly Minor changes can make BIG problemsDaily Standups ensure proper communication

Be aware of the words and phrases you use; many have different meaningsBridgingMulti-homed

Page 16: OpenStack Summit Austin - Split Brain (1)

How System Engineers can help Network Engineers

Configuration

Management

Page 17: OpenStack Summit Austin - Split Brain (1)

How System Engineers can help Network Engineers

Configuration

Management

Page 18: OpenStack Summit Austin - Split Brain (1)
Page 19: OpenStack Summit Austin - Split Brain (1)

Tips for Network EngineersKeep underlay network simple and low costKnow Linux / bash environment wellLevel-up on:

Networking: ifconfig, ip add, ip link, ip netns, ethtool, tcpdump, netcat

Utilities: grep, sed, awk, tr, tar, gzip, gitDisk: df, du, mount

Page 20: OpenStack Summit Austin - Split Brain (1)

Tips for Network EngineersGet comfortable with JSON.Learn bash or python to be more efficientLearn to use configuration management tools like

Chef, Puppet, Ansible, etcMake up 3 - 5 letter acronyms that don’t exist.

Page 21: OpenStack Summit Austin - Split Brain (1)

How Network Engineers can help System EngineersRouting protocol basics

IGP vs EGPRoute selection; ECMPBGP Active vs. Established

Stateful devices with connection timers

Page 22: OpenStack Summit Austin - Split Brain (1)

Our Practices - Organizational TipsStart with a small number of good people.Include Linux, Virtualization, Networking, Storage,

and Software Engineering expertise on an OpenStack-dedicated team.

Operate cohesively

Adopt agile practices where possibleInvolve security and other roles that aren’t yet

OpenStack-dedicated.

Page 23: OpenStack Summit Austin - Split Brain (1)
Page 24: OpenStack Summit Austin - Split Brain (1)

As a system engineer, what was the hardest thing to learn (or accept?) about networking?

Page 25: OpenStack Summit Austin - Split Brain (1)

As a network engineer, what was the hardest thing to learn (or

accept?) about systems?

Page 26: OpenStack Summit Austin - Split Brain (1)

What were you the most surprised about when working

with an overlay in your environment?

Page 27: OpenStack Summit Austin - Split Brain (1)

Network Overlay Online Communications“Overlay” = 3 matches

“Karaoke” = 3 matches

VS.

Page 28: OpenStack Summit Austin - Split Brain (1)

Network Overlay Online Communications“VxLAN” = 16 matches

“beer” OR “bbq” = 16 matches

VS.

Page 29: OpenStack Summit Austin - Split Brain (1)

Network Overlay Online Communications“BGP” = 64 matches

“Keystone” = 65 matches

VS.

Page 30: OpenStack Summit Austin - Split Brain (1)
Page 31: OpenStack Summit Austin - Split Brain (1)
Page 32: OpenStack Summit Austin - Split Brain (1)