report_interval and polling_interval not supported in neutron-api
Bug #1685788 reported by
Yoshi Kadokawa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
Fix Released
|
Undecided
|
Hua Zhang | ||
OpenStack Neutron API Charm |
Fix Released
|
Medium
|
Hua Zhang | ||
OpenStack Neutron Gateway Charm |
Fix Released
|
Medium
|
Hua Zhang | ||
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Medium
|
Hua Zhang |
Bug Description
When the OpenStack clouds get bigger, more messaging transactions will happen,
which will cause more load on rabbitmq server.
In order to mitigate this, report_interval and polling_interval values are important to adjust accordingly to the size of OpenStack cluster.
However, those values are in [agent] section, which is not configurable with config-flags parameter.
Related branches
lp:~zhhuabj/charm-helpers/lp1685788
- Alex Kavanagh (community): Approve
-
Diff: 36 lines (+15/-0)2 files modifiedcharmhelpers/contrib/openstack/context.py (+12/-0)
tests/contrib/openstack/test_os_contexts.py (+3/-0)
Changed in charm-neutron-api: | |
status: | New → Triaged |
Changed in charm-neutron-gateway: | |
status: | New → Triaged |
Changed in charm-neutron-openvswitch: | |
status: | New → Triaged |
Changed in charm-neutron-api: | |
importance: | Undecided → Medium |
Changed in charm-neutron-gateway: | |
importance: | Undecided → Medium |
Changed in charm-neutron-openvswitch: | |
importance: | Undecided → Medium |
Changed in charm-neutron-api: | |
milestone: | none → 17.08 |
Changed in charm-neutron-gateway: | |
milestone: | none → 17.08 |
Changed in charm-neutron-openvswitch: | |
milestone: | none → 17.08 |
Changed in charm-helpers: | |
status: | New → In Progress |
Changed in charm-neutron-api: | |
status: | Triaged → In Progress |
Changed in charm-neutron-gateway: | |
status: | Triaged → In Progress |
Changed in charm-neutron-openvswitch: | |
status: | Triaged → In Progress |
Changed in charm-helpers: | |
assignee: | nobody → Hua Zhang (zhhuabj) |
Changed in charm-neutron-api: | |
assignee: | nobody → Hua Zhang (zhhuabj) |
Changed in charm-neutron-gateway: | |
assignee: | nobody → Hua Zhang (zhhuabj) |
Changed in charm-neutron-openvswitch: | |
assignee: | nobody → Hua Zhang (zhhuabj) |
Changed in charm-helpers: | |
status: | In Progress → Fix Released |
status: | Fix Released → Fix Committed |
Changed in charm-neutron-api: | |
status: | In Progress → Fix Committed |
Changed in charm-neutron-gateway: | |
status: | In Progress → Fix Committed |
Changed in charm-neutron-openvswitch: | |
status: | In Progress → Fix Committed |
Changed in charm-neutron-api: | |
status: | Fix Committed → Fix Released |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
Changed in charm-neutron-gateway: | |
status: | Fix Committed → Fix Released |
Changed in charm-helpers: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi James, Yoshi,
Based on comment in the bug 1685791, I plan to implement the following charm codes, pls review if it's what you want and if I am missing something, thanks.
1, agent_down_time
Just used by neutron-server, so I think config-flags in neutron-api charm has supported it by:
juju set neutron-api config- flags=' agent_down_ time = 75'
2, polling_interval
Just used by l2 agents, set it in neutron-api charm centrally, then neutron-openvswitch charm gets it via it's relations and set it in [agent] of ml2_conf.ini
3, rpc_response_ timeout
Used by all kinds of agents like l2, l3, dhcp, metadata, meter etc, set it in neutron-api charm centrally, then both neutron-openvswitch charm and neutron-gateway charm get it via it's relations and set it in [default] of neutron.conf
4, report_interval
Used by all kinds of agents like l2, l3, dhcp, metadata, metering etc, set it in neutron-api charm centrally, then both neutron-openvswitch charm and neutron-gateway charm get it via it's relations and set it in [agent] of neutron.conf