On Wed, Aug 19, 2015 at 12:53:16PM +0530, saloni.jai...@gmail.com wrote:
> From: Saloni Jain <saloni.j...@tcs.com>
> 
> OpenFlow 1.4 introduces the ability to turn on vacancy events with an
> OFPT_TABLE_MOD message specifying OFPTC_VACANCY_EVENTS. This commit adds
> support for the new feature in ovs-ofctl mod-table.
> As per the openflow specification-1.4, vacancy event adds a mechanism
> enabling the controller to get an early warning based on capacity
> threshold chosen by the controller.
> 
> With this commit, vacancy events can be configured as:
> ovs-ofctl -O OpenFlow14 mod-table <bridge> <table> vacancy-<range>
> The syntax of <range> as <low..high>.
> <range> specify vacancy threshold values, vacancy down and vacancy up.
> 
> To disable vacancy events, following command should be given:
> ovs-ofctl -O OpenFlow14 mod-table <bridge> <table> novacancy
> 
> Signed-off-by: Saloni Jain <saloni.j...@tcs.com>
> Signed-off-by: Shashwat Srivastava <shashwat.srivast...@tcs.com>
> Signed-off-by: Sandeep Kumar <sandeep.kuma...@tcs.com>

Please explain the signoff chain.  Presumably, you are the author.  As
the person providing the patch, that means you need to be the final
signoff.  Who are Shashwat and Sandeep?
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to