openstack/os-vif
Code Issues Proposed changes
8c58816f46
os-vif/os_vif/objects
History
Daniel P. Berrange 9686110d53 os-vif: introduce a ComputeInfo object to represent compute info 
When a compute service is allocating ports with the network service,
it needs to pass across information about the capabilities of the
compute host. Currently each plugin provides information about its
own capabilities. This introduces a ComputeInfo class which,
initially, just contains a dict of PluginInfo classes.

With this change, there is a versioning constraint between the
compute and network hosts. The compute host must not pass the network
host a ComputeInfo object with a version that the network host
is unable to deserialize(). This implies that as a general rule the
version of os-vif on the network host must be at least as new as the
version on the compute hosts. During a live upgrade, the network
hosts must be upgraded before the compute hosts.

Change-Id: I7b51c97b5e03ffa51a56ceb3d4f97e188508379d
2016-03-18 13:37:33 +00:00
..
__init__.py os-vif: introduce a ComputeInfo object to represent compute info 2016-03-18 13:37:33 +00:00
base.py os_vif: ensure objects are in an 'os_vif' namespace 2016-02-17 14:27:23 +00:00
fields.py Adding dev_type field to VIFHostDevice 2016-02-11 12:07:47 +02:00
fixed_ip.py os_vif: ensure objects are in an 'os_vif' namespace 2016-02-17 14:27:23 +00:00
host_info.py os-vif: introduce a ComputeInfo object to represent compute info 2016-03-18 13:37:33 +00:00
instance_info.py os_vif: ensure objects are in an 'os_vif' namespace 2016-02-17 14:27:23 +00:00
network.py Change network vlan to integer 2016-02-22 15:56:50 +02:00
route.py os_vif: ensure objects are in an 'os_vif' namespace 2016-02-17 14:27:23 +00:00
subnet.py os_vif: ensure objects are in an 'os_vif' namespace 2016-02-17 14:27:23 +00:00
vif.py Remove vlan from hostdev and direct vif 2016-02-23 13:53:03 +02:00