← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2048773] [NEW] neutron-meter-agent do not support ovn driver

 

Public bug reported:

I have deployed a openstack system manually, the neutron driver is ovn,
but when I want to install ceilometer, I found it does not include
bandwidth metric, and then I install neutron-meter-agent, but in
/etc/neutron/metering_agent.ini, the interface_driver option only
support ovs and linuxbridge, how should I use neutron meter to enable
ceilometer? or is there some other setting?

here are some config in my system:
/etc/neutron/plugin.ini
[DEFAULT]
[ml2]
mechanism_drivers = ovn
type_drivers = local,flat,vlan,geneve
tenant_network_types = geneve
extension_drivers = port_security,qos,port_device_profile
overlay_ip_version = 4
path_mtu = 9064
[ml2_type_geneve]
vni_ranges = 1:4095
max_header_size = 38

[ml2_type_vlan]
network_vlan_ranges = ext

[ml2_type_flat]
flat_networks = provider

[securitygroup]
enable_security_group = true

[sriov_driver]
vnic_type_prohibit_list = remote-managed

[ovn]
ovn_l3_scheduler = leastloaded
ovn_metadata_enabled = True
enable_distributed_floating_ip = False
ovn_nb_connection = tcp:192.168.122.94:6641
ovn_sb_connection = tcp:192.168.122.94:6642
ovn_emit_need_to_frag = true

/etc/ceilometer/polling.yaml
---
sources:
    - name: some_pollsters
      interval: 300
      meters:
        - cpu
        - cpu_l3_cache
        - memory.usage
        - network.incoming.bytes
        - network.incoming.packets
        - network.outgoing.bytes
        - network.outgoing.packets
        - disk.device.read.bytes
        - disk.device.read.requests
        - disk.device.write.bytes
        - disk.device.write.requests
        - hardware.cpu.util
        - hardware.cpu.user
        - hardware.cpu.nice
        - hardware.cpu.system
        - hardware.cpu.idle
        - hardware.cpu.wait
        - hardware.cpu.kernel
        - hardware.cpu.interrupt
        - hardware.memory.used
        - hardware.memory.total
        - hardware.memory.buffer
        - hardware.memory.cached
        - hardware.memory.swap.avail
        - hardware.memory.swap.total
        - hardware.system_stats.io.outgoing.blocks
        - hardware.system_stats.io.incoming.blocks
        - hardware.network.ip.incoming.datagrams
        - hardware.network.ip.outgoing.datagrams
        - image.size
        - image.download
        - bandwidth
        - switch.port
        - compute.node.cpu.frequency


this command does not show anything.
[root@controller ~]# openstack metric list | grep bandwidth
[root@controller ~]#

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  I have deployed a openstack system manually, the neutron driver is ovn,
  but when I want to install ceilometer, I found it does not include
  bandwidth metric, and then I install neutron-meter-agent, but in
  /etc/neutron/metering_agent.ini, the interface_driver option only
  support ovs and linuxbridge, how should I use neutron meter to enable
  ceilometer? or is there some other setting?
