openstack/openstack-manuals
Code Issues Proposed changes

[common] Change modules to services

Browse Source 
At now, Orchestration and Telemetry are services, not modules.
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

Change-Id: I49ba2eda9e037046e80583dff9615ff6c15287e5
This commit is contained in:
KATO Tomoyuki 2015-10-28 14:05:51 +09:00
parent 760207b6b4
commit e6f76e0ca7
3 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/common-rst/get_started_orchestration.rst
View File

@ -1,8 +1,8 @@
==============================
OpenStack Orchestration module
==============================
===============================
OpenStack Orchestration service
===============================
The Orchestration module provides a template-based orchestration for
The Orchestration service provides a template-based orchestration for
describing a cloud application by running OpenStack API calls to
generate running cloud applications. The software integrates other core
components of OpenStack into a one-file template system. The templates
@ -12,10 +12,10 @@ advanced functionality, such as instance high availability, instance
auto-scaling, and nested stacks. This enables OpenStack core projects to
receive a larger user base.
The service enables deployers to integrate with the Orchestration module
The service enables deployers to integrate with the Orchestration service
directly or through custom plug-ins.
The Orchestration module consists of the following components:
The Orchestration service consists of the following components:
``heat`` command-line client
A CLI that communicates with the heat-api to run AWS CloudFormation

10
doc/common-rst/get_started_telemetry.rst
View File

@ -1,8 +1,8 @@
==========================
OpenStack Telemetry module
==========================
===========================
OpenStack Telemetry service
===========================
The Telemetry module performs the following functions:
The Telemetry service performs the following functions:
- Efficiently polls metering data related to OpenStack services.
@ -14,7 +14,7 @@ The Telemetry module performs the following functions:
- Creates alarms when collected data breaks defined rules.
The Telemetry module consists of the following components:
The Telemetry service consists of the following components:
A compute agent (``ceilometer-agent-compute``)
Runs on each compute node and polls for resource utilization

6
doc/glossary/glossary-terms.xml
View File

@ -874,7 +874,7 @@
<glossdef>
<para>
AWS CloudFormation allows AWS users to create and manage a
collection of related resources. The Orchestration module
collection of related resources. The Orchestration service
supports a CloudFormation-compatible format (CFN).
</para>
</glossdef>
@ -2163,8 +2163,8 @@
<para>An official OpenStack project. Currently consists of Compute
(nova), Object Storage (swift), Image service (glance), Identity
(keystone), Dashboard (horizon), Networking (neutron), and Block
Storage (cinder), the Telemetry module (ceilometer), Orchestration
module (heat), Database service (trove), Bare Metal service (ironic),
Storage (cinder), Telemetry (ceilometer), Orchestration (heat),
Database service (trove), Bare Metal service (ironic),
Data processing service (sahara). However, this
definition is changing based on
community discussions about the "Big Tent".