[ovs-dev] [RFC] Proposal for enhanced select groups

Simon Horman simon.horman at netronome.com
Mon Sep 1 07:59:22 UTC 2014


On Thu, Aug 28, 2014 at 10:11:57AM +0900, Simon Horman wrote:
> On Wed, Aug 27, 2014 at 09:51:59AM -0700, Ben Pfaff wrote:
> > On Wed, Aug 27, 2014 at 10:26:14AM +0900, Simon Horman wrote:

[snip]

> > The proposal seems reasonable on its own but given that EXT-350 allows a
> > standardized way to add group configuration extension I am not sure it
> > makes sense to add a specialized way to do that.
> 
> Thanks, as discussed off-line, on closer examination I see that our
> proposal could fit into EXT-350 as a group property.

We have updated our proposal to use an EXT-350 group property.
The revised version is below.

We have also started on an implementation of EXT-350.  Our current plan is
to implement EXT-350 as an OpenFlow 1.5 group_mod message.  Let me know if
you would like us to make it some kind of experimenter message instead.


Proposal: Proposal for Group Selection Method Property
Version: 0.0.1


Contents
========

1. Introduction
2. How it Works
3. Experimenter Id
4. Experimenter Messages
5. History


1. Introduction
===============

This text describes a Netronome Extension to OpenFlow 1.4 that allows a
controller to provide more information on the selection method for select
groups.  This proposal is in the form of an enhanced select group type.

This may subsequently be proposed as an extension or update to
the OpenFlow specification.


2. How it works
===============

A new Netronome group experimenter property is defined which provides
compatibility with the group mod message defined in EXT-350 to Open Flow
1.4.0 and allows parameters for the selection method of select groups to be
passed by the controller. In particular it allows controllers to:

* Specify the fields used for bucket selection by the select group.

* Designate the selection method used.

* Provide a non-field parameter to the selection method.


3. Experimenter ID
==================

The Experimenter ID of this extension is:

NMX_VENDOR_ID = 0x00001540


4. Group Experimenter Property
==============================

The following group property experimenter type defined by this extension.

enum nmx_group_mod_subtype {
	NMXT_SELECTION_METHOD = 1
}


Modifications to the group table from the controller may be done with a
OFPT_GROUP_MOD message described in a draft of EXT-350, an extension to
the description found in Open Flow 1.4.0 section 7.3.4.3 Modify
Group Entry Message. Of relevance here is that EXT-350 allows properties
to be included in group mod messages.

This proposal is defined in terms of an implementation of struct
ofp_group_prop_experimenter which is described in EXT-350.
The implementation is:

struct nmx_group_prop_selection_method {
    ovs_be16 type;                  /* OFPGPT_EXPERIMENTER. */
    ovs_be16 length;                /* Length in bytes of this property. */
    ovs_be32 experimenter;          /* NMX_VENDOR_ID. */
    ovs_be32 exp_type;              /* NMXT_SELECTION_METHOD. */
    char selection_method[NXM_MAX_SELECTION_METHOD_LEN];
                                    /* Null-terminated */
    ovs_be64 selection_method_param;  /* Non-Field parameter for
                                       * bucket selection. */
    struct ofp_match fields;        /* Fields used for bucket selection.
                                     * Variable size. */
}
OVS_ASSERT(sizeof(struct nmx_group_mod) == 24);


This property may only be used with group mod messages whose:
* command is OFPGC_ADD or OFPGC_MODIFY; and
* type is OFPGT_SELECT


The type field is the OFPGPT_EXPERIMENTER which is
defined in EXT-350 as 0xffff.


The experimenter field is the Experimenter ID (see 3).


The exp_type field is NMXT_SELECTION_METHOD.


The group selection_method is a null-terminated string which if non-zero
length specifies a selection method known to an underlying layer of the
switch. The value of NXM_MAX_SELECTION_METHOD_LEN is 16.

The group selection_method may be zero-length to request compatibility with
Open Flow 1.4.


The selection_method_param provides a non-field parameter for
the group selection_method. It must be all-zeros unless the
group selection_method is non-zero length.

The selection_method_param may for example be used as an initial value for
the hash of a hash group selection method.


The fields field is an ofp_match structure which includes the fields which
should be used as inputs to bucket selection. ofp_match is described in
Open Flow 1.4 section 7.2.2 Flow Match Structures.

Fields must not be specified unless the group selection_method is non-zero
length.

The pre-requisites for fields specified must be satisfied in the match for
any flow that uses the group.

Masking is allowed but not required for fields whose TLVs allow masking.

The fields may for example be used as the fields that are hashed
by a hash group selection method.


5. History
==========

This proposal has been developed independently of any similar work in this
area. No such work is known.



More information about the dev mailing list