I was thinking that as well. But the only reason I could think of that he'd be forced to grab public IPs from dhcp was that he had no access to the DHCP server and network infrastructure. I just kind of assumed that would mean that nova would not be able to allocate the IP for intance in any manner congruent with nova's needs.<br>
<br>-Matt<br><br><div class="gmail_quote">On Mon, Aug 13, 2012 at 2:02 PM, Jānis Ģeņģeris <span dir="ltr"><<a href="mailto:janis.gengeris@gmail.com" target="_blank">janis.gengeris@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, Paul<div><br></div><div>Have you tried to use public IP addresses in place of private ones, I mean as fixed IPs? I'm just curious, because I have thought if something like this could work, but actually haven't tried myself. If you check <a href="https://trystack.org/" target="_blank">https://trystack.org/</a> they have something similar working in production, their Horizon lists the VMs IP as private (and it is the only IP the instance gets assigned by default when spawning), but it's actually publicly routable address. So somone who's involved in TryStack could shed some light how they are doing it.<br>
<br>Regards,<br>--janis</div><br><div class="gmail_quote"><div><div class="h5">On Mon, Aug 13, 2012 at 11:31 PM, Paul Walton <span dir="ltr"><<a href="mailto:paul.d.walton@gmail.com" target="_blank">paul.d.walton@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Hello,<br><br>I have been reading tutorials on installing OpenStack on Ubuntu, and so far they all involve giving the VMs a private IP from the Nova configs. However, in my case I will need to generate VMs that have a publicly accessible IP address, and this address will be handed out by a DHCP server that I do not control and is external to OpenStack. I can do this just fine using standard KVM on our current VM server, but I haven't see yet how OpenStack allows this to occur. For example, several of our current VMs run class websites, and some have static IPs assigned to them, while some are dynamically assigned. These must be accessable from the Internet for our students to access. If someone could point me to a document or tutorial on how to do this in OpenStack then that would be great!<br>
<br>Thanks!<span><font color="#888888"><br clear="all"><br>-- <br><br>Paul Walton<br><br>University of Arkansas<br>College of Engineering<br>CSCE Technical Support Team<br>J.B. Hunt Building, Room 440<br>
</font></span><br></div></div><div class="im">_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">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><br></div></blockquote></div>
<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>
<br></blockquote></div><br>