Reconstructing the SRE

ReconstructingtheSRE

BobWiseCTO

CloudNativeComputingTeam

This presentation is intended to provide information concerning Samsung’s efforts around containers and container orchestration. We do our best to make sure that information presented is accurate and fully up-to-date. However, the presentation may be subject to technical inaccuracies, information that is not up-to-date or typographical errors. As a consequence, Samsung does not in any way guarantee the accuracy or completeness of information provided on this presentation. Samsung reserves the right to make improvements, corrections and/or changes to this presentation at any time.

The information in this presentation or accompanying oral statements may include forward-looking statements. These forward-looking statements include all matters that are not historical facts, statements regarding the Samsung Data System' intentions, beliefs or current expectations concerning, among other things, market prospects, growth, strategies, and the industry in which Samsung operates. By their nature, forward-looking statements involve risks and uncertainties, because they relate to events and depend on circumstances that may or may not occur in the future. Samsung cautions you that forward looking statements are not guarantees of future performance and that the actual developments of Samsung, the market, or industry in which Samsung operates may differ materially from those made or suggested by the forward-looking statements contained in this presentation or in the accompanying oral statements. In addition, even if the information contained herein or the oral statements are shown to be accurate, those developments may not be indicative developments in future periods.

Logos remain the property of their respective owners.

This presentation is intended to provide information concerning Samsung’s efforts around containers and container orchestration. We do our best to make sure that information presented is accurate and fully up-to-date. However, the presentation may be subject to technical inaccuracies, information that is not up-to-date or typographical errors. As a consequence, Samsung does not in any way guarantee the accuracy or completeness of information provided on this presentation. Samsung reserves the right to make improvements, corrections and/or changes to this presentation at any time.

The information in this presentation or accompanying oral statements may include forward-looking statements. These forward-looking statements include all matters that are not historical facts, statements regarding the Samsung Data System' intentions, beliefs or current expectations concerning, among other things, market prospects, growth, strategies, and the industry in which Samsung operates. By their nature, forward-looking statements involve risks and uncertainties, because they relate to events and depend on circumstances that may or may not occur in the future. Samsung cautions you that forward looking statements are not guarantees of future performance and that the actual developments of Samsung, the market, or industry in which Samsung operates may differ materially from those made or suggested by the forward-looking statements contained in this presentation or in the accompanying oral statements. In addition, even if the information contained herein or the oral statements are shown to be accurate, those developments may not be indicative developments in future periods.

Logos remain the property of their respective owners. So there.

ReleasetheKraken.

SDS- CloudNativeComputingTeam

• Our#1jobisimprovingorganizationalvelocity– DeliveringthebusinessvalueofKubernetestoyou,fastest

• RocksolidKubernetesclusterdesignanddeployment,specifictoyou• Optimizeddeploymentpipelinesandcontainerstrategy• 24x7x365Kubernetesoperationssoyoucanfocusonyourbusiness• Organizationalconsultingtorapidlyadapt

• Weare:– IndustryleadersinOperationsAutomation,ClusterOperations,andKubernetesAdoption

– ContributorsandleadersontheKubernetesprojectfor2+years– MaintainersofKraken:production-gradeclustermanagement– DeliveringthisforEnterprisecustomersglobally

MacroTrends

1. MacroTrend:Massiveshiftsinallindustriestowardssophisticatedandcomprehensiveautomationtoenablecompetitiveadvantage

2. Inalltechnologydelivery“CloudNative”architecturesandautomationprevail

3. Outsourcingistheonlypathascompaniescannotadaptandacquireexpertiseinternally

RootCauses:DeepOrganizationalPain• Toolsandprocessesbuiltfortheeraofbaremetalandvirtualmachines

• Devteamsunderpressuretodelivernewfeaturesquickly,notgoingfastenough

• Operationsteamstryingtosupporthastilydeployedfeatures– Qualityissues– Outages– Constantfirefighting– Unhappycustomers– Employeeretentionissues

• Operationsviewedas“justtryingtoblockthings”• “Devops”hascometomeangeneralistswhoareoverwhelmedtryingtohandleeverything

TheCloudNativeDisruption

