Re: [Openstack-qa-team] API extensions and error codes

[Anne Gentle]

Hi David -
The only existing API documentation for extensions was merged in with
this merge request:

https://review.openstack.org/#change,2045

Unfortunately, it appears it has been left behind in subsequent
merges, as it doesn't appear in the Sphinx-built homepage at
http://nova.openstack.org/. See the blank area below here, that's
where it should be. http://nova.openstack.org/#api-extensions

Nova devs - should I rebase and add those in again? What's a good next step?
Thanks,
Anne


On Mon, Feb 13, 2012 at 8:59 AM, David Kranz david.kr...@qrclab.com wrote:
 It seems that a number of Tempest tests are broken because specific error
 codes are being checked that are different from those actually being
 returned from the API calls. I am puzzled because things like the floating
 ip and volume extensions seem to work fine with nova-client/diablo and
 some have different behavior in Essex. The regular APIs are well documented
 about return codes but I could not find any documentation about the
 extensions at all.
 Is there such documentation?

  -David

 --
 Mailing list: https://launchpad.net/~openstack-qa-team
 Post to     : openstack-qa-team@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack-qa-team
 More help   : https://help.launchpad.net/ListHelp

-- 
Mailing list: https://launchpad.net/~openstack-qa-team
Post to : openstack-qa-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-qa-team
More help   : https://help.launchpad.net/ListHelp

[Openstack-qa-team] Flavor list changed in Essex

[David Kranz]

In tracking down a problem with the tempest flavors test I noticed that 
'nova flavor-list' returns this in Essex:


++---+---+--+--+---+-+
| ID |Name   | Memory_MB | Swap | Local_GB | VCPUs | RXTX_Factor |
++---+---+--+--+---+-+
| 1  | m1.tiny   | 512   |  | 0| 1 | 1.0 |
| 2  | m1.small  | 2048  |  | 10   | 1 | 1.0 |
| 3  | m1.medium | 4096  |  | 10   | 2 | 1.0 |
| 4  | m1.large  | 8192  |  | 10   | 4 | 1.0 |
| 5  | m1.xlarge | 16384 |  | 10   | 8 | 1.0 |
++---+---+--+--+---+-+

and this in Diablo:

++---+---+--+--+---+-+
| ID |Name   | Memory_MB | Swap | Local_GB | VCPUs | RXTX_Factor |
++---+---+--+--+---+-+
| 1  | m1.tiny   | 512   | 0| 0| 1 | |
| 2  | m1.small  | 2048  | 0| 20   | 1 | |
| 3  | m1.medium | 4096  | 0| 40   | 2 | |
| 4  | m1.large  | 8192  | 0| 80   | 4 | |
| 5  | m1.xlarge | 16384 | 0| 160  | 8 | |
++---+---+--+--+---+-+

Note that Local_GB changed from 0,20,40,80,160 to 0,10,10,10,10. These 
values are coming straight from the API call.

Is this a bug or a deliberate change?

 -David

--
Mailing list: https://launchpad.net/~openstack-qa-team
Post to : openstack-qa-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-qa-team
More help   : https://help.launchpad.net/ListHelp