<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"OTSUKA, Motohiro" <<a href="mailto:yuanying@oeilvert.org">yuanying@oeilvert.org</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, July 13, 2015 at 8:11 PM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [magnum] The way magnum-conductor communicates with k8s master<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div>Hi, Wanghua</div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div dir="ltr">
<div><br>
</div>
<div> Currently magnum-conductor can communicates with k8s master which has a floating ip in all-in-one deployment. But if magnum-conductor is not deployed on the neutron network node which has the br-ex, how can magnum-conductor communicate with k8s master.
The magnum-conductor node then has no access to the k8s master.</div>
</div>
</div>
</div>
</span></blockquote>
<div>Currently this is a limitation of our architecture.</div>
<div> </div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>The floating IP is a public routed network, so it should be able to communicate in a properly setup cloud.</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div dir="ltr">
<div><br>
</div>
<div> Another question:</div>
<div> Magnum-conductor only communicate with k8s master, why k8s minion has a floating ip too? What is the floating ip of k8s minion used for?</div>
<div><br>
</div>
</div>
</div>
</div>
</span></blockquote>
<div>I think, there is no reason.</div>
<div>Historically, Our heat template come from larsks/heat-kubernetes [1] template.</div>
<div>larsks/heat-kubernetes provides floating ip to minion nodes, this is just a reason.</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>The minion floating ips are needed to access the micro-service front ends from the internet.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div><br>
</div>
<div><br>
</div>
<div>[1]: <a href="https://github.com/larsks/heat-kubernetes">https://github.com/larsks/heat-kubernetes</a> </div>
<div><br>
</div>
<div>
<div>Thanks</div>
<div>-Yuanying</div>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>