OpenStack Compute (nova)

Does admin api work at all in diablo?

Asked by David Kranz

There was a thread about 'diagnostics' that implied that though this did not work with libvirt, the admin api did work. But our system does not perform pause, suspend, etc. The --allow_admin_api is set but 'nova pause xxx' gives

There is no such server action: pause (HTTP 400)

Looking at the source code this is actually what I would expect. Is it supposed to work? And a user asked "why shouldn't a non-admin user be able to pause or suspend a server?"

Question information

Language:
English Edit question
Status:
Expired
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Brian Waldon (bcwaldon) said : 		#1

The current novaclient code is written to work with the essex admin api extensions. The pause feature in particular moved from POST /servers/<SERVER_ID>/pause to POST /servers/<SERVER_ID>/action with a body of {'pause':{}}. Unfortunately there isn't a current branch of novaclient that works with diablo.

Revision history for this message
David Kranz (david-kranz) said : 		#2

Thanks Brian. A few followup questions which I can send to the openstack list if you prefer:

1. Why are pause, etc. considered admin-only apis?
2. Are there any other apis that changed in Essex? Is there a list somewhere?
3. Who decides, and with what process, which incompatible API changes are worth the potential pain caused to users?
4. Is novaclient intended to be per-release going forward or will its python API cover over "wire protocol"
changes to the REST API?

Revision history for this message
Launchpad Janitor (janitor) said : 		#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.