lp:~mcgrue/nova/volume_type_extradata

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1458. By Ben McGraw on 2011-08-22

WIP for the volume metadatachanges. Tests still broken.

1457. By Vladimir Popovski on 2011-08-18

added volume metadata. Fixed test_volume_types_extra_specs

1456. By Vladimir Popovski on 2011-08-18

added unittests for volume_extra_data

1455. By Vladimir Popovski on 2011-08-18

typo

1454. By Vladimir Popovski on 2011-08-18

first cut on types & extra-data (only DB work, no tests)

1453. By Troy Toman on 2011-08-18

Fix to return 413 for over limit exceptions with instances, metadata and personality

1452. By Ed Leafe on 2011-08-18

Fixed several logical errors in the scheduling process. Renamed the 'ZoneAwareScheduler' to 'AbstractScheduler', since the zone-specific designation is no longer relevant. Created a BaseScheduler class that has basic filter_hosts() and weigh_hosts() capabilities. Moved the filters out of one large file and into a 'filters' subdirectory of nova/scheduler.

Since I had to do a lot of editing of the files to change the naming and references, I cleaned up much of the inconsistent formatting. Normally formatting changes don't belong in a code change merge prop, but as I was making large-scale changes to the files, it was simplest to do it all at once.

1451. By Ed Leafe on 2011-08-18

Adds the enabled status of a host when XenServer reports its host's capabilities. This allows the scheduler to ignore hosts whose enabled is False when considering where to place a new instance.

1450. By Brian Lamar on 2011-08-17

DB object was being casted to dict() in API code. This did not work as intended and logic has been updated to reflect a more accurate way of getting information out of DB objects.

1449. By dan wendlandt on 2011-08-16

I'm taking Thierry at his word that I should merge early and merge often :)

In Diablo-3 we introduced "vif-plugging" to the hypervisor "virt" layer, allowing flexibility in how vNICs are attached to the network switch. This allowed non-linux bridge switch technologies (e.g., Open vSwitch, 802.1qbh) to be used with nova.

This blueprint adds a similar capability to linux_net.py, allowing the L3/DHCP capabilities to be "plugged" into Quantum networks. Like in the virt layer, we created a vif driver that represents the behavior of Nova prior to the change (LinuxBridgeInterfaceDriver) and make it the default. We also add a new driver for Open Vswitch that can be enabled using a flag (LinuxOVSInterfaceDriver). The code is designed to support other drivers as well.

Most of the interesting code is at the bottom of linux_net.py, where the drivers are defined. I had to pull some common code related to setting IPs on devices out of ensure_bridge() so it could be used by either approach. The driver's plug() method is invoked by the VlanManager's _setup_network() method. Currently unplug() is unused, which seems to be inline with how the existing nova code works.

In many places in linux_net.py, I had to tweak functions to accept the name of the linux device to configure, rather than just assuming it was the 'bridge' field in the network object, since with OVS it could be any linux device. The code I am least sure about are the changes to bin/nova-dhcpbridge. I changed to this key off of the network ID, rather than the bridge name.

I've tested this with the linux bridge and with the OVS vif-plugging driver. I was able to confirm that L3 forwarding and DHCP were operating correctly.