Merge "small change to section_debconf-api-endppoints.xml"
This commit is contained in:
commit
69051aa2c8
@ -7,19 +7,19 @@
|
||||
<title>Register API endpoints</title>
|
||||
<para>All Debian packages for API services, except the
|
||||
<package>heat-api</package> package, register the service in the
|
||||
Identity Service catalog. This feature is helpful because API
|
||||
endpoints are difficult to remember.</para>
|
||||
Identity service catalog. This feature is helpful because API
|
||||
endpoints can be difficult to remember.</para>
|
||||
<note>
|
||||
<para>The <package>heat-common</package> package and not the
|
||||
<package>heat-api</package> package configures the
|
||||
<para>The <package>heat-common</package> package, not the
|
||||
<package>heat-api</package> package, configures the
|
||||
Orchestration service.</para>
|
||||
</note>
|
||||
<para>When you install a package for an API service, you are
|
||||
prompted to register that service. However, after you install or
|
||||
prompted to register that service. After you install or
|
||||
upgrade the package for an API service, Debian immediately removes
|
||||
your response to this prompt from the <package>debconf</package>
|
||||
database. Consequently, you are prompted to re-register the
|
||||
service with the Identity Service. If you already registered the
|
||||
service with the Identity service. If you already registered the
|
||||
API service, respond <literal>no</literal> when you
|
||||
upgrade.</para>
|
||||
<informalfigure>
|
||||
@ -31,7 +31,7 @@
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</informalfigure>
|
||||
<para>This screen registers packages in the Identity Service
|
||||
<para>This screen registers packages in the Identity service
|
||||
catalog:</para>
|
||||
<informalfigure>
|
||||
<mediaobject>
|
||||
@ -42,8 +42,8 @@
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</informalfigure>
|
||||
<para>You are prompted for the Identity Service
|
||||
<literal>admin_token</literal> value. The Identity Service uses
|
||||
<para>You are prompted for the Identity service
|
||||
<literal>admin_token</literal> value. The Identity service uses
|
||||
this value to register the API service. When you set up the
|
||||
<package>keystone</package> package, this value is configured
|
||||
automatically.</para>
|
||||
@ -97,7 +97,7 @@ keystone --os-token ${AUTH_TOKEN} \
|
||||
--adminurl=http://${PKG_ENDPOINT_IP}:${SERVICE_PORT}${SERVICE_URL})</programlisting>
|
||||
<para>The values of <literal>AUTH_TOKEN</literal>, <literal>KEYSTONE_ENDPOINT_IP</literal>,
|
||||
<literal>PKG_ENDPOINT_IP</literal> and <literal>REGION_NAME</literal> depend on the
|
||||
answer you will provide to the debconf prompts. But the values of <literal>SERVICE_NAME</literal>,
|
||||
answer you will provide to the debconf prompts. The values of <literal>SERVICE_NAME</literal>,
|
||||
<literal>SERVICE_TYPE</literal>, <literal>SERVICE_DESC</literal> and <literal>SERVICE_URL</literal>
|
||||
are already pre-wired in each package, so you don't have to remember them.</para>
|
||||
</section>
|
||||
|
Loading…
x
Reference in New Issue
Block a user