Removed references to Quick Installer for 3.10

_topic_map.yml

@@ -284,8 +284,6 @@ Topics:
     File: host_preparation
   - Name: Installing on Containerized Hosts
     File: rpm_vs_containerized
-  - Name: Quick Installation
-    File: quick_install
   - Name: Advanced Installation
     File: advanced_install
   - Name: Disconnected Installation

admin_guide/backup_restore.adoc

@@ -64,9 +64,6 @@ ifdef::openshift-enterprise,openshift-origin[]
 reinstallation, save all the files used in the initial installation. This may
 include:
 +
-- *_~/.config/openshift/installer.cfg.yml_* (from the
-xref:../install_config/install/quick_install.adoc#install-config-install-quick-install[Quick Installation]
-method)
 - Ansible playbooks and inventory files (from the
 xref:../install_config/install/advanced_install.adoc#install-config-install-advanced-install[Advanced
 Installation] method)
@@ -257,7 +254,7 @@ and displays {product-title}'s configuration:
 
 If you want to deploy etcd on master hosts, then there is no need to create a
 new host. If you want to deploy dedicated etcd out of master hosts, then you
-must create new hosts. 
+must create new hosts.
 
 Choose a system to be the initial etcd member, and restore its etcd backup and
 configuration:

admin_guide/manage_nodes.adoc

@@ -111,12 +111,6 @@ certificates, and other important steps. See the
 xref:../install_config/adding_hosts_to_existing_cluster.adoc#adding-nodes-advanced[advanced
 installation] method for instructions on running the playbook directly.
 
-ifdef::openshift-enterprise[]
-Alternatively, if you used the quick installation method, you can
-xref:../install_config/adding_hosts_to_existing_cluster.adoc#adding-nodes-or-reinstalling-quick[re-run
-the installer to add nodes], which performs the same steps.
-endif::[]
-
 [[deleting-nodes]]
 == Deleting Nodes
 

day_two_guide/topics/adding_master_host.adoc

@@ -11,13 +11,7 @@ documentation.
 The scale up playbook performs all the tasks required to add a new master to the current
 *{rhocp}* environment, including generating certificates, installing *{rhocp}* packages and configuring the host itself.
 
-Depending on the installation procedure chosen when deploying the *{rhocp}* environment,
- there are two different methods for adding nodes to the *{rhocp}* environment:
-
-* Using the quick installer tool
-* Using the advanced install
-
-NOTE: This document focuses on the last option, scale up the environment using the advanced install.
+Add nodes to the *{rhocp}* environment using the advanced installation method.
 
 [[requirements]]
 ==== Requirements
@@ -174,4 +168,4 @@ node03.example.com openshift_node_labels="{'role':'app','zone':'C'}"
 [new_nodes]
 ----
 
-// vim: set syntax=asciidoc:
+// vim: set syntax=asciidoc:

getting_started/install_openshift.adoc

@@ -15,17 +15,6 @@ This guide introduces you to the basic concepts of {product-title}, and helps
 you install a basic application. This guide is not suitable for deploying or
 installing a production environment of {product-title}.
 
-[IMPORTANT]
-====
-This guide uses the quick installer for the initial cluster installation;
-however, as of {product-title} 3.9, the quick installation method is deprecated.
-In a future release, it will be removed completely, and the procedure in this
-guide will be updated accordingly. In addition, using the quick installer to
-upgrade from version 3.7 to 3.9 is not supported. The
-xref:../install_config/install/advanced_install.adoc#install-config-install-advanced-install[advanced installation] method will continue to be supported for new installations and
-cluster upgrades.
-====
-
 [[install-prerequisites]]
 === Prerequisites
 

install_config/adding_hosts_to_existing_cluster.adoc

@@ -11,105 +11,13 @@
 
 toc::[]
 
