{"id":11901,"date":"2020-07-15T07:20:03","date_gmt":"2020-07-15T11:20:03","guid":{"rendered":"https:\/\/origin-www.parsons.com\/?p=11901"},"modified":"2022-10-04T14:47:42","modified_gmt":"2022-10-04T18:47:42","slug":"infrastructure-devsecops-using-ansible-and-jenkins","status":"publish","type":"post","link":"https:\/\/www.parsons.com\/2020\/07\/infrastructure-devsecops-using-ansible-and-jenkins\/","title":{"rendered":"Infrastructure DevSecOps Using Ansible And Jenkins"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Modern DevSecOps practices allow us to develop code faster, more efficiently, and provide guarantees about the status of our environment. Utilizing configuration management utilities such as Ansible, we remove error-prone human interaction from configuration management. <\/p>\n\n\n\n

Deploying a new environment is as easy as modifying a few values in a configuration file and executing a command, creating reproducible development, test, and production environments. Reproducible infrastructure which removes the possibility of mistyping a password, IP address, or configuration file allows us to create exact replicas of our production infrastructure as many times as necessary, ensuring our patterns and new software are functioning correctly. In the event of a failure, knowing the previous state allows us to revert to that configuration \u2013 all in an automated fashion.<\/p>\n\n\n\n

Allowing humans to interactively log in to a machine via SSH and run arbitrary commands is a thing of the past and should be limited to \u201cbreak-glass\u201d situations. If utilizing tools such as Ansible to make human-interaction via SSH is a thing of the past for hosts, so too should be human-interaction with our orchestrators which run those hosts. <\/p>\n\n\n\n

Allowing humans to interactively log in to a machine via SSH and run arbitrary commands is a thing of the past and should be limited to \u201cbreak-glass\u201d situations. If utilizing tools such as Ansible to make human-interaction via SSH is a thing of the past for hosts, so too should be human-interaction with our orchestrators which run those hosts.<\/p><\/div>\n\n\n\n

In this talk, David covers how we are using Ansible, Jenkins, and vCenter to manage our production and testing environments for our on-premises infrastructure.<\/p>\n\n\n\n

Meet The Presenter<\/h3>\n\n\n\n

_________________________________________________________________________<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

David Thomas is a Virtualization Engineer, who manages both corporate and project-based infrastructure that is hosted within VMWare\u2019s Center.
He uses automation to ensure the entire enterprise is up-to-date with the most current configurations and patches.<\/p>\n\n\n\n

_______________________________________________________________________<\/p>\n\n\n\n

______________________________________________________________________________<\/p>\n\n\n\n

Watch The Webinar:<\/h3>\n\n\n\n
\n