Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Thanks for your answer. Indeed I noticed that on my laptop I had the default 192.168.122.x network pre-configured by plain libvirt with name "default" and I wanted to expose that network as external network. But also the L1 hypervisor, being a CentOS 7 system, was pre-configured by libvirt with that same default network and that caused problems. So on L1 hosts, that are the openstack_co1 and openstack_co2 vms, I run:

# virsh net-destroy default
# virsh net-undefine default

so that at the end, from a libvirt point of view:

[root@openstack_co1 ~]# virsh net-list --all
 Name                 State      Autostart     Persistent
[root@openstack_co1 ~]# 

And all went good with openstack so that after assigning a floating ip on 192.168.122.x network to my instance (L2 vm) I was able to connect from my laptop to it via ssh with the configured ssh key (tested both with cirros and with CentOS 7 cloud images). No need to create any particular additional firewall rule on laptop or anywhere.

After all, anyway I reconfigured using a totally different network, to avoid confusion in case I forget to consider again the pre-default libvirt created 192.168.122.x network upon installation of qemu/libvirt packages. Cheers, Gianluca