Breakup deployments.adoc into subdir

Author: adellape

_topic_map.yml

@@ -606,7 +606,16 @@ Topics:
   - Name: Quotas and Limit Ranges
     File: compute_resources
   - Name: Deployments
-    File: deployments
+    Dir: deployments
+    Topics:
+      - Name: How Deployments Work
+        File: how_deployments_work
+      - Name: Basic Deployment Operations
+        File: basic_deployment_operations
+      - Name: Deployment Strategies
+        File: deployment_strategies
+      - Name: Advanced Deployment Strategies
+        File: advanced_deployment_strategies
   - Name: Getting Traffic Into The Cluster
     File: getting_traffic_into_cluster
   - Name: Routes

admin_guide/managing_pods.adoc

@@ -84,10 +84,9 @@ ifdef::openshift-enterprise,openshift-origin[]
 [[manage-pods-limit-run-once-duration]]
 == Limiting Run-once Pod Duration
 
-{product-title} relies on run-once pods to perform tasks such as
-xref:../dev_guide/deployments.adoc#dev-guide-deployments[deploying a pod] or
-xref:../dev_guide/builds.adoc#dev-guide-builds[performing a build]. Run-once pods are pods that
-have a `*RestartPolicy*` of `Never` or `OnFailure`.
+{product-title} relies on run-once pods to perform tasks such as deploying a pod
+or performing a build. Run-once pods are pods that have a `*RestartPolicy*` of
+`Never` or `OnFailure`.
 
 The cluster administrator can use the *RunOnceDuration* admission control
 plug-in to force a limit on the time that those run-once pods can be active.

admin_guide/managing_projects.adoc

@@ -214,8 +214,7 @@ the entire cluster.
 === Developer-specified Node Selectors
 
 {product-title} developers
-xref:../dev_guide/deployments.adoc#assigning-pods-to-specific-nodes[can set a
-node selector on their pod configuration] if they wish to restrict nodes even
+xref:../dev_guide/deployments/basic_deployment_operations.adoc#assigning-pods-to-specific-nodes[can set a node selector on their pod configuration] if they wish to restrict nodes even
 further. This will be in addition to the project node selector, meaning that you
 can still dictate node selector values for all projects that have a node
 selector value.

admin_guide/quota.adoc

@@ -465,6 +465,6 @@ ifdef::openshift-origin,openshift-enterprise,openshift-dedicated[]
 == Accounting for Quota in Deployment Configurations
 
 If a quota has been defined for your project, see
-xref:../dev_guide/deployments.adoc#deployment-resources[Deployment Resources]
+xref:../dev_guide/deployments/basic_deployment_operations.adoc#deployment-resources[Deployment Resources]
 for considerations on any deployment configurations.
 endif::[]

architecture/core_concepts/deployments.adoc

@@ -141,7 +141,7 @@ When a deployment is superseded by another, the previous replication
 controller is retained to enable easy rollback if needed.
 
 For detailed instructions on how to create and interact with deployments,
-refer to xref:../../dev_guide/deployments.adoc#dev-guide-deployments[Deployments].
+refer to xref:../../dev_guide/deployments/basic_deployment_operations.adoc#dev-guide-basic-deployment-operations[Deployments].
 
 Here is an example `*DeploymentConfiguration*` definition with some
 omissions and callouts:

cli_reference/basic_cli_operations.adoc

@@ -258,7 +258,7 @@ $ oc delete all -l <label>
 ----
 
 === set
-Modify a specific property of the specified object. 
+Modify a specific property of the specified object.
 
 ==== set env
 Sets an environment variable on a deployment configuration or a build configuration:
@@ -279,9 +279,9 @@ $ oc set build-secret --source bc/mybc mysecret
 One of the fundamental capabilities of {product-title} is the ability to build
 applications into a container from source.
 
-{product-title} provides CLI access to inspect and manipulate
-xref:../dev_guide/deployments.adoc#dev-guide-deployments[deployment configurations] using standard
-`oc` resource operations, such as `get`, `create`, and `describe`.
+{product-title} provides CLI access to inspect and manipulate deployment
+configurations using standard `oc` resource operations, such as `get`, `create`,
+and `describe`.
 
 === start-build
 Manually start the build process with the specified build configuration file:
@@ -358,15 +358,15 @@ $ oc start-build --list-webhooks
 ----
 
 === deploy
-View a xref:../dev_guide/deployments.adoc#dev-guide-deployments[deployment], or manually start,
-cancel, or retry a deployment:
+View a deployment, or manually start, cancel, or retry a deployment:
+
 ----
 $ oc deploy <deploymentconfig>
 ----
 
 === rollback
 Perform a
-xref:../dev_guide/deployments.adoc#rolling-back-a-deployment[rollback]:
+xref:../dev_guide/deployments/basic_deployment_operations.adoc#rolling-back-a-deployment[rollback]:
 ----
 $ oc rollback <deployment_name>
 ----
@@ -408,9 +408,8 @@ $ oc import-image <image_stream>
 
 === scale
 Set the number of desired replicas for a
-xref:../architecture/core_concepts/deployments.adoc#replication-controllers[replication
-controller] or a xref:../dev_guide/deployments.adoc#dev-guide-deployments[deployment configuration] to
-the number of specified replicas:
+xref:../architecture/core_concepts/deployments.adoc#replication-controllers[replication controller] or a deployment configuration to the number of specified replicas:
+
 ----
 $ oc scale <object_type> <object_name> --replicas=<#_of_replicas>
 ----

dev_guide/app_tutorials/ruby_on_rails.adoc

@@ -301,7 +301,7 @@ $ oc new-app path/to/source/code --name=rails-app -e POSTGRESQL_USER=username -e
 
 With this command, {product-title} fetches the source code, sets up the Builder image, xref:../builds.adoc#dev-guide-builds[builds] your application image, and deploys the newly created image together with the specified xref:../../using_images/db_images/postgresql.adoc#postgresql-environment-variables[environment variables]. The application is named `rails-app`.
 
-You can verify the environment variables have been added by viewing the JSON document of the `rails-app` xref:../deployments.adoc#dev-guide-deployments[DeploymentConfig]:
+You can verify the environment variables have been added by viewing the JSON document of the `rails-app` xref:../deployments/how_deployments_work.adoc#dev-guide-how-deployments-work[DeploymentConfig]:
 
 ----
 $ oc get dc rails-app -o json
@@ -354,7 +354,7 @@ Run the migration from inside the container:
 
 If you are running your Rails application in a `development` or `test` environment you don't have to specify the `RAILS_ENV` environment variable.
 
-* By adding pre-deployment xref:../../dev_guide/deployments.adoc#lifecycle-hooks[lifecycle hooks] in your template. For example check the link:https://github.com/openshift/rails-ex/blob/master/openshift/templates/rails-postgresql.json#L122-L130[hooks example] in our link:https://github.com/openshift/rails-ex[Rails example] application.
+* By adding pre-deployment xref:../../dev_guide/deployments/deployment_strategies.adoc#lifecycle-hooks[lifecycle hooks] in your template. For example check the link:https://github.com/openshift/rails-ex/blob/master/openshift/templates/rails-postgresql.json#L122-L130[hooks example] in our link:https://github.com/openshift/rails-ex[Rails example] application.
 
 === Creating a Route for Your Application