-== Overview
-
-Depending on how your {product-title} cluster was installed, you can add new
-hosts (either nodes or masters) to your installation by using the install tool
-for quick installations, or by using the *_scaleup.yml_* playbook for advanced
-installations.
-
-[[adding-nodes-or-reinstalling-quick]]
-== Adding Hosts Using the Quick Installer Tool
-
-If you used the quick install tool to install your {product-title} cluster, you
-can use the quick install tool to add a new node host to your existing cluster.
-
-[NOTE]
-====
-Currently, you can not use the quick installer tool to add new master hosts. You
-must use the
-xref:../install_config/install/advanced_install.adoc#install-config-install-advanced-install[advanced
-installation] method to do so.
-====
-
-If you used the installer in either
-xref:../install_config/install/quick_install.adoc#running-an-interactive-installation[interactive] or
-xref:../install_config/install/quick_install.adoc#running-an-unattended-installation[unattended] mode, you can re-run the
-installation as long as you have an
-xref:../install_config/install/quick_install.adoc#defining-an-installation-configuration-file[installation configuration
-file] at *_~/.config/openshift/installer.cfg.yml_* (or specify a different
-location with the `-c` option).
-
-////
-If you installed using the
-xref:../install_config/install/advanced_install.adoc#install-config-install-advanced-install[advanced
-installation] method and therefore do not have an installation configuration
-file, you can either try
-xref:../install_config/install/quick_install.adoc#defining-an-installation-configuration-file[creating your own] based on
-your cluster's current configuration, or see the advanced installation method on
-how to
-xref:adding-nodes-advanced[run the playbook for adding new nodes directly].
-////
-
-[IMPORTANT]
-====
-See the
-xref:../scaling_performance/cluster_limits.adoc#scaling-performance-cluster-limits[cluster
-limits] section for the recommended maximum number of nodes.
-====
-
-To add nodes to your installation:
-
-. Ensure you have the latest installer and playbooks by updating the
-*atomic-openshift-utils* package:
-+
-----
-# yum update atomic-openshift-utils
-----
-
-. Run the installer with the `scaleup` subcommand in interactive or
-unattended mode:
-+
-----
-# atomic-openshift-installer [-u] [-c </path/to/file>] scaleup
-----
-
-. The installer detects your current environment and allows you to add additional nodes:
-+
-----
-*** Installation Summary ***
-
-Hosts:
-- 100.100.1.1
-  - OpenShift master
-  - OpenShift node
-  - Etcd (Embedded)
-  - Storage
-
-Total OpenShift masters: 1
-Total OpenShift nodes: 1
-
-
----
-
-We have detected this previously installed OpenShift environment.
-
-This tool will guide you through the process of adding additional
-nodes to your cluster.
-
-Are you ready to continue? [y/N]:
-----
-+
-Choose (y) and follow the on-screen instructions to complete your desired task.
-
 [[adding-nodes-advanced]]
-== Adding Hosts Using the Advanced Install
+== Adding Hosts
 
-If you installed using the advanced install, you can add new hosts to your
-cluster by running the *_scaleup.yml_* playbook. This playbook queries the
-master, generates and distributes new certificates for the new hosts, then runs
-the configuration playbooks on the new hosts only. Before running the
-*_scaleup.yml_* playbook, complete all prerequisite
+You can add new hosts to your cluster by running the *_scaleup.yml_* playbook.
+This playbook queries the master, generates and distributes new certificates for
+the new hosts, then runs the configuration playbooks on the new hosts only.
+Before running the *_scaleup.yml_* playbook, complete all prerequisite
 xref:../install_config/install/host_preparation.adoc#install-config-install-host-preparation[host
 preparation] steps.
 
@@ -118,14 +26,6 @@ preparation] steps.
 The scaleup playbook only configures the new host. It does not update *_NO_PROXY_* in master services and it does not restart master services.
 ====
 
-
-ifdef::openshift-enterprise[]
-This process is similar to re-running the installer in the
-xref:adding-nodes-or-reinstalling-quick[quick installation method to add nodes],
-however you have more configuration options available when using the advanced
-method and when running the playbooks directly.
-endif::[]
-
 You must have an existing inventory file (for example, *_/etc/ansible/hosts_*)
 that is representative of your current cluster configuration in order to run the
 *_scaleup.yml_* playbook.

install_config/configuring_authentication.adoc

@@ -31,18 +31,10 @@ xref:../install_config/install/advanced_install.adoc#configuring-cluster-variabl
 {product-title} user names containing `/`, `:`, and `%` are not supported.
 ====
 
