anchor.diff:  docker-registry     <none>                                    name=registrypod    172.30.17.158       5001
   ----
   
  -And running `osc get se kubernetes-ro` returns the same list filtered down to an individual object:
  +The following example operation returns the same list that is filtered down to an individual object:
   
   ----
   $ osc get se kubernetes-ro
  
positive.code: kubernetes-ro       component=apiserver,provider=kubernetes   <none>              172.30.17.77        80
  ----
  
  === Get
  *`osc get <object_type> _<object_id>_`* +
  This command returns a list of objects of the indicated link:#object-types[object type]. If an object name or ID is optionally included in the request, the list of results will be filtered by that value.
  
  === Describe
  *`osc describe <object_type> <object_id>`* +
  This command returns information about the specific object returned by the query; a specific object name or ID must be provided. The exact information available varies per link:#object-types[object type].
  
  === Create / Create All
  *`osc create -f <file_path>`* +
  *`osc createall _-d <directory_path>_ _-f <file_path>_`* +
  These commands perform the same central function, which is to parse a configuration file and create one or more OpenShift objects based on the file contents. In the `createall` case, you can specify a directory (`-d`) with multiple configuration files, a file (`-f`) that contains multiple configurations, or even pass configurations through STDIN.
  
  === Update
  *`osc update -f <file_path>`* +
  This command attempts to modify an existing object based on the contents of the specified configuration file. If the object does not already exist, this function behaves exactly like link:#create-create-all[`osc create`].
  
  === Delete
  *`osc delete -f <file_path>`* +
  *`osc delete <object_type> <object_id>`* +
  *`osc delete <object_type> -l <label>`* +
  This command deletes the identified OpenShift object. An object configuration can also be passed in via STDIN.
  
  === Log
  *`osc log _-f_ <pod_name> _<container_name>_`* +
  This command retrieves the log output for a specific pod / container. This command does not work for other object types.
  
  == Project Operations
  These advanced operations are used to define and instantiate OpenShift objects at the project level.
  
  === Process
  *`osc process -f <template_file_path>`* +
  This command transforms a project template into a project configuration file.
  
  === Apply
  *`osc apply -f <config_file_path>`* +
  This command creates all of the OpenShift objects for a given project based on the supplied 
  
  == Build Operations
  Being able to build your application into a container from source is a fundamental capability of the OpenShift system. These commands specifically enable you to work with builds.
  
  === Start Build
  *`osc start-build <buildConfig_name>`* +
  *`osc start-build --from-build=<build_name>`* +
  This command enables you to manually trigger a build by specifying either a buildConfig or a previous build as the starting point.
  
  === Cancel Build
  *`osc cancel-build <build_name>`* +
  This command enables you to manually stop a build in progress.
  
  === Build Logs
  *`osc build-logs <build_name>`* +
  This command retrieves the log output for the specified build.
  
negative.code: toc::[]
  
  == Overview
  With the OpenShift command line interface (CLI), you can create and manage OpenShift projects from a terminal. The CLI is ideal in situations where you are:
  
  * Working directly with project source code
  * Scripting OpenShift operations
  * Restricted by bandwidth resources and cannot use the web console
  
  The CLI commands are available directly from the OpenShift binary with the following syntax:
  
  ----
  openshift cli <command>
  ----
  
  However, if `osc` is available on your workstation you can use it as a shortcut in place of `openshift cli` in the command syntax:
  
  ----
  osc <command>
  ----
  
  NOTE: Although `osc` is used in the command examples presented throughout this document, you can substitute `openshift cli` in the command syntax if `osc` is not available on your workstation. 
  
  == Configuring the CLI
  There are many configuration options available for the OpenShift CLI, and you can access these with the `osc --help` command. The following table describes some of the more common options.
  
  .Common CLI Configuration Options
  [cols="4,8",options="header"]
  |===
  
  |Option |Description
  
  .^|`-s, --server`
  |This option allows you to specify the host name of the OpenShift server. You will need to provide this if the server is running on a different host from the CLI.
  
  .^|`--insecure-skip-tls-verify=true`
  |This option allows quick interaction with an HTTPS server; however, note that it is not secure.
  
  a|`--auth-path`
  
  `--certificate-authority`
  
  `--client-certificate`
  
  `--client-key`
  .^|These settings are used to correctly and securely authenticate with an OpenShift server that uses HTTPS. 
  |===
  
  [TIP]
  ====
  *Can I use a configuration file?* +
  The ability to permanently configure `osc` options with a configuration file is planned for a future release and is not available at this time. The current workaround is to use the CLI, or you can create a shell alias to configure the required parameters.  
  ====
  
  == CLI Object Types 
  OpenShift supports the following object types, some of which have abbreviated syntax that you can use with `osc`.
  
  .Supported Object Types
  [options="header"]
  |===
  
  |Object Type |Abbreviated Version
  
  |build |
  |buildconfig |
  |event |`ev`
  |minion |`mi`
  |pod |`po`
  |replicationController |`rc`
  |service |`se`
  |===
  
  == Common CLI Operations
  The CLI allows interaction with the various objects that are managed by OpenShift. The common `osc` operations are invoked by specifying the following:
  
  * An _action_
  * The _object type_ to perform the action on
  * The _object name_ or _ID_ of the specified _object type_
  
  In the following example the `osc get` operation returns a complete list of services that are currently defined.
  
  ----
  $ osc get se
  