multi-cloudkitty-processor daemons will get the incorrect cost
Bug #1675635 reported by
zhangguoqing
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloudkitty |
New
|
Undecided
|
zhangguoqing |
Bug Description
In our environment that have three controller nodes which everyone controller node had run a clouditty-api daemon and a cloudkitty-procssor daemon. All of them are working well, but we find that the total cost is incorrect. It more than the actual consumed, because the three cloudkitty-
So, I think we should make multi-cloudkitt
Changed in cloudkitty: | |
assignee: | nobody → zhangguoqing (474751729-o) |
To post a comment you must log in.
If I want to run two cloudkitty- processor daemons in one same node, when the second daemon starting , it reports below information:
/opt/stack/ cloudkitty/ cloudkitty/ messaging. py:67: FutureWarning: The access_policy argument is changing its default value to <class 'oslo_messaging .rpc.dispatcher .DefaultRPCAcce ssPolicy' > in version '?', please update the code to explicitly set None as the value: access_policy defaults to LegacyRPCAccess Policy which exposes private methods. Explicitly set access_policy to DefaultRPCAcces sPolicy or ExplicitRPCAcce ssPolicy. 'eventlet' )
endpoints, executor=