faucetsdn
running DAQ in cmd/run -n mode skips configured tests
running DAQ in cmd/run -n mode skips configured tests also, it could be related: the firebase app put all the tests that don't run after the report column
As per the options documentation, -n is "no test" (or "network only") mode -- so that behavior is working as intended. It should, in fact, skip all tests (configured or not).
Perhaps describe what you're trying to get the system to do?
The functionality of cmd/run -n has changed from network mode, as it now puts the system into the "hold" state and waits for action from the firebase app to start minimal testing (DHCP for instance) and then generates a report.
Getting the previous "network only" mode with IP address assigned with option -n would be useful so that devices could be configured with the DAQ network switch equipment.
An interactive mode where the device is put on hold, DAQ settings configured, all configured testing initiated, report created then device put again in hold mode would be useful for interactive testing and configuration settings refinement, using a different option switch than -n.
Can you clarify what behavior you're looking for without getting into the details (e.g. "-n") -- just "I want a way to put the system in XXX state such that I can do YYY"
I'm also not sure what you mean by "device is put on hold" -- do you mean it's sitting there but no tests are actively run? There is no direct manipulation of the device, so it can't directly be put into any particular state. And also don't know what "DAQ settings configured" -- that's something that happens before you run DAQ.
Are you saying that you want the mode where the system is "ready" but idle, then tests are run based on an external trigger? (e.g. from Firebase)
On Thu, Nov 7, 2019 at 7:51 AM Francesco Anselmo [email protected] wrote:
The functionality of cmd/run -n has changed from network mode, as it now puts the system into the "hold" state and waits for action from the firebase app to start minimal testing (DHCP for instance) and then generates a report.
Getting the previous "network only" mode with IP address assigned with option -n would be useful so that devices could be configured with the DAQ network switch equipment.
An interactive mode where the device is put on hold, DAQ settings configured, all configured testing initiated, report created then device put again in hold mode would be useful for interactive testing and configuration settings refinement, using a different option switch than -n.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/faucetsdn/daq/issues/214?email_source=notifications&email_token=AAIEPD5DVHCSJNZBGTERXSTQSQ2QVA5CNFSM4JKFEUH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDM3PXQ#issuecomment-551139294, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIEPD2FJZNFXZLCDBBRBOLQSQ2QVANCNFSM4JKFEUHQ .
I would like to have:
- a mode where all devices are assigned IP addresses and I can reach them for device configuration (opening a web page for instance).
- a mode where the system is "ready" but idle and then tests are run based on the Firebase trigger. This allows the configuration to be manipulated via the Firebase app before triggering the test for last minute changes and interactive runs.
Perfect, thanks -- and then, I assume, if it's the same mode that would work as well? E.g.,
"A mode where all devices are assigned IP addresses and are reachable for configuration, and then tests are run based on the Firebase trigger (after configuration through Firebase)"
On Fri, Nov 8, 2019 at 1:46 AM Francesco Anselmo [email protected] wrote:
I would like to have:
- a mode where all devices are assigned IP addresses and I can reach them for device configuration (opening a web page for instance).
- a mode where the system is "ready" but idle and then tests are run based on the Firebase trigger. This allows the configuration to be manipulated via the Firebase app before triggering the test for last minute changes and interactive runs.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/faucetsdn/daq/issues/214?email_source=notifications&email_token=AAIEPD5OTVF3O4E3V6POMG3QSUYONA5CNFSM4JKFEUH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDPNLCA#issuecomment-551474568, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIEPD76VOGYGP5ZDEJADCTQSUYONANCNFSM4JKFEUHQ .
@pisuke If I'm off track let me know, but can the behaviour for:
a mode where all devices are assigned IP addresses and I can reach them for device configuration (opening a web page for instance).
be acheived by cmd/run -n -k?
This lets DHCP testing run and the IP addresses appear on the dashboard and then adds a hold test as per:
This doesn't address anything to do with the following, of course:
a mode where the system is "ready" but idle and then tests are run based on the Firebase trigger. This allows the configuration to be manipulated via the Firebase app before triggering the test for last minute changes and interactive runs.
