evolvable architecture…
FOR HYBRID MULTICLOUD
...with SDN
PRESENTERS
James Kelly
Lead Cloud Architect
Juniper Networks
• Engineer
• Marketer
• Continual Learner
DX IN 2018
SuperOps?
DX = CONTINUOUS IMPROVEMENT
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
today’s STATE of IT
* SFDC State of IT 2017
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
EFFECTIVE
RELIABLE
VELOCITY, AGILITY,
SCALE, REACH
EFFICIENT
DIGITAL OPS,
DEVOPS,
PUBLIC CLOUD, IoT
SECURITY,
SRE
EXPERIMENTATION,
BIG DATA, AI
TCO,
OPEN SOURCE
FASTER
STRONGER
HARDER
BETTER
FUNCTIONAL
STRATEGIC
TRANSFORMATIVE
MODE 1
MODE 2
DX Role of the CIO Bimodal IT ?
FASTER
STRONGER
HARDER
BETTER
FUNCTIONAL
STRATEGIC
TRANSFORMATIVE
MODE 1
MODE 2
DX Role of the CIO Bimodal IT ?
FASTER
STRONGER
HARDER
BETTER
FUNCTIONAL
STRATEGIC
TRANSFORMATIVE
MODE 1
MODE 2
DX Role of the CIO Bimodal IT
WINSIMPLICITY
MULTICLOUD
IS THE PLATFORM
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
MULTICLOUD ENTERPRISE END-TO-END
MULTICLOUD REACHES END-TO-END
Enterprises are rooted where staff, customers, products, and services are Public and Hybrid cloud are multicloud
Data Centers / Private Cloud
Branch / Remote
Campus / HQ
SaaS Public Cloud
Public Cloud
Private / Public WAN
MULTICLOUD TOP-TO-BOTTOM
Clouds provide services and IaaS
(elastic programmable infrastructure)
1
Clouds are inter-connected2
Clouds run cloud-native app stacks3
1
2
3
----- IaaS abstraction -----
WHAT IS IT?
WHAT ABOUT HYBRID CLOUD
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 – 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)
LUCK FAVORS THE PREPARED
Hybrid cloud prepares enterprise IT by design for infinite scale and choice
HYBRID CLOUD – BEST OF BOTH WORLDS
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
EVOLVABLE
HYBRID MULTICLOUD
MULTICLOUD IS THE NEW IT – HOW?
FOR A MULTICLOUD UNIFIED PLATFORM, PARITY = PORTABILITY
• Functionally compatible: APIs, infrastructure and platform primitives, config behavior
• Non-functionally compatible: availability, performance, QoS
• Economically compatible: no prohibitively drastic cost differences
MULTICLOUD 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 MULTI, PRIVATE, PUBLIC CLOUD
UNIFIED PLATFORM
VS.
SEPARATION OF CONCERNS
- layers not silos –
• App Engineering
• Platform Engineering
• DevOps Pipeline Engineering
• Cluster Ops and SRE
• IaaS EngOps: Network, Security, Storage, VMs & Metal
SECURE,
AUTOMATED
MULTICLOUD OPS
LAYERS… SPAN MULTICLOUD
APP ENGINEERING
PLATFORM ENGINEERING
DEVOPS PIPELINE ENGINEERING
CLUSTER OPS / SRE
IaaS I&O ENGINEERING
MULTICLOUD EVOLVABLE ARCHITECTURE
MULTICLOUD-READY apps and platform
• Services as a Platform SaaP is sticky. Easy but not portable.
(e.g. SaaP = plethora of AWS services, or those of many public clouds)
• Don’t use custom cloud services when you can BYO
(e.g. API gateway, auth, DB, message queue, etc.)
• Easier BYO packages and portability with tools like K8s Helm
• Find multi-cloud shims like Minio for S3-like obj. storage
• Avoid API lock-in: OSS-based managed services if can’t BYO
(e.g. Managed MySQL, Kafka, etc.)
• Else, lock-in for business advantage of unique offerings
APP ENGINEERING
PLATFORM ENGINEERING
DEVOPS PIPELINE ENGINEERING
CLUSTER OPS / SRE
IaaS I&O ENGINEERING
MULTICLOUD EVOLVABLE ARCHITECTURE
MULTICLOUD-READY DevOps
• SaaP example: AWS CodeStar not portable
• Portable examples: Jenkins, Spinnaker
General guide:
• CI/CD and gitOps: test automation, deployment pipeline as code
• Consistency between environments: Dev/Test, Staging and Production
What about SDN?
• If you have different IPAM, DNS, Policy, LB, etc. in staging vs. prod
…then you break consistency between environments!
• Ensure the same setups between environments
• Need SDN + DevNetOps – SDN as code, and then SDN CI/CD
• Make this simple or invisible for app and platform engineering
• Multi-tenant/env. SDN makes this easy, instead of one SDN per env.
APP ENGINEERING
PLATFORM ENGINEERING
DEVOPS PIPELINE ENGINEERING
CLUSTER OPS / SRE
IaaS I&O ENGINEERING
MULTICLOUD EVOLVABLE ARCHITECTURE
MULTICLOUD-READY Cluster Ops
• SaaP example: GAE, ECS, etc. not portable
• Portable examples: Kubernetes, Mesos, Nomad, OpenShift…
General guide:
• Clusters aaS: Avoid lock-in using OSS managed services if can’t BYO
• KaaS with serverless containers: better value; Pod = multicloud standard
• Cluster lifecycle (as code): Avoid DSLs by using Terraform or multicloud
shims to setup and scale clusters
What about SDN (with Kubernetes)?
• Multi-tenant/env. SDN makes multi-use/project clusters much simpler
• InfoSec as code: Some SDN security policies, tenant isolation, etc.
• Much variance in KaaS networking/GLB/NLB is unified in some SDNs
that implement Service type: LoadBalancer and Ingress
APP ENGINEERING
PLATFORM ENGINEERING
DEVOPS PIPELINE ENGINEERING
CLUSTER OPS / SRE
IaaS I&O ENGINEERING
PROOF YOU CAN DO IT
MULTICLOUD EVOLVABLE ARCHITECTURE
MULTICLOUD-READY I&O Engineering
• Physical infrastructure itself isn’t portable, but…
General guide:
• IaaS shims make portable automation: Terraform, Minio, Digital Rebar,
• Some primitives and APIs are more portable than others: image formats,
object storage, volumes, networks, firewalls, base OS, auth, etc.
• Artifacts and config as code for software-defined and physical systems
• Copy production environment data into staging for realistic testing
What about SDN?
• Overlays provide separation of concerns and network/security isolation
• Multitenancy is required because of many projects to support
• Choose SDNs for any underlay: physical IP network or cloud IP network
• Choose SDNs that integrate with many orchestration systems
APP ENGINEERING
PLATFORM ENGINEERING
DEVOPS PIPELINE ENGINEERING
CLUSTER OPS / SRE
IaaS I&O ENGINEERING
“IT IS NOT THE STRONGEST
OF THE SPECIES THAT SURVIVE
NOR THE MOST INTELLIGENT
BUT THE ONE
MOST RESPONSIVE TO CHANGE
- Charles Darwin
EVOLUTION IS A GROWTH MINDSET
AGILITY IS THE ABILITY TO ADAPT
The future belongs to the fast!
and agile
Evolvable architecture for hybrid multicloud with sdn

