openstack/fuel-docs
Code Issues Proposed changes

Add crosslinks to the described features

Browse Source 
Change-Id: I9e98033ef5156f8e5f318cc5b0118ea30db782e5
This commit is contained in:
Evgeny Konstantinov
2016-04-20 09:22:54 -07:00
parent 7e332baeaa
commit 8d8961bd89
2 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
userdocs/fuel-user-guide/maintain-environment/deployment-history.rst
View File

@@ -22,7 +22,7 @@ To get the information on a deployment task:
.. code-block:: console
fuel deployment-tasks --task-id <task-id> --statuses ready, pending --nodes 1,2
fuel2 task history show <task-id> --nodes 3 --statuses error skipped
fuel2 task history show <task-id> --nodes 3 --statuses error skipped
where <task-id> is the ID of the deployment task.
@@ -32,4 +32,4 @@ To get the information on a deployment task:
The commands ``fuel deployment-tasks`` and
``fuel2 task history show`` show the deployment tasks
running on nodes; for example, database, upload_configuration,
hiera, and so on.
hiera, and so on.

5
userdocs/release-notes/new_features.rst
View File

@@ -36,11 +36,13 @@ This section lists these improvements:
* Fuel now stores detailed information about all deployments. You can download
the actual cluster settings, network configuration, and serialized cluster
data.
See :ref:`deployment-history` and :ref:`deployment-information`.
* You can now execute a particular deployment graph with the ability to merge
it with the existing deployment graphs of the upstream master release.
This allows you to implement complex orchestrated workflows -- bugfixes
application, reference architecture altering, or even upgrades.
See :ref:`custom-graph`.
* Fuel now supports lifecycle management tasks based on the history of
cluster states. This data-driven feature allows the deployment engineers
@@ -48,6 +50,7 @@ This section lists these improvements:
expressions that can be computed within the context of cluster configuration.
You can now control the tasks assignment and execution depending on the
configuration or changes in the configuration.
See :ref:`data-driven`.
* All deployment tasks that Fuel uses when configuring OpenStack are now
idempotent. This enables the lifecycle management features that require
@@ -82,4 +85,4 @@ This section lists these improvements:
resource utilization thresholds for the OpenStack services and underlying
software components using ``cgroups``. Specifying optimal values helps
to increase performance and reliability of your cloud.
See `blueprint <https://blueprints.launchpad.net/fuel/+spec/cgroups>`__.
See :ref:`cgroups-intro`.