<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;}
@font-face
{font-family:"Helvetica Neue";}
/* 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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z
{mso-style-name:author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#4472C4;}
.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><!--[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="color:#4472C4">Hi Bruce,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4">This looks good – definitely lots of information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4">As we discussed, it’d also be good to have a view that rolls everything up into a single view that show us where everything is.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4">I volunteer to take that on – not sure if I’ll try to do it in EtherCalc or what, but I’ll take a stab at it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4">Bill… <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#4472C4"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jones, Bruce E <bruce.e.jones@intel.com> <br>
<b>Sent:</b> Wednesday, December 5, 2018 6:27 PM<br>
<b>To:</b> Khalil, Ghada <Ghada.Khalil@windriver.com>; Rowsell, Brent <Brent.Rowsell@windriver.com>; Zhao, Forrest <forrest.zhao@intel.com>; Peters, Matt <Matt.Peters@windriver.com>; Guo, Ruijing <ruijing.guo@intel.com>; Rowsell, Brent <Brent.Rowsell@windriver.com>;
Legacy, Allain <Allain.Legacy@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Richard, Joseph <Joseph.Richard@windriver.com>; Ho, Teresa <Teresa.Ho@windriver.com>; Bonnell, Patrick <Patrick.Bonnell@windriver.com>; Qin, Kailun <kailun.qin@intel.com>;
Le, Huifeng <huifeng.le@intel.com>; Xu, Chenjie <chenjie.xu@intel.com>; Zhao, Forrest <forrest.zhao@intel.com>; Chilcote Bacco, Derek A <derek.a.chilcote.bacco@intel.com>; Zvonar, Bill <Bill.Zvonar@windriver.com><br>
<b>Cc:</b> starlingx-discuss@lists.starlingx.io<br>
<b>Subject:</b> RE: "Brent's Patch Reduction Plan" - Networking items<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">> Question: I assume the “Current Date” field means forecast date. So to start, it would be the same as the Planned Date and then gets updated if there are changes to the plan. Is that correct? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Yes, that is correct. I added those at Bill’s suggestion so we can see if we’re on track.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> brucej<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b>From:</b> Khalil, Ghada [<a href="mailto:Ghada.Khalil@windriver.com">mailto:Ghada.Khalil@windriver.com</a>]
<br>
<b>Sent:</b> Wednesday, December 5, 2018 3:06 PM<br>
<b>To:</b> Jones, Bruce E <<a href="mailto:bruce.e.jones@intel.com">bruce.e.jones@intel.com</a>>; Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com">Brent.Rowsell@windriver.com</a>>; Zhao, Forrest <<a href="mailto:forrest.zhao@intel.com">forrest.zhao@intel.com</a>>;
Peters, Matt <<a href="mailto:Matt.Peters@windriver.com">Matt.Peters@windriver.com</a>>; Guo, Ruijing <<a href="mailto:ruijing.guo@intel.com">ruijing.guo@intel.com</a>>; Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com">Brent.Rowsell@windriver.com</a>>;
Legacy, Allain <<a href="mailto:Allain.Legacy@windriver.com">Allain.Legacy@windriver.com</a>>; Webster, Steven <<a href="mailto:Steven.Webster@windriver.com">Steven.Webster@windriver.com</a>>; Richard, Joseph <<a href="mailto:Joseph.Richard@windriver.com">Joseph.Richard@windriver.com</a>>;
Ho, Teresa <<a href="mailto:Teresa.Ho@windriver.com">Teresa.Ho@windriver.com</a>>; Bonnell, Patrick <<a href="mailto:Patrick.Bonnell@windriver.com">Patrick.Bonnell@windriver.com</a>>; Qin, Kailun <<a href="mailto:kailun.qin@intel.com">kailun.qin@intel.com</a>>;
Le, Huifeng <<a href="mailto:huifeng.le@intel.com">huifeng.le@intel.com</a>>; Xu, Chenjie <<a href="mailto:chenjie.xu@intel.com">chenjie.xu@intel.com</a>>; Zhao, Forrest <<a href="mailto:forrest.zhao@intel.com">forrest.zhao@intel.com</a>>; Chilcote Bacco,
Derek A <<a href="mailto:derek.a.chilcote.bacco@intel.com">derek.a.chilcote.bacco@intel.com</a>>; Zvonar, Bill <<a href="mailto:Bill.Zvonar@windriver.com">Bill.Zvonar@windriver.com</a>><br>
<b>Cc:</b> <a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Subject:</b> RE: "Brent's Patch Reduction Plan" - Networking items<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Bruce,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I added information in the etherpad for the following items:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">Title</span></b></span><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">:
Host State Management<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">Title</span></b></span><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">:
DHCP agent rescheduling / rebalancing<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">Title</span></b></span><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">:L3
agent rescheduling / rebalancing<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">Title</span></b></span><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">:
Modeling the provider networks in sysinv<o:p></o:p></span></span></p>
<p class="MsoNormal"><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">Title</span></b></span><span class="author-a-klaqz77zz75zz67zvz72zz86zz87zz71zz70zz69zz86zz90z"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black;background:#E0F1F1">:
Patching script rework<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I also moved the last two items to the re-factoring section since they involve STX development versus upstream neutron.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Question: I assume the “Current Date” field means forecast date. So to start, it would be the same as the Planned Date and then gets updated if there are changes to the plan. Is that correct?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Ghada<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Jones, Bruce E [<a href="mailto:bruce.e.jones@intel.com">mailto:bruce.e.jones@intel.com</a>]
<br>
<b>Sent:</b> Wednesday, December 05, 2018 5:08 PM<br>
<b>To:</b> Khalil, Ghada; Rowsell, Brent; Zhao, Forrest; Peters, Matt; Guo, Ruijing; Rowsell, Brent; Legacy, Allain; Webster, Steven; Richard, Joseph; Ho, Teresa; Bonnell, Patrick; Qin, Kailun; Le, Huifeng; Xu, Chenjie; Zhao, Forrest; Chilcote Bacco, Derek
A; Zvonar, Bill<br>
<b>Cc:</b> <a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a><br>
<b>Subject:</b> "Brent's Patch Reduction Plan" - Networking items<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have been working on turning Brent’s plan for patch reduction into actionable work items.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As part of this effort, I discussed with Brent, Bill and Derek ways we can improve our tracking. We agreed to push all tracking out into the open, and until a better tool becomes available, to use Etherpads.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You can find the Etherpad for the Networking part of the Patch Reduction Plan here:
<a href="https://etherpad.openstack.org/p/stx-openstack-patch-refactoring-neutron">
https://etherpad.openstack.org/p/stx-openstack-patch-refactoring-neutron</a>. Please review and update as needed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have updated this with the latest status I have from Forrest. I do not have the latest status from the Networking team beyond that, so there may be additional updates needed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I don’t know if we want to track this work within the Networking sub-project or within the distro.openstack sub-project. I’m setting up a global Etherpad [0] with links to the sub-project pads, so as long as we agree to use these pads
I’m not sure it matters which sub-project owns the work. We will be able to track all of it across the sub-projects. We should decide, of course.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Feedback graciously welcomed!<o:p></o:p></p>
<p class="MsoNormal"> Brucej<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[0] <a href="https://etherpad.openstack.org/p/stx-openstack-patch-refactoring">
https://etherpad.openstack.org/p/stx-openstack-patch-refactoring</a><o:p></o:p></p>
</div>
</body>
</html>