Replace references to Chef by Ansible

The OpenStack Chef deployment project has been retired, but in the
meantime, two deployment projects based on Ansible are available. Update
some references accordingly.

Change-Id: Idbde34b13bdd414df62c7c757a8bfc664ca69638

security-guide/source/instance-management/security-services-for-instances.rst

@@ -194,7 +194,7 @@ Section *AC-19(d)* in Oz.
 It is recommended to avoid the manual image building process as it is
 complex and prone to error. Additionally, using an automated system
 like Oz for image building or a configuration management utility like
-Chef or Puppet for post-boot image hardening gives you the ability to
+Ansible or Puppet for post-boot image hardening gives you the ability to
 produce a consistent image as well as track compliance of your base
 image to its respective hardening guidelines over time.
 

security-guide/source/management/continuous-systems-management.rst

@@ -187,16 +187,14 @@ use it.
 
 There are many configuration management solutions; at the time of this
 writing there are two in the marketplace that are robust in their
-support of OpenStack environments: Chef and :term:`Puppet`. A
+support of OpenStack environments: Ansible and :term:`Puppet`. A
 non-exhaustive listing of tools in this space is provided below:
 
--  Chef
-
 -  Puppet
 
--  Salt Stack
+-  OpenStack-Ansible
 
--  Ansible
+-  Kolla-Ansible
 
 Policy changes
 --------------

security-guide/source/management/integrity-life-cycle.rst

@@ -61,7 +61,7 @@ Note that the node boot process begins with two insecure operations:
 DHCP and TFTP. Then the boot process uses TLS to download the remaining
 information required to deploy the node. This may be an operating system
 installer, a basic install managed by
-`Chef <https://www.chef.io/chef/>`__ or
+`Ansible <https://www.ansible.com/>`__ or
 `Puppet <https://puppetlabs.com/>`__, or even a complete file system
 image that is written directly to disk.