Source: devops.com
Nine Pillars of DevOps Best PracticesCategory: Software, Data, Infrastructure, automation
Home » Blogs » Nine Pillars of DevOps Best Practices
In a prior blog I explained my 27-factor DevOps assessment model which includes nine pillars of DevOps and three dimensions of people, process and technology.
Git, Perforce, Mercurial, etc).• A software version management (SVM) system is used to manage all versions of tools and infrastructure configurations and tests that are used in the build process.
Logs and proactive system alerts are in place for most DevOps component failures, and are organized in a manner to quickly identify the highest-priority problems.• Snapshot and trend results of each metric from each DevOps pipeline stage (for example, builds, artifacts, tests) are automatically calculated in process and visible to everyone in the Dev, QA and Ops Teams.• Key performance indicators (KPIs) for the DevOps infrastructure components are automatically gathered, calculated and made visible to anyone on the team that subscribes to them.
Developers are empowered and trained to take personal responsibility for security.• Security assurance automation and security monitoring practices are embraced by the organization.• All information security platforms that are in use expose full functionality via APIs for automation capability.• Proven version control practices and tools are used for all application software, scripts, templates and blueprints that are used in DevOps environments.• Immutable infrastructure mindsets are adopted to ensure production systems are locked down.• Security controls are automated so as not to impede DevOps agility.• Security tools are integrated into the CI/CD pipeline.• Source code for key intellectual property on build or test machines are only accessible by trusted users with verified credentials.
In a prior blog I explained my 27-factor DevOps assessment model which includes nine pillars of DevOps and three dimensions of people, process and technology.
Git, Perforce, Mercurial, etc).• A software version management (SVM) system is used to manage all versions of tools and infrastructure configurations and tests that are used in the build process.
Logs and proactive system alerts are in place for most DevOps component failures, and are organized in a manner to quickly identify the highest-priority problems.• Snapshot and trend results of each metric from each DevOps pipeline stage (for example, builds, artifacts, tests) are automatically calculated in process and visible to everyone in the Dev, QA and Ops Teams.• Key performance indicators (KPIs) for the DevOps infrastructure components are automatically gathered, calculated and made visible to anyone on the team that subscribes to them.
Developers are empowered and trained to take personal responsibility for security.• Security assurance automation and security monitoring practices are embraced by the organization.• All information security platforms that are in use expose full functionality via APIs for automation capability.• Proven version control practices and tools are used for all application software, scripts, templates and blueprints that are used in DevOps environments.• Immutable infrastructure mindsets are adopted to ensure production systems are locked down.• Security controls are automated so as not to impede DevOps agility.• Security tools are integrated into the CI/CD pipeline.• Source code for key intellectual property on build or test machines are only accessible by trusted users with verified credentials.
Related Articles
Community Partners
DevOps Careers