On this page
AWS OpsWorks is a cloud computing service from Amazon Web Services (AWS) that manages infrastructure deployment for cloud administrators. It automates deployment, configurations and operational tasks for distributed applications. With OpsWorks, cloud administrators and developers can define the infrastructure and resource configurations, such as storage and database options, and then select the operating system and instance type on which to deploy the application.
GitLab is a single application for the whole DevOps lifecycle that includes not only configuration management, but also capabilities for project management, source code management, CI/CD, and monitoring. GitLab is designed for Kubernetes and cloud native applications.
GitLab and its CI/CD is Cloud Native, purpose built for the cloud model. GitLab can be easily deployed on Kubernetes and used to deploy your application to Kubernetes with support out of the box.
| || |
CM modeling is the concept to consolidate the interactions between IT service assets, configuration items and infrastructure. Shows the interaction and relationship of services, infrastructure, and assets with each other, it will ease to find the root cause of an incident and problem.
| || |
Configure Management automation is used to make the server reach a desirable state, previously defined by provisioning scripts using a tool’s specific language and features ensuring that every system you’re responsible for is configured accurately and consistently.
| || |
CM monitoring includes the process of recording and reporting configuration item descriptions (e.g., hardware, software, firmware, etc.) and all departures from the baseline during design and production. In the event of discovered problems, the verification of baseline configuration and approved modifications can be quickly determined.
| || |
CM governance is a review that assesses compliance with established performance requirements, commercial and appropriate government standards, and functional, allocated, and product baselines. Configuration governance confirm that the system and subsystem configuration documentation complies with the functional and physical performance characteristics before acceptance into an architectural baseline.
| || |
If you feel there are inaccurate statements in this comparison or a tool missing, please edit this page or propose edits by opening an issue. You can also send an email to firstname.lastname@example.org with your suggested edits if you're unable to open an issue or edit this page.
We strive for technical accuracy and will review and update this post for inaccuracies as quickly as possible.