<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi all,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you to Thierry for providing this SIG!</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
+1 for me and my employer (Yahoo! JAPAN).<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We are interested in building over 1K compute-node scale cluster with an upstreamed code.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;"><br>
</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">From YJ, </span><span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">we can share our way</span><span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;"> of
deploying/operating clusters,</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">because w</span><span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">e've already deployed/operated many
clusters that have several hundred compute.</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">It also may be possible to share the actual performance data of our clusters or to try revised configs to our deployed cluster from this SIG.</span><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Cheers,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">Tatsumi.</span></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>差出人:</b> Arnaud MORIN <arnaud.morin@gmail.com><br>
<b>送信日時:</b> 2019年11月14日 16:10<br>
<b>宛先:</b> Stig Telfer <stig.openstack@telfer.org><br>
<b>CC:</b> openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org><br>
<b>件名:</b> Re: [sig] Forming a Large scale SIG</font>
<div> </div>
</div>
<div>
<div dir="auto">Hi all,
<div dir="auto"><br>
</div>
<div dir="auto">+1 for me and my employer (OVH).</div>
<div dir="auto">We are mostly interested in sharing good practices when deploying a region at scale, and operating it.</div>
<div dir="auto"><br>
</div>
<div dir="auto">For the deployment part, my main pain point is about the configuration parameters I should use on different software (e.g. nova behind wsgi). </div>
<div dir="auto">The current doc is designed to deploy a small pod, but when we are going large, usually some of those params needs tuning. I'd like to identify them and eventually tag them to help other being aware that they are useful at large scale.</div>
<div dir="auto"><br>
</div>
<div dir="auto">About operating, I am pretty sure we can share some good advices as well. E.g., avoid restarting neutron agents in a single shot.</div>
<div dir="auto"><br>
</div>
<div dir="auto">So definitely interested in that group. Thanks for bringing that up.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Cheers.</div>
</div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">Le mer. 13 nov. 2019 à 19:00, Stig Telfer <<a href="mailto:stig.openstack@telfer.org">stig.openstack@telfer.org</a>> a écrit :<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
Hi Thierry & all - <br>
<br>
Thanks for your mail. I’m interested in joining this SIG. Among others, I’m interested in participating in discussions around these common problems:<br>
<br>
- golden signals for scaling bottlenecks (and what to do about them)<br>
- using Ansible at scale<br>
- strategies for simplifying OpenStack functionality in order to scale<br>
<br>
Cheers,<br>
Stig<br>
<br>
<br>
> On 13 Nov 2019, at 11:18, Thierry Carrez <<a href="mailto:thierry@openstack.org" target="_blank" rel="noreferrer">thierry@openstack.org</a>> wrote:<br>
> <br>
> Hi everyone,<br>
> <br>
> In Shanghai we held a forum session to gauge interest in a new SIG to specifically address cluster scaling issues. In the past we had several groups ("Large deployments", "Performance", LCOO...) but those efforts were arguably a bit too wide and those groups
are now abandoned.<br>
> <br>
> My main goal here is to get large users directly involved in a domain where their expertise can best translate into improvements in the software. It's easy for such a group to go nowhere while trying to boil the ocean. To maximize its chances of success and
make it sustainable, the group should have a narrow focus, and reasonable objectives.<br>
> <br>
> My personal idea for the group focus was to specifically address scaling issues within a single cluster: basically identify and address issues that prevent scaling a single cluster (or cell) past a number of nodes. By sharing analysis and experience, the
group could identify common pain points that, once solved, would help raising that number.<br>
> <br>
> There was a lot of interest in that session[1], and it predictably exploded in lots of different directions, including some that are definitely past a single cluster (like making Neutron better support cells). I think it's fine: my initial proposal was more
of a strawman. Active members of the group should really define what they collectively want to work on. And the SIG name should be picked to match that.<br>
> <br>
> I'd like to help getting that group off the ground and to a place where it can fly by itself, without needing external coordination. The first step would be to identify interested members and discuss group scope and objectives. Given the nature of the group
(with interested members in Japan, Europe, Australia and the US) it will be hard to come up with a synchronous meeting time that will work for everyone, so let's try to hold that discussion over email.<br>
> <br>
> So to kick this off: if you are interested in that group, please reply to this email, introduce yourself and tell us what you would like the group scope and objectives to be, and what you can contribute to the group.<br>
> <br>
> Thanks!<br>
> <br>
> [1] <a href="https://etherpad.openstack.org/p/PVG-large-scale-SIG" rel="noreferrer noreferrer" target="_blank">
https://etherpad.openstack.org/p/PVG-large-scale-SIG</a><br>
> <br>
> -- <br>
> Thierry Carrez (ttx)<br>
> <br>
<br>
<br>
</blockquote>
</div>
</div>
</body>
</html>