Just to let you know that the provider network can be used to spin up 
instances, not the best use cases but some production have adopted that 
solution. 

Just my 2 cents, 

Remo 


> On May 2, 2016, at 21:42, Jagga <jagg...@gmail.com> wrote:
> 
> Thanks.  This definitely helps.
> 
> Sent from my iPhone
> 
> On May 2, 2016, at 9:27 PM, Aqsa Malik <aqs...@gmail.com 
> <mailto:aqs...@gmail.com>> wrote:
> 
>> This is by design in OpenStack. A VM can't access the external network 
>> unless assigned a floating IP.
>> Each private network exists behind the router and access to external 
>> networks all happens via SNAT or Floating IPs. Each router uplink and 
>> floating IP is allocated from the external network subnet.
>> Just as an add on,  Hosts without floating IPs can still create outbound 
>> connections to the external network, as the provider router performs SNAT to 
>> the router's external IP. The IP address of the physical router is used as 
>> the gateway_ip of the external network subnet, so the provider has a default 
>> router for Internet traffic.
>> The internal network is for traffic between virtual machines in OpenStack, 
>> and between the virtual machines and the network nodes that provide l3 
>> routes out to the public network (and floating IPs for connections back in 
>> to the VMs).
>> I hope this helps.
>> 
>> On Tue, May 3, 2016 at 8:32 AM, Jagga Soorma <jagg...@gmail.com 
>> <mailto:jagg...@gmail.com>> wrote:
>> Hi Guys,
>> 
>> Need some clarification regarding routing for instances without a floating 
>> ip address. Basically we have instances connected to a priv network that is 
>> also connected to our external network and our security group allows all 
>> egress traffic. However, we can't seem to get to any resource on our 
>> external network till a floating ip address is assigned. Once we assign a 
>> floating ip address we can get out.  Is that by design or is there something 
>> wrong with our configuration?
>> 
>> Thanks.
>> 
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
>> Post to     : openstack@lists.openstack.org 
>> <mailto:openstack@lists.openstack.org>
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
>> 
>> 
>> 
>> 
>> -- 
>> Aqsa Malik
>> Military College of Signals NUST
>> 
>> visit my blog at
>> http://www.techiworld4u.blogspot.com 
>> <http://www.techiworld4u.blogspot.com/>!DSPAM:1,57282df9310471829368241! 
>> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> Post to     : openstack@lists.openstack.org 
> <mailto:openstack@lists.openstack.org>
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> 
> 
> !DSPAM:1,57282df9310471829368241!

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to