Improve the Development Process with DevOps Practices презентация

of the Enterprise Applications in the IT operations management segment.
Technologies and tools: .NET, Python…

product from definition of business requirements to the product release.
The Dev and Ops teams have different success metrics.
Lack of communication between the Dev and Ops teams.
There is a difference between development and target environment configurations.
Slow and long delivery processes with unpredictable delivery date. 

different environments and teams.
Project Continuity ensures that a project can be successfully completed even if a team changes.
Time-to-market and cost requires control over your project development, since these are critical elements that directly affect revenue and your position in the market. So make sure you are using effective ways to optimize this business driver.

manage 3rd-party dependencies manually
No standardized development workplace configuration
Deployment on staging and production environment is fulfilled manually
Lack of knowledge sharing
Low repeatability of the deployment process
Launching a new team requires significant efforts

a native package platform (PIP, NPM, NuGet, etc.)
Documents describe development environment configuration or prebuild virtual machine with a configured development environment
Team may use a Build and Continuous Integration System, however, the changes in the configuration are applied manually
Knowledge transfer from the development team to the operational team, and between development teams is performed verbally or via documentation
Repeatability of the deployment process is satisfactory
Launching a new team requires significant effort

an up to date development environment
Environment configuration and deployment procedures are documented in the form of a code deployed to source control
It is possible to track changes: who and when introduced any changes, what version was deployed, on whichdevelopers’ workstation, and other staging and production environment variables
Team uses virtualization
High repeatability of the deployment process
Launching a new team does not require significant effort

production environments are aligned with configuration as much as possible:
The number of manual steps on environment deployment is as low as possible

a product or feature development from A to Z: from the stage of requirement gathering to the release date.
The development and operational teams need to share common success indicators focused on the delivery result.
The operations team needs to define requirements for monitoring, log management and disaster recovery, as well as help the development team design a solution that complies with these requirements.

as close to the target environment as possible.
To apply an “infrastructure as code” approach.
To automate quality control and acceptance testing

versions

Ops or DevOps

Dev

Deploy

showcases
Exploratory testing

Commit

Deploy

Unit & Integration Tests

Functional Tests

Production Monitoring

https://puppetlabs.com/
Ansible: http://www.ansible.com/home
Log management and Monitoring
Newrelic: http://newrelic.com/
Loggly: https://www.loggly.com/
Logstash: https://www.elastic.co/products/logstash
Testing:
JMeter: http://jmeter.apache.org/
Selenium: http://www.seleniumhq.org/

Reduced Risks