<html><body>
<p><font size="3" face="sans-serif">Hi Adrian</font><font size="2" face="sans-serif">,</font><br>
<br>
<font size="2" face="sans-serif">If I summarize your option, it would be,</font><br>
<br>
<font size="2" face="sans-serif">1) Have a function like this,</font><br>
<br>
<font size="2" face="sans-serif"> magnum bay-create --name swarmbay --baymodel swarmbaymodel </font><font size="2" face="sans-serif"><b>--baymodel-property-override apiserver_port=8766</b></font><font size="2" face="sans-serif"> </font><br>
<br>
<br>
<font size="2" face="sans-serif">And then magnum pass that property to override baymodel default properties, and create the bay.</font><br>
<br>
<br>
<font size="2" face="sans-serif">2) You talked another BP, about adjust bay api_address to be a URL, For bay attribute api_address should be return format like following</font><br>
<font size="2" face="sans-serif">tcp://192.168.45.12:7622 or <a href="http://192.168.45.12:8234">http://192.168.45.12:8234</a></font><br>
<br>
<br>
<br>
<br>
<font size="2" face="sans-serif">Is it ?</font><br>
<br>
<br>
<font size="2" face="sans-serif">Thanks</font><br>
<br>
<font size="2" face="sans-serif">Best Wishes,</font><br>
<font size="2" face="sans-serif">--------------------------------------------------------------------------------</font><br>
<font size="2" face="sans-serif">Kai Qiang Wu (吴开强 Kennan）<br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: wkqwu@cn.ibm.com<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</font><br>
<font size="2" face="sans-serif">--------------------------------------------------------------------------------</font><br>
<font size="2" face="sans-serif">Follow your heart. You are miracle! </font><br>
<br>
<img width="16" height="16" src="cid:1__=C7BBF4F5DF96C4088f9e8a93df938@cn.ibm.com" border="0" alt="Inactive hide details for Adrian Otto ---06/13/2015 02:04:22 PM---Hongbin, Good use case. I suggest that we add a parameter to "><font size="2" color="#424282" face="sans-serif">Adrian Otto ---06/13/2015 02:04:22 PM---Hongbin, Good use case. I suggest that we add a parameter to magnum bay-create that will allow the u</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Adrian Otto <adrian.otto@rackspace.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">06/13/2015 02:04 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<font size="3" face="sans-serif">Hongbin,</font><br>
<br>
<font size="3" face="sans-serif">Good use case. I suggest that we add a parameter to magnum bay-create that will allow the user to override the baymodel.apiserver_port attribute with a new value that will end up in the bay.api_address attribute as part of the URL. This approach assumes implementation of the magnum-api-address-url blueprint. This way we solve for the use case, and don't need a new attribute on the bay resource that requires users to concatenate multiple attribute values in order to get a native client tool working.<br>
</font><br>
<font size="3" face="sans-serif">Adrian</font><br>
<font size="3" face="sans-serif"><br>
On Jun 12, 2015, at 6:32 PM, Hongbin Lu <</font><a href="mailto:hongbin.lu@huawei.com"><font size="3" color="#0000FF" face="sans-serif"><u>hongbin.lu@huawei.com</u></font></a><font size="3" face="sans-serif">> wrote:<br>
</font>
<ul style="padding-left: 36pt"><font size="2" color="#1F497D" face="Calibri">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.</font><br>
<font size="2" color="#1F497D" face="Calibri"> </font><br>
<font size="2" color="#1F497D" face="Calibri">Best regards,</font><br>
<font size="2" color="#1F497D" face="Calibri">Hongbin</font><br>
<font size="2" color="#1F497D" face="Calibri"> </font><br>
<font size="2" face="Tahoma"><b>From:</b></font><font size="2" face="Tahoma"> Adrian Otto [</font><a href="mailto:adrian.otto@rackspace.com"><font size="2" color="#0000FF" face="Tahoma"><u>mailto:adrian.otto@rackspace.com</u></font></a><font size="2" face="Tahoma">] </font><font size="2" face="Tahoma"><b><br>
Sent:</b></font><font size="2" face="Tahoma"> June-12-15 2:22 PM</font><font size="2" face="Tahoma"><b><br>
To:</b></font><font size="2" face="Tahoma"> OpenStack Development Mailing List (not for usage questions)</font><font size="2" face="Tahoma"><b><br>
Subject:</b></font><font size="2" face="Tahoma"> Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint</font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="3" face="Times New Roman">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. </font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="3" face="Times New Roman">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.</font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="3" face="Times New Roman">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.</font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="3" face="Times New Roman">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.</font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="3" face="Times New Roman">Adrian</font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="3" face="Times New Roman"> </font>
<ul style="padding-left: 36pt"><font size="3" face="Times New Roman">On Jun 11, 2015, at 6:05 PM, Kai Qiang Wu(Kennan) <</font><a href="mailto:wkqwu@cn.ibm.com"><font size="3" color="#0000FF" face="Times New Roman"><u>wkqwu@cn.ibm.com</u></font></a><font size="3" face="Times New Roman">> wrote:</font><br>
<font size="3" face="Times New Roman"> </font><br>
<font size="2" face="Arial">If I understand the bp correctly, </font><font size="3" face="Times New Roman"><br>
</font><font size="2" face="Arial"><br>
the apiserver_port is for public access or API call service endpoint. If it is that case, user would use that info</font><font size="3" face="Times New Roman"><br>
</font><font size="2" face="Arial"><br>
htttp(s)://<ip>:<port></font><font size="3" face="Times New Roman"><br>
</font><font size="2" face="Arial"><br>
so port is good information for users.</font><font size="3" face="Times New Roman"><br>
<br>
</font><font size="2" face="Arial"><br>
If we believe above assumption is right. Then</font><font size="3" face="Times New Roman"><br>
</font><font size="2" face="Arial"><br>
1) Some user not needed to change port, since the heat have default hard code port in that</font><font size="3" face="Times New Roman"><br>
</font><font size="2" face="Arial"><br>
2) If some users want to change port, (through heat, we can do that) We need add such flexibility for users.<br>
That's bp </font><a href="https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port" target="_blank"><font size="2" color="#1155CC" face="Arial"><u>https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port</u></font></a><font size="2" face="Arial"> try to solve. </font><font size="3" face="Times New Roman"><br>
</font><font size="2" face="Arial"><br>
It depends on how end-users use with magnum. </font><font size="3" face="Times New Roman"><br>
<br>
</font><font size="2" face="Arial"><br>
Welcome to more inputs about this, If many of us think it is not necessary to customize the ports. we can drop the bp.</font><font size="3" face="Times New Roman"><br>
<br>
</font><font size="2" face="Arial"><br>
Thanks </font><font size="3" face="Times New Roman"><br>
<br>
</font><font size="2" face="Arial"><br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</font><font size="2" face="sans-serif">吴开强</font><font size="2" face="Arial"> Kennan</font><font size="2" face="sans-serif">）</font><font size="2" face="Arial"><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </font><a href="mailto:wkqwu@cn.ibm.com"><font size="2" color="#0000FF" face="Arial"><u>wkqwu@cn.ibm.com</u></font></a><font size="2" face="Arial"><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! </font><font size="3" face="Times New Roman"><br>
<br>
<graycol.gif></font><font size="2" color="#424282" face="Arial">Jay Lau ---06/11/2015 01:17:42 PM---I think that we have a similar bp before: </font><a href="https://blueprints.launchpad.net/magnum/+spec/override-nat"><font size="2" color="#0000FF" face="Arial"><u>https://blueprints.launchpad.net/magnum/+spec/override-nat</u></font></a><font size="3" face="Times New Roman"><br>
</font><font size="1" color="#5F5F5F" face="Arial"><br>
From: </font><font size="1" face="Arial">Jay Lau <</font><a href="mailto:jay.lau.513@gmail.com"><font size="1" color="#0000FF" face="Arial"><u>jay.lau.513@gmail.com</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>
To: </font><font size="1" face="Arial">"OpenStack Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size="1" color="#0000FF" face="Arial"><u>openstack-dev@lists.openstack.org</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>
Date: </font><font size="1" face="Arial">06/11/2015 01:17 PM</font><font size="1" color="#5F5F5F" face="Arial"><br>
Subject: </font><font size="1" face="Arial">Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint</font><br>
<hr width="100%" size="2" align="left" noshade><br>
<font size="3" face="Times New Roman"><br>
<br>
<br>
I think that we have a similar bp before: </font><a href="https://blueprints.launchpad.net/magnum/+spec/override-native-rest-port"><font size="3" color="#0000FF" face="Times New Roman"><u>https://blueprints.launchpad.net/magnum/+spec/override-native-rest-port</u></font></a><font size="3" face="Times New Roman"><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 <</font><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><font size="3" color="#0000FF" face="Times New Roman"><u>wkqwu@cn.ibm.com</u></font></a><font size="3" face="Times New Roman">>: </font>
<ul style="padding-left: 36pt"><font size="2" color="#222222" face="Arial">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. <br>
<br>
Source:</font><a href="https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port" target="_blank"><font size="2" color="#1155CC" face="Arial"><u>https://blueprints.launchpad.net/magnum/+spec/configurable-coe-api-port</u></font></a><font size="3" face="Times New Roman"><br>
</font><font size="2" color="#222222" face="Arial"><br>
<br>
@Sdake and I have some discussion now, but may need more input from your side.</font><font size="3" face="Times New Roman"><br>
</font><font size="2" color="#222222" face="Arial"><br>
<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.</font><font size="3" face="Times New Roman"><br>
</font><font size="2" color="#222222" face="Arial"><br>
<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 </font><font size="2" color="#333333" face="Consolas">dns-nameserver</font><font size="2" color="#2F2F2F" face="Arial"> </font><font size="2" color="#222222" face="Arial">etc.)</font><font size="3" face="Times New Roman"><br>
<br>
</font><font size="2" color="#222222" face="Arial"><br>
<br>
Thanks</font><font size="3" face="Times New Roman"><br>
<br>
</font><font size="2" face="Arial"><br>
<br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (</font><font size="2" face="sans-serif">吴开强</font><font size="2" face="Arial"> Kennan</font><font size="2" face="sans-serif">）</font><font size="2" face="Arial"><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: </font><a href="mailto:wkqwu@cn.ibm.com" target="_blank"><font size="2" color="#0000FF" face="Arial"><u>wkqwu@cn.ibm.com</u></font></a><font size="2" face="Arial"><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! </font><font size="3" face="Times New Roman"><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank"><font size="3" color="#0000FF" face="Times New Roman"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></a><font size="3" color="#0000FF" face="Times New Roman"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="#0000FF" face="Times New Roman"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a></ul>
<font size="3" face="Times New Roman"><br>
<br>
<br>
-- <br>
Thanks,<br>
<br>
Jay Lau (Guangya Liu)</font><font size="2" face="Courier New">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><font size="2" color="#0000FF" face="Courier New"><u>OpenStack-dev-request@lists.openstack.org</u></font></a><font size="2" face="Courier New">?subject:unsubscribe</font><font size="2" color="#0000FF" face="Courier New"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><font size="2" color="#0000FF" face="Courier New"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><br>
<font size="3" face="Times New Roman">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><font size="3" color="#0000FF" face="Times New Roman"><u>OpenStack-dev-request@lists.openstack.org</u></font></a><font size="3" face="Times New Roman">?subject:unsubscribe</font><font size="3" color="#0000FF" face="Times New Roman"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><font size="3" color="#0000FF" face="Times New Roman"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a></ul>
<font size="3" face="Times New Roman"> </font>
<p><font size="3" face="sans-serif">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org"><font size="3" color="#0000FF" face="sans-serif"><u>OpenStack-dev-request@lists.openstack.org</u></font></a><font size="3" face="sans-serif">?subject:unsubscribe</font><font size="3" color="#0000FF" face="sans-serif"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><font size="3" color="#0000FF" face="sans-serif"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><tt><font size="2">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
</font></tt>
<p></ul>
</body></html>