Operationalize the network to affect positive cultural change across IT silos to accelerate time to market because the second place is the first loser in an application world.

1. Operationalize all the
NETWORK things
Lori MacVittie
Principal Technical Evangelist @ F5 Networks
@lmacvittie

2. About Lori
Developer Lori
• 9 years software
development
– Enterprise architecture
– Telecom
– ISVs
• 21 years coding
– LAMP FTW
Networking Lori
• 6 years Network Computing
Test Lab
– Networking
– Security
– Integration and Middleware
• 8 years F5 Networks
– Technical Marketing
– Evangelism
M.S. Computer Science

3. Time to market
is the new measure of success

4. That’s why orgs are changing
32
PERCENT
41
PERCENT
chose Agile to
accelerate time to market
chose DevOps to
accelerate time to market
Sources: Version One, 8th Annual State of Agile. CA, What Smart Businesses Know About DevOps.

5. Notice something missing?
Dev Ops
?

6. The network is in the way
of IT professionals surveyed say that once an
application completes the dev process, it takes
a week or more to move into production; for
14% of those, it’s a month or more. 43
PERCENT
Organizations citing biggest challenge
to application deployments is time to
provision network services. 44
PERCENT
Data: InformationWeek 2014 DevOps Survey, ESG

7. Why is the network in the way?
24% 22% 16% 12%
CHANGES CAUSE
SERVICE
DISRUPTION
NETWORK
CHANGES ARE
SLOW
HARD TO
MANAGE
CHANGES TO THE
NETWORK
APPLICATION
CHANGES
REQUIRE
NETWORK
CHANGES
Source: IDC's Why the Network Matters Survey

8. because traditional methods
Scaling, provisioning and
management are realized
device by device, system by
system
Error prone Time consuming
Difficult to
troubleshoot

9. are not speedy, safe or scalable
Small Biz Med Biz Large Ent
Computer Economics 2014
Average computing devices
connected to networks
Desktop Laptop
Smartphone Tablet
25,180
Data Breach: The Cloud Multiplier Effect Ponemon, June 2014
Median device to engineer ratio

10. Change with Devops for the Network
Dev Ops Network

11. Isn’t DevOps Dev and Ops?

12. Security Network “Operations” Storage
O P E R AT I O N S
Net + Ops Has Same Issues as Dev + Ops

13. IT has Turret Syndrome
• Groups don’t collaborate well
• Group success is measured
on different metrics
• Handoffs between groups
are awkward and cause
bottlenecks
• Processes are inefficient and
burdened by a tower/silo
mentality (even within silos)

14. Operationalize
People collaborating and using
Programmability to optimize the
Processes necessary to meet business
Priorities
SHARING
AUTOMATION
MEASUREMENT

15. … all the network things
ADC
Local
Load
Balancing
Router Switch
Firewall
STATEFUL
LAYER 4-7
STATELESS
LAYER 2-4
Application
Security
Identity and
Access
DDoS
Protectio
n
Global
Load
Balancing
Application
Performance
Secure Web
Gateway
Malware
Detection
Application
Proxies

16. Align all the priority things
Value of IT to the business
IT contribution to strategy
Customer satisfaction
Innovative new ideas
Availability
Projects delivered on time
IT cost controls
Productivity improvement
Business cost controls
Revenue growth
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Top 10
CIO Priorities
Business Concerns
IT Concerns

17. Measure all deployment things
Measurements often associated with DevOps:
• Deploy frequency
• Volume of defects
• MTTR
• Number & Frequency of outages
• Number & Frequency of performance issues
• Time/cost per release (deployment)

18. Automate all the network things
MEASURES IMPACTED
• Time/cost per release (deployment)
• Volume of defects
• Number & Frequency of outages

19. Optimize all the process things
MEASURES IMPACTED
• Deploy frequency
• MTTR
• Time/cost per release (deployment)
Remember .. automating poor processes accelerates the rate of failure

20. Add some Dev to Your (Net) Ops
TRADITIONAL DEV (OPS)
• Months / waterfall
• Manual configuration
• Product manuals
• Minutes / agile
• Programmability / API’s
• Developer community

21. ALL
API-Enabled
infrastructure
is somewhat
or very
important
40
PERCENT
57
PERCENT
71
PERCENT
Need to Code Score: 5
OF THOSE WHO SAY SDN WILL IMPACT THEIR ORG
OF THOSE WHO SAY DEVOPS WILL IMPACT THEIR ORG
SOURCE: F5 State of Application Delivery, 2014

22. Operations
CONFIGURE VLAN
SET UP ROUTE
ADD A SNAT
MAKE A POOL
MAKE A NODE
MAKE A MEMBER
ADD MEMBER TO POOL
CONFIGURE VLAN
SET UP ROUTE
ADD A SNAT
MAKE A POOL
MAKE A NODE
MAKE A MEMBER
ADD MEMBER TO POOL
CONFIGURE VLAN
SET UP ROUTE
ADD APP POLICY
CONFIGURE LOG
CONNECT IDENTITY STORE
DEFINE GROUPS
ACTIVATE POLICY
BEFORE APIs

23. AFTER APIs
Operations
CONFIGURE VLAN
SET UP ROUTE
ADD A SNAT
MAKE A POOL
MAKE A NODE
MAKE A MEMBER
ADD MEMBER TO POOL
CONFIGURE VLAN
SET UP ROUTE
ADD APP POLICY
CONFIGURE LOG
CONNECT IDENTITY STORE
DEFINE GROUPS
ACTIVATE POLICY
CONFIGURE VLAN
SET UP ROUTE
ADD A SNAT
MAKE A POOL
MAKE A NODE
MAKE A MEMBER
ADD MEMBER TO POOL

24. TOOLS and FRAMEWORKS USING APIs to AUTOMATE

25. OF THOSE WHO SAY DEVOPS WILL IMPACT THEIR ORG
ALL
OF THOSE WHO SAY SDN WILL IMPACT THEIR ORG
Data path
programmability
is somewhat or
very important
42
PERCENT
51
PERCENT
100
PERCENT
Need to Code Score: 10
SOURCE: F5 State of Application Delivery, 2014

26. Programmability “in the network”
SDN APPS
DATA PATH Routing &
Switching
Data path CONTROL PLANE
programmability
enabled by SDN apps
that extend an SDN
controller
Data path
programmability enabled
by network services
directly
Performance Access and
Identity
Availability Security Mobility

27. ALL
App Templates
are somewhat or
very important
33
PERCENT
51
PERCENT
52
PERCENT
Need to Code Score: 0-2
OF THOSE WHO SAY SDN WILL IMPACT THEIR ORG
OF THOSE WHO SAY DEVOPS WILL IMPACT THEIR ORG
SOURCE: F5 State of Application Delivery, 2014

28. App Templates vs Feature-driven APIs

29. App Templates
ANSIBLE Vagrant
Template –like systems

30. Operationalizing all the network things
People collaborating and using
Programmability to optimize the
Processes necessary to meet business
Priorities
SHARING
AUTOMATION
MEASUREMENT

31. Operationalize all the
NETWORK things
Lori MacVittie
Principal Technical Evangelist @ F5 Networks
@lmacvittie