Activity log for bug #1188218

Date Who What changed Old value New value Message
2013-06-06 14:42:00 Mark McLoughlin bug added bug
2013-06-06 14:43:01 Mark McLoughlin bug task added ironic
2013-06-06 14:43:13 Mark McLoughlin bug task added ceilometer
2013-06-06 14:43:24 Mark McLoughlin bug task added tripleo
2013-06-06 14:43:58 Mark McLoughlin description I guess this is a subset of bug #1004468 and https://blueprints.launchpad.net/ceilometer/+spec/non-libvirt-hw However, it's a bit different for nova-baremetal. There is no hypervisor we can query for CPU, disk and network statistics so we can't just add another plugin for ceilometer's compute agent. Instead, we will need an agent which runs inside each baremetal instance and posts samples to ceilometer's public /meters/ API At a first glance, these look like the counters which require a guest agent: cpu Cumulative ns inst ID pollster CPU time used cpu_util Gauge % inst ID pollster CPU utilisation disk.read.request Cumulative request inst ID pollster Number of read requests disk.write.request Cumulative request inst ID pollster Number of write requests disk.read.bytes Cumulative B inst ID pollster Volume of read in B disk.write.bytes Cumulative B inst ID pollster Volume of write in B network.incoming.bytes Cumulative B iface ID pollster number of incoming bytes on the network network.outgoing.bytes Cumulative B iface ID pollster number of outgoing bytes on the network network.incoming.packets Cumulative packets iface ID pollster number of incoming packets network.outgoing.packets Cumulative packets iface ID pollster number of outgoing packets For the other compute counters, we can add baremetal support to the ceilometer compute agent - e.g. these counters: instance Gauge instance inst ID both Duration of instance instance:<type> Gauge instance inst ID both Duration of instance <type> (openstack types) memory Gauge MB inst ID notification Volume of RAM in MB cpus Gauge vcpu inst ID notification Number of VCPUs disk.root.size Gauge GB inst ID notification Size of root disk in GB disk.ephemeral.size Gauge GB inst ID notification Size of ephemeral disk in GB One thing to consider is access control to these counters - we probably don't usually allow tenants to update these counters in, but in this case the tenant will require that ability. It's unclear whether this guest agent would live in ceilometer, nova baremetal or ironic. It's interfacing with (what should be) a very stable ceilometer API, so there's no particular need for it to live in ceilometer. I'm also adding a tripleo task, since I expect tripleo will want these metrics available for things like auto-scaling or simply resource monitoring. I guess this is a subset of bug #1004468 and https://blueprints.launchpad.net/ceilometer/+spec/non-libvirt-hw However, it's a bit different for nova-baremetal. There is no hypervisor we can query for CPU, disk and network statistics so we can't just add another plugin for ceilometer's compute agent. Instead, we will need an agent which runs inside each baremetal instance and posts samples to ceilometer's public /meters/ API At a first glance, these look like the counters which require a guest agent:  cpu Cumulative ns inst ID pollster CPU time used  cpu_util Gauge % inst ID pollster CPU utilisation  disk.read.request Cumulative request inst ID pollster Number of read requests  disk.write.request Cumulative request inst ID pollster Number of write requests  disk.read.bytes Cumulative B inst ID pollster Volume of read in B  disk.write.bytes Cumulative B inst ID pollster Volume of write in B  network.incoming.bytes Cumulative B iface ID pollster number of incoming bytes on the network  network.outgoing.bytes Cumulative B iface ID pollster number of outgoing bytes on the network  network.incoming.packets Cumulative packets iface ID pollster number of incoming packets  network.outgoing.packets Cumulative packets iface ID pollster number of outgoing packets For the other compute counters, we can add baremetal support to the ceilometer compute agent - e.g. these counters:  instance Gauge instance inst ID both Duration of instance  instance:<type> Gauge instance inst ID both Duration of instance <type> (openstack types)  memory Gauge MB inst ID notification Volume of RAM in MB  cpus Gauge vcpu inst ID notification Number of VCPUs  disk.root.size Gauge GB inst ID notification Size of root disk in GB  disk.ephemeral.size Gauge GB inst ID notification Size of ephemeral disk in GB One thing to consider is access control to these counters - we probably don't usually allow tenants to update these counters in, but in this case the tenant will require that ability. It's unclear whether this guest agent would live in ceilometer, nova baremetal or ironic. It's interfacing with (what should be) a very stable ceilometer API, so there's no particular need for it to live in ceilometer. I'm also adding a tripleo task, since I expect tripleo will want these metrics available for things like auto-scaling or simply resource monitoring. We'd need at least a diskimage-builder element which includes the guest agent.
2013-06-06 14:45:30 Mark McLoughlin description I guess this is a subset of bug #1004468 and https://blueprints.launchpad.net/ceilometer/+spec/non-libvirt-hw However, it's a bit different for nova-baremetal. There is no hypervisor we can query for CPU, disk and network statistics so we can't just add another plugin for ceilometer's compute agent. Instead, we will need an agent which runs inside each baremetal instance and posts samples to ceilometer's public /meters/ API At a first glance, these look like the counters which require a guest agent:  cpu Cumulative ns inst ID pollster CPU time used  cpu_util Gauge % inst ID pollster CPU utilisation  disk.read.request Cumulative request inst ID pollster Number of read requests  disk.write.request Cumulative request inst ID pollster Number of write requests  disk.read.bytes Cumulative B inst ID pollster Volume of read in B  disk.write.bytes Cumulative B inst ID pollster Volume of write in B  network.incoming.bytes Cumulative B iface ID pollster number of incoming bytes on the network  network.outgoing.bytes Cumulative B iface ID pollster number of outgoing bytes on the network  network.incoming.packets Cumulative packets iface ID pollster number of incoming packets  network.outgoing.packets Cumulative packets iface ID pollster number of outgoing packets For the other compute counters, we can add baremetal support to the ceilometer compute agent - e.g. these counters:  instance Gauge instance inst ID both Duration of instance  instance:<type> Gauge instance inst ID both Duration of instance <type> (openstack types)  memory Gauge MB inst ID notification Volume of RAM in MB  cpus Gauge vcpu inst ID notification Number of VCPUs  disk.root.size Gauge GB inst ID notification Size of root disk in GB  disk.ephemeral.size Gauge GB inst ID notification Size of ephemeral disk in GB One thing to consider is access control to these counters - we probably don't usually allow tenants to update these counters in, but in this case the tenant will require that ability. It's unclear whether this guest agent would live in ceilometer, nova baremetal or ironic. It's interfacing with (what should be) a very stable ceilometer API, so there's no particular need for it to live in ceilometer. I'm also adding a tripleo task, since I expect tripleo will want these metrics available for things like auto-scaling or simply resource monitoring. We'd need at least a diskimage-builder element which includes the guest agent. I guess this is a subset of bug #1004468 and https://blueprints.launchpad.net/ceilometer/+spec/non-libvirt-hw However, it's a bit different for nova-baremetal. There is no hypervisor we can query for CPU, disk and network statistics so we can't just add another plugin for ceilometer's compute agent. Instead, we will need an agent which runs inside each baremetal instance and posts samples to ceilometer's public /meters/ API At a first glance, these look like the counters which require a guest agent:  cpu CPU time used  cpu_util CPU utilisation  disk.read.request Number of read requests  disk.write.request Number of write requests  disk.read.bytes Volume of read in B  disk.write.bytes Volume of write in B  network.incoming.bytes number of incoming bytes on the network  network.outgoing.bytes number of outgoing bytes on the network  network.incoming.packets number of incoming packets  network.outgoing.packets number of outgoing packets For the other compute counters, we can add baremetal support to the ceilometer compute agent - e.g. these counters:  instance Duration of instance  instance:<type> Duration of instance <type> (openstack types)  memory Volume of RAM in MB  cpus Number of VCPUs  disk.root.size Size of root disk in GB  disk.ephemeral.size Size of ephemeral disk in GB One thing to consider is access control to these counters - we probably don't usually allow tenants to update these counters in, but in this case the tenant will require that ability. It's unclear whether this guest agent would live in ceilometer, nova baremetal or ironic. It's interfacing with (what should be) a very stable ceilometer API, so there's no particular need for it to live in ceilometer. I'm also adding a tripleo task, since I expect tripleo will want these metrics available for things like auto-scaling or simply resource monitoring. We'd need at least a diskimage-builder element which includes the guest agent.
2013-06-10 23:14:40 Robert Collins tripleo: status New Triaged
2013-06-10 23:14:43 Robert Collins tripleo: importance Undecided Medium
2013-06-10 23:15:12 Robert Collins ironic: status New Incomplete
2013-06-20 16:01:48 Julien Danjou ceilometer: status New Triaged
2013-06-21 00:50:22 aeva black bug added subscriber Devananda van der Veen
2013-07-31 18:29:48 aeva black ironic: status Incomplete Triaged
2013-07-31 18:29:51 aeva black ironic: importance Undecided Medium
2013-10-02 13:35:56 vijaykumar bug added subscriber vijaykumar
2013-11-15 05:44:16 Lianhao Lu bug added subscriber Lianhao Lu
2014-04-28 20:00:29 gordon chung ceilometer: importance Undecided Medium
2014-07-08 16:29:43 aeva black ironic: milestone juno-3
2014-08-19 17:22:41 Ruby Loo ironic: status Triaged Fix Committed
2014-09-04 16:19:40 Thierry Carrez ironic: status Fix Committed Fix Released
2014-09-17 21:37:31 Sean Dague nova: status Triaged Won't Fix
2014-10-16 09:59:06 Thierry Carrez ironic: milestone juno-3 2014.2
2015-05-20 12:08:10 Emma Foley bug added subscriber Emma Foley
2015-07-07 16:06:17 gordon chung ceilometer: status Triaged Fix Released
2015-07-07 16:06:31 gordon chung ceilometer: assignee Zhai, Edwin (edwin-zhai)
2016-05-26 23:36:24 Brent Eagles tripleo: status Triaged Incomplete
2019-01-22 13:07:35 Juan Antonio Osorio Robles tripleo: status Incomplete Invalid