<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=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
tt
        {mso-style-priority:99;
        font-family:"Courier New";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1488791003;
        mso-list-template-ids:-86986902;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
--></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-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A use case could be the cloud is behind a proxy and the API port is filtered. In this case, users have to start the service in an alternative port.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hongbin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Adrian Otto [mailto:adrian.otto@rackspace.com]
<br>
<b>Sent:</b> June-12-15 2:22 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for raising this for discussion. Although I do think that the API port humber should be expressed in a URL that the local client can immediately use for connecting a native client to the API, I am not convinced that this needs to
 be a separate attribute on the Bay resource. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In general, I think it’s a reasonable assumption that nova instances will have unique IP addresses assigned to them (public or private is not an issue here) so unique port numbers for running the API services on alternate ports seems like
 it may not be needed. I’d like to have input from at least one Magnum user explaining an actual use case for this feature before accepting this blueprint.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">One possible workaround for this would be to instruct those who want to run nonstandard ports to copy the heat template, and specify a new heat template as an alternate when creating the BayModel, which can implement the port number as
 a parameter. If we learn that this happens a lot, we should revisit this as a feature in Magnum rather than allowing it through an external workaround.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I’d like to have a generic feature that allows for arbitrary key/value pairs for parameters and values to be passed to the heat stack create call so that this, and other values can be passed in using the standard magnum client and API without
 further modification. I’m going to look to see if we have a BP for this, and if not, I will make one.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Adrian<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Jun 11, 2015, at 6:05 PM, Kai Qiang Wu(Kennan) <<a href="mailto:wkqwu@cn.ibm.com">wkqwu@cn.ibm.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">If I understand the bp correctly,
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">the apiserver_port is for public access or API call service endpoint. If it is that case, user would use that info</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">htttp(s)://<ip>:<port></span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">so port is good information for users.</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">If we believe above assumption is right. Then</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">1) Some user not needed to change port, since the heat have default hard code port in that</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">2) If some users want to change port, (through heat, we can do that)  We need add such flexibility for users.</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">That's  bp </span>
<a href="https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1155CC">https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port</span></a><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> try
 to solve. </span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">It depends on how end-users use with magnum.  </span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Welcome to more inputs about this, If many of us think it is not necessary to customize the ports. we can drop the bp.</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Thanks </span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Best Wishes,</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">--------------------------------------------------------------------------------</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Kai Qiang Wu (</span><span lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun">吴开强</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">  Kennan</span><span lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun">)</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: <a href="mailto:wkqwu@cn.ibm.com">wkqwu@cn.ibm.com</a><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park,  <br>
        No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">--------------------------------------------------------------------------------</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Follow your heart. You are miracle!
</span><br>
<br>
<graycol.gif><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#424282">Jay Lau ---06/11/2015 01:17:42 PM---I think that we have a similar bp before:
<a href="https://blueprints.launchpad.net/magnum/+spec/override-nat">https://blueprints.launchpad.net/magnum/+spec/override-nat</a></span><br>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">Jay Lau <<a href="mailto:jay.lau.513@gmail.com">jay.lau.513@gmail.com</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">06/11/2015 01:17 PM</span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject:
</span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint</span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal"><br>
<br>
<br>
I think that we have a similar bp before: <a href="https://blueprints.launchpad.net/magnum/+spec/override-native-rest-port">
https://blueprints.launchpad.net/magnum/+spec/override-native-rest-port</a><br>
<br>
 I have some discussion before with Larsks, it seems that it does not make much sense to customize this port as the kubernetes/swarm/mesos cluster will be created by heat and end user do not need to care the ports,different kubernetes/swarm/mesos cluster will
 have different IP addresses so there will be no port conflict.<br>
<br>
2015-06-11 9:35 GMT+08:00 Kai Qiang Wu <<a href="mailto:wkqwu@cn.ibm.com" target="_blank">wkqwu@cn.ibm.com</a>>:
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">I’m moving this whiteboard to the ML so we can have some discussion to refine it, and then go back and update the whiteboard. </span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"><br>
Source:</span><a href="https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1155CC">https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port</span></a><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"><br>
@Sdake and I have some discussion now, but may need more input from your side.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"><br>
1. keep apserver_port in baymodel, it may only allow admin to have (if we involved policy) create that baymodel, have less flexiblity for other users.</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"><br>
2. apiserver_port was designed in baymodel, if moved from baymodel to bay, it is big change, and if we have other better ways. (it also may apply for<br>
other configuration fileds, like </span><span style="font-size:10.0pt;font-family:Consolas;color:#333333">dns-nameserver</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#2F2F2F"> </span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222">etc.)</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#222222"><br>
Thanks</span><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</span><span lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun">吴开强</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">  Kennan</span><span lang="ZH-CN" style="font-size:10.0pt;font-family:SimSun">)</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </span><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">wkqwu@cn.ibm.com</span></a><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park,  <br>
        No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br>
--------------------------------------------------------------------------------<br>
Follow your heart. You are miracle! </span><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><u><span style="color:blue"><br>
</span></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
-- <br>
Thanks,<br>
<br>
Jay Lau (Guangya Liu)<tt><span style="font-size:10.0pt">__________________________________________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>OpenStack Development Mailing List (not for usage questions)</tt><br>
<tt>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</tt><br>
<tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt></span><o:p></o:p></p>
</div>
<p class="MsoNormal">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>