WHY OPEN INFRASTRUCTURE MATTERS HELLO! My name is Thierry Carrez - - PowerPoint PPT Presentation

▶
why open infrastructure matters hello
SMART_READER_LITE
LIVE PREVIEW

WHY OPEN INFRASTRUCTURE MATTERS HELLO! My name is Thierry Carrez - - PowerPoint PPT Presentation

May 16, 2023 335 likes •1.09k views

WHY OPEN INFRASTRUCTURE MATTERS HELLO! My name is Thierry Carrez I work for the OpenStack Foundation I am tcarrez on Twitter And ttx on Freenode IRC 0. A PARADOX Is free software really free DEVELOPMENT INFRASTRUCTURE DEVELOPMENT

slide-1
SLIDE 1

WHY OPEN INFRASTRUCTURE MATTERS

slide-2
SLIDE 2

HELLO!

My name is Thierry Carrez I work for the OpenStack Foundation I am tcarrez on Twitter And ttx on Freenode IRC

slide-3
SLIDE 3

0. A PARADOX

Is free software really free

slide-4
SLIDE 4

DEVELOPMENT INFRASTRUCTURE

slide-5
SLIDE 5

DEVELOPMENT INFRASTRUCTURE

╺ Proprietary operating systems (OS/X)

slide-6
SLIDE 6

DEVELOPMENT INFRASTRUCTURE

╺ Proprietary operating systems (OS/X) ╺ Proprietary services (GitHub)

slide-7
SLIDE 7

DEVELOPMENT INFRASTRUCTURE

╺ Proprietary operating systems (OS/X) ╺ Proprietary services (GitHub) ╺ “Free software needs free tools” (Benjamin Mako Hill)

slide-8
SLIDE 8

RUNTIME INFRASTRUCTURE

slide-9
SLIDE 9

RUNTIME INFRASTRUCTURE

╺ Proprietary services (Amazon Web Services)

slide-10
SLIDE 10

RUNTIME INFRASTRUCTURE

╺ Proprietary services (Amazon Web Services) ╺ Open infrastructure

slide-11
SLIDE 11

1. INFRASTRUCTURE

Application deployers want programmable infrastructure

slide-12
SLIDE 12

PILING UP ABSTRACTIONS

slide-13
SLIDE 13

Market pressure Commoditizing the lower layers

PILING UP ABSTRACTIONS

slide-14
SLIDE 14

Market pressure Commoditizing the lower layers

PILING UP ABSTRACTIONS

Developers pressure Abstracting differences between lower layers

slide-15
SLIDE 15

Users Applications

slide-16
SLIDE 16

Physical hardware Users

slide-17
SLIDE 17

Physical hardware Users Application developers & deployers

slide-18
SLIDE 18

Physical hardware Users Hardware virtualization Application developers & deployers

slide-19
SLIDE 19

Physical hardware Users Hardware virtualization IaaS APIs Application developers & deployers

slide-20
SLIDE 20

Physical hardware Users Hardware virtualization IaaS APIs Application deployment APIs Application developers & deployers

slide-21
SLIDE 21

INFRASTRUCTURE EVOLUTION

slide-22
SLIDE 22

INFRASTRUCTURE EVOLUTION

╺ Caring less and less about infrastructure

slide-23
SLIDE 23

INFRASTRUCTURE EVOLUTION

╺ Caring less and less about infrastructure ╺ Commoditizing hardware: scale out vs. scale up

slide-24
SLIDE 24

INFRASTRUCTURE EVOLUTION

╺ Caring less and less about infrastructure ╺ Commoditizing hardware: scale out vs. scale up ╺ Commoditizing runtime envs: cattle vs. pets

slide-25
SLIDE 25

INFRASTRUCTURE EVOLUTION

╺ Caring less and less about infrastructure ╺ Commoditizing hardware: scale out vs. scale up ╺ Commoditizing runtime envs: cattle vs. pets ╺ VMs, containers, functions… this is not over

slide-26
SLIDE 26

INFRASTRUCTURE EVOLUTION

╺ Caring less and less about infrastructure ╺ Commoditizing hardware: scale out vs. scale up ╺ Commoditizing runtime envs: cattle vs. pets ╺ VMs, containers, functions… this is not over ╺ More software, less hardware

slide-27
SLIDE 27

Physical hardware Users Application developers & deployers

slide-28
SLIDE 28

Physical hardware Users Hardware virtualization Application developers & deployers

slide-29
SLIDE 29

Physical hardware Users Hardware virtualization IaaS APIs Application developers & deployers

slide-30
SLIDE 30

Physical hardware Users Hardware virtualization IaaS APIs Application deployment APIs Application developers & deployers

slide-31
SLIDE 31

Users Application developers & deployers Infrastructure providers

slide-32
SLIDE 32

Infrastructure providers

slide-33
SLIDE 33

2. OPEN

Providing infrastructure using open source components

slide-34
SLIDE 34

AVAILABILITY

Lack of barrier to trying out the software with all of its functionality. Absence of friction in transitioning from experimentation to production.

slide-35
SLIDE 35

SUSTAINABILITY

Existence of a multi-vendor market able to provide maintenance services over the software, making the choice of a given

  • rganization to use the software less

dependent on the health of the software vendor, and limiting the risk of lock-in.

slide-36
SLIDE 36

FLUID JOB MARKET

Easy identification of potential recruits based

  • n the open record of their contributions to

the technology they are interested in. Easily evaluation of recruiting organizations based on the open source technologies they are using.

