Module 1 Communication Skills

Published on
Embed video
Share video
Ask about this video

Scene 1 (0s)

OOE Ops. Introduction to DevOps.

Scene 2 (2m 0s)

Introduction to DevOps. Definition DevOps is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production while ensuring high quality. Implications of this definition - Practices and tools - Do not restrict the scope of DevOps to testing and development.

Scene 3 (4m 1s)

Introduction to DevOps. Perspective involved. Business.

Scene 4 (6m 2s)

Benefits of working in a DevOps environment. Timelines.

Scene 5 (8m 3s)

Benefits of working in a DevOps environment. Imbalance.

Scene 6 (10m 4s)

Benefits of working in a DevOps environment. Blame Game.

Scene 7 (12m 5s)

Benefits of working in a DevOps environment. Where is Operations? Development is All Well (Waterfall, Agile) Where is Operations?.

Scene 8 (14m 6s)

Benefits of working in a DevOps environment. History DevOps Back in 2007 Patrick Debois [Belgian Engineer] Initially it was Agile Infrastructure but later coined the phrase DevOps Velocity conference in 2008 And if you see you may come across more tangential DevOps Initiative WinOps DevSecOps BizDevOps.

Scene 9 (16m 7s)

Benefits of working in a DevOps environment. More Handshakes.

Scene 10 (18m 8s)

Benefits of working in a DevOps environment. No More Handshakes.

Scene 11 (20m 9s)

DevOps Lifecycle. DevOps lifecycle is a combination of different phases of continuous software development, integration, testing, deployment, and monitoring. A competent DevOps lifecycle is necessary to leverage the full benefits of the DevOps methodology..

Scene 12 (22m 10s)

DevOps Lifecycle. Key Components. Continuous development Continuous integration Continuous testing Continuous deployment Continuous monitoring Continuous feedback Continuous operations.

Scene 13 (24m 11s)

DevOps Lifecycle. Continuous development. Continous Development The first phase where the planning & sotware development takes place.

Scene 14 (26m 11s)

DevOps Lifecycle. Continuous integration. Continuous integration (CI) includes different steps related to the execution of the test process. Along with this, clients also provide information to be incorporated for adding new features to the application. Most changes happen in the source code during this phase..

Scene 15 (28m 12s)

DevOps Lifecycle. Continuous testing. Continous Testing The developed functionality in continously tested for bugs,The test environments are simulated using docker container..

Scene 16 (30m 13s)

DevOps Lifecycle. Continuous deployment. Continuous deployment (CD) ensures hassle-free product deployment without affecting the application’s performance. It is necessary to ensure that the code is deployed precisely on all available servers during this phase. This process eliminates the need for scheduled releases and accelerates the feedback mechanism, allowing developers to address issues more quickly and with greater accuracy..

Scene 17 (32m 14s)

DevOps Lifecycle. Continuous monitoring. Continous Monitoring For Sustaining the availability of Services in the application.lt also helps in tracking any unusal system behaviour.

Scene 18 (34m 15s)

DevOps Lifecycle. Continuous feedback. Continuous feedback is essential to ascertain and analyze the final outcome of the application. It sets the tone for improving the current version and releasing a new version based on stakeholder feedback..

Scene 19 (36m 16s)

DevOps Lifecycle. Continuous operations. The shortest and least complex step of the DevOps life cycle. Continuous service has the aim of automating the process of launching an application and subsequent updates. Continuous operations provide shorter development times, enabling developers to continually improve the application’s time-to-market..

Scene 20 (38m 17s)

Activity Time. The trainer will ask the participants to make groups and discuss on topic DevOps life cycle.

Scene 21 (40m 18s)

DevOps Stages. code Dev -sest Deploy Monitor. The Plan stage covers everything that happens before the developers start writing code, and it’s where a Product Manager or Project Manager earns their keep. Requirements and feedback are gathered from stakeholders and customers and used to build a product roadmap to guide future development..

Scene 22 (42m 19s)

DevOps Stages. code Dev -sest Deploy Monitor. In addition to the standard toolkit of a software developer, the team has a standard set of plugins installed in their development environments to aid the development process, help enforce consistent code-styling and avoid common security flaws and code anti-patterns..

Scene 23 (44m 20s)

DevOps Stages. code Dev -sest Deploy Monitor. Build.

Scene 24 (46m 21s)

DevOps Stages. code Dev -sest Deploy Monitor. Test.

Scene 25 (48m 22s)

DevOps Stages. code Dev -sest Deploy Monitor. Release.

Scene 26 (50m 23s)

DevOps Stages. code Dev -sest Deploy Monitor. Deploy.

Scene 27 (52m 23s)

DevOps Stages. code Dev -sest Deploy Monitor. Operate.

Scene 28 (54m 24s)

DevOps Stages. code Dev -sest Deploy Monitor. Monitor.

Scene 29 (56m 25s)

DevOps Stages. Five different categories of DevOps practices Treat Ops as first-class citizens from the point of view of requirements Make Dev more responsible for relevant incident handling Enforce the deployment process used by all, including Dev and Ops personnel Use continuous deployment Develop infrastructure code, such as deployment scripts.

Scene 30 (58m 26s)

DevOps Stages. • Treat Operations personnel as first• class stakeholders • Get their input when developing requirements • Small teams • Limited coordination • Unit tests Build • Build tools • Supports continuous integration Testing • Automated testing • User acceptance testing Deployment • Deployment tools • Supports continuous deployment • Monitoring • Respondng to error conditions DevOps life cycle processes [Notation: Portefls Value Chain].

Scene 31 (1h 0m 27s)

