From aa34a4dcca9ad76e767988bb4260b5cd70c88a6b Mon Sep 17 00:00:00 2001 From: Sapan Bhatia Date: Fri, 14 Mar 2008 21:00:43 +0000 Subject: [PATCH] Description fpr planetflow2 --- qaapi/qa/tests/node/description/planetflow2.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 qaapi/qa/tests/node/description/planetflow2.txt diff --git a/qaapi/qa/tests/node/description/planetflow2.txt b/qaapi/qa/tests/node/description/planetflow2.txt new file mode 100644 index 0000000..1d5fed0 --- /dev/null +++ b/qaapi/qa/tests/node/description/planetflow2.txt @@ -0,0 +1,10 @@ +There are many stages of this test. Basically planetflow2 is a 'chain of responsibility'. There are a set of dots and a set of arcs joining these dots, and each arc has to be tested. Specifically, the arcs are: + +(i) The packet should be received by the user-space data-collection process in root context +(ii) The packet should get incorporated in one or the other flow +(iii) The flow should get serialized into the fprobe raw dumps +(iv) The logs get shipped out to PF central +(v) The logs at PF central are successfully imported into silk - and the packet seen in (i) is appropriately reflected in the database. + +For now, this test supports only (i) and (ii). +It sends out a packet and checks if it shows up as a flow. If it succeeds, it means that ULOG and fprobe are running fine, which means that flows are getting collected at least on the node. -- 2.45.2