<p>I'd like to add i am not at all familiar with the quantum stack atm. You may want to tag this thread with quantum and ask again. OpenStack is slated to integrate quantum in folsom and a workable solution may exist there. I do think my last suggestion has some merit and i hope you give it an honest assessment.</p>
<p>Cheers<br>
Matt</p>
<div class="gmail_quote">On Aug 13, 2012 8:15 PM, "Narayan Desai" <<a href="mailto:narayan.desai@gmail.com">narayan.desai@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Aug 13, 2012 at 9:16 PM, Paul Walton <<a href="mailto:paul.d.walton@gmail.com">paul.d.walton@gmail.com</a>> wrote:<br>
> I can certainly see the advantage to the current approach when you own the<br>
> network, but there are so many cases where you simply can't modify the<br>
> existing infrastructure. In my case, there is simply no reason for me to<br>
> manage the network. Up until now, all I have needed was for my VM to make a<br>
> DHCP request, and get a public IP. However, I really like the idea of<br>
> OpenStack, and my boss is convinced that we need to be using it. So, unless<br>
> OpenStack has the ability to do this, then I'm left with having my boss<br>
> petition the network admins to give us a subnet to use. Which may take a<br>
> fair amount of time.<br>
><br>
> I don't like the idea of hacking a solution together, so I guess the real<br>
> question is, can OpenStack currently do this or not?<br>
<br>
I think that the answer is no, OpenStack can't make use of externally<br>
controlled (via DHCP) addresses. There isn't a way that I can think of<br>
that you can make the APIs function properly in that mode.<br>
<br>
That said, you don't need a complete network allocation in order to<br>
use it either. As long as you have a set of statically assigned<br>
addresses, you can configure OpenStack to use them. Even if the<br>
network admins will only give you a few addresses, that will work<br>
properly. The major issue is the fact that dhcp can change your<br>
address while an instance has an address allocated to it, so if that<br>
can't happen, you should be ok.<br>
-nld<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote></div>