openstack/venus-specs
Code Issues Proposed changes

change the show style of the document

Browse Source 
Change-Id: I5ccf44c4cf59b88f7d3b54df2e207142bb82babc
This commit is contained in:
jiasirui 2021-05-26 16:41:22 +08:00
parent 3cc717c439
commit 4a3d777113
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
priorities/xena-priorities.rst
View File

@ -19,29 +19,38 @@ https://openinfrafoundation.formstack.com/forms/april2021_vptg_survey
https://ethercalc.net/oz7q0gds9zfi
Topics:
Background
============
It’s difficult to retrieve logs, since there are many modules in the platform, e.g. systems service, compute, storage, network and other platform services.
Because of distributed and interaction between components of the cloud platform, and scattered logs between components, it will take more time to locate problems.
Current function
============
Provide a simple and easy-to-use way to retrieve all log and the context .
Realize log association, field value statistics, and provide multi-scene and multi-dimensional visual analysis reports.
Current progress
============
Develop devstack-based depAdd log retrieval of other modules such as vitrage
loyment for venus
Develop the configuration, based on which you can retrieve the chain log of the call
Next step
============
Develop alarm task code to set threshold for the number of error logs of different modules at different times, and provides alarm services and notification services
The configuration, analysis and alarm of Venus will be integrated into horizon in the form of plugin.
Develop a deployment method based on kolla-ansible
Evaluate whether to collect event data (considering usage, pressure, etc.)
Summarize the log specifications of some typical scenarios and develop them to venus
promblem
Promblem
============
Many projects's log records are not standardized, so they can only support full-text retrieval, not multi-dimensional analysis