After additional research I was able to connect to the meta service.
I added the following lines to local.conf file before running the stack.sh
configuration script:
enable_service q-meta
enable_service q-dhcp
After that I was able to connect to meta service IP address: 169.254.169.254 .
In addition, I created and later connected using SSH to an ubuntu instance
using a private key generated by openstack.
It turned out to be able to use meta service, anther "hidden" service is started,
It is called meta-service-proxy service, It is used to forward meta data request to
real meta service. it is started by the regular q-dhcp service for each tenant.
Hello
After additional research I was able to connect to the meta service.
I added the following lines to local.conf file before running the stack.sh
configuration script:
enable_service q-meta
enable_service q-dhcp
After that I was able to connect to meta service IP address: 169.254.169.254 .
In addition, I created and later connected using SSH to an ubuntu instance
using a private key generated by openstack.
It turned out to be able to use meta service, anther "hidden" service is started,
It is called meta-service-proxy service, It is used to forward meta data request to
real meta service. it is started by the regular q-dhcp service for each tenant.
Thanks and best regards,
Yuli