Last active
March 28, 2020 13:27
-
-
Save petardenev/2e583d9ad84e37a7a0f3bfa41a61d303 to your computer and use it in GitHub Desktop.
DevOps Service Description
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DevOps services help align application development and IT operational teams through the use of agile techniques—including sprints, continuous integration, and continuous deployment—as part of the SDLC(Software Development Lifecycle) process. | |
These services automate many of the operational tasks that application developers depend on to accelerate the development process. | |
They also help IT deliver and update applications faster while making improvement across the ITIL Operations Model including change control, release management, and governance. | |
These services address the following four major issues: | |
BREAKING DOWN SILOS FOR THE FUTURE | |
Realize the full power and benefit of DevOps by realigning development, test, and operational organizations from existing silos to create an integrated team. | |
With leadership, sponsorship and alignment in place, this can be achieved incrementally over time. As these groups coalesce into one team, operations employees learn how applications are built, and developers and QA staff learn how applications run in production. | |
This requires process—and sometimes organizational— change to drive significant increases in productivity and efficiency. | |
SDLC MODERNIZATION | |
DevOps assess the agility of your SDLC process by focusing on two important factors: | |
- how long it takes to develop your software and DevOps Services | |
- streamline test and release management. | |
The expected result is the reduce the release cycles from weeks to days or even hours, dramatically improving time-to-market for software delivery. | |
DEVOPS RESEARCH & ASSESSMENT | |
Organizations can struggle to identify capability gaps and cultural impediments impacting performance of their DevOps environment. | |
DevOps measures, tracks, and benchmarks against the most important outcomes for success. | |
We drive improvement through capabilities and identify priorities for capability improvement, tracking progress to demonstrate value and ID next steps. | |
TESTING | |
Most organizations struggle with execution of quality assurance in a measured, structured, and consistent way. | |
DevOps can solve much of this inefficiency through the use of more frequent testing cycles (“fail faster”) and platform-driven automation that reduces human error. | |
When your tested software approaches deployment, we follow a roll-forward/roll-back approach where code is deployed and then extended, and old software is withdrawn as we prove that the new code works correctly. | |
This all happens quickly as code is validated through automated functional tests as part of the deployment process itself. | |
RELEASE MANAGEMENT | |
To complete your software lifecycle automation, I can redefine your release management processes (RMPs) by: | |
∙ Developing an application templating process | |
∙ Creating standard virtual runtime templates | |
∙ Establishing a package repository management and deployment capability | |
∙ Enabling automated testing for integration and function | |
∙ Defining an end-to-end release process management model | |
Those five issues described are often solved with implementation of the following features: | |
1. Continuous Integration and Continuous Delivery Pipelines | |
2. Automated Software Deployment to On-Premise Hardware or in a Cloud Service Provider Infrastructure | |
3. Strong collaboration with all software development teams to provide continuous improvements in the software engineering tools, build procedures and release cycles. | |
4. Design, develop and implement software integrations. | |
5. Troubleshoot production issues and coordinate with the development team to streamline code deployment. | |
6. Automate source code analysis and communicate detailed reviews to development teams to ensure continuous improvements in applications and increase in overall service performance | |
7. Provide the ability to have independent build procedures that allow easier migrations of live environments (Development, Production, Integration, Test) with zero downtime. | |
8. Conduct systems tests for security, performance, and availability. | |
9. Develop and maintain design and troubleshooting documentation. | |
Common software tools used in the devops processes: | |
o Bug Management System – Jira, Redmine | |
o Collaborative Documentation System – Confluence, Docuwiki | |
o Configuration Management – Chef, Ansible, Puppet, SaltStack; | |
o Source Code Management – Git, BitBucket; | |
o Infrastructure Provision Platform – Docker, Vagrant, Kubernetes, Heroku, AWS | |
o Software Build Tools – Gradle, Apache Maven, Cake Build, MSBuild | |
o Continuous Integration and Deployment – Jenkins, Bamboo, TeamCity, TravisCI | |
o Monitoring and Alerting tools – Nagios, Prometheus, PagerDuty, Graphite, Kibana, Icinga, Datadog | |
o Artifact Management Tools – Atifactory, Nexus | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment