File: cinder-api.templates

package info (click to toggle)
cinder 2014.1.3-11
  • links: PTS, VCS
  • area: main
  • in suites: jessie-kfreebsd
  • size: 29,764 kB
  • sloc: python: 106,385; sh: 540; sql: 398; makefile: 111
file content (48 lines) | stat: -rw-r--r-- 1,781 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.

Template: cinder/register-endpoint
Type: boolean
Default: false
_Description: Register Cinder in the Keystone endpoint catalog?
 Each OpenStack service (each API) should be registered in order to be
 accessible. This is done using "keystone service-create" and "keystone
 endpoint-create". This can be done automatically now.
 .
 Note that you will need to have an up and running Keystone server on which to
 connect using the Keystone authentication token.

Template: cinder/keystone-ip
Type: string
_Description: Keystone server IP address:
 Please enter the IP address of the Keystone server, so that cinder-api can
 contact Keystone to do the Cinder service and endpoint creation.

Template: cinder/keystone-auth-token
Type: password
_Description: Keystone authentication token:
 To configure its endpoint in Keystone, cinder-api needs the Keystone
 authentication token.

Template: cinder/endpoint-ip
Type: string
_Description: Cinder endpoint IP address:
 Please enter the IP address that will be used to contact Cinder.
 .
 This IP address should be accessible from the clients that will use this
 service, so if you are installing a public cloud, this should be a public
 IP address.

Template: cinder/region-name
Type: string
Default: regionOne
_Description: Name of the region to register:
 OpenStack supports using availability zones, with each region representing
 a location. Please enter the zone that you wish to use when registering the
 endpoint.