All Debian packages for API services, except the heat-api package, register the service in the Identity Service catalog. This feature is helpful because API endpoints are difficult to remember.
![]() | Note |
---|---|
The heat-common package and not the heat-api package configures the Orchestration service. |
When you install a package for an API service, you are
prompted to register that service. However, after you install or
upgrade the package for an API service, Debian immediately removes
your response to this prompt from the debconf
database. Consequently, you are prompted to re-register the
service with the Identity Service. If you already registered the
API service, respond no
when you
upgrade.
![](figures/5/figures/debconf-screenshots/api-endpoint_1_register_endpoint.png)
This screen registers packages in the Identity Service catalog:
![](figures/5/figures/debconf-screenshots/api-endpoint_2_keystone_server_ip.png)
You are prompted for the Identity Service
admin_token
value. The Identity Service uses
this value to register the API service. When you set up the
keystone package, this value is configured
automatically.
![](figures/5/figures/debconf-screenshots/api-endpoint_3_keystone_authtoken.png)
This screen configures the IP addresses for the service. The
configuration script automatically detects the IP address used by
the interface that is connected to the default route
(/sbin/route
and /sbin/ip
).
Unless you have a unique set up for your network, press ENTER.
![](figures/5/figures/debconf-screenshots/api-endpoint_4_service_endpoint_ip_address.png)
This screen configures the region name for the service. For
example, us-east-coast
or
europe-paris
.
![](figures/5/figures/debconf-screenshots/api-endpoint_5_region_name.png)