Evolvable architecture for hybrid multicloud with sdn

  • 1.
  • 2.
    PRESENTERS James Kelly Lead CloudArchitect Juniper Networks • Engineer • Marketer • Continual Learner
  • 3.
  • 4.
    DX = CONTINUOUSIMPROVEMENT 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 today’s STATE of IT * SFDC State of IT 2017
  • 5.
    DIGITAL IQ TODAY DigitalIQ sentiment is dropping Only half of executives rate their Digital IQ strongly Technology and competitors are NOT WAITING PWC’s Digital IQ survey ‘17
  • 6.
    EFFECTIVE RELIABLE VELOCITY, AGILITY, SCALE, REACH EFFICIENT DIGITALOPS, DEVOPS, PUBLIC CLOUD, IoT SECURITY, SRE EXPERIMENTATION, BIG DATA, AI TCO, OPEN SOURCE
  • 7.
  • 8.
  • 9.
  • 10.
  • 11.
  • 12.
    MULTICLOUD: REALITY, NOTA 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
  • 13.
    MULTICLOUD ENTERPRISE END-TO-END MULTICLOUDREACHES END-TO-END Enterprises are rooted where staff, customers, products, and services are Public and Hybrid cloud are multicloud Data Centers / Private Cloud Branch / Remote Campus / HQ SaaS Public Cloud Public Cloud Private / Public WAN
  • 14.
    MULTICLOUD TOP-TO-BOTTOM Clouds provideservices and IaaS (elastic programmable infrastructure) 1 Clouds are inter-connected2 Clouds run cloud-native app stacks3 1 2 3 ----- IaaS abstraction -----
  • 15.
    WHAT IS IT? WHATABOUT HYBRID CLOUD
  • 16.
    BUSINESS MOTIVATIONS FORCLOUD 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 – 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)
  • 17.
    LUCK FAVORS THEPREPARED Hybrid cloud prepares enterprise IT by design for infinite scale and choice HYBRID CLOUD – BEST OF BOTH WORLDS 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
  • 18.
  • 19.
    MULTICLOUD IS THENEW IT – HOW? FOR A MULTICLOUD UNIFIED PLATFORM, PARITY = PORTABILITY • Functionally compatible: APIs, infrastructure and platform primitives, config behavior • Non-functionally compatible: availability, performance, QoS • Economically compatible: no prohibitively drastic cost differences
  • 20.
    MULTICLOUD PLATFORM Unified CloudPlatform • 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 MULTI, PRIVATE, PUBLIC CLOUD UNIFIED PLATFORM VS.
  • 21.
    SEPARATION OF CONCERNS -layers not silos – • App Engineering • Platform Engineering • DevOps Pipeline Engineering • Cluster Ops and SRE • IaaS EngOps: Network, Security, Storage, VMs & Metal
  • 22.
  • 23.
    LAYERS… SPAN MULTICLOUD APPENGINEERING PLATFORM ENGINEERING DEVOPS PIPELINE ENGINEERING CLUSTER OPS / SRE IaaS I&O ENGINEERING
  • 24.
    MULTICLOUD EVOLVABLE ARCHITECTURE MULTICLOUD-READYapps and platform • Services as a Platform SaaP is sticky. Easy but not portable. (e.g. SaaP = plethora of AWS services, or those of many public clouds) • Don’t use custom cloud services when you can BYO (e.g. API gateway, auth, DB, message queue, etc.) • Easier BYO packages and portability with tools like K8s Helm • Find multi-cloud shims like Minio for S3-like obj. storage • Avoid API lock-in: OSS-based managed services if can’t BYO (e.g. Managed MySQL, Kafka, etc.) • Else, lock-in for business advantage of unique offerings APP ENGINEERING PLATFORM ENGINEERING DEVOPS PIPELINE ENGINEERING CLUSTER OPS / SRE IaaS I&O ENGINEERING
  • 25.
    MULTICLOUD EVOLVABLE ARCHITECTURE MULTICLOUD-READYDevOps • SaaP example: AWS CodeStar not portable • Portable examples: Jenkins, Spinnaker General guide: • CI/CD and gitOps: test automation, deployment pipeline as code • Consistency between environments: Dev/Test, Staging and Production What about SDN? • If you have different IPAM, DNS, Policy, LB, etc. in staging vs. prod …then you break consistency between environments! • Ensure the same setups between environments • Need SDN + DevNetOps – SDN as code, and then SDN CI/CD • Make this simple or invisible for app and platform engineering • Multi-tenant/env. SDN makes this easy, instead of one SDN per env. APP ENGINEERING PLATFORM ENGINEERING DEVOPS PIPELINE ENGINEERING CLUSTER OPS / SRE IaaS I&O ENGINEERING
  • 26.
    MULTICLOUD EVOLVABLE ARCHITECTURE MULTICLOUD-READYCluster Ops • SaaP example: GAE, ECS, etc. not portable • Portable examples: Kubernetes, Mesos, Nomad, OpenShift… General guide: • Clusters aaS: Avoid lock-in using OSS managed services if can’t BYO • KaaS with serverless containers: better value; Pod = multicloud standard • Cluster lifecycle (as code): Avoid DSLs by using Terraform or multicloud shims to setup and scale clusters What about SDN (with Kubernetes)? • Multi-tenant/env. SDN makes multi-use/project clusters much simpler • InfoSec as code: Some SDN security policies, tenant isolation, etc. • Much variance in KaaS networking/GLB/NLB is unified in some SDNs that implement Service type: LoadBalancer and Ingress APP ENGINEERING PLATFORM ENGINEERING DEVOPS PIPELINE ENGINEERING CLUSTER OPS / SRE IaaS I&O ENGINEERING
  • 27.
  • 28.
    MULTICLOUD EVOLVABLE ARCHITECTURE MULTICLOUD-READYI&O Engineering • Physical infrastructure itself isn’t portable, but… General guide: • IaaS shims make portable automation: Terraform, Minio, Digital Rebar, • Some primitives and APIs are more portable than others: image formats, object storage, volumes, networks, firewalls, base OS, auth, etc. • Artifacts and config as code for software-defined and physical systems • Copy production environment data into staging for realistic testing What about SDN? • Overlays provide separation of concerns and network/security isolation • Multitenancy is required because of many projects to support • Choose SDNs for any underlay: physical IP network or cloud IP network • Choose SDNs that integrate with many orchestration systems APP ENGINEERING PLATFORM ENGINEERING DEVOPS PIPELINE ENGINEERING CLUSTER OPS / SRE IaaS I&O ENGINEERING
  • 29.
    “IT IS NOTTHE STRONGEST OF THE SPECIES THAT SURVIVE NOR THE MOST INTELLIGENT BUT THE ONE MOST RESPONSIVE TO CHANGE - Charles Darwin
  • 30.
    EVOLUTION IS AGROWTH MINDSET AGILITY IS THE ABILITY TO ADAPT The future belongs to the fast! and agile