Every Debian package that contains an API service contains the debconf logic to register themselves into the Keystone end-point catalogue (at the exception of the Orchestration service, which is configured within the heat-common package and not in the heat-api package). This is very useful because the URLs and ports of each API are difficult to remember. When installing a package containing an API server, the first debconf screen prompts users whether to register the service. However, after the package is installed (or upgraded), the answer to this prompt is immediately removed form the debconf database. As a consequence, this debconf screen displays every time, which enables the user to re-register the API in the Identity Service, but making sure that it is registered only once. If you answer yes to the previous prompt and the API service is already registered in the Identity Service database, do not answer yes again when you upgrade. The following debconf screens are necessary for the package to reach Keystone and register itself in the catalog. The following screen prompts for the value in the admin_token of Keystone, which is necessary for registering an API server in the Identity Service. This admin_token is normally configured automatically when setting-up the keystone package. The following screen is the IP addresses of the service that the user is configuring. The configuration script automatically detects the IP address by using /sbin/route and /sbin/ip (detecting the IP address used by the interface that is connected to the default route). So in most cases, and unless you have a very specific network set up, you simply press ENTER. The last parameter is the region name for the service you are currently configuring. For example, us-east-coast or europe-paris.