DOCSLIB.ORG

Devops in Government

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Devops in Government DevOps in Government 011001000000110100101101110001000000100011101 101111011101100110010101110010011011100110110 101100101011011100111010000100000011100000111 001001100101011100110110010101101110011101000 110010101100100001000000110001001111001001000 000100011101101111011101100100110001101111011 011110111000000101100001000000110000101101110 011001000010000001001110011001010111010001000 0010111000001110000 0100010001100101011101100100111101110000 0111001100100000011010010110111000100000 0100011101101111011101100110010101110010 0110111001101101011001010110111001110100 0010000001110000011100100110010101110011 0110010101101110011101000110010101100100 0010000001100010011110010010000001000111 0110111101110110010011000110111101101111 0111000000101100001000000110000101101110 GOVLOOP 010000010111000001110000 E-BOOK 2019 1 In any organization that creates its own technology applications or software, there are two broad teams that complete that task: developers and operations staff. Traditionally, these teams follow a linear development Executive process. Developers create code for the service based on broad parameters provided by the organization’s Summary leadership. Once the developers build the product, they send it to the operations team to deploy and manage. This handoff is often referred to as “tossing it over the wall” because operations and development staff pass the product off without truly understanding how each team is using the application. It’s like there is a wall between them that prevents transparency or meaningful communication. That wall creates all sorts of problems. Because developers don’t have a clear view of how operations will use the service, the product they create often doesn’t stand the test of real-world deployment. The new service can disrupt existing workflows, overload or damage current IT systems, compromise security or even fail regulatory requirements because developers didn’t have enough information during development. DevOps is a project management methodology that solves this problematic product handoff between developers and operations staff. Instead of operating in silos, both teams collaborate on a project from start to finish. The phrase DevOps is simply a condensed version of the terms “development” and “operations,” but what it actually means is not as simple. That’s because it’s an IT services management approach, and is related more to a cultural shift and organizational environment than technology. So instead of being a specific toolset, analysis or process, it’s a more holistic approach and cultural mindset change. For the purposes of this e-book, we are defining DevOps as an IT services management approach that stresses communication, collaboration, continuous feedback, experimentation and integration between software developers and IT professionals. In the following pages, we offer practical tips to improve and achieve DevOps from government experts who are leading successful efforts at their organizations. We’ll focus on four critical categories: culture, automation, measurement and sharing (CAMS), and how DevOps tools and technologies can aid in these areas. These tools can make development and operations workflows more streamlined and collaborative, automating previously time-consuming, manual or static tasks involved in integration, development, testing, deployment or monitoring. Additionally, we’ll take a look at why DevOps matters to all government employees today, and how it affects end users and citizens; methods you can use to achieve DevOps; benefits of DevOps; and its history. 2 DevOps at a 75% 2x 80% of CIOs identified DevOps as a IT teams practicing DevOps of government efforts to Glance top priority. processes are two times as likely transform performance don’t to exceed their goals in profit, fully meet their objectives. market share, and productivity. What impact does 2,604x DevOps have on 80% How much faster advanced of federal IT projects were self- government? How does DevOps teams recover from 17% described as “agile” or “iterative” it help you achieve IT incidents. of technology professionals said in 2017. in 2018 that their teams have your agency’s mission, fully embraced DevOps. and where did it evolve 0010001100101011101100100111101110000011 from? These stats will 7x lower 1001100100000011010010110111000100000010 help set the context for failure rate on IT changes made why DevOps culture, by advanced DevOps teams 0011101101111011101100110010101110010011 technology and compared to lower-performing 0111001101101011001010110111001110100001 teams. outcomes are more “Within 3 months,0000001110000011100100110010101110011011 IT improved important than ever 0010101101110011101000110010101100100001 for governments at all its time to resolution 66%, levels. reduced call 0000001100010011110010010000001000111011waiting time 50%, and increased0111101110110010011000110111101101111011 customer satisfaction 1000000101100001000000110000101101110010by 140%.” 0100010001100101011101100100111101110000 - Carol Johnson, IT director for Telegraph Media on DevOps 000010111000001110000 strategies in 2016. 0111001100100000011010010110111000100000 Source: Atlassian and HDI Trends You Need to Know: DevOps and IT Support 0100011101101111011101100110010101110010 0110111001101101011001010110111001110100 0010000001110000011100100110010101110011 3 0110010101101110011101000110010101100100 0010000001100010011110010010000001000111 0110111101110110010011000110111101101111 0111000000101100001000000110000101101110 010000010111000001110000 What is DevOps? Benefits of DevOps The ‘Why’ of As government transitions away from linear Collaboration — the very core of DevOps — is DevOps for application development processes and into the always a good thing. Bringing more minds to the Government new era of collaborative processes, application table engenders more diverse ideas and helps Today development is becoming quicker, cheaper and focus teams on a common mission. Plus, it increases more efficient. Instead of operating in their transparency across an organization because traditional silos, developers and operations staff different departments and teams are working have begun to work together on projects from more closely together. But in addition to the basic start to finish. benefits of collaboration, there are a ton of other reasons to use the DevOps process. It can help your That’s where DevOps comes in. agency achieve: DevOps is an evolving philosophy and framework Quicker development: For many DevOpers, this is that encourages faster, better application the most important benefit of the process. With development and faster release of new or revised DevOps, the end goal is to develop and shape software features or products to customers. It code more quickly and efficiently, and with more evolved from original agile practices in project iterations. Because developers and operations management that were then applied to technical teams don’t have to waste time throwing code project management and IT projects. The practice back and forth over a metaphorical wall, they can of DevOps encourages smoother, continuous release iterations of their product sooner. And communication, collaboration, integration, when they need to make changes or improvements visibility and transparency between application to those applications, they can do so faster development teams (Dev) and their IT operations because both teams have a shared understanding team (Ops) counterparts. of the project’s functions and goals. Greater quality assurance: But even as workers deliver more services faster, they don’t have to sacrifice quality with DevOps. Actually, the process minimizes errors through two distinct attributes First, DevOps allows both teams to see the full scope of a project. That means they have a better understanding of how any single change — say, a 4 change in a line of code or an update to a hosting Happier end users: Ultimately, DevOps helps platform — will affect the rest of the application. government agencies better serve citizens in In traditional development processes, one change the digital age. As users increasingly expect could derail an entire project. That’s far less likely government resources to be provided with the same because of the collaborative workflow of DevOps. mobility, agility and utility as private sector services, Second, automation replaces many human agencies seek ways to quickly meet those demands. processes within DevOps. DevOps reduces human When they turn to DevOps, they’re able to deliver error by automating many core development and those services and meet citizen expectations. deployment functions. Better end products: With DevOps, “we see higher- quality solutions, and at the same time we see flexibility,” said Texas.gov Director of Technology Peter Eichorn. When they incorporate DevOps practices, both developers and operations workers gain a better understanding of the product they’re working on. Developers get to know the real- world conditions in which their code will operate. Operations teams learn what makes their services tick and why they were built that way. Together, both teams can make better decisions about how to build and deploy services, and that results in a better product overall. And because there are minimal barriers between the development and operations environments, employees can make changes with minimal stress to ensure that applications keep pace with evolving needs and scenarios. 5 CAMS and DevOps Some people group DevOps goals into four categories: culture,
Load more

