Performing a PoC of ACI/APIC Neutron integration with OpenStack Juno [0]. My network node doesn't have the router namespace that would normally proxy the metadata HTTP requests as the L3 is being provided by ACI.
The difficulty is cloud-images query this service on boot for various instance properties including the public key for login!
Is there some other way of implementing this service *or* have I made a mistake in my install?
[0]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Yes, metadata service is of course supported. If you are using this heavily, I recommend reaching out through your sales team to get the latest update to the plugins, which has a distributed metadata proxy running on each compute node (which will be available in GA form early next month).
For your specific issue, there is a bit of configuration that may be missing in the dhcp agent we need in some distros. You would need to use this to enable isolated_subnets function and restart the dhcp agent. Give that a try. Its only needed on the older versions of the plugin but may be the issue you are hitting.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This worked perfectly. My instances now receive a static route for the metadata proxy via the DHCP namespace and can get their startup parameters (including the public key) correctly now. Many thanks
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Comments
0 comments
Please sign in to leave a comment.