yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #13177
[Bug 1302814] [NEW] nova notifications configuration takes tenant_id in config
Public bug reported:
Since Icehouse, Neutron is able to send notifications to Nova API about some networking events.
To make it working, you have to provide "nova_admin_tenant_id" in neutron.conf, which is painful for configuration management when deploying OpenStack in production.
Like in all OpenStack projects, we should have a new parameter
"nova_admin_tenant_name" without hitting Keystone API to ask for the
real ID.
** Affects: neutron
Importance: Undecided
Assignee: Emilien Macchi (emilienm)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Emilien Macchi (emilienm)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1302814
Title:
nova notifications configuration takes tenant_id in config
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Since Icehouse, Neutron is able to send notifications to Nova API about some networking events.
To make it working, you have to provide "nova_admin_tenant_id" in neutron.conf, which is painful for configuration management when deploying OpenStack in production.
Like in all OpenStack projects, we should have a new parameter
"nova_admin_tenant_name" without hitting Keystone API to ask for the
real ID.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1302814/+subscriptions
Follow ups
References