Hi,
As an example you can look at
https://docs.google.com/document/d/1D-1n8nCEFurYzvEBxIRfXfffnImcIPwWSctAG-NXonY/edit?usp=sharing
Under the “Logical Model + Provisioning Status + Operation Status + Statistics”
there are some details on thoughts on how to implement this.
Regards,
-Sam.
From: John Dewey [mailto:[email protected]]
Sent: Thursday, March 06, 2014 2:34 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Health monitoring and statistics
for complex LB configurations.
On Wednesday, March 5, 2014 at 12:41 PM, Eugene Nikanorov wrote:
Hi community,
Another interesting questions were raised during object model discussion about
how pool statistics and health monitoring should be used in case of multiple
vips sharing one pool.
Right now we can query statistics for the pool, and some data like in/out bytes
and request count will be returned.
If we had several vips sharing the pool, what kind of statistics would make
sense for the user?
The options are:
1) aggregated statistics for the pool, e.g. statistics of all requests that has
hit the pool through any VIP
2) per-vip statistics for the pool.
Would it be crazy to offer both? We can return stats for each pool associated
with the VIP as you described below. However, we also offer an aggregated
section for those interested.
IMO, having stats broken out per-pool seem more helpful than only aggregated,
while both would be ideal.
John
Depending on the answer, the statistics workflow will be different.
The good option of getting the statistics and health status could be to query
it through the vip and get it for the whole logical instance, e.g. a call like:
lb-vip-statistics-get --vip-id vip_id
the would result in json that returns statistics for every pool associated with
the vip, plus operational status of all members for the pools associated with
that VIP.
Looking forward to your feedback.
Thanks,
Eugene.
_______________________________________________
OpenStack-dev mailing list
[email protected]<mailto:[email protected]>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev