VM resume issue network

[MSoares]

Dear people,

I had to install Openstack in a new machine and it was done sucessfully following the Ansible script.

I have configured main.yml files for openstack-compute and openstack-controller Iike follows:
openstack_controller_node: localhost
controller_ip: 127.0.0.1
pub_iface: eth0
flat_iface: veth1

After that I created the initial private network followinf the example:
nova network-create vmprivate --fixed-range-v4 10.11.12.0/24 --fixed-cidr 10.11.12.0/24 --bridge br100 --bridge-interface veth1

My local machine is configured like that:

I was able to enter dashboard and add a base VM and resume it with IP address 10.11.12.05. After that I enter into "Instances"in order to assign floating IP and for my surprise it appears in same range 10.11.12.01. I tryed to dissasociate and associate again and it appears 10.11.12.02. I have done this sequence until reach 10.11.12.05.

I have verified ifconfig and nova service-list and show ID

I do not understand why the IP folatind address is not in 192.168.1.X range? What I have done wrongly?

Please help me in order to achieve this configuration.

Bests regards,

[teiszler]

@MSoares,

Apologies for my absence. I hope you are having a good start to the new year. The floating IP pool should have been created with a separate command. It seems that you possibly used the same CIDR range for both the nova network command and the nova floating-ip-bulk-create command.

nova network-create vmprivate --fixed-range-v4 10.11.12.0/24 --fixed-cidr 10.11.12.0/24 --bridge br100 --bridge-interface veth1

The above command you used is for the creation of the private network segment shared internally by the VM instances. To create the floating IP range, you should execute:

nova floating-ip-bulk-create <cidr>

where the CIDR is a different range from the one you used in the creation of vmprivate. It should likely be on the same network segment as the host machine which is 192.168.1.64/24. This is assuming that whomever is handing out the DHCP addresses to this host will also do so for any other VMs that show up on that segment.

Regards,
Tom

[MSoares]

Dear Tom,

thanks for your help.

I figured out the issue and it was my bad configuration on CIDR.

I have tryed to install and configure Faceswap but I found some issue, I will post it http://forum.openedgecomputing.org/t/faceswap-connectivity-to-server/173/2 and hope that you will helps us.