Model-Driven DevOps

Steven Carter has more than 25 years of industry experience working in large universities, government research and development laboratories, and private sector companies. He has been a speaker at several industry conferences and written blogs and articles in technical journals. He has spent time as a system administrator running some of the world’s largest supercomputers and a network engineer building out the world’s first SDN network for the Department of Energy. In addition, Steven has a wide range of experience in networking, including operations, embedded software development, and sales. He has spent the past 5 years working for Red Hat Ansible and Cisco Systems consulting and coding for many of the world’s largest organizations as they modernize and secure their operations by incorporating DevOps. He currently works as a principal DevOps engineer for Cisco Systems creating CI/CD pipelines for deploying cloud applications and network infrastructure in secure and classified environments. He holds a BS in computer engineering, an MS in computer science, an MBA, and a CCIE in routing and switching.Jason King is a solutions architect at Cisco, supporting the public sector community. In his 11 years at Cisco, he has focused on cloud, automation, programmability, and HPC. Prior to joining Cisco, he spent 10 years building and tuning some of the world’s largest HPC clusters at Lawrence Livermore National Laboratory. He holds an MS in computer science and a CCIE in routing and switching.

• Chapter 1: A Lightbulb Goes Off Enterprise IT as a Source of Risk to the BusinessObservations of a Train WreckDevOps Seems Like a Better WayWhat Is DevOps?AutomationInfrastructure as CodeCI/CDApps vs. InfrastructureHarnessing Automation-at-ScaleWhy Are Enterprise IT Departments Not Adopting DevOps?Human FactorsBusiness FactorsSummaryChapter 2: A Better Way The Goal: Business TransformationConstraints-Based ITBusiness TransformationDevOps in ActionWhy Model-Driven DevOps?Network Infrastructure Is DifferentWhat Is Model-Driven DevOps?What Is a Data Model?Source of TruthDevOps as a FrameworkDevSecOps: Baked-In SecuritySummaryChapter 3: Consumable Infrastructure APIsWhy API over CLI?PlatformsPhysical Hardware ProvisioningConsolidated Control PointNorthbound vs. Southbound APIsAPI and Feature NormalizationFabricwide ServicesScalabilitySummaryChapter 4: Infrastructure as Code Why Infrastructure as Code?Source of TruthData ModelsCommon IaC ToolsOrganizationTypes of Source of TruthCodeData FlowSummaryChapter 5: Continuous Integration/Continuous Deployment CI/CD OverviewApplications vs. InfrastructureCI/CD in ActionSource Code ManagementCore FeaturesCollaboration FeaturesSCM SummaryContinuous Integration ToolsCI EnginesHow They WorkSample WorkflowInfrastructure Simulation ToolsCisco Modeling LabsTest and ValidationLintingSchema/Model ValidationFunctional TestingTest and Validation SummaryContinuous DeploymentContinuous MonitoringSummaryChapter 6: Implementation Model-Driven DevOps Reference ImplementationThe GoalDevOps RoadmapArchitectureNetwork as an ApplicationConsistencySimulationAutomationCreating a Source of TruthMoving DataMDD Source of TruthAutomation ToolingMDD DataAutomation RunnerCisco Network Services OrchestratorTestingLintingSnapshotting the Test NetworkData Validation and State CheckingData ValidationPushing Data to the DevicesState CheckingRestoreContinuous Integration Workflow SummaryDeploymentScaleStarting WorkflowsSummaryChapter 7: Human Factors Culture and the Need for ChangeStart with the WhyOrganizationLeadershipRole ModelsBuilding a TeamBreak Down the SilosCommunityNew ToolsSummary of Organization-Level ChangesIndividualProgramming vs. AutomationVersion Control ToolsData FormatsAPIsTemplatingLinux/UNIXWait! Where Do I Fit In?Summary9780137644674 TOC 6/23/2022

Select Guide Rating