
In order to proceed with switching flavor in OSC from novaclient/self api onto SDK few new methods need to be supported. Those include flavor access and set of extra_specs related operations. While extra_specs in terms of SDK should be a separate resource, it is not easy to implement it this way. On the other hand all those operations are definive subset of flavor related operations. In addition also merge FlavorDetail into Flavor class Change-Id: Ia4f60acce5e0e5665e2ba704fe4cd0ec81437eb5
4.2 KiB
Compute API
For details on how to use compute, see /user/guides/compute
openstack.compute.v2._proxy
The Compute Class
The compute high-level interface is available through the
compute
member of a ~openstack.connection.Connection
object. The
compute
member will only be added if the service is
detected.
Server Operations
openstack.compute.v2._proxy.Proxy
Network Actions
openstack.compute.v2._proxy.Proxy
Starting, Stopping, etc.
openstack.compute.v2._proxy.Proxy
Modifying a Server
openstack.compute.v2._proxy.Proxy
Image Operations
openstack.compute.v2._proxy.Proxy
Flavor Operations
openstack.compute.v2._proxy.Proxy
Service Operations
openstack.compute.v2._proxy.Proxy
Volume Attachment Operations
openstack.compute.v2._proxy.Proxy
Keypair Operations
openstack.compute.v2._proxy.Proxy
Server IPs
openstack.compute.v2._proxy.Proxy
Server Group Operations
openstack.compute.v2._proxy.Proxy
Server Interface Operations
openstack.compute.v2._proxy.Proxy
Availability Zone Operations
openstack.compute.v2._proxy.Proxy
Limits Operations
openstack.compute.v2._proxy.Proxy
Hypervisor Operations
openstack.compute.v2._proxy.Proxy
Extension Operations
openstack.compute.v2._proxy.Proxy