I suggest submitting the entire patch when it's ready. I don't feel
like reviewing a test case in isolation.
On Fri, Dec 12, 2014 at 02:31:29PM +0530, Shashwat Srivastava wrote:
> Hi Ben/Team,
>
> Thanks for the reply.
>
> We are working on implementation of vacancy events and have developed th
Hi Ben/Team,
Thanks for the reply.
We are working on implementation of vacancy events and have developed the
module for same.
As suggested, we have made a separate test case for [ofproto -
asynchronous message control (OpenFlow 1.4)].
The commands (ovs-ofctl ofp-print
051F0018040
On Thu, Dec 11, 2014 at 04:35:28PM +0530, Shashwat Srivastava wrote:
> Query 1: Will the testcase for table status messages (where vacancy reason
> value can be OFPTR_VACANCY_UP or OFPTR_VACANCY_DOWN) be written in
> [ofproto - asynchronous message control (OpenFlow 1.5)] block or shall we
> mak
Hi Team,
We are working on implementation of Vacancy Events as specified in
openflow specs 1.4.
While writing the test cases, in the test case no. 724 (ofproto -
asynchronous message control (OpenFlow 1.5)) we have added our vacancy
test case
check_async 3 for OFPTR_VACANCY_UP and we are usi
