[Ops] Moving "Deploy an empty role" to Fuel UG

Moving "Deploying an Empty Role through Fuel CLI" article
from Ops Guide to Fuel User Guide due to deprecation of
Ops Guide.

Change-Id: I5ea490a757a696879ddcffb208268d56c59353cb

userdocs/fuel-user-guide/cli.rst

@@ -37,6 +37,7 @@ This section includes the following topics:
    cli/cli_nodes.rst
    cli/cli_node_group.rst
    cli/cli_roles.rst
+   cli/cli_nodes_empty_role.rst
    cli/cli_plugins.rst
    cli/cli_graphs.rst
    cli/cli_config_openstack.rst

userdocs/fuel-user-guide/cli/cli_nodes_empty_role.rst

@@ -0,0 +1,145 @@
+.. _cli-nodes-empty-role:
+
+Deploy a node with an empty role
+--------------------------------
+
+You may need to deploy a node with an operating system installed only,
+that is an empty role, where you can further deploy your own service
+out of Fuel control.
+
+**To deploy a node with an empty role:**
+
+#. Verify available operating systems:
+
+   .. code-block:: console
+
+      fuel release
+
+   **Example of system response:**
+
+   .. code-block:: console
+
+      id | name                       | state       | operating_system | version
+      ---|----------------------------|-------------|------------------|-----------
+      2  | Mitaka on Ubuntu 14.04     | available   | Ubuntu           | mitaka-9.0
+      3  | Mitaka on Ubuntu+UCA 14.04 | available   | Ubuntu           | mitaka-9.0
+      1  | Mitaka on CentOS 6.5       | unavailable | CentOS           | mitaka-9.0
+
+
+   Note down the operating system ``id`` you need to install on the node.
+
+#. Verify available nodes:
+
+   .. code-block:: console
+
+      fuel node
+
+   **Example of system response:**
+
+   .. code-block:: console
+
+      id | status   | name             | cluster | ip        | mac               | roles | pending_roles | online | group_id
+      ---|----------|------------------|---------|-----------|-------------------|-------|---------------|--------|---------
+      2  | discover | Untitled (90:9b) | None    | 10.20.0.4 | 08:00:27:f5:90:9b |       |               | True   | None
+      3  | discover | Untitled (53:f1) | None    | 10.20.0.5 | 08:00:27:14:53:f1 |       |               | True   | None
+      1  | discover | Untitled (7c:11) | None    | 10.20.0.3 | 08:00:27:72:7c:11 |       |               | True   | None
+
+
+#. Create a new environment if you do not have one:
+
+   .. code-block:: console
+
+      fuel env create --name <ENV_NAME> --release 2
+
+   **Example of system response:**
+
+   .. code-block:: console
+
+      Environment `<ENV_NAME>` with id=1 was created!
+
+#. Verify that the environment has been created:
+
+   .. code-block:: console
+
+      fuel env
+
+   **Example of system response:**
+
+   .. code-block:: console
+
+      id | status | name       | release_id
+      ---|--------|------------|-----------
+      1  | new    | <ENV_NAME> | 2
+
+   Note down the ``id`` of the environment.
+
+#. Verify available roles:
+
+   .. code-block:: console
+
+      fuel role --release 2
+
+   **Example of system response:**
+
+   .. code-block:: console
+
+      name
+      -------------------
+      compute-vmware
+      compute
+      cinder-vmware
+      virt
+      base-os
+      controller
+      ceph-osd
+      ironic
+      cinder
+      cinder-block-device
+      mongo
+
+   The role that you need is ``base-os``.
+
+#. Add one of the discovered nodes to the environment with the ``base-os`` role assigned:
+
+   .. code-block:: console
+
+      fuel node set --env 1 --node 1 --role base-os
+
+   **Example of system response:**
+
+   .. code-block:: console
+
+      Nodes [1] with roles ['base-os'] were added to environment 1
+
+#. Verify the status of the nodes:
+
+   .. code-block:: console
+
+      fuel node
+
+   **Example of system response:**
+
+   .. code-block:: console
+
+      id | status   | name             | cluster | ip        | mac               | roles | pending_roles | online | group_id
+      ---|----------|------------------|---------|-----------|-------------------|-------|---------------|--------|---------
+      1  | discover | Untitled (7c:11) | 1       | 10.20.0.3 | 08:00:27:72:7c:11 |       | base-os       | True   | 1
+      2  | discover | Untitled (90:9b) | None    | 10.20.0.4 | 08:00:27:f5:90:9b |       |               | True   | None
+      3  | discover | Untitled (53:f1) | None    | 10.20.0.5 | 08:00:27:14:53:f1 |       |               | True   | None
+
+
+Your node with an empty role has been added to the environment.
+
+.. note::
+
+   By default, Fuel does not apply network configuration.
+   To set up network configuration, run the ``netconfig`` puppet manifests
+   that comes with ``fuel-library``.
+   Fuel automatically executes the following tasks on ``base-os`` nodes only:
+
+   * ``hiera``
+   * ``globals``
+   * ``logging``
+
+   See the `tasks.yaml <https://github.com/openstack/fuel-library/blob/master/deployment/puppet/deployment_groups/tasks.yaml#L130>`__
+   configuration file

userdocs/fuel-user-guide/configure-environment/add-nodes.rst

@@ -43,3 +43,4 @@ For more information, see
    - *System requirements* in *Fuel Installation Guide*
    - :ref:`add-label-ug`
    - :ref:`change-hostname-slave-nodes`
+   - :ref:`cli-nodes-empty-role`