Hi,
After sucessfully configured neutron-api , nova-compute, ovn-central and ovn-chassis and tested all , and everything is working I add one new ovn-dedicated-chassis with following commands .
# juju deploy --channel 23.09/stable --config neutron.yaml ovn-dedicated-chassis --to=us-ovn-chassi-vm-01
# juju integrate ovn-dedicated-chassis:ovsdb ovn-central:ovsdb
# juju integrate ovn-dedicated-chassis:certificates vault:certificates
where the content of neutron.yaml is :
ovn-chassis:
bridge-interface-mappings: 'ovsbr2004:eno3.2004 ovsbr2000:eno2'
ovn-bridge-mappings: 'physnet1:ovsbr2004 physnet2:ovsbr2000'
neutron-api:
neutron-security-groups: true
flat-network-providers: "physnet1 physnet2"
debug: true
verbose: true
ovn-dedicated-chassis:
bridge-interface-mappings: 'ovsbr-us01:enp2s0'
ovn-bridge-mappings: 'physnet-us01:ovsbr-us01'
the juju status ovn* output is :
openstack maas-dc3-default maas-dc3/default 3.1.8 unsupported 23:32:41Z
App Version Status Scale Charm Channel Rev Exposed Message
ceph-osd active 0 ceph-osd reef/stable 577 no Unit is ready (1 OSD)
neutron-api 23.1.0 active 1 neutron-api 2023.2/stable 583 no Unit is ready
neutron-api-mysql-router 8.0.37 active 0 mysql-router 8.0/stable 189 no Unit is ready
neutron-api-plugin-ovn 23.1.0 active 0 neutron-api-plugin-ovn 2023.2/stable 113 no Unit is ready
nova-compute 28.0.1 active 3 nova-compute 2023.2/stable 718 no Unit is ready
ovn-central 22.09.1 active 2 ovn-central 23.09/stable 190 no Unit is ready (northd: active)
ovn-chassis 23.09.0 active 3 ovn-chassis 23.09/stable 233 no Unit is ready
ovn-dedicated-chassis 22.03.3 active 1 ovn-dedicated-chassis 23.09/stable 132 no Unit is ready
Unit Workload Agent Machine Public address Ports Message
neutron-api/0* active idle 24 172.19.0.116 9696/tcp Unit is ready
neutron-api-mysql-router/0* active idle 172.19.0.116 Unit is ready
neutron-api-plugin-ovn/0* active idle 172.19.0.116 Unit is ready
nova-compute/7* active idle 10 172.19.0.14 Unit is ready
ovn-chassis/3* active idle 172.19.0.14 Unit is ready
nova-compute/8 active idle 12 172.19.0.13 Unit is ready
ovn-chassis/2 active idle 172.19.0.13 Unit is ready
nova-compute/9 active idle 13 172.19.0.12 Unit is ready
ovn-chassis/0 active idle 172.19.0.12 Unit is ready
ovn-central/3* active idle 24 172.19.0.116 6641-6642/tcp Unit is ready (northd: active)
ovn-central/4 active idle 25 172.19.0.117 6641-6642/tcp Unit is ready (leader: ovnnb_db, ovnsb_db)
ovn-dedicated-chassis/5* active idle 47 172.16.92.14 Unit is ready
Machine State Address Inst id Base AZ Message
10 started 172.19.0.14 srv-compute-04 ubuntu@22.04 default Deployed
12 started 172.19.0.13 srv-compute-03 ubuntu@22.04 default Deployed
13 started 172.19.0.12 srv-compute-02 ubuntu@22.04 default Deployed
24 started 172.19.0.116 neutron-vm-01 ubuntu@22.04 default Deployed
25 started 172.19.0.117 neutron-vm-02 ubuntu@22.04 default Deployed
47 started 172.16.92.14 us-ovn-chassi-vm-01 ubuntu@22.04 us-psychz-dallas Deployed
The ovn success create the route on it as describe at juju exec --unit ovn-central/4 ‘ovn-nbctl lr-list’
b7ce849c-4e65-48b1-b63f-08ac93133e78 (neutron-509d5f16-8ff3-4b56-80bb-bf6610050045)
a442144c-0566-4d93-bc43-c715482fa131 (neutron-7ba69395-d7cb-4e04-9a63-2f9121c14a57)
The agent was correctly set
root@juju-vm-01:~# openstack network agent list
+--------------------------------------+----------------------+--------------------------+-------------------+-------+-------+----------------------------+
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |
+--------------------------------------+----------------------+--------------------------+-------------------+-------+-------+----------------------------+
| us-ovn-chassi-vm-01.maas | OVN Controller agent | us-ovn-chassi-vm-01.maas | | :-) | UP | ovn-controller |
| srv-compute-04.maas | OVN Controller agent | srv-compute-04.maas | | :-) | UP | ovn-controller |
| 393ddc3c-007c-5e12-822b-d0fe92876ae2 | OVN Metadata agent | srv-compute-04.maas | | :-) | UP | neutron-ovn-metadata-agent |
| srv-compute-03.maas | OVN Controller agent | srv-compute-03.maas | | :-) | UP | ovn-controller |
| 6a84b4c9-0ffe-5712-a246-394dfb2056a5 | OVN Metadata agent | srv-compute-03.maas | | :-) | UP | neutron-ovn-metadata-agent |
| srv-compute-02.maas | OVN Controller agent | srv-compute-02.maas | | :-) | UP | ovn-controller |
| f00652d5-9d85-5a43-ab9c-c07184137e7e | OVN Metadata agent | srv-compute-02.maas | | :-) | UP | neutron-ovn-metadata-agent |
+--------------------------------------+----------------------+--------------------------+-------------------+-------+-------+----------------------------+
all network openvswitch was correctly setup
root@us-ovn-chassi-vm-01:~# ovs-vsctl show
77336bda-281f-47fc-a7c0-24316c8bbd49
Bridge ovsbr-us01
fail_mode: standalone
datapath_type: system
Port ovsbr-us01
Interface ovsbr-us01
type: internal
Port enp2s0
Interface enp2s0
type: system
Port patch-provnet-2a99c055-8f5a-4de7-9e8e-cba7a03d1a3f-to-br-int
Interface patch-provnet-2a99c055-8f5a-4de7-9e8e-cba7a03d1a3f-to-br-int
type: patch
options: {peer=patch-br-int-to-provnet-2a99c055-8f5a-4de7-9e8e-cba7a03d1a3f}
Bridge br-int
fail_mode: secure
datapath_type: system
Port patch-br-int-to-provnet-2a99c055-8f5a-4de7-9e8e-cba7a03d1a3f
Interface patch-br-int-to-provnet-2a99c055-8f5a-4de7-9e8e-cba7a03d1a3f
type: patch
options: {peer=patch-provnet-2a99c055-8f5a-4de7-9e8e-cba7a03d1a3f-to-br-int}
Port br-int
Interface br-int
type: internal
Port ovn-srv-co-1
Interface ovn-srv-co-1
type: geneve
options: {csum="true", key=flow, remote_ip="172.19.8.14"}
Port ovn-srv-co-0
Interface ovn-srv-co-0
type: geneve
options: {csum="true", key=flow, remote_ip="172.19.8.13"}
Port ovn-srv-co-2
Interface ovn-srv-co-2
type: geneve
options: {csum="true", key=flow, remote_ip="172.19.8.12"}
ovs_version: "2.17.9"
At all process the unique error that I found is at /var/log/ovn/ovn-controller.log
2024-06-21T22:40:06.446Z|00048|binding|INFO|Claiming lport cr-lrp-d279bca1-935a-47cd-b0bd-dbed8ac43446 for this chassis.
2024-06-21T22:40:06.446Z|00049|binding|INFO|cr-lrp-d279bca1-935a-47cd-b0bd-dbed8ac43446: Claiming fa:16:3e:f0:4b:d0 XXX.XXX.XXX.XXX/28
2024-06-21T22:40:06.447Z|00050|lflow|WARN|error parsing actions "reg0[15] = check_out_port_sec(); next;": Syntax error at `check_out_port_sec' expecting field name.
when I look at unit now neutron package is installed . Should it not have it ? Is that correct ? the fa:16:3e:f0:4b:d0 is the MAC address from the virtual router , what is missing to create it ?
Best regards,
Saulo