-If you installed {product-title} using
-the
-ifdef::openshift-enterprise[]
-xref:../install_config/install/quick_install.adoc#install-config-install-quick-install[Quick Installation] or
-endif::[]
-xref:../install_config/install/advanced_install.adoc#install-config-install-advanced-install[Advanced Installation]
-method, the
-ifdef::openshift-enterprise[]
-xref:DenyAllPasswordIdentityProvider[Deny All] identity provider is
-used by default, which denies access for all user names and
-passwords. To allow access, you must choose a different identity provider and
-configure the master configuration file appropriately (located at
+The xref:DenyAllPasswordIdentityProvider[Deny All] identity provider is used by
+default, which denies access for all user names and passwords. To allow access,
+you must choose a different identity provider and configure the master
+configuration file appropriately (located at
 *_/etc/origin/master/master-config.yaml_* by default).
 endif::[]
 ifdef::openshift-origin[]

install_config/configuring_sdn.adoc

@@ -81,14 +81,6 @@ See
 xref:../install_config/install/advanced_install.adoc#advanced-install-networking-variables-table[Configuring Cluster Variables] for descriptions of networking-related Ansible variables
 that can be set in your inventory file.
 
-ifdef::openshift-enterprise[]
-For initial xref:../install_config/install/quick_install.adoc#install-config-install-quick-install[quick installations],
-the *ovs-subnet* plug-in is installed and configured by default as well, and can
-be
-xref:../install_config/master_node_configuration.adoc#master-configuration-files[reconfigured post-installation]
-using the `*networkConfig*` stanza of the *_master-config.yaml_* file.
-endif::[]
-
 [[configuring-the-pod-network-on-masters]]
 == Configuring the Pod Network on Masters
 

install_config/install/host_preparation.adoc

@@ -319,28 +319,28 @@ devices, which is not supported for production use and only appropriate for
 proof of concept environments. For production environments, you must create a
 thin pool logical volume and re-configure Docker to use that volume.
 
-Docker stores images and containers in a graph driver, which is a pluggable storage technology, such as *DeviceMapper*, 
-*OverlayFS*, and *Btrfs*. Each has advantages and disadvantages. For example, OverlayFS is faster than DeviceMapper 
-at starting and stopping containers, but is not Portable Operating System Interface for Unix (POSIX) compliant 
+Docker stores images and containers in a graph driver, which is a pluggable storage technology, such as *DeviceMapper*,
+*OverlayFS*, and *Btrfs*. Each has advantages and disadvantages. For example, OverlayFS is faster than DeviceMapper
+at starting and stopping containers, but is not Portable Operating System Interface for Unix (POSIX) compliant
 because of the architectural limitations of a union file system and is not supported prior to Red Hat Enterprise
-Linux 7.2. See the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/?version=7[Red Hat Enterprise Linux] release notes 
+Linux 7.2. See the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/?version=7[Red Hat Enterprise Linux] release notes
 for information on using OverlayFS with your version of RHEL.
 
-For more information on the benefits and limitations of DeviceMapper and OverlayFS, 
+For more information on the benefits and limitations of DeviceMapper and OverlayFS,
 see xref:../../scaling_performance/optimizing_storage.adoc#choosing-a-graph-driver[Choosing a Graph Driver].
 
 
 [[configuring-docker-overlayfs]]
 === Configuring OverlayFS
 
-OverlayFS is a type of union file system. It allows you to overlay one file system on top of another. 
-Changes are recorded in the upper file system, while the lower file system remains unmodified. 
+OverlayFS is a type of union file system. It allows you to overlay one file system on top of another.
+Changes are recorded in the upper file system, while the lower file system remains unmodified.
 
 xref:../../scaling_performance/optimizing_storage.adoc#comparing-overlay-graph-drivers[Comparing the Overlay vs. Overlay2 Graph Drivers]
 has more information about the *overlay* and *overlay2* drivers.
 
-For information on enabling the OverlayFS storage driver for the Docker service, see the 
-link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/managing_containers/#using_the_overlay_graph_driver[Red Hat 
+For information on enabling the OverlayFS storage driver for the Docker service, see the
+link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/managing_containers/#using_the_overlay_graph_driver[Red Hat
 Enterprise Linux Atomic Host documentation].
 
 
@@ -719,15 +719,8 @@ Containerized Hosts]
 to prepare your hosts.
 
 When you are ready to proceed, you can install {product-title} using the
-xref:quick_install.adoc#install-config-install-quick-install[quick installation] or
-xref:advanced_install.adoc#install-config-install-advanced-install[advanced installation] method.
-
-[IMPORTANT]
-====
-As of {product-title} 3.9, the quick installation method is deprecated. In a
-future release, it will be removed completely. In addition, using the quick
-installer to upgrade from version 3.7 to 3.9 is not supported.
-====
+xref:advanced_install.adoc#install-config-install-advanced-install[advanced
+installation] method.
 endif::[]
 
 ifdef::openshift-origin[]

