A fake (in-memory) hypervisor+api. Allows nova testing w/o a hypervisor. This module also documents the semantics of real hypervisor connections.
Bases: object
The interface to this class talks in terms of ‘instances’ (Amazon EC2 and internal Nova terminology), by which we mean ‘running virtual machine’ (XenAPI terminology) or domain (Xen or libvirt terminology).
An instance has an ID, which is the identifier chosen by Nova to represent the instance further up the stack. This is unfortunately also called a ‘name’ elsewhere. As far as this layer is concerned, ‘instance ID’ and ‘instance name’ are synonyms.
Note that the instance ID or name is not human-readable or customer-controlled – it’s an internal ID chosen by Nova. At the nova.virt layer, instances do not have human-readable names at all – such things are only known higher up the stack.
Most virtualization platforms will also have their own identity schemes, to uniquely identify a VM or domain. These IDs must stay internal to the platform-specific layer, and never escape the connection interface. The platform-specific layer is responsible for keeping track of which instance ID maps to which platform-specific ID, and vice versa.
In contrast, the list_disks and list_interfaces calls may return platform-specific IDs. These identify a specific virtual disk or specific virtual network interface, and these IDs are opaque to the rest of Nova.
Some methods here take an instance of nova.compute.service.Instance. This is the datastructure used by nova.compute to store details regarding an instance, and pass them into this layer. This layer is responsible for translating that generic datastructure into terms that are specific to the virtualization platform.
Return performance counters associated with the given disk_id on the given instance_name. These are returned as [rd_req, rd_bytes, wr_req, wr_bytes, errs], where rd indicates read, wr indicates write, req is the total number of I/O requests made, bytes is the total number of bytes transferred, and errs is the number of requests held up due to a full pipeline.
All counters are long integers.
This method is optional. On some platforms (e.g. XenAPI) performance statistics can be retrieved directly in aggregate form, without Nova having to do the aggregation. On those platforms, this method is unused.
Note that this function takes an instance ID, not a compute.service.Instance, so that it can be called by compute.monitor.
Destroy (shutdown and delete) the specified instance.
The given parameter is an instance of nova.compute.service.Instance, and so the instance is being specified as instance.name.
The work will be done asynchronously. This function returns a Deferred that allows the caller to detect when it is complete.
Return performance counters associated with the given iface_id on the given instance_id. These are returned as [rx_bytes, rx_packets, rx_errs, rx_drop, tx_bytes, tx_packets, tx_errs, tx_drop], where rx indicates receive, tx indicates transmit, bytes and packets indicate the total number of bytes or packets transferred, and errs and dropped is the total number of packets failed / dropped.
All counters are long integers.
This method is optional. On some platforms (e.g. XenAPI) performance statistics can be retrieved directly in aggregate form, without Nova having to do the aggregation. On those platforms, this method is unused.
Note that this function takes an instance ID, not a compute.service.Instance, so that it can be called by compute.monitor.
Return the IDs of all the virtual disks attached to the specified instance, as a list. These IDs are opaque to the caller (they are only useful for giving back to this layer as a parameter to disk_stats). These IDs only need to be unique for a given instance.
Note that this function takes an instance ID, not a compute.service.Instance, so that it can be called by compute.monitor.
Return the IDs of all the virtual network interfaces attached to the specified instance, as a list. These IDs are opaque to the caller (they are only useful for giving back to this layer as a parameter to interface_stats). These IDs only need to be unique for a given instance.
Note that this function takes an instance ID, not a compute.service.Instance, so that it can be called by compute.monitor.
Reboot the specified instance.
The given parameter is an instance of nova.compute.service.Instance, and so the instance is being specified as instance.name.
The work will be done asynchronously. This function returns a Deferred that allows the caller to detect when it is complete.
Create a new instance/VM/domain on the virtualization platform.
The given parameter is an instance of nova.compute.service.Instance. This function should use the data there to guide the creation of the new instance.
The work will be done asynchronously. This function returns a Deferred that allows the caller to detect when it is complete.
Once this successfully completes, the instance should be running (power_state.RUNNING).
If this fails, any partial instance should be completely cleaned up, and the virtualization platform should be in the state that it was before this call began.
Fake LDAP server for test harnesses.
This class does very little error checking, and knows nothing about ldap class definitions. It implements the minimum emulation of the python ldap library to work with nova.
Bases: object
Fake LDAP connection.
Modify the object at dn using the attribute list.
Args: dn – a dn attrs – a list of tuples in the following form:
([MOD_ADD | MOD_DELETE | MOD_REPACE], attribute, value)
Search for all matching objects under dn using the query.
Args: dn – dn to search under scope – only SCOPE_BASE and SCOPE_SUBTREE are supported query – query to filter objects by fields – fields to return. Returns all fields if not specified
Bases: exceptions.Exception
Duplicate exception class from real LDAP module.
Bases: exceptions.Exception
Duplicate exception class from real LDAP module.
Based a bit on the carrot.backeds.queue backend... but a lot better.
Bases: object
Singleton backend for testing
Bases: object