<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div dir="ltr" id="yui_3_16_0_1_1418831515084_16619"><span id="yui_3_16_0_1_1418831515084_16807">This means whatever tools the operators are using, it need to make sure the IP address assigned inside the VM matches with Openstack has assigned to the port.</span></div><div id="yui_3_16_0_1_1418831515084_17767" dir="ltr"><span id="yui_3_16_0_1_1418831515084_16807">Bringing the question that i had in another thread on the same topic:</span></div><div id="yui_3_16_0_1_1418831515084_17111" dir="ltr"><br><span id="yui_3_16_0_1_1418831515084_16807"></span></div><div id="yui_3_16_0_1_1418831515084_17422" dir="ltr"><span id="yui_3_16_0_1_1418831515084_16807">If one wants to use the provider DHCP server and not have Openstack's DHCP or L3 agent/DVR, it may not be possible to do so even with DHCP disabled in Openstack network. Even if the provider DHCP server is configured with the same start/end range in the same subnet, there's no guarantee that it will match with Openstack assigned IP address for bulk VM launches or when there's a failure case.</span></div><div id="yui_3_16_0_1_1418831515084_19867" dir="ltr"><span id="yui_3_16_0_1_1418831515084_16807">So, how does one deploy external DHCP with Openstack?</span></div><div id="yui_3_16_0_1_1418831515084_20505" dir="ltr"><span id="yui_3_16_0_1_1418831515084_16807"><br></span></div><div id="yui_3_16_0_1_1418831515084_18704" dir="ltr"><span id="yui_3_16_0_1_1418831515084_16807">If Openstack hasn't assigned a IP address when DHCP is disabled for a network, can't port_update be done with the provider DHCP specified IP address to put the anti-spoofing and security rules?</span></div><div id="yui_3_16_0_1_1418831515084_20507" dir="ltr"><span id="yui_3_16_0_1_1418831515084_16807"></span></div><div id="yui_3_16_0_1_1418831515084_20509" dir="ltr">With Openstack assigned IP address, port_update cannot be done since IP address aren't in sync and can overlap.</div><div id="yui_3_16_0_1_1418831515084_21990" dir="ltr"><br></div><div id="yui_3_16_0_1_1418831515084_20511" dir="ltr">Thanks,</div><div id="yui_3_16_0_1_1418831515084_20513" dir="ltr">Paddu<br></div><div class="qtdSeparateBR"><br><br></div><div id="yui_3_16_0_1_1418831515084_16632" style="display: block;" class="yahoo_quoted"><div id="yui_3_16_0_1_1418831515084_16631" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;"><div id="yui_3_16_0_1_1418831515084_16630" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"><div id="yui_3_16_0_1_1418831515084_16629" class="y_msg_container"><br>On 12/16/14 4:30 AM, "Pasquale Porreca" <<a id="yui_3_16_0_1_1418831515084_17761" ymailto="mailto:pasquale.porreca@dektech.com.au" href="mailto:pasquale.porreca@dektech.com.au">pasquale.porreca@dektech.com.au</a>><br>wrote:<br><br>>I understood and I agree that assigning the ip address to the port is<br>>not a bug, however showing it to the user, at least in Horizon dashboard<br>>where it pops up in the main instance screen without a specific search,<br>>can be very confusing.<br>><br>>On 12/16/14 12:25, Salvatore Orlando wrote:<br>>> In Neutron IP address management and distribution are separated<br>>>concepts.<br>>> IP addresses are assigned to ports even when DHCP is disabled. That IP<br>>> address is indeed used to configure anti-spoofing rules and security<br>>>groups.<br>>> <br>>> It is however understandable that one wonders why an IP address is<br>>>assigned<br>>> to a port if there is no DHCP server to communicate that address.<br>>>Operators<br>>> might decide to use different tools to ensure the IP address is then<br>>> assigned to the instance's ports. On XenServer for instance one could<br>>>use a<br>>> guest agent reading network configuration from XenStore; as another<br>>> example, older versions of Openstack used to inject network<br>>>configuration<br>>> into the instance file system; I reckon that today's configdrive might<br>>>also<br>>> be used to configure instance's networking.<br>>> <br>>> Summarising I don't think this is a bug. Nevertheless if you have any<br>>>idea<br>>> regarding improvements on the API UX feel free to file a bug report.<br>>> <br>>> Salvatore<br>>> <br>>> On 16 December 2014 at 10:41, Pasquale Porreca <<br>>> <a ymailto="mailto:pasquale.porreca@dektech.com.au" href="mailto:pasquale.porreca@dektech.com.au">pasquale.porreca@dektech.com.au</a>> wrote:<br>>>><br>>>> Is there a specific reason for which a fixed ip is bound to a port on a<br>>>> subnet where dhcp is disabled? it is confusing to have this info shown<br>>>> when the instance doesn't have actually an ip on that port.<br>>>> Should I fill a bug report, or is this a wanted behavior?<br>>>><br>>>> --<br>>>> Pasquale Porreca<br>>>><br>>>> DEK Technologies<br>>>> Via dei Castelli Romani, 22<br>>>> 00040 Pomezia (Roma)<br>>>><br>>>> Mobile +39 3394823805<br>>>> Skype paskporr<br>>>><br>>>> _______________________________________________<br>>>> OpenStack-dev mailing list<br>>>> <a ymailto="mailto:OpenStack-dev@lists.openstack.org" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>>>> <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><br>>>><br>>> <br>>> <br>>> <br>>> _______________________________________________<br>>> OpenStack-dev mailing list<br>>> <a ymailto="mailto:OpenStack-dev@lists.openstack.org" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>>> <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><br>>> <br>><br>>-- <br>>Pasquale Porreca<br>><br>>DEK Technologies<br>>Via dei Castelli Romani, 22<br>>00040 Pomezia (Roma)<br>><br>>Mobile +39 3394823805<br>>Skype paskporr<br>><br>>_______________________________________________<br>>OpenStack-dev mailing list<br>><a ymailto="mailto:OpenStack-dev@lists.openstack.org" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>><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><br><br><br></div> </div> </div> </div> </div></body></html>