Merge pull request #5065 from bfallonf/links_1484441

Bug 1484441 Fixed links in advanced install topic

Author: Brice Fallon-Freeman

install_config/install/advanced_install.adoc

@@ -38,7 +38,7 @@ Technology Preview feature.
 ====
 
 ifdef::openshift-enterprise[]
-Alternatively, you can use the xref:quick_install.adoc#install-config-install-quick-install[quick installation]
+Alternatively, you can use the xref:../../install_config/install/quick_install.adoc#install-config-install-quick-install[quick installation]
 method if you prefer an interactive installation experience.
 endif::[]
 
@@ -140,7 +140,7 @@ can be assigned cluster-wide:
 |`ansible_ssh_user`
 |This variable sets the SSH user for the installer to use and defaults to
 `root`. This user should allow SSH-based authentication
-xref:host_preparation.adoc#ensuring-host-access[without requiring a password]. If
+xref:../../install_config/install/host_preparation.adoc#ensuring-host-access[without requiring a password]. If
 using SSH key-based authentication, then the key should be managed by an SSH
 agent.
 
@@ -192,7 +192,7 @@ more information.
 |`openshift_rolling_restart_mode`
 |This variable enables rolling restarts of HA masters (i.e., masters are taken
 down one at a time) when
-xref:../upgrading/automated_upgrades.adoc#running-the-upgrade-playbook-directly[running
+xref:../../install_config/upgrading/automated_upgrades.adoc#running-the-upgrade-playbook-directly[running
 the upgrade playbook directly]. It defaults to `services`, which allows rolling
 restarts of services on the masters. It can instead be set to `system`, which
 enables rolling, full system restarts and also works for single master clusters.
@@ -281,7 +281,7 @@ assigned. This network block should be a private block and must not conflict
 with existing network blocks in your infrastructure to which pods, nodes, or the
 master may require access. Defaults to `10.128.0.0/14` and cannot be arbitrarily
 re-configured after deployment, although certain changes to it can be made in
-the xref:../configuring_sdn.adoc#configuring-the-pod-network-on-masters[SDN
+the xref:../install_config/configuring_sdn.adoc#configuring-the-pod-network-on-masters[SDN
 master configuration].
 
 |`osm_host_subnet_length`
@@ -296,7 +296,7 @@ re-configured after deployment.
 |`openshift_use_flannel`
 |This variable enables *flannel* as an alternative networking layer instead of
 the default SDN. If enabling *flannel*, disable the default SDN with the
-`openshift_use_openshift_sdn` variable. For more information, see xref:../configuring_sdn.adoc#using-flannel[Using Flannel].
+`openshift_use_openshift_sdn` variable. For more information, see xref:../install_config/configuring_sdn.adoc#using-flannel[Using Flannel].
 
 |`openshift_docker_additional_registries`
 |{product-title} adds the specified additional registry or registries to the
@@ -488,7 +488,7 @@ every Ansible installation of {product-title}:
 |This check ensures that a host has the recommended amount of memory for the
 specific deployment of {product-title}. Default values have been derived from
 the
-xref:../../install_config/install/prerequisites.html#system-requirements[latest
+xref:../../install_config/install/prerequisites.adoc#system-requirements[latest
 installation documentation]. A user-defined value for minimum memory
 requirements may be set by setting the `openshift_check_min_host_memory_gb`
 cluster variable in your inventory file.
@@ -497,7 +497,7 @@ cluster variable in your inventory file.
 |This check only runs on etcd, master, and node hosts. It ensures that the mount
 path for an {product-title} installation has sufficient disk space remaining.
 Recommended disk values are taken from the
-xref:../../install_config/install/prerequisites.html#system-requirements[latest
+xref:../../install_config/install/prerequisites.adoc#system-requirements[latest
 installation documentation]. A user-defined value for minimum disk space
 requirements may be set by setting `openshift_check_min_host_disk_gb` cluster
 variable in your inventory file.
