Hi, I'm not sure if your message was incomplete, did you intend to add your solution? I haven't checked the docs in a while, but there are several ways to access VMs, for example: - Horizon Dashboard - Something like virt-manager - 'virsh console <instance>' directly on the hypervisor (requires privileged access and a running qemu agent) - SSH access via floating IP This is just from the top of my head, there are probably many more options. For the Horizon Dashboard access you need to have a nova-novncproxy service running on the control node(s). The access through a bastion node has to be configured individually, for example via SSH tunneling. So there's no single correct answer but plenty of options. If you have found a solution for your specific use case, nobody would mind if you shared it. :-) Regards, Eugen Zitat von ussefelboukhari@gmail.com:

In test environments, some users choose to build their infrastructure inside KVM virtual machines, while others use cloud instances such as EC2 bare-metal that support nested virtualization. After deploying OpenStack, many of them face a major issue: they are unable to access their OpenStack instances.

I encountered the same problem myself. After several weeks of intensive troubleshooting, I eventually found a solution. That is why I would like to share this solution with others who face the same issue, and hopefully contribute to the OpenStack community by providing recommendations that could be added to the official OpenStack documentation.