DevOps Delivery Pipeline. The most common components of a pipeline in DevOps are build automation or continuous integration, test automation, and deployment automation..

Scene 32 (1h 2m 28s)

DevOps Delivery Pipeline. DevOps Myths & Misconception DevOps is a Team CI/CD is all about DevOps Non-Compliant to Industry Standards.

Scene 33 (1h 4m 29s)

DevOps Delivery Pipeline. DevOps Myths & Misconception Automation eliminates ALL bottlenecks “Universal" Continuous Delivery pipeline All about Tools Release as fast as Amazon / Facebook.

Scene 34 (1h 6m 30s)

DevOps Delivery Pipeline. Benefits of CI: Small changes are easy to integrate into large codebases. More comfortable for other team members to see what you have been working. Fewer integration issues allow rapid code delivery. Bugs are identified early, making them easier to fix, resulting in less debugging work..

Scene 35 (1h 8m 31s)

DevOps Delivery Pipeline. Benefits of the CD: Faster bug fixes and features delivery. CD allows the team to work on features and bug fixes in small batches, which means user feedback is received much quicker. It reduces the overall time and cost of the project..

Scene 36 (1h 10m 32s)

Activity Time. Learners need to form into groups and search for the topic DevOps Agile and discuss same with the trainer.

Scene 37 (1h 12m 33s)

DevOps on Cloud. The centralized nature of cloud computing provides DevOps automation with a standard and centralized platform for processes like testing, deployment, and production. Most public and private cloud computing providers support DevOps systemically on their platform, including continuous integration and continuous development tools. Cloud-based DevOps lessens the need to account for resources leveraged..

Scene 38 (1h 14m 34s)

DevOps on Cloud. Cloud as a Catalyst for DevOps On-demand self-service Broad network access Resource pooling Rapid elasticity It is the Capabilities can be elastically provisioned and released Measured service.

Scene 39 (1h 16m 34s)

DevOps on Cloud. Python File Operations | Learn to Perform any Operation in Python File.

Scene 40 (1h 18m 35s)

DevOps on Cloud. Software as a Service (SaaS) In this the consumer is provided the capability to use the provider’s applications running on a cloud infrastructure The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based e-mail) or an application interface The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, storage. For an example, you can relate google apps, Cisco WebEx, as a Service, Office 365 service, where Provider deals with the licensing of software’s.

Scene 41 (1h 20m 36s)

DevOps on Cloud. Platform as a Service (PaaS) The consumer is provided the capability to deploy onto the cloud infrastructure consumer- created or acquired applications created using programming languages, libraries, services, and tools supported by the provider The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but consumer has control over the deployed applications and possibly configuration settings for the application-hosting environment For an Example: .NET Development platform is considered as a platform..

Scene 42 (1h 22m 37s)

DevOps on Cloud. Infrastructure as a Service (IaaS) The consumer is provided the capability to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications The consumer does not manage or control the underlying cloud infrastructure but the consumer has control over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., host firewalls). For this, you can consider any Server Provisioning is IaaS,.

Scene 43 (1h 24m 38s)

DevOps on Cloud. Three of the unique aspects of the cloud that impact DevOps Three of the unique aspects of the cloud that impact DevOps: The ability to create and switch environments simply Simply create and migrate environments is—as is the ease of cloning new instances The ability to create VMs easily Administering the running VMs are important to find out for which VM we are paying but not using it Tool such as Janitor Monkey to scan an account The management of databases.

Scene 44 (1h 26m 39s)

Various AWS services. AWS is the best cloud service provider, and DevOps is the implementation of the software development lifecycle. Here are some reasons which make AWS DevOps a highly popular combination, such as: AWS CloudFormation AWS EC2 AWS Cloud Watch AWS Code Pipeline.

Scene 45 (1h 28m 40s)

Various AWS services. [image]. Flickr / Yahoo Flickr was able to reach 10+ Deploy per day after adopting DevOps • In 2009 You May Also Refer: YouTube Link: https://www.youtube.com/watch?v=LdOe18KhtT4.

Scene 46 (1h 30m 41s)

Various AWS services. [image]. Netflix Netflix's streaming service is a large distributed system hosted on Amazon Web Services (AWS) So many components that have to work together to provide reliable video streams to customers across a wide range of devices Netflix engineers needed to focus heavily on the quality attributes of reliability and robustness for both server- and client-side components Achieved this with DevOps by introducing a tool called Chaos Monkey Chaos Monkey is basically a script that runs continually in all Netflix environments, causing chaos by randomly shutting down server instances Thus, while writing code, Netflix developers are constantly operating in an environment of unreliable services and unexpected outages Unique opportunity to test their software in unexpected failure conditions.

Scene 47 (1h 32m 42s)

Activity Time. Learners need to form into groups and find out real-time case studies for DevOps technology.

Scene 48 (1h 34m 43s)

Various AWS services. Anti-Patterns Blame Culture A blame culture is one that tends toward blaming and punishing people when mistakes are made, either at an individual or an organizational level Silos A departmental or organizational silo describes the mentality of teams that do not share their knowledge with other teams in the same company Root Cause Analysis Root cause analysis (RCA) is a method to identify contributing and “root” causes of events or near-misses/close calls and the appropriate actions to prevent a recurrence Human Errors Human error, the idea that a human being made a mistake that directly caused a failure, is often cited as the root cause in a root cause analysis.

Scene 49 (1h 36m 44s)

Various AWS services. Example for Silos TVS India T. V. Sundaram Iyengar Founded in 1978.

Scene 50 (1h 38m 45s)

Various AWS services. Three dimensions of DevOps People Process Tools / Technology.