Configuration drift occurs when a standardized group of IT resources, be they virtual servers, standard router configurations in VNF deployments, or any other deployment group that is built from a standard template, diverge in configuration over time. As administrators make changes to one resource that isn’t made to another in the same group, or if a new service is installed on some of them, then configurations can drift. Configuration drift can make it very hard to manage IT systems over time. The Infrastructure as Code methodology from DevOps is designed to combat Configuration Drift and other infrastructure management problems.
Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See
Trademarks for appropriate markings.