KATO Tomoyuki 31b31410f9 Factor out Install Guide for Debian with debconf

To simplify the build tool chain,
factor out Install Guide for Debian with debconf.
Continueously, keep Install Guide for Debian without debconf
in the doc/install-guide directory. Also, use the contents
at doc/install-guide as possible for consistency.

On the following patches, clean up doc/install-guide sources
to cleanup the contents and build tool chains.

Change-Id: I8df6b3b382137d08d60f85bc41bcd98ac1f4eb47

2016-05-19 17:37:53 +09:00

3.5 KiB

Raw Blame History

orphan

Register API endpoints

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.

This screen registers packages in the Identity service catalog:

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.

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.

This screen configures the region name for the service. For example, us-east-coast or europe-paris.

The Debian package post installation scripts will then perform the below commands for you:

# openstack --os-token ${AUTH_TOKEN} \
  --os-url=http://${KEYSTONE_ENDPOINT_IP}:35357/v3/ \
  --os-domain-name default \
  --os-identity-api-version=3 \
  service create \
  --name=${SERVICE_NAME} \
  --description="${SERVICE_DESC}" \
  ${SERVICE_TYPE}

# openstack --os-token ${AUTH_TOKEN} \
  --os-url=http://${KEYSTONE_ENDPOINT_IP}:35357/v3/ \
  --os-domain-name default \
  --os-identity-api-version=3 \
  endpoint create \
  --region "${REGION_NAME}" \
  ${SERVICE_NAME} public http://${PKG_ENDPOINT_IP}:${SERVICE_PORT}${SERVICE_URL}

# openstack --os-token ${AUTH_TOKEN} \
  --os-url=http://${KEYSTONE_ENDPOINT_IP}:35357/v3/ \
  --os-domain-name default \
  --os-identity-api-version=3 \
  endpoint create \
  --region "${REGION_NAME}" \
  ${SERVICE_NAME} internal http://${PKG_ENDPOINT_IP}:${SERVICE_PORT}${SERVICE_URL}

# openstack --os-token ${AUTH_TOKEN} \
  --os-url=http://${KEYSTONE_ENDPOINT_IP}:35357/v3/ \
  --os-domain-name default \
  --os-identity-api-version=3 \
  endpoint create \
  --region "${REGION_NAME}" \
  ${SERVICE_NAME} admin http://${PKG_ENDPOINT_IP}:${SERVICE_PORT}${SERVICE_URL}

The values of AUTH_TOKEN, KEYSTONE_ENDPOINT_IP, PKG_ENDPOINT_IP, and REGION_NAME depend on the answer you will provide to the debconf prompts. But the values of SERVICE_NAME, SERVICE_TYPE, SERVICE_DESC, and SERVICE_URL are already pre-wired in each package, so you don't have to remember them.

3.5 KiB Raw Blame History

Register API endpoints

3.5 KiB

Raw Blame History