yahoo-eng-team team mailing list archive

[Michael H Wilson <geekinutah@xxxxxxxxx>]

Thanks for the suggestion. If you'd like to propose some code for this
or if you can convince someone else to get on board I would suggest
filing a blueprint. It might also be beneficial to start a mailing list
thread on this and get some additional eyes. A bug report is not really
appropriate for what you are wanting which is a change in intended
behavior.

** Changed in: nova
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1227698

Title:
  nova should distinguish between "private_ip" "accessible_private_ip"
  and "public_ip" (or "private_ip", "public_ip", "internal_ip")

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  As described in https://bugs.launchpad.net/bugs/1227694 I think it
  would be useful to have three categories of IPs in nova.

  While using salt-cloud https://github.com/saltstack/salt-cloud this
  distinction would also be useful in the sense that by default it tries
  to connect to the public IP by ssh to deploy salt. If
  "accessible_private_ip" existed, then it could try that out too if no
  public IP is available. (It also uses some recognized private IP
  ranges to "test" if they are private).

  The other reason for this request is that I find it confusion to use
  the label public_ip on a 172.x.x.x range on a private intranet-only
  cloud infrastructure (for example).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1227698/+subscriptions