<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:DengXian;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word;text-justify-trim:punctuation">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks for your sharing during PTG, it is impressive.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hope we can have more communication in the future.<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal" align="left" style="text-align:left"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Xin-Ran<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" align="left" style="text-align:left"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Liye Pang(</span><span lang="ZH-CN" style="font-size:11.0pt;font-family:SimSun">逄立业</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">)
<pangliye@inspur.com> <br>
<b>Sent:</b> Tuesday, April 27, 2021 9:59 AM<br>
<b>To:</b> openstack-discuss@lists.openstack.org<br>
<b>Subject:</b> [venus][ptg]Venus vPTG Summary April 2021<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" align="left" style="text-align:left"><o:p> </o:p></p>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"> Thanks for all your participation! We've conducted the first meeting of venus last week and it is successful.
<o:p></o:p></p>
<p class="MsoNormal"> Here's the summary of the topics we have discussed:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> *Progress in the past six months:<o:p></o:p></p>
<p class="MsoNormal"> - Develop devstack-based deployment for venus<o:p></o:p></p>
<p class="MsoNormal"> - Add log retrieval of modules such as vitrage<o:p></o:p></p>
<p class="MsoNormal"> - Develop the configuration, based on which you can retrieve the chain log of the call<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> *Next step:<o:p></o:p></p>
<p class="MsoNormal"> - 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<o:p></o:p></p>
<p class="MsoNormal"> - The configuration, analysis and alarm of Venus will be integrated into horizon in the form of plugin.<o:p></o:p></p>
<p class="MsoNormal"> - Develop a deployment method based on kolla-ansible<o:p></o:p></p>
<p class="MsoNormal"> - (discuss)Summarize the log specifications of some typical scenarios and develop them to venus<o:p></o:p></p>
<p class="MsoNormal"> - Evaluate whether to collect event data (considering usage, pressure, etc.We will continue to discuss with the telemetry project team)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> *Promblem:<o:p></o:p></p>
<p class="MsoNormal"> - Many projects's log records are not standardized, so they can only support full-text retrieval, not multi-dimensional analysis<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Full discussion (PTG etherpad): [1] <a href="https://etherpad.opendev.org/p/venus-xena-ptg">
https://etherpad.opendev.org/p/venus-xena-ptg</a><o:p></o:p></p>
<p class="MsoNormal"> Introduction of venus: [2] <a href="https://youtu.be/mE2MoEx3awM">
https://youtu.be/mE2MoEx3awM</a><o:p></o:p></p>
</div>
</body>
</html>