Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Learning OpenStack Networking (Neutron), Second Edition

You're reading from   Learning OpenStack Networking (Neutron), Second Edition Wield the power of OpenStack Neutron networking to bring network infrastructure and capabilities to your cloud

Arrow left icon
Product type Paperback
Published in Nov 2015
Publisher Packt
ISBN-13 9781785287725
Length 462 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
James Denton James Denton
Author Profile Icon James Denton
James Denton
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Learning OpenStack Networking (Neutron) Second Edition
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Preparing the Network for OpenStack FREE CHAPTER 2. Installing OpenStack 3. Installing Neutron 4. Building a Virtual Switching Infrastructure 5. Creating Networks with Neutron 6. Managing Security Groups 7. Creating Standalone Routers with Neutron 8. Router Redundancy Using VRRP 9. Distributed Virtual Routers 10. Load Balancing Traffic to Instances 11. Firewall as a Service 12. Virtual Private Network as a Service Additional Neutron Commands Virtualizing the Environment Index

Exploring how instances retrieve their metadata


In Chapter 3, Installing Neutron, we briefly covered the process instances accessing metadata over the network, through either a proxy in the router namespace or the DHCP namespace. The latter is described in the following section.

The DHCP namespace

Instances can access metadata at http://169.254.169.254, followed by a URI that corresponds to the version of metadata, usually /latest. When an instance is connected to a network that does not utilize a Neutron router as the gateway, the instance must learn how to reach the metadata service. This can be accomplished in a few different ways, including:

  • Setting a route manually on the instance

  • Allowing DHCP to provide a route

When enable_isolated_metadata is set to true in the DHCP configuration file at /etc/neutron/dhcp_agent.ini, each DHCP namespace provides a proxy to the metadata service running on the controller node. The proxy service listens directly on port 80, as shown in the following figure...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £13.99/month. Cancel anytime
Visually different images