yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #00000
[Blueprint separate-nova-adminapi] Separate Nova Admin API
Blueprint changed by OpenStack Hudson:
Whiteboard changed:
It looks like the best approach is to break out each piece of admin api
functionality into a separate OpenStack Compute API extension.
Gerrit topic: https://review.openstack.org/#q,topic:bp/separate-nova-
adminapi,n,z
Addressed by: https://review.openstack.org/2354
Creating mechanism that loads Admin API extensions
Is there some info that can be shared on why extensions was chose
instead of a separate api? (maybe just some pros/cons)
(bcwaldon) The driving reason is that I didn't want to duplicate code we
could get for free by stacking extensions on top of the existing compute
api. The extension mechanism is actually designed to handle exactly this
case (implementation-driven functionality).
+
+
+ Addressed by: https://review.openstack.org/2528
+ Move 'diagnostics' subresource to admin extension
--
Separate Nova Admin API
https://blueprints.launchpad.net/nova/+spec/separate-nova-adminapi