CloudNativeHasDramaticallyRaisedtheBar

ClassicEnterpriseITisEspeciallyBehind

Fromthehighlyrecommended:https://www.slideshare.net/adriancockcroft/dockercon-state-of-the-art-in-microservices

CloudNativeMarketRealities

Enormousdifferencesbetweencompaniesintheabilitytoexecuteonsoftwareproductdeliveryhaveemergedonallthreeaxes:

• Velocity• Quality• Efficiency

CloudNativeMarketRealities

Thecompanieswinninginallthreeofthesecategoriesshareonthingincommon:

• Velocity• Quality• Efficiency

Theme:UsingCloudNativeApproaches

(a) Containerized. Applicationsdeployedinunitsthatcanbeeasilymanagedanddealtwithbyeveryone:developers,productmanagers,andoperations.

(b) Dynamicallymanaged. Automaticallyandresponsivelydeployedbyanorchestrationenginethatconsiderscustomerexperienceandcost.

(c) Micro-servicesoriented. Looselycoupledandrapidlyadaptableservicesthatcanbeinnovatedanddeployedseparatelywhilethesystemasawholecontinuestooperate.

WhatisCloudNative?

CloudNativeOrganizationsAreHighPerformanceBasedOn:

HowTheyBehaveHowTheyMeasure

HighPerformanceOrgsEmbraceChange

HighPerformanceOrgsEmbraceRapidChangeWithAutomation

PuppetLabs2017 StateofDevops ReportHighlyRecommendedReading

https://puppet.com/resources/whitepaper/2017-state-of-devops-report

MonolithicComplexDependenciesLarge,CentrallyControlledTeamsMonthstoProductionWaterfallProcessManualQAManualSecurityAudits

LotsofSimplePartsIndependentPartsSmall,IndependentTeamsSpecialistsnotGeneralistsSREPatternContinuousIntegrationContinuousDeploymentAutomatedQAUbiquitousAutomationAutomatedSecurity

ChangeResistant ChangeEmbracing

EmbraceTheChange

LotsofSimplePartsIndependentPartsSmall,IndependentTeamsContinuousIntegrationContinuousDeploymentAutomatedQAUbiquitousAutomationAutomatedSecurity

KeyInsight

OptimizedforMTBF OptimizedforMTTR

LotsofSimplePartsIndependentPartsSmall,IndependentTeamsContinuousIntegrationContinuousDeploymentAutomatedQAUbiquitousAutomationAutomatedSecurity

KeyInsight

MeasuredbyMTBF MeasuredbyMTTR

MeanTimeBetweenFailuredrivesfailurepreventionandriskaversionMeanTimeToRepairdrivesresponsivenessandallowsrisks

LotsofSimplePartsIndependentPartsSmall,IndependentTeamsSpecialistsnotGeneralistsSREPatternContinuousIntegrationContinuousDeploymentAutomatedQAUbiquitousAutomationAutomatedSecurity

EmbraceTheChange

LotsofSimplePartsIndependentParts

Small,IndependentTeamsSpecialists,notGeneralistsAdoptionoftheSREPattern

ContinuousIntegrationContinuousDeploymentAutomatedQAUbiquitousAutomationAutomatedSecurity

Architecture(Microservices)

ExecutionFundamentals

LotsofSimplePartsIndependentParts

Small,IndependentTeamsSpecialists,notGeneralistsAdoptionoftheSREPattern

ContinuousIntegrationContinuousDeploymentAutomatedQAUbiquitousAutomationAutomatedSecurity

Architecture(Microservices)

ExecutionFundamentals

CloudNative

Devops Positives• Breakingdownsilos• Nomore“throwingitoverthewall”• Orientationtoinfrastructureascode• Orientationtoautomation• ValuingcodingskillsinoperationsDevops fails:

– Companyrenamesopstodevops.– Improvementfail

Devops Anti-PatternsinLargerOrgs• Renameopstodevops.• Disbandops,“wejustmakethedevs doit”• Addadevops groupwithyetanothersilobetweendevandops• Expecteveryonetoknoweverything

– “Weonlyhavefullstackdevops”– Thisisunrealistic

