How to setup ?

[MrBE4R]

Hi,

We use openstack at univ-nantes in production since 2015 with a network which now exist in our efficientip ipam and I was wondering if it was possible to use an existing neutron network with an existing network in eip ?

What I mean is, we got our neutron network and subnet with a name like this :

• network : public
• subnet : public
  And our eip network like :
• net-os-vm

I was wondering how to make neutron and eip work together ?
In /etc/neutron/neutron.conf I have :

[DEFAULT]
ipam_driver = eip

[solidserver]

address = ipam.intra.univ-nantes.fr
username = the_username_in_eip
password = the_password_in_eip

[eip_connector]

username = neutron
password = the_password_of_neutron
project_name = service
user_domain_id = default
project_domain_id = default
auth_uri = the_url_of_keystone

But when i try to start an instance it failed with an error

Failed : to retrieve [subnet-uuid-in-neutron] in IPAM

I've tried to rename the subnet in openstack from public to net-os-vm with no luck.

Is it possible to bind the neutron network to the eip network? How should I proceed ?

Thanks for your time.
Jeff

[yterrade]

Hello,
This is not a scenario I've thought of.

Your EIP IPAM network should belong to a Block and this Block should belong to a Space. If you do not meet those requirements, I am not sure if there is a solution (I will let you know if I find something).
If the requirements are met, you should then create in Neutron an adress-scope with the same name as your EIP Space, then a subnet-pool inside this address-scope with the same name and range as your EIP block. Then you should be able to move your Neutron subnet to the subnet-pool
(https://docs.openstack.org/neutron/latest/admin/config-subnet-onboard.html)

I did not test all of this, so maybe it will require some other workarounds. Let me know if you need any advice

Cheers
Yoann

[MrBE4R]

Hello,

Thanks for your answer. Unfortunately I didn't manage to get it working (and I will not try any further on a friday :) ). It may be related to the fact that the scope's name contain spaces (even though it would be kind of stupid).

I'll need to redeploy my test-bed in the same configuration as my production to test any further.

Thanks again.

Cheers,
Jeff

[MrBE4R]

Hello again,

Just to be sure, if in eip I have :

• space : foo
• network block : bar
• network cidr : 192.168.0.0/24

In openstack i should set :

• network name : foo
• subnet name : bar
• subnet pool : 192.168.0.0/24

Is that right ?
I'm asking because we use flat networking and thus our compute are using some ip in this range.

Moreover, should we use the dhcp from neutron or from eip ?

Thanks for your time.

Jeff

[yterrade]

Hello,
Using your example, you should have
On your SolidServer

• space : foo
• block : bar - 192.168.0.0/24 (or any other prefix length)
• subnet : sn0 - 192.168.0.0/28 (or any other prefix length)
• pool : pool0 - start 192.168.0.1 end : 192.168.0.14

In Openstack :

• address-scope : foo (with ip_version = 4)
• subnetpool : bar (with prefix 192.168.0.0/24 and address-scope foo)
• subnet : sn0 (with subnetpool bar, network and CIDR 192.168.0.0/28)
• allocation-pool ( with start 192.168.0.1 and end 192.168.0.14). The allocation-pool can be created at the same time as the subnet or using subnet-update (both with --allocation-pool option)

If you start with an empty configuration, every item created in Openstack/Neutron will be replicated on your SolidServer (so you won't have to manually create the space, the block etc ...)

If you are using Horizon dashboard, you may not be able to create this containers hierarchy (I did not find any way to do but maybe it can be done with the latest versions). That's why you should use Neutron cli to do it (This might doable with Openstack cli as well but in my version there is no way to create a subnet with a mask value different from 16)

You should notice that there is no relationship between the IPAM and the Neutron Network.

So far, I have always used Neutron DHCP and activated IPAM to DHCP replication on the SolidServer. This is probably the quickest way to set everything up.

Yoann