Convergence & Standards in IT Infrastructure. 15 Minute Analysis (Nominal)

Transcription

1 Convergence & Standards in IT Infrastructure 15 Minute Analysis (Nominal)

2 About Me Co-Host of Packet Pushers Podcast Freelance Network Architect/Engineer Blog: EtherealMind.com Newsletter PacketPushers.net

3 Convergence 3

4 Define Things that were separate become combined 4

5 Impact Disrupts vendor strategies, client architectures In my view, leading form of change or disruption in the technology market 5

6 Change in 2015 Infrastructure has been static from Applications changed dramatically in this time only so much change is possible Infrastructure now the focus DevOps Convergence / HyperConvergence Increase capacity / performance prevent operational creep 6

7 7

8 Silicon Convergence CPUs, southbound / northbound Disk controllers (IDE, SCSI) now integrated PCI-x SSD. Network adapters - now integrated on motherboard. Integration onto single silicon die 8

9 Convergence and Abstraction Abstraction manages complexity Creates multiple layers of interoperable elements Abstraction Manage complexity through defined interfaces Middleware Application Each elements operates with defined interfaces Example: car gearbox made the engine independent of differential Example: credit cards abstract us from cash 9 Operations DB File Runtime Software Infrastructure MS Linux Operating System compute storage network Virtualization compute storage network Hardware

10 Convergence & Abstraction 2 Virtualization creates abstraction from server hardware and operating system Docker abstracts the application from the operating systems Overlay networks abstract packet forwarding from the physical network hardware 10

11 Protocol Convergence HTTPS will dominate soon SSH for administration DNS of course Layer 4 is out of fashion in this decade 11

12 Private Cloud Convergence Rack scale computing Nutanix EVO:Rail & EVO:Rack Cisco UCS Data Centre Operating Systems Mesosphere vrealize SCVVM Compute / Storage / Network no longer separate disciplines integrated skills still need experts but many skills will disappear 12

13 Public Cloud as Convergence Azure / Amazon / Google hosted is convergence hosted documents platform convergence writ large 13

14 Orchestration Commoditises DC wide software control reduces demand for unique features If you have to develop/ integrate an API to deploy a one-off trick Orchestration Forces Simplification Manage complexity through defined interfaces Operations Orchestration Middleware Application Application Application Hardware Services Infrastructure Software Operating System Virtualization File Runtime.. 14

15 End of Knob Twiddling Convergence changes several things about Enterprise IT Value derived from preparing the platform No more knob twiddling custom vendor features that don't really add value I could do this or implement this hack analysing 15

16 Valuing Differentiation Commoditisation trend If I m not using vendor-specific features. then products become less differentiated Value shifts from knobby features to software integration & orchestration Which brings me to. standards & integration 16

17 Standards 17

18 Why Standards? Critical to market success eg. Roman success of standardised weights & measures standard railway gauges Reliability - open tends to better open standards are often more considered, better thought through. Interoperability reduces customer risk which creates demand modular exchange of components Open Markets are bigger than closed markets less risk on investment by vendors / manufacturers customers are more likely to buy (no training the market ) 18

19 What is Open? Define open? Open source Open Access Open Standard Open Process Open API Examples Linux OpenStack, Open Daylight An open box must have only one open side to be useful? 19

20 How much Open-ness? Linux - open source IETF, IEEE etc - open standards Published APIs - open access vendor specific product specific 20

21 Slow but Necessary use of radio spectrum and access to emergency services are multi-decade commitments some create legal precedents and rules But startups are driven to move fast or die 5 to 10 years of SDO standards process do or die EtherealMind.COm 21

22 Standards Development Organisations MEF, ITU, DMTF, IEEE, IETF, Have SDOs passed their use-by date? A question of relevance and NOT existence Linux Foundation, Apache Foundation ship first, ship fast, ship anything Who sends delegates to Standards Bodies Universities & Vendors Which people are selected? hint: not always the best or brightest 22

23 New Laws? Law of Open Source: quality and strength of the project is 100% dependent on the interests, energy and capability of the developer community Law of Open Standards: importance, validity and timeliness of relevant specification is 100% dependent on interests, energy and compromises of the individuals who have been empowered to manage, organize and complete the work effort of the SDO Reference: Open Standards, Open Source, Open Loop 23

24 Its up to You Do something in public to support standards Tell vendors, constantly Tell resellers, constantly Blog / Facebook / Twitter / LinkedIn 24

25 Wrap Up 25

26 Takeaways - Convergence natural for any mature market place incumbent vendors are playing defense to slow it down Happening in 26

27 Takeaways - Standards Open isn t a standard Standards are necessary for functional markets Customers get best outcome with modular replacements 27

28 About Me Co-Host of Packet Pushers Podcast Freelance Network Architect/Engineer Blog: EtherealMind.com Newsletter PacketPushers.net