Instead,wewantapatternforspecializationwithcollaboration….

TheSRE(SiteReliabilityEngineer)• Helpsproductteamsengineerforoperability

– Architecture– Tooling

• Ownscapacityplanning• EnsuresCItoolingisworkingandadequate• Helpsdevelopmentgofasterwithpositiveassistance• Spendsalotoftimeondevelopingtooling,typicallymonitoring,CI,andoperationalanalytics

• EnsureproductmanagementsetsSLOs(servicelevelobjectives)anderrorbudgets– Tracksandenforces

BenTraynor – SREVPatGoogle“OutsideGoogle,weoftenobservethatthereisn'tparityofesteembetweentheSWEandoperationsteams,whichcombinespoorlywiththefactthattheyoftenhavedifferentincentives.That'showweendupwiththemodelthatexistsintheindustrytoday,whereSWEteamswritesomethingandthrowitoverawalltotheoperationsteams,whothentrytomakeitwork,andcan't,andthrowitback,andsoon.”

CD Monitoring

EvolvingfromDevops:ClusterOps

InfraOps

ClusterOps

Cluster

AppOpsApp App

ProductMgt

InfraOpsInfraInfra

ClusterOpsandtheSRERole

InfraOps

ClusterOps

Cluster

AppOpsApp App

ProductMgt

InfraOpsInfraInfra

TechnologyProgressiontoPlatforms…DeconstructionNeeded

Impacttothedevelopment• OperationsmovingupthestackwhileDevelopmentismovingdownthestack• StillalotcomplexityandseparationbetweenOperations/Developmentteams• Outsourcewheneconomiesofscalemakeitmorebeneficialtopushtoa3rd party

BareMetal

OS/VirtualMachines

Application

Hypervisor

OS/VirtualMachines

Application

Dependencies Dependencies

BareMetal

Dependencies

Application

InfrastructureInfrastructure

Application Application

VM’s IAAS/PAASCo-Lo

BareMetal

Dependencies

Application

Infrastructure

OS/VirtualMachines

3rd Party

Operations

Development

AreaofResponsibility

OrganizationalTrendtoOutsourcing…DeconstructionNeeded

ImprovementstoDevelopmentProcess.• Fasterreleasecyclesmeansquickertomarket.• Smaller,morereliabledeployments.• Quickerrecovery,reduceriskwhenissuesoccur.Shiftinfocusto

MTTRvsMTTF.• Economiesofscalearegettingtothebuildvsbuydecision

InfrastructureOperations

ClusterOperations

AppOperations

ClusterOperations

AppOperations

ClusterOperations

AppOperations

Application Application

IAAS/PAAS

OS/VirtualMachines

FutureState

KubernetesContainersPipelineAlerting,MonitoringPerformance/EfficiencyMaintenanceReporting

SpeedtoMarket

ImprovementstoOrganizationalVelocity.• SubjectmatterexpertsonDay1• Noneedtospinupanewoperationsteam• AllowdevelopmentteamstofocusonProductvsTooling• Morecostefficientthandoingitin-house

MultipleFactors• TechnologyprogressiontoPlatforms• OrganizationalTrendtoOutsourcing

– SomeSREfunctionswillbeoutsideyourorg• Bestpractices:

– SpecialistsoverGeneralists– CollaborationoverSilos

ReconstructingtheSRE

AREApplication

CRECluster

IREInfra

AREConcerns• ApplicationSLI/SLO• Availabilitytargets• Podautoscaling• Capacityplanning• Deployments/Canaries• ApplicationCI/CD• Apppackagingpractices• AppSLIcapture• Applicationarchitecture• Applicationmonitoring• Applicationlogging

SLO– ServiceLevelObjectiveSLI– ServiceLevelIndicator

CRE/IREConcerns• ClusterSLI/SLO• ClusterCapacity• Nodeautoscaling• Controlplanedesign• Clusterupgrades• Clusterutilization• Under/overcapacity

nodes• Nodespecs• Dockerversion• Network

configuration• Namespacedesign• Failuredomains• Clustermonitoring• Clusterlogging

KubernetesFactors