install_config/install/index.adoc

@@ -7,13 +7,6 @@
 :experimental:
 :prewrap!:
 
-ifdef::openshift-enterprise[]
-The xref:../../install_config/install/quick_install.adoc#install-config-install-quick-install[quick installation]
-method allows you to use an interactive CLI utility to install {product-title}
-across a set of hosts. This installer is a self-contained wrapper intended for
-usage on a Red Hat Enterprise Linux 7 host.
-endif::[]
-
 ifdef::openshift-origin[]
 You can quickly get {product-title} running by choosing an installation method
 in xref:../../getting_started/administrators.adoc#getting-started-administrators[Getting Started for

install_config/install/planning.adoc

@@ -48,35 +48,6 @@ ifdef::openshift-enterprise[]
 * _Is my installation supported if integrating with other technologies?_ See the link:https://access.redhat.com/articles/2176281[OpenShift Container Platform Tested Integrations] for a list of tested integrations.
 endif::[]
 
-[[installation-methods]]
-== Installation Methods
-
-[IMPORTANT]
-====
-As of {product-title} 3.9, the quick installation method is deprecated. In a
-future release, it will be removed completely. In addition, using the quick
-installer to upgrade from version 3.7 to 3.9 is not supported.
-====
-
-Both the quick and advanced installation methods are supported for development
-and production environments. If you want to quickly get {product-title} up and
-running to try out for the first time, use the quick installer and let the
-interactive CLI guide you through the configuration options relevant to your
-environment.
-
-For the most control over your cluster’s configuration, you can use the advanced
-installation method. This method is particularly suited if you are already
-familiar with Ansible. However, following along with the {product-title}
-documentation should equip you with enough information to reliably deploy your
-cluster and continue to manage its configuration post-deployment using the
-provided Ansible playbooks directly.
-
-If you install initially using the quick installer, you can always further tweak
-your cluster’s configuration and adjust the number of hosts in the cluster using
-the same installer tool. If you wanted to later switch to using the advanced
-method, you can create an inventory file for your configuration and carry on
-that way.
-
 ifdef::openshift-origin[]
 [[planning-cloud-providers]]
 === On-premises vs Cloud Providers

install_config/install/rpm_vs_containerized.adoc

@@ -52,18 +52,13 @@ Containerized methods:
 |===
 
 [[install-config-install-install-methods-containerized]]
-== Install Methods for Containerized Hosts
+== Install Method for Containerized Hosts
 
-As with the RPM installation, you can choose between the xref:../../install_config/install/quick_install.adoc#install-config-install-quick-install[quick] and xref:../../install_config/install/advanced_install.adoc#install-config-install-advanced-install[advanced] install methods for the containerized install.
+As with the RPM installation, you can use the
+xref:../../install_config/install/advanced_install.adoc#install-config-install-advanced-install[advanced]
+installation method for the containerized install.
 
-For the quick installation method, you can choose between the RPM or
-containerized method on a per host basis during the interactive installation, or
-set the values manually in an
-xref:../../install_config/install/quick_install.adoc#defining-an-installation-configuration-file[installation
-configuration file].
-
-For the advanced installation method, you can set the Ansible variable
-`*containerized=true*` in an
+You can set the Ansible variable `*containerized=true*` in an
 xref:../../install_config/install/advanced_install.adoc#configuring-ansible[inventory
 file] on a cluster-wide or per host basis.
 
@@ -99,23 +94,6 @@ openshift_docker_insecure_registries=<registry_hostname>
 openshift_docker_blocked_registries=<registry_hostname>
 ----
 
-ifdef::openshift-enterprise[]
-For the quick installation method, you can export the following environment
-variables on each target host:
-
-----
-# export OO_INSTALL_ADDITIONAL_REGISTRIES=<registry_hostname>
-# export OO_INSTALL_INSECURE_REGISTRIES=<registry_hostname>
-----
-
-
-[IMPORTANT]
-====
-Blocked Docker registries cannot currently be specified using the quick
-installation method.
-====
-endif::[]
-
 The configuration of additional, insecure, and blocked Docker registries occurs
 at the beginning of the installation process to ensure that these settings are
 applied before attempting to pull any of the required images.