Saturday, April 05, 2014

The OpenStack Networking components are deployed on the Controller, Compute, and Network nodes in the following configuration:

Controller node: may host the Neutron server service, which provides the networking API and communicates with and tracks the agents.DHCP agent:
spawns and controls dnsmasq processes to provide leases to instances.
This agent also spawns neutron-ns-metadata-proxy processes as part of
the metadata system.Metadata agent:
Provides a metadata proxy to the nova-api-metadata service. The
neutron-ns-metadata-proxy direct traffic that they receive in their
namespaces to the proxy.OVS plugin agent:
Controls OVS network bridges and routes between them via patch, tunnel,
or tap without requiring an external OpenFlow controller. L3 agent: performs L3 forwarding and NAT.

For each network you create, the Network
node (or Controller node, if combined) will have a unique network
namespace (netns) created by the DHCP and Metadata agents. The netns hosts an interface and IP addresses for dnsmasq and the neutron-ns-metadata-proxy. You can view the namespaces with the `ip netns list` command, and can interact with the namespaces with the `ip netns exec namespace command` command.

1. From the instance to a router,
2. Through a NAT rule in the router namespace,
3. To an instance of the neutron-ns-metadata-proxy,
4. To the actual Nova metadata service

Reproducing Dirrect_access_to_Nova_metadataI was able to get list of EC2 metadata available, but not their values. However, my major concern was getting values of metadata obtained in post Direct_access _to_Nova_metadata and also at /openstack location. The last ones seem to me important not less then present in EC2 list . Not all of /openstack metadata are provided by EC2 list.

Commands been run bellow are supposed to verify
Nova&Neutron Set up to be performed successfully , otherwise passing
four steps 1,2,3,4 is supposed to fail and it will force you to analyse
corresponding Logs file ( View References). It doesn't matter did you set up RDO Havana cloud environment manually or via packstackRun on Controller Node :-

Launching browser to http://169.254.169.254/openstack/latest/meta_data.json on another Two Node Neutron GRE+OVS F20 Cluster. Output is sent directly to browser

2. I have provided some information about the OpenStack metadata api, which is available at /openstack, but if you are concerned about the EC2 metadata API.
browser should be launched to http://169.254.169.254/latest/meta-data/