<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:10pt;">
<div>Hi,</div>
<div> </div>
<div>Had the session in Austin summit for the maintenance:</div>
<div><font size="2"><span style="font-size:11pt;"><a href="https://etherpad.openstack.org/p/AUS-ops-Nova-maint"><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>https://etherpad.openstack.org/p/AUS-ops-Nova-maint</u></span></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div>Now the discussion have gotten to a point that should start prototyping a service hosting the maintenance. For maintenance Nova could have a link to this new service, but no functionality for the maintenance should be placed in Nova project. Was working
to have this, but now looking better to have the prototype first:<br>
<a href="https://review.openstack.org/310510/"><font color="#0563C1"><u>https://review.openstack.org/310510/</u></font></a></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div>From the discussion over above review, the new service might have maintenance API connection point that links to host by utilizing “hostid” used in Nova and then there should be “tenant _id” specific end point to get what needed by project. Something like:</div>
<div><font size="2"><span style="font-size:11pt;"><a href="http://maintenancethingy/maintenance/{hostid}"><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>http://</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>maintenancethingy</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>/</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>maintenance/</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>{hostid}</u></span></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"><a href="http://maintenancethingy/maintenance/{hostid}/{tenant_id}"><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>http://</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>maintenancethingy</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>/</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>maintenance/</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>{hostid}/</u></span></font><font size="2" color="#0563C1"><span style="font-size:10pt;"><u>{tenant_id}</u></span></font></a></span></font></div>
<div>This will ensure tenant will not know details about host, but can get needed information about maintenance effecting to his instances.</div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div>In Telco/NFV side we have OPNFV Doctor project that sets the requirements for this from that direction. I am personally interested in that part, but to have this to serve all operator requirements, it is best to bring this here.</div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div>This could be further discussed in Barcelona and should get other people interested to help starting with this. Any suggestion for the Ops session?</div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div>Looking forward,</div>
<div>Tomi</div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
</span></font>
</body>
</html>