Saturday, 2021-08-21

opendevreviewMerged openstack/openstack-ansible stable/wallaby: Fix permissions for files created on repo server  https://review.opendev.org/c/openstack/openstack-ansible/+/80471101:56
depasqualeciao guys15:28
depasqualeI finally managed to install a complete stable/wallaby on my lab (3 compute+2 compute+3 ceph)15:29
depasqualeI am experiencing now issues with neutron (I am pretty sure it is)15:29
depasqualefirst I was able to instantiate a VM (cirros) but no IP was assigned neither for provider (flat) or private net (vxlan)15:30
depasqualenow I am facing a generic: Error: "Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance..:"15:31
depasqualecan someone help me to understand the provider (flat) network configuration in openstack-ansible?15:32
depasqualeI am pretty sure I am wrong for small configs... here my config -> https://paste.opendev.org/show/808230/15:35
depasqualeNOTE: there is an error in paste... the real file is from line 1 to line 228... I think the problem is somewhere from line 65-8715:38
noonedeadpunkdepasquale: `net_name: "physnet1"` - should be real interface on the computes15:47
noonedeadpunkoh, sorry, `host_bind_override: "provider0"` ofc15:47
depasqualeciao thanks for the reply15:48
depasqualeI had renamed the NIC of all the machines to have "provider0" in netplan15:48
noonedeadpunkaha15:49
depasqualeso that I do not have to organize too much groups in the configuration15:49
depasqualephysnet1 is coming from the official doc example here https://docs.openstack.org/openstack-ansible/wallaby/user/prod/provnet_groups.html15:49
noonedeadpunkok, but iirc in neutron then you should have network with type flat and provider-physical-network=physnet1 ?15:51
noonedeadpunkalso - you setup lxb, ovs, ovn?15:52
depasqualethis is as ml2_config.ini looks like in my deploy (/etc/neutron/plugin/ml2/ml2_conf.ini) https://paste.opendev.org/show/808231/15:52
depasqualeI used the default config15:52
noonedeadpunkThis looks correct as long as provider-physical-network=physnet1 for the flat network in neutron15:52
noonedeadpunkthen it's lxb15:53
depasqualefor sure I have removed from conf.d ovn config15:53
depasqualeyes15:53
noonedeadpunkand how networks are created? can you share openstack network show output?15:53
depasqualewait wait there is an error in the file pasted15:53
depasquale [ml2_type_vlan] network_vlan_ranges = physnet1:101:200,physnet1:301:400 # ML2 VXLAN networks15:54
depasqualeline 13 was wrong15:54
noonedeadpunkwell, looks like multiple vlan ranges...15:54
depasqualeif I have physnet1:provider0:<ranges> neutron fails15:55
noonedeadpunkyeah, fair point15:56
depasqualewhat a mess... I do not understand why it is like this...15:57
depasqualein your opinion the openstack_user_config.yml (first link pasted) is correct in lines 65-87?15:58
noonedeadpunkSo I have smth like that in my sandbox https://paste.opendev.org/show/808232/15:58
noonedeadpunkoh, wait15:59
depasqualecan I ask you to share the netplan configuration?15:59
noonedeadpunkyou can;'t have flat and vlan on exact same physical interface15:59
depasqualebecause you have bond0 and bond0.22 and I have for both the same NIC... 16:00
depasqualeoooook 16:00
noonedeadpunkyeah, you can't have that16:00
depasqualethanks16:00
noonedeadpunkbecause neutron will try to manage that interface and will take it for bridge16:00
noonedeadpunkbut, are you sure you really need vlan network?:)16:00
depasqualegive me a second... I will share my netplan config so that you can give me an advice16:00
depasqualehttps://paste.opendev.org/show/808234/16:02
noonedeadpunkI use old interfaces format - not netplan https://paste.opendev.org/show/808233/16:02
depasqualethanks for your time16:02
depasqualeI want to have both private networks (per project) and a provider shared network for "external" internet16:03
noonedeadpunkeventually, to be clear - you don't need bridges br-vxlan and br-vlan - they're used everywhere in docs more as a figure of speach and to be clear and consitent16:03
noonedeadpunkbr-vxlan can be just a regular interface with IP address on it16:03
depasqualeuhm... ok16:04
noonedeadpunkyeah, but why you need vlan?) as I used vlanonly because I wanted to bring in customer networks that are not part of the provider network16:04
noonedeadpunkand with br-vlan, what will neutron do - create like br-vlan.200 and add it to another bridge that also makes not that much sense16:05
depasqualeso what you suggest for my use case?16:05
depasqualeI am behind a router with a net 192.168.4.0/24 that has access to internet16:05
noonedeadpunkI'd say that you don't really need vlan networks (unless you know you need) and just use vxlan for tenant nets16:06
depasqualethe other networks (MTU 9000) are connected to dedicated NIC and switch with no path to internet16:06
depasqualemy undestanding is that vlan are needed in my use cases if I want to allocate floatingIp to make some NAT with the external world (SaaS apps)16:07
noonedeadpunkif you need vlan net and on the same physical interface - just do like me - move "flat" to tagged vlan, and use provider0 as vlan network16:07
noonedeadpunkyou can you vxlan for that and I'd really recommend using it instead of vlan for tenant networks16:07
depasqualeok thanks for the advice16:08
noonedeadpunkbecause with vxlan you don;'t need to care about setiing up switches to server vlan ranges16:08
noonedeadpunk*serve16:08
noonedeadpunkand don't have that limit of amount of networks that are possible to be created16:08
noonedeadpunk(because you can have only 4094 vlan nets)16:09
depasqualeright! thats why in my plan I would create just 1 provider network shared between all "projects"... but I will try your solution 16:10
depasqualejust for my understanding how you make possible for a proxy server (not on openstack) to reach a VM in openstack with vxlan?16:11
depasqualeis an openstack config? or do I have to operate something at "controller" OS level?16:12
noonedeadpunkwell, technically you can configure vxlan on proxy as well....16:12
noonedeadpunkbut dunno - maybe for your usecase vlan is what you need)16:12
noonedeadpunkeventually you can configure vxlan on any machine outside of the openstack until you have same physical net connected16:13
depasqualeI was thinking about it right now :)16:14
noonedeadpunkbut you need to keep in mind that machine when setting up dhcp pool for net because neutron won't be aware about these machines outside of the openstack16:14
depasqualebut the first suggestion that I will considerate in my current configuration is to avoid to have two configurations on the same NIC16:14
noonedeadpunkyeah, totally16:15
depasqualeyes yes my 192.168.4.0/24 net has no DHCP agents16:15
depasqualethere is just a router/firewall and a proxy server 16:15
depasqualeok so let's start from the topic identified16:16
depasqualeif someone read the text before, I have reworked the network configuration and deployed the configuration again, than executed os-neutron-install on all the interested nodes... I am able to start a VM, but the VM is not getting an IP address neither from a provider (non VLAN) net and neither from a vxlan (internal project) net18:26
depasqualehere the log for Cirros after the boot with a net type flat, shared, named "provider" https://paste.opendev.org/show/808235/18:27
depasqualeStarting network: udhcpc: started, v1.29.3 udhcpc: sending discover udhcpc: sending discover udhcpc: sending discover Usage: /sbin/cirros-dhcpc <up|down> udhcpc: no lease, failing FAIL18:28
depasqualeany idea/suggestion?18:28

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!