KubernetesConceptual

Node(Server)

DockerDaemon

KubernetesNodeController

Node(Server)

DockerDaemon

Node(Server)

DockerDaemon

KubernetesControlPlane

Status:Cluster isreadyforwork

ToAPI: Run (1)ofcontainerX

Node(Server)

DockerDaemon

Node(Server)

DockerDaemon

Node(Server)

DockerDaemon

ReplicaSet (replicationset)Managespodcount

Node(Server)

DockerDaemon

Node(Server)

DockerDaemon

Node(Server)

DockerDaemon

Status:ClusterisrunningX

Pod(X)

ContainerContainerContainer

OrchestratingMultipleApplications

Node(Server)

DockerDaemon

Node(Server)

DockerDaemon

Node(Server)

DockerDaemon

KubernetesNamespace(Environments)

Service

KubernetesNamespace• Virtualcluster• Fundamentaladminunit,mapstodifferentorganizationalpatterns:– Resourcenamescoping,i.e.

• dev,qa,orprod– Teamsorprojects

• Group1,group2– Services

• WhatQuotasareattachedto,andfuturepermission-relatedconcepts– ReflectionofGoogleoperationalphilosophy– Micro/ACLsgettoounwieldy

KubernetesNamespaces:KeytotheCRE/AREContract• Namespacesareformalproductionentities,managedbyCRE• Devpipelinesthatcreate/modifynamespacesgetCREoversight• RBACconfigurationofnamespacesisacriticalrole• CREownsnamespacequotas• AREhasbroadpermissionsinsidethenamespace• CREownsthepodschedulingrules/contraints(taints/tolerations)

• Reportingbrokenoutbynamespace

ManagedClusterOps Services• OurgoalistoenableCustomerstofocusentirelyontheircorebusiness.• Fastestpathtoproductionclusters• Continuousmonitoringandalerting• Performanceandefficiencyanalysis

• ClusterReadinessEvaluation• StrategicBusinessAnalysis• POCDelivery• DevelopmentPipelinePlanning• DedicatedOn-boardingTeam• ManagedClusterOperations• Otherservicestoacceleratebenefitsto

yourbusiness.

ProfessionalAccelerationServices:Ourgoalistoacceleratebenefitstoyourbusinessfromcontainers,cloud-native,andfasterdeployments:

HardwareOperations

ClusterOperations

AppOperations

Quickestandandmostcosteffectivepath

SDS– CNCTCommercialOffering

ContactandProjectInfo• BobWise

– @countspongebob ontwitterandgithub– bob.wise@samsung.com

• CNCThomepage:– http://samsung-cnct.github.io/

• Krakenrepo– ProductiongradeclustermanagementforKubernetes– opensource,Apachelicense– https://github.com/samsung-cnct/kraken– #krakenchannelonkubernetes slack

Reconstructing the SRE

Software

Transcript of Reconstructing the SRE

VOLUNTEER SRE TEACHER ORIENTATION INFORMATIONnewcastleanglican.org.au/.../2015/06/SRE...Booklet.pdf · 3 Why teach Christian SRE (School Scripture)? 4 SRE Volunteer Code of Conduct

SRE 3130 C - SRE 3131 C - SRE 3132 C - Qlima

Lab Manual SRE

SRE Complete Chapters

Apostila Java SRE

Reconstructing the East

Reconstructing the South

Sre ayyan industries

Full Paper - SRE-Discussion Papers and SRE-Research Reports

SRE hex - Bosello High Technology , a ZEISS companybosello.eu/web/wp-content/uploads/2017/11/Catalogues-SRE-HEX.pdf · SRE hex SRE HEX 40.50 – 50.70 • Available in three different

B - SRE-Discussion Papers and SRE-Research Reports

Barampta on the Sre Mela Maidan

Sre TX Final

Getting the SRE Model Right - info.xmatters.com

Monk Reference SRE

SRE CORPORATION

Cisco SRE Service Module Configuration and Installation Guide · Cisco SRE Service Module Configuration and Installation Guide About the Cisco Service Modules 3 Cisco SRE Service

SRE Basics

sre 1913

Load balancing in the SRE way