This document discusses digital transformation and the role of IT. It notes that digital IQ is dropping among executives and that technology and competitors are not waiting. It discusses how digital transformation is leading to more efficient, effective, reliable operations with greater velocity, agility, scale and reach. IT roles are blurring between business and technology functions. Innovation is imperative for businesses facing disruption. Security must be pervasive. Planning is needed for AI. Bimodal IT approaches are discussed as are the roles of the CIO and standardized vs cloud-native approaches. Multicloud is discussed as the new platform reality. Automation, DevOps, and digital operations are key parts of digital transformation.
4. DX CHANGE IS CONSTANT
TECHNOLOGY GEEKS
SERVICE PROVIDERS
BUSINESS “PARTNER”
BUSINESS SHAPERS
-1980s
90s-2000s
00s-2010s
TODAY
A brief history of highly effective IT
LINES BLUR BETWEEN IT AND BUSINESS
• IT leaders shape the future of the business innovation
• IT owns most of the customer experience
INNOVATION IS AN IMPERATIVE
• As disruption impacts every industry: The choice is in between predator or prey.
• Focus is on technology that is differentiating. Drab tech is kicked is SaaS
SECURITY IS A MUST
• More threatening than competitors, breaches are devastating
• Must be pervasive in culture, processes, applications and infrastructure
AI IS HIGHLY ANTICIPATED, AND NEEDS PLANNING
• Business plans for AI are well defined: 23%, Technology plans for AI: 20%*
• New levels of market, business, and operations awareness
THE STATE OF IT TODAY
* State of the IT 2017
5. DIGITAL IQ TODAY
Digital IQ sentiment is dropping
Only half of executives rate their Digital IQ strongly
Technology and competitors are
NOT WAITING
PWC’s Digital IQ survey ‘17
9. The mind of a CIO
PREDICTABILITY
(Smooth running IT team today)
FUTURE-PROOF
INNOVATION
(Strengthen and protect IT team for future)
ADD & ACCELERATE
BUSINESS VALUE
(Happy CEO & lines of business)
REDUCE TCO
(Happy CFO)
AGILE
STEADY
BUSINESSTECHNOLOGY
11. STANDARDIZE & CONSOLIDATE THE OLD
(and anything not business differentiated or advantageous)
+
CLOUD-FIRST & CLOUD-NATIVE THE NEW
(and refactor anything business differentiated or advantageous)
BIMODAL IT
it’s not about here or there… it is about
An at-scale computing platform for
• DevOps
• Digital Ops
• Internet of Things
• Big Data- and AI-driven Research and Insights
CLOUD
IS THE NEW COMPUTER
13. ENGINEERING. SIMPLICITY.
One Junos Self-driving Networks Contrail Enterprise Multicloud
SIMPLE IS A HUGE FEAT OF ENGINEERING.
SIMPLE IS HARDER THAN COMPLEX…
15. MULTICLOUD: REALITY, NOT A STRATEGY
AIMING FOR MULTICLOUD
AS THE INFRASTRCTURE IDEAL
State of the Cloud Survey ‘17
MULTIPLE AZs MULTIPLE ACCOUNTS MULTIPLE REGIONS MULTIPLE VENDORS
THE STRATEGY: HOW TO CHOOSE & CONSUME WISELY
85% ofenterprises
16. MULTICLOUD OVERVIEW
Clouds provide services and IaaS
(elastic programmable infrastructure)
1
Clouds are inter-connected2
Clouds run cloud-native app stacks3
1
2
3
----- IaaS abstraction -----
18. BUSINESS MOTIVATIONS FOR CLOUD CHOICE
Defn. HYBRID CLOUD:
Hybrid cloud spans at least one public and one private cloud
Better modern use: A unified platform that spans multiple clouds
HYBRID CLOUD IS THE NEW IT – WHY?
VENUE:
• Geography for reach, migration, compliance or sovereignty
• Cost advantages
• Feature advantages
RESILIENCE:
• Disaster recovery and avoidance site
• Active-active setups for high availability
AGILITY:
• Speed of abstracting away infrastructure for developers
• Circumvent challenges: budget, staff, experience
• Hardware & software innovation pace of hyper-scale clouds
FLEXIBILITY:
• Design split-tier applications for best of both worlds
• Lifecycle / environment for dev, test, staging, production
• Bursting (seasonal, occasional etc. spiky usage vs. steady usage)
19. LUCK FAVORS THE PREPARED
Hybrid cloud prepares enterprise IT by design for infinite scale and choice
HYBRID CLOUD IS THE NEW IT – WHY?
THE GOOD:
• Global infrastructure platform
• Ecosystem: Big Data, Machine Learning, IoT Platforms
• Economic flexibility and alignment with value
• Instant and elastic scale and failover possibilities
• YES! Security – expert SecOps in large clouds
THE BAD:
• No end of amortization – A perpetual investment
• Platform and data locality lock-in
• Aspects of unpredictability
PUBLIC CLOUD
THE GOOD:
• Control and compliance over location and systems
• Data sovereignty and locality
• Custom SLAs, platforms and hardware
• Trust for mission-critical workloads and security
THE BAD:
• Time and skill to build/maintain/scale the platform
• Reserves and CapEx beyond current needs
• Aspects of inflexibility
PRIVATE CLOUD
20. LUCK FAVORS THE PREPARED
Hybrid cloud prepares enterprise IT by design for infinite scale and choice
HYBRID CLOUD IS THE NEW IT – HOW?
THE GOOD:
• Global infrastructure platform
• Ecosystem: Big Data, Machine Learning, IoT Platforms
• Economic flexibility and alignment with value
• Instant and elastic scale
• YES! Security
THE BAD:
• No end of amortization – A perpetual investment
• Platform and data locality lock-in
• Unpredictable
PUBLIC CLOUD
THE GOOD:
• Control and compliance
• Data sovereignty and locality
• Custom SLAs, platforms and hardware
• Trust for mission-critical workloads and security
THE BAD:
• Time and skill to build and maintain the platform
• Reserves and CapEx beyond current needs
PRIVATE CLOUD
A HYBRID CLOUD UNIFIED PLATFORM REQUIRES SOME PARITY…
• Functionally compatible: APIs, infrastructure and platform primitives, config behavior
• Non-functionally compatible: availability, performance, QoS
• Economically compatible: no prohibitively drastic cost differences
21. HYBRID CLOUD PLATFORM
Unified Cloud Platform
• Application and DevOps pipeline portability and mobility
• Multicloud I&O management and orchestration
• Consistency and parity of core experience
• Economic optimization with flexibility
HYBRID CLOUD PLATFORM
Doing everything, all at once!
• Context switching efficiency loses
• Poor portability of DevOps automations and apps
• Cloud data and services lock-in
• Long-term management and cost control nightmare
DISPARATE PRIVATE + PUBLIC CLOUD
UNIFIED PLATFORM
VS.
23. WHY WE AUTOMATE
CONSISTENCY
Improve reliability
SPEED
The future belongs to the fast
SCALE
Optimized capacity for demand
BUSINESS
OUTCOMESINSTRUMENTATION
Handle complexity and improve human interaction
24. COEFFICIENTS OF AUTOMATION
space – API architecture and integration
time – continuous processes and X- as code
AGILE gitOps
aaS ARCHITECTURE DigitalOps
&
DevOps
25. “Google is living a few years in the future
and sending the rest of us a message”
- Doug Cutting
26. “Google is living a few years in the future
and sending the rest of us a message”
CI / CD / CR
MICROSERVICES ARCH.
& CONTAINERS
RELIABILITY ENGINEERING
& IaC
DEVOPS
27. CI / CD / CR
MICROSERVICES ARCH.
& CONTAINERS
RELIABILITY ENGINEERING
& IaC
DEVOPS
MORE APP DEVELOPER IMPACT
MORE INFRASTRUCTURE & OPS IMPACT
29. AGILE W/O MICROSERVICES MICROSERVICES W/O AGILE AGILE + MICROSERVICES
THE RIGHT ARCHITECTURE FOR AGILE
“A clumsy ninja” “Brilliantly bottlenecked” “Lean and mean”
30. Small Teams
Clean Interfaces
Innovation and Upgrade Velocity
Scale Out
Reusable Components
MICROSERVICES
Large applications are broken
down into small, loosely coupled
and composable autonomous
pieces packaged into containers
BENEFITS
MICRO-SERVICES (as containers)
BIG impact projects come from many SMALL teams and tasks
Fault Tolerance
32. Software-defined networking and security suite
for OpenStack, VMware, Mesos, OpenShift,
Kubernetes, NFV and SDWAN
High-performance, next-generation firewall for
securing virtualized and cloud environments.
Available in container technology as cSRX
Virtualized, full-featured, carrier-grade router.
Ideal for NFV environments, rapid service
introduction and cost-effective scale-out
JUNIPER’S SOFTWARE SIDE OF CLOUD
Intent-driven and AI platform for
infrastructure/network ops and management:
monitoring, analytics, and real-time response
optimizations
36. REVENUE GROWTH:
Raise your prices
Find more customers
Sell larger transactions
Sell more often
$OFTWARE-BASED GROWTH:
Price and transaction frequency:
• Recurring revenue for licenses and support
Average Sale Size:
• More services & integration than hardware
More customers:
• Sell for public & private cloud infrastructure
• Free trial or freemium conversions
• Easy reselling and value-add
• Right-size license counts per consumer or
other value metrics
Other business advantages:
• Rooted: can’t rip & replace API integrations
• Price disaggregation and flexibility
• Software is closer to the business value
37. SALES STRATEGIES
Add & accelerate value to the business
CUSTOMER’S
Top-of-mind
Application Innovation
drives business value, information and agility
Automation
drives IT agility, quality, speeds application
iteration and abstracts infrastructure
Hybrid cloud platform
enables automation, scale and flexibility
Business
Software
Hardware
IT VALUE CHAIN SALES INSERTIONS
Talk business needs, opportunities, lines
of business and finances
Talk app use cases, time to value,
developers/NoOps, legacy vs. containers
Talk Dev(Net)Ops, CI/CD, SDN,
integration services, simplicity and speed
Talk pub vs. prvt, lift & shift cases, scale,
orchestration platforms, SDN, security
(speeds and feeds…you’ve got it covered)…
Editor's Notes
Horses into unicorns
1. Hybrid and Multi cloud: Achieving evolvability without cloud vendor lock-in
2. DevOps: Better together with cloud and micro-services
3. The future of network automation: DevNetOps for SDN and Data Centers
- The theme is the evolution of automation in security and networking as pertains to cloud and data centers
4. Juniper Solution: Cloud interconnection and Transit VPCs
5. Juniper Solution: Multi-cloud portable cloud-native stacks with Kubernetes and OpenShift
Geeks phase was a DX from analog to digital
SP phase was a DX to the digital workforce (client and server computing)
Business partner phase was DX was the IT department enabling web, mobile, data mining, search and some cloud
Business shaper phase DX is software-defined business functions, GTM, and offerings
DevOps > Deploy more often and better quality > speed business outcomes
Digital Ops > Automation processes with software > happier more efficient
Transformation vs functional vs strategic role of the CIO
PWC’s latest survey, which polled 2,216 executives at companies with annual revenue of more than $500 million, found executives’ confidence in their organization’s digital abilities is actually at the lowest it has been since we started tracking. Just 52% of executives rated their Digital IQ as strong, down 15% from the year before.
4-3-2-1
4:Harder-Better-Faster-Stronger
3:Mind of a CIO: Functional, transformation, strategic
2: bimodal IT: Mode 1 and mode2
1: Juniper: engineering simplicity
Functional vs Transformational vs Strategic role of the CIO
Along with predictability – standardization and consolidation
4-3-2-1
4:Harder-Better-Faster-Stronger
3:Mind of a CIO: Functional, transformation, strategic
2: bimodal IT: Mode 1 and mode2
1: Juniper: engineering simplicity
4-3-2-1
4:Harder-Better-Faster-Stronger
3:Mind of a CIO: Functional, transformation, strategic
2: bimodal IT: Mode 1 and mode2
1: Juniper: engineering simplicity
More Examples: Qfabric, Junos Space Platform, JSA subscription pricing, Universal chassis, Contrail Enterprise Multicloud, Contrail SDWAN and subscription pricing
WISELY? =
Add and accelerate revenue
Lower TCO
Futureproof, protect against lock-in and lock-out
Standardize and consolidate, lest things get unwieldly and prevent 1-3
+3 clouds can also run *some* legacy applications
Personally, I related to hybrid cloud like my credit cards. They give me the elasticity to buy whatever I need on credit margin rather than saving. It can be a lifesaver in an emergency. For a businesses, not buying, but rather investing, elasticity is crucial to business agility to seize a business opportunity.
On “YES! Security”… Gone are the notions that systems are secure because they are within the Enterprise walls. Public cloud companies have some of the best security talent on the planet. Just like private SecOps, it is dependent on how it’s used.
While you want to get as close as possible to parity, private and public clouds will not be homogenous in all respects, and actually this diversity, like in biology is a good protection in cases of failure. Eventually a private cloud or public cloud or a part of it may fail, and at that time it is very useful to be able to fail over to another cloud provided that there is capacity – not always possible if private clouds run at 100% capacity, but there are probably more than one public clouds out there suitable.
Modelling the unicorns
Consistency and correctness implied
API Archttecture =
X aaS = everything is an API and service – generally composed of microservices
X as Code = everything is programmable and everything follows sw dev patterns
Continuous processes = everything is orchestrated on a pipeline for speed, consistency (quality) and instrumented for real-time continuous response and optimization
Continuous integration > delivery > deployment > response
Microservice = perfect match for nimble agile process where many step steps are favored
Original use: http://www.zdnet.com/article/hadoop-creator-google-is-living-a-few-years-in-the-future-and-sending-the-rest-of-us-messages/
DevOps and CI/CD have gained popular adoption, but Google technology and practices like K8s and SRE are largely making this much easier than, for example, trying to follow in the footsteps of Netflix
1. Quick and clumsy; 2. Rushing into a bottleneck; 3. The micro-services bullets of an agile chamber
Small teams that don’t incur the n-squared collaboration overhead to highly like large teams (see Jeff Bezos’s 2-pizza rule)
Clean interfaces created with APIs in this case isolate internal changes from the total system integration
Innovation and Upgrade Velocity because teams can innovate in parallel and upgrade their component without affecting the whole system
Reusable components that specialize in one task (like the Unix philosophy) are often reusable in many bigger solutions and help portability and avoid lock-in
Scale out architectures are built on the divide and conquer premise that micro-services being all equally small and thin tasks can be replicated many times across many machines to meet elastic scale requirements instead of feeding a given task more memory and CPU and getting to get bulkier instances
Fault tolerance comes from the scale out model whereby a micro-service replicated many times represents a function, and with the failure of any instance, the function as a whole is still up and running
+ others considerations: Dependency injection and service discovery
Original use: http://www.zdnet.com/article/hadoop-creator-google-is-living-a-few-years-in-the-future-and-sending-the-rest-of-us-messages/
frequent transactions <= licensed for recurring revenues
Raise average sale size <= more services and integration than hardware
More customers <= easier to resell with channels, give free trials, right-size per consumer or value metric