+ 
+ here are some config in my system:
+ /etc/neutron/plugin.ini
+ [DEFAULT]
+ [ml2]
+ mechanism_drivers = ovn
+ type_drivers = local,flat,vlan,geneve
+ tenant_network_types = geneve
+ extension_drivers = port_security,qos,port_device_profile
+ overlay_ip_version = 4
+ path_mtu = 9064
+ [ml2_type_geneve]
+ vni_ranges = 1:4095
+ max_header_size = 38
+ 
+ [ml2_type_vlan]
+ network_vlan_ranges = ext
+ 
+ [ml2_type_flat]
+ flat_networks = provider
+ 
+ [securitygroup]
+ enable_security_group = true
+ 
+ [sriov_driver]
+ vnic_type_prohibit_list = remote-managed
+ 
+ [ovn]
+ ovn_l3_scheduler = leastloaded
+ ovn_metadata_enabled = True
+ enable_distributed_floating_ip = False
+ ovn_nb_connection = tcp:192.168.122.94:6641
+ ovn_sb_connection = tcp:192.168.122.94:6642
+ ovn_emit_need_to_frag = true
+ 
+ /etc/ceilometer/polling.yaml
+ ---
+ sources:
+     - name: some_pollsters
+       interval: 300
+       meters:
+         - cpu
+         - cpu_l3_cache
+         - memory.usage
+         - network.incoming.bytes
+         - network.incoming.packets
+         - network.outgoing.bytes
+         - network.outgoing.packets
+         - disk.device.read.bytes
+         - disk.device.read.requests
+         - disk.device.write.bytes
+         - disk.device.write.requests
+         - hardware.cpu.util
+         - hardware.cpu.user
+         - hardware.cpu.nice
+         - hardware.cpu.system
+         - hardware.cpu.idle
+         - hardware.cpu.wait
+         - hardware.cpu.kernel
+         - hardware.cpu.interrupt
+         - hardware.memory.used
+         - hardware.memory.total
+         - hardware.memory.buffer
+         - hardware.memory.cached
+         - hardware.memory.swap.avail
+         - hardware.memory.swap.total
+         - hardware.system_stats.io.outgoing.blocks
+         - hardware.system_stats.io.incoming.blocks
+         - hardware.network.ip.incoming.datagrams
+         - hardware.network.ip.outgoing.datagrams
+         - image.size
+         - image.download
+         - bandwidth
+         - switch.port
+         - compute.node.cpu.frequency
+ 
+ 
+ this command does not show anything.
+ [root@controller ~]# openstack metric list | grep bandwidth
+ [root@controller ~]#

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2048773

Title:
  neutron-meter-agent do not support ovn driver

Status in neutron:
  New

Bug description:
  I have deployed a openstack system manually, the neutron driver is
  ovn, but when I want to install ceilometer, I found it does not
  include bandwidth metric, and then I install neutron-meter-agent, but
  in /etc/neutron/metering_agent.ini, the interface_driver option only
  support ovs and linuxbridge, how should I use neutron meter to enable
  ceilometer? or is there some other setting?

  here are some config in my system:
  /etc/neutron/plugin.ini
  [DEFAULT]
  [ml2]
  mechanism_drivers = ovn
  type_drivers = local,flat,vlan,geneve
  tenant_network_types = geneve
  extension_drivers = port_security,qos,port_device_profile
  overlay_ip_version = 4
  path_mtu = 9064
  [ml2_type_geneve]
  vni_ranges = 1:4095
  max_header_size = 38

  [ml2_type_vlan]
  network_vlan_ranges = ext

  [ml2_type_flat]
  flat_networks = provider

  [securitygroup]
  enable_security_group = true

  [sriov_driver]
  vnic_type_prohibit_list = remote-managed

  [ovn]
  ovn_l3_scheduler = leastloaded
  ovn_metadata_enabled = True
  enable_distributed_floating_ip = False
  ovn_nb_connection = tcp:192.168.122.94:6641
  ovn_sb_connection = tcp:192.168.122.94:6642
  ovn_emit_need_to_frag = true

  /etc/ceilometer/polling.yaml
  ---
  sources:
      - name: some_pollsters
        interval: 300
        meters:
          - cpu
          - cpu_l3_cache
          - memory.usage
          - network.incoming.bytes
          - network.incoming.packets
          - network.outgoing.bytes
          - network.outgoing.packets
          - disk.device.read.bytes
          - disk.device.read.requests
          - disk.device.write.bytes
          - disk.device.write.requests
          - hardware.cpu.util
          - hardware.cpu.user
          - hardware.cpu.nice
          - hardware.cpu.system
          - hardware.cpu.idle
          - hardware.cpu.wait
          - hardware.cpu.kernel
          - hardware.cpu.interrupt
          - hardware.memory.used
          - hardware.memory.total
          - hardware.memory.buffer
          - hardware.memory.cached
          - hardware.memory.swap.avail
          - hardware.memory.swap.total
          - hardware.system_stats.io.outgoing.blocks
          - hardware.system_stats.io.incoming.blocks
          - hardware.network.ip.incoming.datagrams
          - hardware.network.ip.outgoing.datagrams
          - image.size
          - image.download
          - bandwidth
          - switch.port
          - compute.node.cpu.frequency

  
  this command does not show anything.
  [root@controller ~]# openstack metric list | grep bandwidth
  [root@controller ~]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2048773/+subscriptions