yahoo-eng-team team mailing list archive

[Eric Windisch <eric@xxxxxxxxxxx>]

Public bug reported:

While the docker registry port is most likely to be static for any given
host during the runtime of the compute service, the registry port is
rediscovered on every spawn/snapshot/etc.

While it is possible that the registry container might be relaunched and
the port moved, the impact of performing extra list_containers calls is
probably not worth it, especially considering that in most cases the
code will fallback to the 'default registry port', or that the deployer
will choose a static port by launching the registry with '-p 5042:5000'

** Affects: nova
     Importance: Undecided
         Status: Confirmed

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

-- 
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/1286171

Title:
  docker performs slow registry port discovery (/w containers list) on
  each spawn/snapshot/etc

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  While the docker registry port is most likely to be static for any
  given host during the runtime of the compute service, the registry
  port is rediscovered on every spawn/snapshot/etc.

  While it is possible that the registry container might be relaunched
  and the port moved, the impact of performing extra list_containers
  calls is probably not worth it, especially considering that in most
  cases the code will fallback to the 'default registry port', or that
  the deployer will choose a static port by launching the registry with
  '-p 5042:5000'

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