anchor.diff:  ... Connect the removable media to a system that is connected to the Internet.
   ... Review the images and configuration manifests to mirror:
   +
  +ifdef::openshift-origin[]
  +[source,terminal]
  +----
  +$ oc adm release mirror -a ${LOCAL_SECRET_JSON}  \
  +     --from=quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE} \
  +     --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} \
  +     --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE} --dry-run
  +----
  +endif::[]
  +ifndef::openshift-origin[]
   [source,terminal]
   ----
   $ oc adm release mirror -a ${LOCAL_SECRET_JSON}  \
  
positive.code:      --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} \
       --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE} --dry-run
  ----
  ... Record the entire `imageContentSources` section from the output of the previous
  command. The information about your mirrors is unique to your mirrored repository, and you must add the `imageContentSources` section to the `install-config.yaml` file during installation.
  ... Mirror the images to a directory on the removable media:
  +
  [source,terminal]
  ----
  $ oc adm release mirror -a ${LOCAL_SECRET_JSON} --to-dir=${REMOVABLE_MEDIA_PATH}/mirror quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE}-${ARCHITECTURE}
  ----
  ... Take the media to the restricted network environment and upload the images to the local container registry.
  +
  [source,terminal]
  
negative.code: 
  .. Export the name of the repository to mirror:
  +
  ifndef::openshift-origin[]
  [source,terminal]
  ----
  $ PRODUCT_REPO='openshift-release-dev'
  ----
  +
  For a production release, you must specify `openshift-release-dev`.
  endif::[]
  ifdef::openshift-origin[]
  [source,terminal]
  ----
  $ PRODUCT_REPO='openshift'
  ----
  endif::[]
  
  .. Export the path to your registry pull secret:
  +
  