Weitere ähnliche Inhalte Ähnlich wie What the business thinks about (20) Mehr von DevOps4Networks (6) Kürzlich hochgeladen (20) What the business thinks about1. DevOps4Networks Lightning Talk
What the Business Thinks
Nathan Sowatskey
SDN and Network Programming Lead DevNet
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 1
2. Nathan Sowatskey
• Currently SDN and Network
Programming Lead DevNet
• With Cisco since 2000, 10+ years as
technical leader in core software
groups
• Last 2-3 years TME for SDN and
Network Programming
• Decades of software development
experience
• http://es.linkedin.com/in/nathansowatsk
ey
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 2
3. What the Business Thinks
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
4. “When do we want it?
…
NOW!*”
The business
*Or a week/month/year ago …
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
5. “Everything that can be
automated will be
automated.”
In the Age of the Smart Machine: The Future of Work and Power
Shoshana Zuboff - http://en.wikipedia.org/wiki/Shoshana_Zuboff
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 5
6. “We need “SDN”.”
A typical conversation
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
7. “We need “SDN”.”
“Why? What for?”
A typical conversation
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
8. “We need “SDN”.”
“Why? What for?”
“I don’t know! Because we have
funding for “SDN”?”
A typical conversation
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
9. “Open*, SDN, *Flow, APIs,
DevOps, Python, Scripts, SDKs,
Controllers, ACI, OSS,
Orchestration ….“
A typical conversation
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
10. “Open*, SDN, *Flow, APIs,
DevOps, Python, Scripts, SDKs,
Controllers, ACI, OSS,
Orchestration ….“
“Whatever, I just want it
automated”
A typical conversation
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 10
11. Why Automation?
12
10
8
6
4
2
0
Low
Automation
Medium
Automation
High
Automation
Full
Automation
Various: http://www.methodsandtools.com/archive/archive.php?id=94,
http://www.infoq.com/articles/test-automation-continuous-delivery,
http://devopsanywhere.blogspot.com/2013/02/sysadmin-productivity-and-chef.
html
$ Cost
Quality
Productivity
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 11
12. OS and Sys Admins Did It
First - DevOps
A change from manually configuring every
server, operating system, and virtual
machine to operating a nimble set of
infrastructure at scale
1 Server Admin : 100-200 Servers
to
1 Server Admin : 5,000 – 10,000 Servers
CLI + Bash scripts + Reactive configuration
to
Orchestrated configuration and integration
with development
Network Operations
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 12
13. So why can’t the
networking dudes do
this?
• Practically anyone you ask in IT
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
14. If we automate, will I
still have a job?
• Practically anyone you ask in networking
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 14
15. We have been here
before – plus ça
change
Automation is not new … what’s new is that the business can’t afford
NOT to automate
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
16. “Buying a new switch costs
thousands.
A typical customer
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 16
17. “Buying a new switch costs
thousands.
Changing an OSS costs millions.
A typical customer
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 17
18. “Buying a new switch costs
thousands.
Changing an OSS costs millions.
What am I going to optimise for?”
A typical customer
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
19. “A consistent API would be great!
A typical customer
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 19
20. “A consistent API would be great!
I can cope with two APIs.
A typical customer
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 20
21. “A consistent API would be great!
I can cope with two APIs.
What I can’t work with is NO
APIs.”
A typical customer
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
22. Before and After APIs and Automation
Do you support RFCnnnn?
What is your cost/port?
Do you have my favourite CLI
dongle?
Have you fixed that bug in IOS?
Is XYZ feature supported on all
platforms in the same way?
Do you have an API for that?
Do you support my DevOps
framework and/or programming
language?
Can I configure that via an API?
Have you fixed the bug in that
API/Plugin?
Is this API/Plugin available
across all platforms
consistently?
© 2013-2014 Cisco and/or its affiliates. All rights reserved. Cisco Public 22
Hinweis der Redaktion DevOps is a methodology and mindset of combining the efforts of the operations team with development. This is a means automating servers and operating systems in conjunction with development efforts, and programming all repeatable tasks. This results in higher consistency with development, less fires to fight, and a faster development cycle with less back-outs and stalls.
For us networking folk, this is good and bad news. The good news is they have a large tool set and experience doing this, and there are a lot of shared components for us to work with. Unfortunately this also can accelerate the requirement of network programmability, and even potentially cause a false sense of confidence with a different domain. In order for Network Operations to truly integrate with DevOps it will take people from both sides to collaborate and share experience. This is where it’s critical to ‘know the language’.