<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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:11.0pt;
font-family:"Calibri",sans-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.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:924656003;
mso-list-type:hybrid;
mso-list-template-ids:-1683955364 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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">Hi Bruce,<o:p></o:p></p>
<p class="MsoNormal">Please check my inline comments.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Best Regards<o:p></o:p></p>
<p class="MsoNormal">Shuicheng<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></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> Jones, Bruce E <bruce.e.jones@intel.com>
<br>
<b>Sent:</b> Wednesday, September 25, 2019 4:07 AM<br>
<b>To:</b> Lin, Shuicheng <shuicheng.lin@intel.com>; starlingx-discuss@lists.starlingx.io; Hu, Yong <yong.hu@intel.com><br>
<b>Subject:</b> RE: About task "update keystone on the host from the SRPM" of Openstack Train<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Shuicheng, thank you. I tend to agree with you that Option 2 is the way to go, but I have some questions that maybe you or someone else in the community can answer.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo2">
Do we know how long it will take CentOS to produce the RPM on Train’s Keystone?<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-left:.5in">[shuicheng] Per history of Stein and Rocky, it is about 1 month after OpenStack’s release date.<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo2">
Do we know if the Stein Keystone is compatible with Train?<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-left:.5in">[shuicheng] I assume Host keystone (Stein) should have no communication with OpenStack(Train). Please correct me if it is wrong.<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo2">
How did we handle this in the past?<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-left:.5in">[shuicheng] Based on git history, we always use SRPM/RPM from CentOS for keystone.<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l0 level1 lfo2">
Why do we need CentOS to provide an RPM? Can we make our own from upstream Train sources?<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-left:.5in">[shuicheng] We could do it. Option 1 is to use upstream keystone code directly.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> The risk is other dependent packages may need be upgraded together.<o:p></o:p></p>
<p class="MsoNormal"> For Option 2, CentOS help handle the dependency.<o:p></o:p></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"><b>From:</b> Lin, Shuicheng <br>
<b>Sent:</b> Monday, September 23, 2019 6:44 PM<br>
<b>To:</b> <a href="mailto:starlingx-discuss@lists.starlingx.io">starlingx-discuss@lists.starlingx.io</a>; Jones, Bruce E <<a href="mailto:bruce.e.jones@intel.com">bruce.e.jones@intel.com</a>>; Hu, Yong <<a href="mailto:yong.hu@intel.com">yong.hu@intel.com</a>><br>
<b>Subject:</b> About task "update keystone on the host from the SRPM" of Openstack Train<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal">There is a task 36619 [0] “update keystone on the host from the SRPM” of story 2006544 “Integrate with OpenStack Train (master)”.<o:p></o:p></p>
<p class="MsoNormal">Due to Train is not released yet, and it will take sometime for CentOS to support Train and provide the SRPM.<o:p></o:p></p>
<p class="MsoNormal">We have two option as below. And I prefer Option 2, since host keystone is to serve flock service, not OpenStack service.<o:p></o:p></p>
<p class="MsoNormal">Please help provide your suggestion.<o:p></o:p></p>
<p class="MsoNormal">Thanks in advance.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Option 1:<o:p></o:p></p>
<p class="MsoNormal">To catch stx 3.0 release, we need switch SRPM to use upstream git directly.
<o:p></o:p></p>
<p class="MsoNormal">Advantage:<o:p></o:p></p>
<p class="MsoNormal">Host keystone will align with containerized keystone.<o:p></o:p></p>
<p class="MsoNormal">Disadvantage:<o:p></o:p></p>
<p class="MsoNormal">A few keystone related packages need switch from SRPM to git repository.<o:p></o:p></p>
<p class="MsoNormal">Other rpms may need be upgraded also if they have dependency on keystone.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Option 2:<o:p></o:p></p>
<p class="MsoNormal">We defer the upgrade task to stx 4.0, wait until SRPM is available in CentOS mirror.<o:p></o:p></p>
<p class="MsoNormal">Advantage:<o:p></o:p></p>
<p class="MsoNormal">Follow current design, and related packages could be upgraded easily together.<o:p></o:p></p>
<p class="MsoNormal">Disadvantage:<o:p></o:p></p>
<p class="MsoNormal">Host keystone will differ from containerized keystone.<o:p></o:p></p>
<p class="MsoNormal">Not sure when CentOS will provide SRPM for Train.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[0]: <a href="https://storyboard.openstack.org/#!/story/2006544">
https://storyboard.openstack.org/#!/story/2006544</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best Regards<o:p></o:p></p>
<p class="MsoNormal">Shuicheng<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>