Skip to content

Instantly share code, notes, and snippets.

@petardenev
petardenev / building-devops
Created June 28, 2019 13:20
Common Practical Approach in Building DevOps Software Solutions
Situation 1: New project, DevOps engineer starts building the solution from scratch, his workflow should stick with the logic below:
1.1 Cloud-Platform independence achieved with use of:
Linux - masterless Puppet/Chef-solo/SALT-masterless/Ansible
Windows - Powershell DSC/ WinRM/ Аpache Brooklyn
1.2 Have a control script, eg. bash or powershell, it will automate use of the Puppet modules/DSC Configurations, cluster configurations, hostnames, etc things needed for implementation before having а running application stack(AppStack here is to be considered as separate Development Environment, it can be DEV/QA/PROD/ETC)
1.3 Have the CI/CD software solution done with package deployment, e.g. the software is to be delivered to the servers as rpm/deb package and installed from a repository, for example Sonatype Nexus OSS https://www.sonatype.com/nexus-repository-oss can store and distribute Maven/Java, npm, NuGet, RubyGems, Docker, P2, OBR, APT and YUM.
1.4 Minimize usage of public IP addresses
@petardenev
petardenev / devops-service-description
Last active March 28, 2020 13:27
DevOps Service Description
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