<font size=2 face="sans-serif">There is also a tempest patch now to ease
some of the libvirt-specific keys checked in the new diagnostics tests
there:</font>
<br>
<br><a href=https://review.openstack.org/#/c/51412/><font size=3 color=blue><u>https://review.openstack.org/#/c/51412/</u></font></a><font size=3>
</font>
<br>
<br><font size=2 face="sans-serif">To relay some of my concerns that I
put in that patch:</font>
<br>
<br><font size=2 face="Arial"><i>I'm not sure how I feel about this. It
should probably be more generic but I think we need more than just a change
in tempest to enforce it, i.e. we should have a nova patch that changes
the doc strings for the abstract compute driver method to specify what
the minimum keys are for the info returned, maybe a doc api sample change,
etc?</i></font>
<br>
<br><font size=2 face="Arial"><i>For reference, here is the mailing list
post I started on this last week:</i></font>
<br>
<br><a href="http://lists.openstack.org/pipermail/openstack-dev/2013-October/016385.html"><font size=2 color=#0000a1 face="Arial"><i>http://lists.openstack.org/pipermail/openstack-dev/2013-October/016385.html</i></font></a>
<br>
<br><font size=2 face="Arial"><i>There are also docs here (these examples
use xen and libvirt):</i></font>
<br>
<br><a href="http://docs.openstack.org/grizzly/openstack-compute/admin/content/configuring-openstack-compute-basics.html"><font size=2 color=#0000a1 face="Arial"><i>http://docs.openstack.org/grizzly/openstack-compute/admin/content/configuring-openstack-compute-basics.html</i></font></a>
<br>
<br><font size=2 face="Arial"><i>And under procedure 4.4 here:</i></font>
<br>
<br><a href="http://docs.openstack.org/admin-guide-cloud/content/ch_introduction-to-openstack-compute.html#section_manage-the-cloud"><font size=2 color=#0000a1 face="Arial"><i>http://docs.openstack.org/admin-guide-cloud/content/ch_introduction-to-openstack-compute.html#section_manage-the-cloud</i></font></a><font size=2 face="sans-serif"><br>
</font>
<br><font size=2 face="sans-serif">=============</font>
<br>
<br><font size=2 face="sans-serif">I also found this wiki page related
to metering and the nova diagnostics API:</font>
<br>
<br><a href=https://wiki.openstack.org/wiki/EfficientMetering/FutureNovaInteractionModel><font size=3 color=blue><u>https://wiki.openstack.org/wiki/EfficientMetering/FutureNovaInteractionModel</u></font></a><font size=3>
</font>
<br>
<br><font size=2 face="sans-serif">So it seems like if at some point this
will be used with ceilometer it should be standardized a bit which is what
the Tempest part starts but I don't want it to get lost there.</font>
<br><font size=2 face="sans-serif"><br>
</font>
<br><font size=1 face="Arial">Thanks,</font>
<br>
<br><font size=3 color=#8f8f8f face="Arial"><b>MATT RIEDEMANN</b></font><font size=1 face="Arial"><br>
Advisory Software Engineer<br>
Cloud Solutions and OpenStack Development</font>
<table width=680 style="border-collapse:collapse;">
<tr height=8>
<td width=680 colspan=2 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<hr>
<tr valign=top height=8>
<td width=418 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=1 color=#4181c0 face="Arial"><b>Phone:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-253-7622</font><font size=1 color=#4181c0 face="Arial"> | <b>Mobile:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-990-1889</font><font size=1 color=#4181c0 face="Arial"><b><br>
E-mail:</b></font><font size=1 color=#5f5f5f face="Arial"> </font><a href=mailto:mriedem@us.ibm.com target=_blank><font size=1 color=#5f5f5f face="Arial"><u>mriedem@us.ibm.com</u></font></a>
<td width=261 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<div align=right><img src=cid:_1_09B39E1009B3987C0011B74C86257C03 width=83 height=30 alt=IBM><font size=1 color=#5f5f5f face="Arial"><br>
<br>
3605 Hwy 52 N<br>
Rochester, MN 55901-1407<br>
United States</font></div></table>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Gary Kotton <gkotton@vmware.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">OpenStack Development
Mailing List <openstack-dev@lists.openstack.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">10/12/2013 01:42 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
[nova] Looking for clarification on the diagnostics API</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=1 face="Calibri">Yup, it seems to be hypervisor specific.
I have added in the Vmware support following you correcting in the Vmware
driver.</font>
<br><font size=1 face="Calibri">Thanks</font>
<br><font size=1 face="Calibri">Gary </font>
<br>
<br><font size=2 face="Calibri"><b>From: </b>Matt Riedemann <</font><a href=mailto:mriedem@us.ibm.com><font size=2 color=blue face="Calibri"><u>mriedem@us.ibm.com</u></font></a><font size=2 face="Calibri">><b><br>
Reply-To: </b>OpenStack Development Mailing List <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size=2 color=blue face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size=2 face="Calibri">><b><br>
Date: </b>Thursday, October 10, 2013 10:17 PM<b><br>
To: </b>OpenStack Development Mailing List <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size=2 color=blue face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size=2 face="Calibri">><b><br>
Subject: </b>Re: [openstack-dev] [nova] Looking for clarification on the
diagnostics API</font>
<br>
<br><font size=2 face="sans-serif">Looks like this has been brought up
a couple of times:</font><font size=1 face="Calibri"><br>
</font><font size=1 color=blue face="Calibri"><u><br>
</u></font><a href=https://lists.launchpad.net/openstack/msg09138.html><font size=3 color=blue face="Calibri"><u>https://lists.launchpad.net/openstack/msg09138.html</u></font></a><font size=1 face="Calibri"><br>
</font><font size=1 color=blue face="Calibri"><u><br>
</u></font><a href=https://lists.launchpad.net/openstack/msg08555.html><font size=3 color=blue face="Calibri"><u>https://lists.launchpad.net/openstack/msg08555.html</u></font></a><font size=1 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
But they seem to kind of end up in the same place I already am - it seems
to be an open-ended API that is hypervisor-specific.</font><font size=1 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
</font><font size=1 face="Calibri"><br>
</font><font size=1 face="Arial"><br>
Thanks,</font><font size=1 face="Calibri"> <br>
</font><font size=3 color=#8f8f8f face="Arial"><b><br>
MATT RIEDEMANN</b></font><font size=1 face="Arial"><br>
Advisory Software Engineer<br>
Cloud Solutions and OpenStack Development</font>
<table width=680 style="border-collapse:collapse;">
<tr height=8>
<td width=678 colspan=2 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;">
<hr>
<tr valign=top height=8>
<td width=416 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=1 color=#4181c0 face="Arial"><b>Phone:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-253-7622</font><font size=1 color=#4181c0 face="Arial"> | <b>Mobile:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-990-1889</font><font size=1 color=#4181c0 face="Arial"><b><br>
E-mail:</b></font><font size=1 color=#5f5f5f face="Arial"> </font><a href=mailto:mriedem@us.ibm.com target=_blank><font size=1 color=#5f5f5f face="Arial"><u>mriedem@us.ibm.com</u></font></a>
<td width=259 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;">
<div align=right><img src=cid:_1_09BCCED809BCCAD80011B74C86257C03 width=83 height=30 alt=IBM><font size=1 color=#5f5f5f face="Arial"><br>
<br>
3605 Hwy 52 N<br>
Rochester, MN 55901-1407<br>
United States</font></div></table>
<br><font size=1 face="Calibri"><br>
<br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
From: </font><font size=1 face="sans-serif">Matt
Riedemann/Rochester/IBM</font><font size=1 color=#5f5f5f face="sans-serif"><br>
To: </font><font size=1 face="sans-serif">"OpenStack
Development Mailing List" <</font><a href="mailto:openstack-dev@lists.openstack.org"><font size=1 color=blue face="sans-serif"><u>openstack-dev@lists.openstack.org</u></font></a><font size=1 face="sans-serif">>,
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Date: </font><font size=1 face="sans-serif">10/10/2013
02:12 PM</font><font size=1 color=#5f5f5f face="sans-serif"><br>
Subject: </font><font size=1 face="sans-serif">[nova]
Looking for clarification on the diagnostics API</font><font size=1 face="Calibri"><br>
</font>
<hr noshade><font size=1 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
Tempest recently got some new tests for the nova diagnostics API [1] which
failed when I was running against the powervm driver since it doesn't implement
that API. I started looking at other drivers that did and found that
libvirt, vmware and xenapi at least had code for the get_diagnostics method.
I found that the vmware driver was re-using it's get_info method
for get_diagnostics which led to bug 1237622 [2] but overall caused some
confusion about the difference between the compute driver's get_info and
get_diagnostics mehods. It looks like get_info is mainly just used
to get the power_state of the instance.</font><font size=1 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
First, the get_info method has a nice docstring for what it needs returned
[3] but the get_diagnostics method doesn't [4]. From looking at the
API docs [5], the diagnostics API basically gives an example of values
to get back which is completely based on what the libvirt driver returns.
Looking at the xenapi driver code, it looks like it does things a
bit differently than the libvirt driver (maybe doesn't return the exact
same keys, but it returns information based on what Xen provides).</font><font size=1 face="Calibri">
<br>
</font><font size=2 face="sans-serif"><br>
I'm thinking about implementing the diagnostics API for the powervm driver
but I'd like to try and get some help on defining just what should be returned
from that call. There are some IVM commands available to the powervm
driver for getting hardware resource information about an LPAR so I think
I could implement this pretty easily.</font><font size=1 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
I think it basically comes down to providing information about the processor,
memory, storage and network interfaces for the instance but if anyone has
more background information on that API I'd like to hear it.</font><font size=1 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
[1] </font><a href=https://github.com/openstack/tempest/commit/da0708587432e47f85241201968e6402190f0c5d><font size=3 color=blue face="Calibri"><u>https://github.com/openstack/tempest/commit/da0708587432e47f85241201968e6402190f0c5d</u></font></a><font size=2 face="sans-serif"><br>
[2] </font><a href="https://bugs.launchpad.net/nova/+bug/1237622"><font size=3 color=blue face="Calibri"><u>https://bugs.launchpad.net/nova/+bug/1237622</u></font></a><font size=2 face="sans-serif"><br>
[3] </font><a href=https://github.com/openstack/nova/blob/2013.2.rc1/nova/virt/driver.py#L144><font size=3 color=blue face="Calibri"><u>https://github.com/openstack/nova/blob/2013.2.rc1/nova/virt/driver.py#L144</u></font></a><font size=2 face="sans-serif"><br>
[4] </font><a href=https://github.com/openstack/nova/blob/2013.2.rc1/nova/virt/driver.py#L299><font size=3 color=blue face="Calibri"><u>https://github.com/openstack/nova/blob/2013.2.rc1/nova/virt/driver.py#L299</u></font></a><font size=2 face="sans-serif"><br>
[5] </font><a href=http://paste.openstack.org/show/48236/><font size=3 color=blue face="Calibri"><u>http://paste.openstack.org/show/48236/</u></font></a><font size=1 face="Calibri"><br>
</font><font size=2 face="sans-serif"><br>
</font><font size=1 face="Calibri"><br>
</font><font size=1 face="Arial"><br>
Thanks,</font><font size=1 face="Calibri"> <br>
</font><font size=3 color=#8f8f8f face="Arial"><b><br>
MATT RIEDEMANN</b></font><font size=1 face="Arial"><br>
Advisory Software Engineer<br>
Cloud Solutions and OpenStack Development</font>
<table width=680 style="border-collapse:collapse;">
<tr height=8>
<td width=678 colspan=2 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;">
<hr>
<tr valign=top height=8>
<td width=416 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=1 color=#4181c0 face="Arial"><b>Phone:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-253-7622</font><font size=1 color=#4181c0 face="Arial"> | <b>Mobile:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-990-1889</font><font size=1 color=#4181c0 face="Arial"><b><br>
E-mail:</b></font><font size=1 color=#5f5f5f face="Arial"> </font><a href=mailto:mriedem@us.ibm.com target=_blank><font size=1 color=#5f5f5f face="Arial"><u>mriedem@us.ibm.com</u></font></a>
<td width=259 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;">
<div align=right><img src=cid:_1_0E0B2EAC0E0B2AAC0011B74C86257C03 width=83 height=30 alt=IBM><font size=1 color=#5f5f5f face="Arial"><br>
<br>
3605 Hwy 52 N<br>
Rochester, MN 55901-1407<br>
United States</font></div></table>
<br><font size=1 face="Calibri"><br>
</font><tt><font size=2>_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br><font size=2 face="sans-serif">[attachment "ATT00001..gif"
deleted by Matt Riedemann/Rochester/IBM] [attachment "ATT00002..gif"
deleted by Matt Riedemann/Rochester/IBM] </font>
<br>