<div dir="ltr">On the last point, I would lean towards having one weekly (could be monthly) stats script that collects a few numbers we can keep track of ongoing and cease surfacing them in the main ops weekly unless there is a notable portion to it. <br><br>I really don't want to call these target metrics or anything but "total instances in Cloud VPS", "Total tools in Tools", "% on Grid", "% on k8s", "new ldap user count", "new Tools user count", "nova-fullstack failures (? or uptime?)"....if this was run on a cron and sent via email to the labs-admin list before the meeting that would be ideal I guess. <br><br>We have a similar weekly or months stats generator for Phab (user count, issue count, etc) and over time it creates a view of normal. If we suddenly have 100 new ldap users where we usually have 10, or if someone notices new Tools hasn't gone up in a few weeks, etc. These are hard to quantify baselines where we will be happy to we put them in front of our faces over time I believe.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 17, 2017 at 1:53 PM, Bryan Davis <span dir="ltr"><<a href="mailto:bd808@wikimedia.org" target="_blank">bd808@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* nginx ECDH config push breaking various random servers in prod/labs<br>
(to be discussed again next week when Brandon is back)<br>
** Probably will want to think about how to keep packages updated in<br>
Toolforge/WMCS owned projects<br>
<br>
* PCC backend now supports future parser<br>
** email to ops@ coming soon<br>
<br>
* s6 done for new labsdb hosts - T153743<br>
** s2 importing now<br>
<br>
* Faidon building a sheet for FY17/18 procurement planning<br>
** We have "second region deployment" listed for Q1<br>
** RobH is un-busy at the moment so we may want to start that process<br>
<br>
* nodejs debs are built for stretch now.<br>
** We probably should start thinking about when we will move the k8s<br>
containers to stretch.<br>
<br>
* No need to report k8s adoption metrics up to TechOps<br>
** Toolforge k8s is not a TechOps goal anymore<br>
** We have the graphs, do we even need/want to track this internally?<br>
<span class="HOEnZb"><font color="#888888"><br>
Bryan<br>
--<br>
Bryan Davis Wikimedia Foundation <<a href="mailto:bd808@wikimedia.org">bd808@wikimedia.org</a>><br>
[[m:User:BDavis_(WMF)]] Manager, Cloud Services Boise, ID USA<br>
irc: bd808 v:<a href="tel:415.839.6885%20x6855" value="+14158396885">415.839.6885 x6855</a><br>
<br>
______________________________<wbr>_________________<br>
Labs-admin mailing list<br>
<a href="mailto:Labs-admin@lists.wikimedia.org">Labs-admin@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/labs-admin" rel="noreferrer" target="_blank">https://lists.wikimedia.org/<wbr>mailman/listinfo/labs-admin</a><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Chase Pettet</div></div><div>chasemp on <a href="https://phabricator.wikimedia.org/p/chasemp/" target="_blank">phabricator</a> and IRC<br></div></div></div></div></div></div></div></div>
</div>