yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #76683
[Bug 1188218] Re: Support standard ceilometer compute metrics with nova baremetal
** Changed in: tripleo
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1188218
Title:
Support standard ceilometer compute metrics with nova baremetal
Status in Ceilometer:
Fix Released
Status in Ironic:
Fix Released
Status in OpenStack Compute (nova):
Won't Fix
Status in tripleo:
Invalid
Bug 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 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1188218/+subscriptions