Recommended publications
  • Towards an Application Lifecycle Management Framework
    VTT CREATES BUSINESS FROM TECHNOLOGY Technology and market foresight • Strategic research • Product and service development • IPR and licensing Dissertation VTT PUBLICATIONS 759 • Assessments, testing, inspection, certification • Technology and innovation management • Technology partnership • • • VTT PUBLICATIONS 759 TOWARDS AN APPLICATION LIFECYCLE MANAGEMENT FRAMEWORK AN APPLICATION 759 TOWARDS • VTT PUBLICATIONS VTT PUBLICATIONS 742 Elina Mattila. Design and evaluation of a mobile phone diary for personal health management. 2010. 83 p. + app. 48 p. 743 Jaakko Paasi & Pasi Valkokari (eds.). Elucidating the fuzzy front end – Experiences from the INNORISK project. 2010. 161 p. 744 Marja Vilkman. Structural investigations and processing of electronically and protonically conducting polymers. 2010. 62 p. + app. 27 p. 745 Juuso Olkkonen. Finite difference time domain studies on sub-wavelength aperture structures. 2010. 76 p. + app. 52 p. 746 Jarkko Kuusijärvi. Interactive visualization of quality Variability at run-time. 2010. 111 p. 747 Eija Rintala. Effects of oxygen provision on the physiology of baker’s yeast Saccharomyces cerevisiae. 2010. 82 p. + app. 93 p. 748 Virve Vidgren. Maltose and maltotriose transport into ale and lager brewer’s yeast strains. 2010. 93 p. + app. 65 p. 749 Toni Ahonen, Markku Reunanen & Ville Ojanen (eds.). Customer value driven service business development. Outcomes from the Fleet Asset Management Project. 2010. 43 p. + app. 92 p. 750 Tiina Apilo. A model for corporate renewal. Requirements for innovation management. 2010. 167 p. + app. 16 p. 751 Sakari Stenudd. Using machine learning in the adaptive control of a smart environment. 2010. 75 p. 752 Evanthia Monogioudi. Enzymatic Cross-linking of ββ-casein and its impact on digestibility and allergenicity.
    [Show full text]
  • Devsecops in Reguated Industries Capgemini Template.Indd
    DEVSECOPS IN REGULATED INDUSTRIES ACCELERATING SOFTWARE RELIABILITY & COMPLIANCE TABLE OF CONTENTS 03... Executive Summary 04... Introduction 07... Impediments to DevSecOps Adoption 10... Playbook for DevSecOps Adoption 19... Conclusion EXECUTIVE SUMMARY DevOps practices enable rapid product engineering delivery and operations, particularly by agile teams using lean practices. There is an evolution from DevOps to DevSecOps, which is at the intersection of development, operations, and security. Security cannot be added after product development is complete and security testing cannot be done as a once-per-release cycle activity. Shifting security Left implies integration of security at all stages of the Software Development Life Cycle (SDLC). Adoption of DevSecOps practices enables faster, more reliable and more secure software. While DevSecOps emerged from Internet and software companies, it can benefit other industries, including regulated and high security environments. This whitepaper covers how incorporating DevSecOps in regulated Industries can accelerate software delivery, reducing the time from code change to production deployment or release while reducing security risks. This whitepaper defines a playbook for DevSecOps goals, addresses challenges, and discusses evolving workflows in DevSecOps, including cloud, agile, application modernization and digital transformation. Bi-directional requirement traceability, document generation and security tests should be part of the CI/CD pipeline. Regulated industries can securely move away
    [Show full text]
  • CADET: Debugging and Fixing Misconfigurations Using Counterfactual Reasoning
    CADET: Debugging and Fixing Misconfigurations using Counterfactual Reasoning Md Shahriar Iqbal∗ Rahul Krishna∗ Mohammad Ali Javidian University of South Carolina Columbia University Purdue University [email protected] [email protected] [email protected] Baishakhi Ray Pooyan Jamshidi Columbia University University of South Carolina [email protected] [email protected] Abstract Swap Mem. Swap Memory Modern computing platforms are highly-configurable with thou- sands of interacting configuration options. However, configuring GPU Resource these systems is challenging and misconfigurations can cause un- 512 Mb Latency 1Gb Memory Pressure expected non-functional faults. This paper proposes CADET (short 2Gb 3Gb for Causal Debugging Toolkit) that enables users to identify, ex- 4Gb Latency plain, and fix the root cause of non-functional faults early and in a GPU Growth GPU Growth principled fashion. CADET builds a causal model by observing the (a) (b) (c) performance of the system under different configurations. Then, it uses casual path extraction followed by counterfactual reason- Figure 1: Observational data (in Fig.1a) (incorrectly) shows ing over the causal model to (a) identify the root causes of non- that high GPU memory growth leads to high latency. The trend functional faults, (b) estimate the effects of various configuration is reversed when the data is segregated by swap memory. options on the performance objective(s), and (c) prescribe candi- date repairs to the relevant configuration options to fix the non- functional fault. We evaluated CADET on 5 highly-configurable systems by comparing with state-of-the-art configuration optimiza- heat dissipation [15, 71, 74, 84]. The sheer number of modalities tion and ML-based debugging approaches.
    [Show full text]
  • Enterprise Application Lifecycle Management Solutions Enterprise Application Lifecycle Management Solutions
    Enterprise Application Lifecycle Management Solutions Enterprise Application Lifecycle Management Solutions This extensive onsite knowledge gained from years of expe- Products and Solutions for rience combined with our trusted relationships with end- users, puts us in a unique position to self-instrument the Comprehensive Enterprise products crucially needed by our customers to successfully accomplish their Enterprise Application Lifecycle Manage- Application Lifecycle ment projects. Management With this in mind, we have developed Our Enterprise Application Lifecycle Ma- RaySuite. nagement Solutions include delivering RaySuite is a comprehensive set of products that automates various tasks within an Enterprise Application Lifecycle. consulting and software packaging ser- vices to enterprises undergoing an OS This automation ranges from the analysis of the existing application portfolio and license inventories via complex migration or implementing a software license management and software packaging, all the way deployment tool. We have successfully to comprehensive quality control and fi nally software deployment in production. These automated processes served over 600 enterprise customers are sustainable and can be replicated for every change and with excellent results. every patch. A central database and a common user interface found throughout all RaySuite products form a consistent solution and off er a strong contrast to existing patchwork solutions that are often found in enterprises, as a result of limited vision and the implementation of various suppliers. Al- though Raynet guarantees a consistent approach with the use of its entire product range, it is still possible to buy and implement the individual products of RaySuite autono- mously as well as integrate them with existing third-party or home-grown products.
    [Show full text]
  • Automatic Deployment of Distributed Software Systems: Definitions and State of the Art
    Open Archive TOULOUSE Archive Ouverte (OATAO) OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. This is an author-deposited version published in : http://oatao.univ-toulouse.fr/ Eprints ID : 14816 To link to this article : DOI :10.1016/j.jss.2015.01.040 URL : http://dx.doi.org/10.1016/j.jss.2015.01.040 To cite this version : Arcangeli, Jean-Paul and Boujbel, Raja and Leriche, Sébastien Automatic Deployment of Distributed Software Systems: Definitions and State of the Art. (2015) Journal of Systems and Software, vol. 103. pp. 198-218. ISSN 0164-1212 Any correspondance concerning this service should be sent to the repository administrator: [email protected] Automatic deployment of distributed software systems: Definitions and state of the art a, a b Jean-Paul Arcangeli ∗, Raja Boujbel , Sébastien Leriche a Université de Toulouse, UPS, IRIT, 118 Route de Narbonne, F-31062 Toulouse, France b Université de Toulouse, ENAC, 7 Avenue Édouard Belin, F-31055 Toulouse, France a b s t r a c t Deployment of software systems is a complex post-production process that consists in making software available for use and then keeping it operational. It must deal with constraints concerning both the system and the target machine(s), in particular their distribution, heterogeneity and dynamics, and satisfy requirements from different stakeholders. In the context of mobility and openness, deployment must react to the instability of the network of machines (failures, connections, disconnections, variations in the quality of the resources, etc.).
    [Show full text]
  • Devops Point of View an Enterprise Architecture Perspective
    DevOps Point of View An Enterprise Architecture perspective Amsterdam, 2020 Management summary “It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.”1 Setting the scene Goal of this Point of View In the current world of IT and the development of This point of view aims to create awareness around the IT-related products or services, companies from transformation towards the DevOps way of working, to enterprise level to smaller sizes are starting to help gain understanding what DevOps is, why you need it use the DevOps processes and methods as a part and what is needed to implement DevOps. of their day-to-day organization process. The goal is to reduce the time involved in all the An Enterprise Architecture perspective software development phases, to achieve greater Even though it is DevOps from an Enterprise Architecture application stability and faster development service line perspective, this material has been gathered cycles. from our experiences with customers, combined with However not only on the technical side of the knowledge from subject matter experts and theory from organization is DevOps changing the playing within and outside Deloitte. field, also an organizational change that involves merging development and operations teams is Targeted audience required with an hint of cultural changes. And last but not least the skillset of all people It is specifically for the people within Deloitte that want to involved is changing. use this as an accelerator for conversations and proposals & to get in contact with the people who have performed these type of projects.
    [Show full text]
  • Code Debugging Tool to Help Teach Mainframe Programming Languages Claudio Gonçalves Bernardo Paulo Roberto Chineara Batuta Msc
    Code Debugging Tool to Help Teach Mainframe Programming Languages Claudio Gonçalves Bernardo Paulo Roberto Chineara Batuta MSc. Computer Engineer MBA Software Quality Universidade Paulista Centro Universitário Araraquara Brazilia – Brazil São Paulo - Brazil [email protected] [email protected] Abstract – The purpose of testing activity is to discover errors in important to check the quality of software at various stages of software and for this objective to be achieved many activities development, not only restricting the testing phase of the software. must be performed. There are several types of test and while An appropriate test is one that discovers the greatest possible some are generated and focused on functional verification of a number of faults in the software and when this software is designed component and incorporating components in the structure of the to run in an large environment, also known as Mainframe, becomes program, others are applied to point traceability requirements. an even greater difficulty, since this environment is complex and the There are systems tests designed to validate part of a software characteristics of each facility are different. Universities see this component, which is a part of software solution greater. Its difficulty as a major obstacle to the teaching of languages such as function is only to be a small part of a more complex reality. The Cobol, PL/I, Easytrieve, Assembler and others, who did not die and different types of tests are complementary and in most cases are will not die, as a single system mainframe can deliver thousands of applicable to all software developed. All aim to develop programs virtual Linux platforms with a small fraction the dollar cost, power with the fewest mistakes as possible, allowing the product to and space [20].
    [Show full text]
  • Radiant Info School Project Management Project Management
    Radiant info school Project Management Project Management Life Cycle Managing your digital media project is one of the most important and often overlooked aspects of the development process. You will find that effort you put into planning, scheduling, and organizing your project will pay off enormously. Here we'll outline some proven techniques for planning, scheduling, and completing your project. A project has five phases. Here's a brief summary of each: . Initiation Articulate your vision for the project, establish goals, assemble your team, and define expectations and the scope of your project. Develop a Business Case Undertake a Feasibility Study Establish the Project Charter It will help you to define the scope of your project. Writing the Project Charter is typically one of the most challenging steps in the Project Life Cycle, as it defines the parameters within which the project must be delivered. It sets out the project vision, objectives, scope and implementation, thereby giving the team clear boundaries within which the project must be delivered. Appoint the Project Team Set up the Project Office Perform Phase Review Radiant info school Project Management . Planning Refine the scope, identify specific tasks and activities to be completed, and develop a schedule and budget. Create a Project Plan Create a Resource Plan Create a Financial Plan Create a Quality Plan Create a Risk Plan Create an Acceptance Plan Create a Communications Plan Create a Procurement Plan Contract the Suppliers Define the Tender Process Issue a Statement of Work Issue a Request for Information Issue a Request for Proposal Create Supplier Contract Perform Phase Review execution Build Deliverables Monitor and Control Perform Time Management Perform Cost Management Perform Quality Management Perform Change Management This process helps you to manage all requests for change within your project.
    [Show full text]
  • Planning in Software Project Management
    PLANNING IN SOFTWARE PROJECT MANAGEMENT AN EMPIRICAL RESEARCH OF SOFTWARE COMPANIES IN VIETNAM Thesis presented to the Faculty of Economics and Social Sciences at the University of Fribourg (Switzerland) in fulfillment of the requirements for the degree of Doctor of Economics and Social Sciences by Quynh Mai NGUYEN from Vietnam Accepted by the Faculty of Economics and Social Sciences on May 30th, 2006 at the proposal of Professor Dr. Andreas Meier (first advisor) Professor Dr. Jacques Pasquier (second advisor) Professor Dr. Laurent Donzé (third advisor) Fribourg, Switzerland 2006 The Faculty of Economics and Soci al Sciences at the University of Fribourg neither approves nor disapproves the opinions expressed in a doctoral dissertati on. They are to be considered those of the author (decision of the Faculty Council of January 23rd, 1990). To my parents, and To Phuong and Trung, my children ACKNOWLEDGEMENT I would like to express my extreme gratitude to Prof. Dr. Andreas Meier for his guidance, encouragement and helpful supervision during the process of this thesis. I would like to thank Prof. Jacques Pasquier and Prof. Laurent Donzé for their review and comments. My special thanks also go to Dr. Fredric William Swierczek for his invaluable help, advices and suggestions for improvement. Without their help and advice this dissertation could not be completed. I would like to thank my friends, Dr. Bui Nguyen Hung, and Dr. Nguyen Dac Hoa, Mrs. Nguyen Thuy Quynh Loan for their assistance and helpful suggestions and contributions. I would like to thank the government of Switzerland and the Swiss – AIT – Vietnam Management Development Program (SAV) for giving me the scholarship for this PhD program.
    [Show full text]
  • Creating Integrated IBM Websphere Solutions Using Application Lifecycle Management
    Front cover Creating Integrated IBM WebSphere Solutions using Application Lifecycle Management Creating an end to end solution using the WebSphere portfolio Delivering effective application lifecycle management using CLM Increasing control and agility using BPM and ODM Emrah Barkana Antonella Bertoletti Stefano Bussaglia Ernest Calalang Sebastian Kapciak Leonardo Olivera Sergio Polastri Fabio Silva ibm.com/redbooks International Technical Support Organization Creating Integrated IBM WebSphere Solutions using Application Lifecycle Management December 2014 SG24-8243-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (December 2014) This edition applies to IBM Rational Collaborative Lifecycle Management V4.0.6, WebSphere Application Server V8.5.5, WebSphere Liberty Core 8.5.5, IBM Worklight V6.2, and DB2 V10.5.3. © Copyright International Business Machines Corporation 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii IBM Redbooks promotions . ix Preface . xi Authors. xi Now you can become a published author, too! . xiv Comments welcome. xiv Stay connected to IBM Redbooks . .xv Chapter 1. Introduction. 13 1.1 Business integration problems . 14 1.2 The business scenario . 14 1.3 Application Lifecycle Management . 15 1.4 Using this book . 16 1.4.1 Goals and objectives. 17 1.4.2 How this book is organized . 17 Chapter 2. Solution overview. 19 2.1 The solution architecture. 20 2.2 Middleware products used for the solution . 20 2.2.1 Additional solution artifacts . 21 2.2.2 Integration of the components .
    [Show full text]
  • Software Deployment and Update Overview
    SSooffttwwaarree DDeeppllooyymmeenntt aanndd UUppddaattee User Guide Version R95 English February 4, 2021 Copyright Agreement The purchase and use of all Software and Services is subject to the Agreement as defined in Kaseya’s “Click-Accept” EULATOS as updated from time to time by Kaseya at http://www.kaseya.com/legal.aspx. If Customer does not agree with the Agreement, please do not install, use or purchase any Software and Services from Kaseya as continued use of the Software or Services indicates Customer’s acceptance of the Agreement.” ©2019 Kaseya. All rights reserved. | www.kaseya.com Contents i Software Deployment and Update Overview Contents Software Deployment and Update Overview ............................................................................................. i Software Deployment and Update Module Minimum Requirements ............................................. ii Getting Started .................................................................................................................................... iii Master Catalog and Local Software Catalog.................................................................................... iii Profiles, Assignment and Deployment .............................................................................................. v Scanning ............................................................................................................................................... v Deployment Options ..........................................................................................................................
    [Show full text]
  • Introduction to Devops on AWS
    Introduction to DevOps on AWS October 2020 Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2020 Amazon Web Services, Inc. or its affiliates. All rights reserved. Contents Introduction .......................................................................................................................... 1 Continuous Integration ........................................................................................................ 2 AWS CodeCommit ........................................................................................................... 2 AWS CodeBuild ................................................................................................................ 3 AWS CodeArtifact ............................................................................................................ 3 Continuous Delivery ...........................................................................................................
    [Show full text]