<html 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="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">I completely agree about the general rule of thumb. I am only looking at the team that specifically supports openstack. For us frontend support for public clouds is handled by another team/org all together.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">So what I am looking at is the people who are in charge of the care/feeding of the openstack system specifically.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Which means: people who do the dev work on openstack, community participation, the integrations work, the capacity monitoring and server additions, the responding to alarms/monitoring around openstack, the
POC of new features. Any automation work specifically around openstack. Any testing specifically done against openstack.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">For us we have both private and public clouds in 4 different regions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We try to maintain either N or N-1 release cadence.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We build our own packages.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We have lots of existing legacy systems that we need to integrate with.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We have a number of local patches that we carry (the majority around cellsv1).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">So given that would you be willing to share your compute node/engineer ratio?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">___________________________________________________________________<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Kris Lindgren<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Senior Linux Systems Engineer<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">GoDaddy</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">"Van Leeuwen, Robert" <rovanleeuwen@ebay.com><br>
<b>Date: </b>Thursday, September 8, 2016 at 1:33 AM<br>
<b>To: </b>"Kris G. Lindgren" <klindgren@godaddy.com>, OpenStack Operators <openstack-operators@lists.openstack.org><br>
<b>Subject: </b>Re: [Openstack-operators] Openstack team size vs's deployment size<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">> I was hoping to poll other operators to see what their average team size vs’s deployment size is,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">> as I am trying to use this in an internal company discussion.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">> Right now we are in the order of ~260 Compute servers per Openstack Dev/Engineer. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">> So trying to see how we compare with other openstack installs, particularly those running with more than a few hundred compute nodes.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">In my opinion it highly depends on too many things to have general rule of thumb.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Just a few things that I think would impact required team size:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* How many regions you have: setting up and managing a region usually takes more time then adding computes to an existing region</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* How often do you want/need to upgrade</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* Are you offering more then “core IAAS services” e.g. designate/trove/…</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* What supporting things do you need around your cloud and who manage e.g. networking, setting up dns / repositories / authentication systems etc</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* What kind of SDN are you using/ how it needs to be integrated existing networks</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* What kind of hardware you are rolling and what is the average size of the instances. E.G. hosting 1000 tiny instances on a 768GB / 88 core hypervisor will probably create more support tickets
then 10 large instances on a low-spec hypervisor.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* How you handle storage ceph/san/local?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* Do you need live-migration when doing maintenance or are you allowed to bring down an availability zone</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* Are you building your own packages / Using vendor packages</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">* The level of support the users expect and which team is taking care of that</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">In my private cloud experience rolling compute nodes and the controllers are not the bulk of the work.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">The time goes in all the things that you need around the cloud and customizations that takes time.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">It might be a bit different for public cloud providers where you might deliver as-is and do not need any integrations.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">But you might need other things like very reliable billing and good automation around misbehaving users.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Cheer,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Robert van Leeuwen</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>