How do I enable an instance to access the OpenStack and EC2 APIs on the controller? [closed]

asked 2013-09-18 19:46:43 -0600

johnmshields gravatar image

In our Grizzly installation we have separate physical controller, network, and compute servers (as shown http://docs.openstack.org/grizzly/openstack-network/admin/content/connectivity.html (in the docs)).

Everything is working great network-wise except that we have requirements for some VM instances to access the OpenStack and/or EC2 APIs that run on the controller. However, for some reason the network does not allow us to route from an instance to the controller.

Is this normal?

Is it possible to allow network access to the controller from the instances it controls?

Thanks!

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by rbowen
close date 2016-09-22 14:05:45.949025

Comments

I posted a similar question, although allinone deployment...https://ask.openstack.org/en/question/5594/iptables-issue-between-spawned-instance-and-compute-host/ I'm trying quantum networking in place of nova networking to see if I can make that work...haven't worked out all the kinks yet...if that doesn't work may try installing web server proxy (httpd and rewrite module?) on separate vm to forward requests from instances back to compute host

jholmes gravatar imagejholmes ( 2013-10-05 01:26:12 -0600 )edit

Closing: This question relates to a version of OpenStack which has been marked End Of Life - https://releases.openstack.org/ If you are still experiencing the problem with a more recent version of OpenStack, please open a new question. Thanks!

rbowen gravatar imagerbowen ( 2016-09-22 14:05:41 -0600 )edit