Hi Rob,
On 24/10/13 11:06, Robert Collins wrote:
> Hi there.
>
> Create a provider network in Neutron to represent your external lan,
> and either a) use that as your only network - in which case you'll
> need your external router to handle 169.254.169.254 - the metadata
> agent - or b) add that as a second network when you spawn instances,
> in which case the private overlay network you have running will have
> addresses assigned by neutron - and you'll want to push a host route
> for 169.254.169.254 as you'll have your default route be via the
> provider network..
Okay, is this using Flat Networking or something else?
What's the significance of the 169.254.169.254 address? If I were to
add a host route at the external router, to where do I route it?
Would this give the VM unfettered access to the network? I found last
time I tried flat networking, some packet filtering still occurred.
--
Stuart Longland
Contractor
_ ___
\ /|_) | T: +61 7 3535 9619
\/ | \ | 38b Douglas Street F: +61 7 3535 9699
SYSTEMS Milton QLD 4064 http://www.vrt.com.au
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
