<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=us-ascii">
<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:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:199829257;
mso-list-type:hybrid;
mso-list-template-ids:-1449911264 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:20.0pt">Fellow Open Stackers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">I have been thinking on how to handle SmartNICs, GPUs, FPGA handling across different projects within OpenStack with Cyborg taking a leading role in it.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Cyborg is important project and address accelerator devices that are part of the server and potentially switches and storage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">It is address 3 different use cases and users there are all grouped into single project.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:20.0pt">Application user need to program a portion of the device under management, like GPU, or SmartNIC for that app usage. Having a common way to do it across
different device families and across different vendor is very important. And that has to be done every time a VM is deploy that need usage of a device. That is tied with VM scheduling.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:20.0pt">Administrator need to program the whole device for specific usage. That covers the scenario when device can only support single tenant or single use
case. That is done once during OpenStack deployment but may need reprogramming to configure device for different usage. May or may not require reboot of the server.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="font-size:20.0pt">Administrator need to setup device for its use, like burning specific FW on it. This is typically done as part of server life-cycle event.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:20.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">The first 2 cases cover application life cycle of device usage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">The last one covers device life cycle independently how it is used.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Managing life cycle of devices is Ironic responsibility, One cannot and should not manage lifecycle of server components independently. Managing server devices outside server management violates customer service
agreements with server vendors and breaks server support agreements.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Nova and Neutron are getting info about all devices and their capabilities from Ironic; that they use for scheduling. We should avoid creating new project for every new component of the server and modify nova
and neuron for each new device. (the same will also apply to cinder and manila if smart devices used in its data/control path on a server).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Finally we want Cyborg to be able to be used in standalone capacity, say for Kubernetes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Thus, I propose that Cyborg cover use cases 1 & 2, and Ironic would cover use case 3.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Thus, move all device Life-cycle code from Cyborg to Ironic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Concentrate Cyborg of fulfilling the first 2 use cases.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Simplify integration with Nova and Neutron for using these accelerators to use existing Ironic mechanism for it.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Create idempotent calls for use case 1 so Nova and Neutron can use it as part of VM deployment to ensure that devices are programmed for VM under scheduling need.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Create idempotent call(s) for use case 2 for TripleO to setup device for single accelerator usage of a node.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">[Propose similar model for CNI integration.]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Let the discussion start!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:20.0pt">Thanks.,<br>
Arkady<o:p></o:p></span></p>
</div>
</body>
</html>