Christian Perrier wrote: > Last release of Nova includes: > > * Configures Neutron credentials through Debconf. > > ....but the wording of the new templates doesn't fit the style of > other templates. > > The "funny" part is that these templates do have the following warning: > > # These templates have been reviewed by the debian-l10n-english > # team
Ah yes. I remember it well. [...] > Reworded as: > > (please note that I think something should be said about what the hell > is the "my_ip directive" and users should be given a clue of what they > should put there but I have no bloody idea myself) > > Template: nova/my-ip > Type: string > _Description: Value for my_ip: > Please enter the IP address that will be set in the my_ip directive of > nova.conf. It seems to mean "the IP address nova expects to have as an OpenStack compute node" (I see HOWTOs advising not to let the machine get a dynamic DHCP address). All the examples use IPv4 addresses in private ranges... oh, and apparently there's a default setting of use_ipv6=False... so maybe we need to say something like: . This value will be the static address for this compute node, and must use IPv4 unless use_ipv6 is manually set to "True". > > Template: nova/neutron_url > Type: string > Default: http://127.0.0.1:9696 > _Description: Neutron server URL: > Please enter the URL of the Neutron server. > > Template: nova/neutron_admin_tenant_name > Type: string > Default: admin > _Description: Neutron admin tenant name: > Nova needs to be able to communicate with Neutron through Keystone. Therefore > Nova needs to know the Neutron admin tenant, username and password. Maybe that could be shortened a little, but it'll do. [...] -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
