Open Stack

Assaf
Thanks for replying.  I have been playing around metadata service to make sure our product is not breaking it.  If namespace is really needed if we want metadata service, then we need to know about it and document it in our product.
Thanks and Regards! Wanjing

> Date: Wed, 11 Mar 2015 22:38:09 -0400
> From: amuller at redhat.com
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [neutron] [metadata] metadata service when NOT using name space
> 
> Can you explain why are you not using namespaces? (I'm really curious).
> 
> I've been thinking of proposing to deprecate that option only for the simple
> truth that it's not tested and we have no idea if it works anymore, or if anyone
> actually uses it.
> 
> ----- Original Message -----
> > When use_namespaces is True, there will be a namespace metadata proxy
> > launched for either dhcp or router namespace, this proxy will accept metada
> > service request , and then proxy the request to metadata server via metadata
> > agent. But when use_namespaces is False, there is no namespace metadata
> > proxy running, how is the request from vm going to get to matadata server
> > then? I also checked that there is no NAT rule in the iptables. So do we
> > support metadata service with no namespace? If we do , how is it supposed to
> > work? This is Juno.
> > 
> > Regards!
> > 
> > Wanjing Xu
> > 
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150312/f033d366/attachment.html>