decelerate docs!

docs/docsite/rst/index.rst

@@ -9,7 +9,7 @@ Welcome to the Ansible documentation!
 Ansible is an IT automation tool.  It can configure systems, deploy software, and orchestrate more advanced IT tasks
 such as continuous deployments or zero downtime rolling updates.
 
-Ansible's main goals are simplicity and ease-of-use. It also has a strong focus on security and reliability, featuring a minimum of moving parts, usage of OpenSSH for transport (with an accelerated socket mode and pull modes as alternatives), and a language that is designed around auditability by humans--even those not familiar with the program.
+Ansible's main goals are simplicity and ease-of-use. It also has a strong focus on security and reliability, featuring a minimum of moving parts, usage of OpenSSH for transport (with other transports and pull modes as alternatives), and a language that is designed around auditability by humans--even those not familiar with the program.
 
 We believe simplicity is relevant to all sizes of environments, so we design for busy users of all types: developers, sysadmins, release engineers, IT managers, and everyone in between. Ansible is appropriate for managing all environments, from small setups with a handful of instances to enterprise environments with many thousands of instances.
 

docs/docsite/rst/intro_configuration.rst

@@ -1172,7 +1172,7 @@ first disable 'requiretty' in /etc/sudoers on all managed hosts.
 
 By default, this option is disabled to preserve compatibility with
 sudoers configurations that have requiretty (the default on many distros), but is highly
-recommended if you can enable it, eliminating the need for :doc:`playbooks_acceleration`::
+recommended if you can enable it.
 
     pipelining = False
 
@@ -1189,76 +1189,6 @@ This is the location of the ssh binary. It defaults to ``ssh`` which will use th
 
 This option is usually not required, it might be useful when access to system ssh is restricted, or when using ssh wrappers to connect to remote hosts. 
 
-.. _accelerate_settings:
-
-Accelerated Mode Settings
--------------------------
-
-Under the [accelerate] header, the following settings are tunable for :doc:`playbooks_acceleration`.  Acceleration is
-a useful performance feature to use if you cannot enable :ref:`pipelining` in your environment, but is probably
-not needed if you can.
-
-.. _accelerate_port:
-
-accelerate_port
-===============
-
-.. versionadded:: 1.3
-
-This is the port to use for accelerated mode::
-
-    accelerate_port = 5099
-
-.. _accelerate_timeout:
-
-accelerate_timeout
-==================
-
-.. versionadded:: 1.4
-
-This setting controls the timeout for receiving data from a client. If no data is received during this time, the socket connection will be closed. A keepalive packet is sent back to the controller every 15 seconds, so this timeout should not be set lower than 15 (by default, the timeout is 30 seconds)::
-
-    accelerate_timeout = 30
-
-.. _accelerate_connect_timeout:
-
-accelerate_connect_timeout
-==========================
-
-.. versionadded:: 1.4
-
-This setting controls the timeout for the socket connect call, and should be kept relatively low. The connection to the `accelerate_port` will be attempted 3 times before Ansible will fall back to ssh or paramiko (depending on your default connection setting) to try and start the accelerate daemon remotely. The default setting is 1.0 seconds::
-
-    accelerate_connect_timeout = 1.0
-
-Note, this value can be set to less than one second, however it is probably not a good idea to do so unless you're on a very fast and reliable LAN. If you're connecting to systems over the internet, it may be necessary to increase this timeout.
-
-.. _accelerate_daemon_timeout:
-
-accelerate_daemon_timeout
-=========================
-
-.. versionadded:: 1.6
-
-This setting controls the timeout for the accelerated daemon, as measured in minutes. The default daemon timeout is 30 minutes::
-
-    accelerate_daemon_timeout = 30
-
-Note, prior to 1.6, the timeout was hard-coded from the time of the daemon's launch. For version 1.6+, the timeout is now based on the last activity to the daemon and is configurable via this option.
-
-.. _accelerate_multi_key:
-
-accelerate_multi_key
-====================
-
-.. versionadded:: 1.6
-
-If enabled, this setting allows multiple private keys to be uploaded to the daemon. Any clients connecting to the daemon must also enable this option::
-
-    accelerate_multi_key = yes
-
-New clients first connect to the target node over SSH to upload the key, which is done via a local socket file, so they must have the same access as the user that launched the daemon originally.
-
 .. _selinux_settings:
 
 Selinux Specific Settings

docs/docsite/rst/intro_getting_started.rst

@@ -26,7 +26,7 @@ machines over SSH.
 
 By default, Ansible 1.3 and later will try to use native 
 OpenSSH for remote communication when possible.  This enables ControlPersist (a performance feature), Kerberos, and options in ``~/.ssh/config`` such as Jump Host setup.  However, when using Enterprise Linux 6 operating systems as the control machine (Red Hat Enterprise Linux and derivatives such as CentOS), the version of OpenSSH may be too old to support ControlPersist. On these operating systems, Ansible will fallback into using a high-quality Python implementation of
-OpenSSH called 'paramiko'.  If you wish to use features like Kerberized SSH and more, consider using Fedora, OS X, or Ubuntu as your control machine until a newer version of OpenSSH is available for your platform -- or engage 'accelerated mode' in Ansible.  See :doc:`playbooks_acceleration`.
+OpenSSH called 'paramiko'.  If you wish to use features like Kerberized SSH and more, consider using Fedora, OS X, or Ubuntu as your control machine until a newer version of OpenSSH is available for your platform.
 
 In releases up to and including Ansible 1.2, the default was strictly paramiko.  Native SSH had to be explicitly selected with the ``-c`` ssh option or set in the configuration file.