Thomas Goirand wrote: > Justin B Rye wrote: >> So "Value for my-ip" *must* be inside a private IPv4 range? And we're >> also taking it for granted that it needs to be a unique value on the >> same LAN as its neighbours! So how about something like this: >> >> Template: nova/my-ip >> Type: string >> _Description: Node IP address: >> Please enter the IP address for this node on the private network >> being used locally by OpenStack. >> . >> This value will be stored in the my_ip directive of nova.conf. > > Hi, > > "on the private network" should be changed by "on the management > network", because there's also a virtual machine network which connects > all compute nodes, and the network gateway (eg: neutron-server). > > "used locally by OpenStack" isn't appropriate either, IMO. It's really > used by nova, and not by the neutron agent that does the networking, and > which would be setup on the same machine, for example.
Okay, we're gradually getting there... oh, and now this diagram's beginning to make sense: http://docs.openstack.org/admin-guide-cloud/content/figures/9/a/common/figures/Neutron-PhysNet-Diagram.png We probably can't safely refer to the value of my_ip as just the "node IP address". And eliminating the word "private" would also lose the only hint that it has to be in an RFC1918-style private address range. But how about: Template: nova/my-ip Type: string _Description: IP address on Nova management network: Please enter the IP address for this physical node on the private network being used for OpenStack Compute management. . This value will be stored in the my_ip directive of nova.conf. -- 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] Archive: http://lists.debian.org/[email protected]