@@ -553,7 +553,7 @@ openshift_disable_check=memory_availability,disk_availability
 ====
 A similar set of health checks meant to run for diagnostics on existing clusters
 can be found in
-xref:../../admin_guide/diagnostics_tool.adoc#ansible-based-tooling-health-checkss[Ansible-based Health Checks]. Another set of checks for checking certificate expiration can be
+xref:../../admin_guide/diagnostics_tool.adoc#admin-guide-health-checks-via-ansible-playbook[Ansible-based Health Checks]. Another set of checks for checking certificate expiration can be
 found in
 xref:../../install_config/redeploying_certificates.adoc#install-config-redeploying-certificates[Redeploying Certificates].
 ====
@@ -716,7 +716,7 @@ openshift_examples_modify_imagestreams=true
 
 GlusterFS can be configured to provide
 xref:../../architecture/additional_concepts/storage.adoc#architecture-additional-concepts-storage[peristent storage] and
-xref:../storage_examples/gluster_dynamic_example.adoc#install-config-persistent-storage-dynamically-provisioning-pvs[dynamic provisioning] for {product-title}. It can be used both containerized within
+xref:../install_config/storage_examples/gluster_dynamic_example.adoc#install-config-persistent-storage-dynamically-provisioning-pvs[dynamic provisioning] for {product-title}. It can be used both containerized within
 {product-title} and non-containerized on its own nodes.
 
 [[advanced-install-containerized-glusterfs-persistent-storage]]
@@ -829,8 +829,8 @@ Hello from Heketi.
 After successful installation, see
 link:https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/html/container-native_storage_for_openshift_container_platform/chap-documentation-red_hat_gluster_storage_container_native_with_openshift_platform-gluster_pod_operations[Operations on a Red Hat Gluster Storage Pod in an OpenShift Environment] to check the status of the GlusterFS clusters.
 
-xref:../storage_examples/gluster_dynamic_example.adoc#install-config-persistent-storage-dynamically-provisioning-pvs[Dynamic provisioning] of GlusterFS volumes can occur by
-xref:../storage_examples/gluster_dynamic_example.html#create-a-pvc-ro-request-storage-for-your-application[creating a PVC to request storage].
+xref:../install_config/storage_examples/gluster_dynamic_example.adoc#install-config-persistent-storage-dynamically-provisioning-pvs[Dynamic provisioning] of GlusterFS volumes can occur by
+xref:../install_config/storage_examples/gluster_dynamic_example.adoc#create-a-pvc-ro-request-storage-for-your-application[creating a PVC to request storage].
 
 [[advanced-install-configuring-openshift-container-registry]]
 === Configuring the OpenShift Container Registry
@@ -2279,7 +2279,7 @@ Preview phase.
 
 . Ensure that one or more source projects for the TSB were defined via
 `openshift_template_service_broker_namespaces` as described in
-xref:../../install_config/install/advanced_install.html#configuring-template-service-broker[Configuring the Template Service Broker].
+xref:../../install_config/install/advanced_install.adoc#configuring-template-service-broker[Configuring the Template Service Broker].
 
 . Run the following command to enable unauthenticated access for the TSB:
 +
@@ -2539,8 +2539,8 @@ ifdef::openshift-origin[]
 xref:../../install_config/configuring_authentication.adoc#AllowAllPasswordIdentityProvider[Allow
 All].
 endif::[]
-- Deploy an xref:../registry/index.adoc#install-config-registry-overview[integrated Docker registry].
-- Deploy a xref:../router/index.adoc#install-config-router-overview[router].
+- Deploy an xref:../../install_config/registry/index.adoc#install-config-registry-overview[integrated Docker registry].
+- Deploy a xref:../../install_config/router/index.adoc#install-config-router-overview[router].
 ifdef::openshift-origin[]
 - xref:../../install_config/imagestreams_templates.adoc#install-config-imagestreams-templates[Populate your {product-title} installation]
 with a useful set of Red Hat-provided image streams and templates.