10 Commits (9616c5f4754649965735d8cdcba225941b3cebf3)

Author	SHA1	Message	Date
Robert Kukura	0b790f6496	ML2: DB changes for hierarchical port binding ... To support hierarchical port binding, the driver and segment columns are moved from the ml2_port_bindings and ml2_dvr_port_bindings tables to a new ml2_port_binding_levels table. This new table can store multiple levels of binding information for each port. It has the host as part of its primary key so that it can be used for both normal and DVR port bindings. The cap_port_filter column is also removed from the ml2_dvr_port_bindings table, since the adjacent driver and segment columns are being moved, and this can trivially be done via the same DB migration. It was included in the table by mistake and was never used. The logic required for hierarchical port binding will be implemented in a dependent patch. Gerrit Spec: https://review.openstack.org/#/c/139886/ Partially-implements: blueprint ml2-hierarchical-port-binding Change-Id: I08ddc384763087fbac0fa3da3ed6e99b897df031	8 years ago
Romil Gupta	db5e370b0d	Schema enhancement to support MultiSegment Network ... Description: Currently, there is nothing in the schema that ensures segments for a network are returned in the same order they were specified when the network was created, or even in a deterministic order. Solution: We need to add another field named 'segment_index' in 'ml2_network_segment' table containing a numeric position index. With segment_index field we can retrieve the segments in the order in which user created. This patch set also fixes ML2 invalid unit test case in test_create_network_multiprovider(). Closes-Bug: #1224978 Closes-Bug: #1377346 Change-Id: I560c34c6fe1c5425469ccdf9b8b4905c123d496d	9 years ago
Arvind Somya	6c38103e09	ML2 Type Driver refactor part 2 ... This commit builds on top of part 1 to introduce support for creating dynamic network segments in ML2. Change-Id: I399e1569baae6f24054aac15c4c51a2e44a20e5b Partially implements: Blueprint ml2-type-driver-refactor	9 years ago
Vivekanandan Narasimhan	10579d28d7	L2 Model additions to support DVR ... This patch introduces the models, the DB migrations and the config options required by the L2 layer to support DVR east/west traffic. These changes will be used by the control-plane made of ML2, L2pop and L2 agent. Two new configuration options have been introduced: 'dvr_base_mac' is used to set DVR MAC addresses apart from tenant ones (every distributed router will have ports being created on compute hosts) and 'enable_distributed_routing' is used to enable dvr support in the L2 agent. This gives the capability of rolling out the dvr functionality in stages. Partially-implements: blueprint neutron-ovs-dvr DocImpact Change-Id: Iab6505f239d2c4c9bcbf4e32a292d7b4b5320c8e Authored-by: Vivekanandan Narasimhan <vivekanandan.narasimhan@hp.com> Co-Authored-By: Armando Migliaccio <armamig@gmail.com>	9 years ago
Ann Kamyshnikova	40223f44d6	Fix 'server_default' parameter usage in models ... In ml2 models parameter 'default' is used for vnic_type, profile and vif_details, but in migrations 27cc183af192_ml2_vnic_type, 157a5d299379_ml2_binding_profile and 50d5ba354c23_ml2_binding_vif_details is used 'server_default' parameter. Usage 'default' and 'server_default' should be equal in models and migration. So models in models is added 'server_default' parameter. Partial-bug: #1295539 Change-Id: If6a17f381d2550daf64916ad3c1b120f41406d56	9 years ago
Bob Kukura	cb106a7193	ML2 binding:profile port attribute ... The ML2 plugin stores the binding:profile port attribute, defined as a dictionary, in its ml2_port_bindings DB table. Since the plugin can support a variety of MechanismDrivers with different needs for binding:profile attribute content, the plugin will accept, store, and return arbitrary key/value pairs within the attribute. As with the binding:host_id attribute, updates to binding:profile trigger rebinding. Implements: blueprint ml2-binding-profile Change-Id: I01cba8d09dde9de1c6160d0235b0d289eed91b29	9 years ago
Bob Kukura	be8a068943	Replace binding:capabilities with binding:vif_details ... In addition to binding:vif_type, the neutron core plugin needs to supply various information to nova's VIF driver, such as VIF security details and PCI details when SR-IOV is being used. This information is read-only, requires admin privileges, and is not intended for normal users. Rather than add separate mechanisms throughout the stack for each such requirement, the binding:capabilities port attibute, which is a dictionary and is not currently not used by nova, is renamed to binding:vif_details to serve as a general-purpose mechanism for supplying binding-specific details to the VIF driver. This patch does not remove or replace the CAP_PORT_FILTER boolean previously used in binding:capabilities. A separate patch should implement the specific key/value pairs carried by binding:vif_details to implement VIF security. Another patch will implement the key/value pairs needed for SR-IOV. The ML2 plugin now allows the bound mechanism driver to supply the binding:vif_details dictionary content, instead of just the CAP_PORT_FILTER boolean previously carried by the binding:capabilities attribute. DocImpact: Need to update portbinding extension API, but no impact on user or administrator documentation. Implements: blueprint vif-details Related-Bug: 1112912 Change-Id: I34be746fcfa73c70f72b4f9add8eff3ac88c723f	9 years ago
Irena Berezovsky	9623e6c967	Add support to request vnic type on port ... This patch adds support for requested vnic_type to be plugged to neutron port to ML2 plugin. This patch contains: 1. New attribute 'binding:vnic_type' added to port binding extension. Possible values are 'direct', 'macvtap' and 'normal'. 'binding:vnic_type' is allowed to be defined on port creation or changed on port update by admin or tenant user. 'binding:vnic_type' can be also skipped in port defintion 2. Management of vnic_type by ML2 plugin, assuming default vnic_type=normal 3. Add 'vnic_type' to ml2_port_bindings DB table 4. Add supported vnic_types for MechanismDrivers that are capable to bind port. 5. Add DB migration script for ml2_vnic_type. DocImpact: Need to update portbindings API docs and include in SR-IOV user docs Change-Id: Ic88708fa9ece742f807c1d09bb49e499f99bd092 Implements: blueprint ml2-request-vnic-type	9 years ago
Bob Kukura	8bc02a7fbe	Implement ML2 port binding ... The ml2 plugin uses mechanism drivers to determine which network segment and what VIF driver to use for a port. Mechanism drivers supporting the openvswitch, linuxbridge, and hyperv agents are added. The binding:host attribute is set on ports belonging to the dhcp and l3 agents so that they can be bound. To use with devstack until it is updated, set "Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch,linuxbridge" in localrc. The hyperv L2 agent does not currently implement the agents_db RPC, and will therefore not work with its ml2 mechanism driver. This issue will be tracked as a bug to be fixed in a separate merge. implements blueprint: ml2-portbinding Change-Id: Icb9c70d8b0d7fcb34b57adc760bb713b740e5dad	10 years ago
Mark McClain	ee3fe4e836	Rename Quantum to Neutron ... This change renames everything to Neutron while providing backwards compatible adjustments for Grizzly configuration files. implements blueprint: remove-use-of-quantum Change-Id: Ie7d07ba7c89857e13d4ddc8f0e9b68de020a3d19	10 years ago