slide-37
SLIDE 37

TRANSPARENCY

Ability to look under the hood and understand how the software works, or why it behaves the way it does. Increases your speed in reacting to unexpected behavior or failures.

slide-38
SLIDE 38

SELF-SERVICE

Ability to find and fix issues by yourself, without even depending on a vendor. That further increases your speed in reacting to unexpected behavior or failures.

slide-39
SLIDE 39

INFLUENCEABILITY

Possibility to engage in the community developing the software, and to influence its direction by contributing directly to it. Organizations that engage in the open source communities can make sure the software adapts to future needs by growing the features they will need tomorrow.

slide-40
SLIDE 40

OPEN SOURCE BENEFITS

  • Availability
  • Sustainability
  • Fluid job market
  • Transparency
  • Self-service
  • Influenceability
slide-41
SLIDE 41

3. THE THREE Cs

Capabilities, Compliance and Cost

slide-42
SLIDE 42

CAPABILITIES

One size does not fit all. Some features are just overpriced (GPUs). Some features are just missing.

slide-43
SLIDE 43

COMPLIANCE

Legal requirements around data locality. Confidentiality around strategic companies.

slide-44
SLIDE 44

COST

If you are interested by private infrastructure,

  • pen infrastructure will keep the price low.

And if you want to provide public infrastructure, you should not start from scratch.

slide-45
SLIDE 45

4. INTEROPERABILITY

Facilitating hybrid cloud scenarios

slide-46
SLIDE 46

Cost per CPU core Number of cores

slide-47
SLIDE 47

Cost per CPU core Number of cores Public cloud pricing

slide-48
SLIDE 48

Cost per CPU core Number of cores Private cloud

slide-49
SLIDE 49

Cost per CPU core Number of cores

slide-50
SLIDE 50

Cost per CPU core Number of cores Public infrastructure makes more sense Private infrastructure makes more sense

slide-51
SLIDE 51

Number of cores Time

slide-52
SLIDE 52

Number of cores Time

slide-53
SLIDE 53

Number of cores Time Private infrastructure makes more sense Public infrastructure makes more sense

slide-54
SLIDE 54

HYBRID, INTEROPERABLE INFRASTRUCTURE

slide-55
SLIDE 55

HYBRID, INTEROPERABLE INFRASTRUCTURE

╺ Hybrid clouds allow to optimize cost

slide-56
SLIDE 56

HYBRID, INTEROPERABLE INFRASTRUCTURE

╺ Hybrid clouds allow to optimize cost ╺ Hybrid clouds enable capabilities & compliance

slide-57
SLIDE 57

HYBRID, INTEROPERABLE INFRASTRUCTURE

╺ Hybrid clouds allow to optimize cost ╺ Hybrid clouds enable capabilities & compliance ╺ Interoperable public & private clouds reduce applications cost

slide-58
SLIDE 58

INTEROPERABILITY IN OPEN INFRA

slide-59
SLIDE 59

OpenStack Promises interoperability at the infrastructure layer

INTEROPERABILITY IN OPEN INFRA

slide-60
SLIDE 60

OpenStack Promises interoperability at the infrastructure layer

INTEROPERABILITY IN OPEN INFRA

Kubernetes Promises interoperability at the app deployment layer

slide-61
SLIDE 61

5. FUTURE-PROOF

Investing in communities rather than in products

slide-62
SLIDE 62

THE FUTURE

slide-63
SLIDE 63

THE FUTURE

╺ Abstractions will continue to be piled

slide-64
SLIDE 64

THE FUTURE

╺ Abstractions will continue to be piled ╺ There is no miracle technology that will end all technologies

slide-65
SLIDE 65

THE FUTURE

╺ Abstractions will continue to be piled ╺ There is no miracle technology that will end all technologies ╺ There will always be applications and infrastructure

slide-66
SLIDE 66

BE FUTURE-PROOF

slide-67
SLIDE 67

BE FUTURE-PROOF

╺ Open source allows to invest in communities, rather than products

slide-68
SLIDE 68

BE FUTURE-PROOF

╺ Open source allows to invest in communities, rather than products ╺ OpenStack community takes the angle of the infrastructure provider, and helps them build and

  • perate open source solutions for infrastructure
slide-69
SLIDE 69

SO… WHY CHOOSE OPEN INFRA ?

  • Availability
  • Sustainability
  • Fluid job market
  • Transparency
  • Self-service
  • Influenceability
  • Compliance
  • Capabilities
  • Cost
  • Interoperability
  • Enabling hybrid usage
  • Future-proof
slide-70
SLIDE 70

6. ENABLE INNOVATION

Creating ideal conditions for innovation everywhere

slide-71
SLIDE 71

AVOID MONOPOLIES

It is not economically sane to have all of the world’s infrastructure needs being provided by a couple of Internet giant companies.

slide-72
SLIDE 72

AVOID MONOCULTURES

It is not safe to have all of the worlds infrastructure needs being provided by a couple of Internet giants

slide-73
SLIDE 73

ENABLE EVERYONE

Giving everyone access to infrastructure providing technologies makes sure that we maximize innovation in the world.

slide-74
SLIDE 74

THANKS!

Any questions? Shy? You can reach me at @tcarrez on Twitter Or email me at thierry@openstack.org Credits

Presentation template by SlidesCarnival.com (licensed under CC-BY-4.0) Photographs by Unsplash.com (licensed under Unsplash licence)