The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Service alarms are going off and you are on the hook to restore stability, but you need to prevent any more changes to production while you dig further. You could "freeze" production by announcing it in the office, sending a message on Slack, or sending an email to the affected teams, but that may not be enough or may require extra work that would distract you from debugging and fixing the problem.
Many of the available configuration management tools, such as Ansible, Terraform, Puppet, Chef, and Saltstack provide automation for infrastructure, cloud, compliance and security management, and integration for deployment and continuous deployment (CI / CD). But what is the best tool to start automating your particular environment? The difficult task of evaluating Configuration Management Tools prevents DevOps from evolving technically and proposing improvements to the environment they manage.
Among the updates that we ignore most are driver updates, and sometimes for good reason. There have been plenty of cases wherein a driver update caused more harm than good. This could be due to two reasons. One, the user blindly clicked the update without taking a minute to read what the update actually achieves, or two, the user was not equipped to understand what the update achieves. Whatever the reason, one thing is clear: we cannot leave the cybersecurity of an organization up to chance.
Last October, we added Managed Backups. Managed Backups is a fantastic feature in Skeddly where you simply configure your backup plan, add resources to the plan, and Skeddly manages the actions used to create and delete your backups for you. Today, I’m going to introduce you to a similar feature for starting and stopping your cloud resources: Managed Start/Stops.
