<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>I think Anthony suggested that we don’t use enable_dhcp and choose a different attribute which can provide values, instead of TRUE/FALSE.</div><div><br></div><div>In case that customer have an external DHCPv6 server and an internal OpenStack router, then dnsmasq should still send out RA with right bits set (depending on Stateful or Stateless), which in turn triggers VM to initiate right messages to solicit IPv6 address and/or Optional Information. This use case is also captured in the table show in the previous email. I copied and pasted it below.</div><div><br></div><div>Shixiong</div><div><br></div><div><img apple-inline="yes" id="5EAB0635-512C-444A-8B55-C35E5678B684" height="533" width="693" apple-width="yes" apple-height="yes" src="cid:ED9CB3CC-F323-4900-8A17-1CB0B12FDE90@nc.rr.com"></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><br><div><div>On Jan 22, 2014, at 7:07 AM, Ian Wells <<a href="mailto:ijw.ubuntu@cack.org.uk">ijw.ubuntu@cack.org.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">On 21 January 2014 22:46, Veiga, Anthony <span dir="ltr"><<a href="mailto:Anthony_Veiga@cable.comcast.com" target="_blank">Anthony_Veiga@cable.comcast.com</a>></span> wrote:<br><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div class="im">
<div><br>
</div>
<span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div style="word-wrap:break-word">
<div>Hi, Sean and Xuhan:</div>
<div><br>
</div>
<div>I totally agree. This is not the ultimate solution with the assumption that we had to use “enable_dhcp”.</div>
<div><br>
</div>
<div>We haven’t decided the name of another parameter, however, we are open to any suggestions. As we mentioned during the meeting, the second parameter should highlight the need of addressing. If so, it should have at least four values:</div>
<div><br>
</div>
<div>1) off (i.e. address is assigned by external devices out of OpenStack control)</div>
<div>2) slaac (i.e. address is calculated based on RA sent by OpenStack dnsmasq)</div>
<div>3) dhcpv6-stateful (i.e. address is obtained from OpenStack dnsmasq acting as DHCPv6 stateful server)</div>
<div>4) dhcpv6-stateless (i.e. address is calculated based on RA sent from either OpenStack dnsmasq, or external router, and optional information is retrieved from OpenStack dnsmasq acting as DHCPv6 stateless server)</div>
</div>
</div>
</blockquote>
</span>
</div></div></blockquote><div><br></div><div>So how does this work if I have an external DHCPv6 server and an internal router? (How baroque do we have to get?) enable_dhcp, for backward compatibility reasons, should probably disable *both* RA and DHCPv6, despite the name, so we can't use that to disable the DHCP server. We could add a *third* attribute, which I hate as an idea but does resolve the problem - one flag for each of the servers, one for the mode the servers are operating in, and enable_dhcp which needs to DIAF but will persist till the API is revved.<br>
-- <br></div><div>Ian.<br></div></div></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>