Public bug reported:
In ancient times keystone replaced the port for the compute service
based upon it's local configuration file (templated catalog). This is
silly and should not be done as it means you would need to configure the
compute_port variable in keystone for it to reflect the catalog instead
of updating the static data.
The keystone config should have no bearing on the nova port.
** Affects: keystone
Importance: Wishlist
Assignee: Morgan Fainberg (mdrnstm)
Status: In Progress
** Changed in: keystone
Status: New => Triaged
** Changed in: keystone
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1335278
Title:
compute_port in config options
Status in OpenStack Identity (Keystone):
In Progress
Bug description:
In ancient times keystone replaced the port for the compute service
based upon it's local configuration file (templated catalog). This is
silly and should not be done as it means you would need to configure
the compute_port variable in keystone for it to reflect the catalog
instead of updating the static data.
The keystone config should have no bearing on the nova port.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1335278/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
