I'm trying to install flow entries for traffic monitoring in SDN. I wonder if I can set the action as "continue indexing the flow table"? Here is one scenario:
A layer 2 switch with one existing flow entry: "match:dst_mac=00:01, action:outport=1, priority=1", I want to monitor network traffic with src_mac=00:02. Now I'm trying to add an high-priority flow entry "match:src_mac=00:02, action:continue_indexing, priority=2". How can I write the action field? I can't find any similar actions in OpenFlow 1.3.0.
Thanks for your answering!
You can either leverage multiple tables for pipeline matching, or
output the packets to the controller first and then inject those packets containing action "Table" back to the tables.
Related
I want to build a smart search agent which would use Watson conversation to process the request and give response but will use my own database say SQL server to search the desired output.
In Short Instead of writing intents and dialogues manually or importing from a csv file, I want to write my won code in .net in such a way that all the request and responses are influenced by my own data stored in my database. I only intent to use watson's processing and interpreting capability. But the processing must happen on my data.
E.g If the user searches for a word say "Dog", the Watson conversation service must search in my database and give relevant answers to the user based on the search.
Take a look at the solution architecture in the Watson Conversation documentation. Your database would be one of the depicted backend systems. Your application would be, as you mentioned, written in .NET and would use WCS to process the user input. It would return a response with all the associated metadata. Instead of having complete answers configured in a dialog, you would use something I have described as "replaced markers" in my collection of examples. Those markers are kind of hints to your application of which database query or which action to perform.
Note that WCS requires some intents and entities to work on. If you want to rely just on the detected intents and entities, you could work with one or two generic dialog nodes. As another technique you could use data from your database to generate intents and entities as an initial setup. In my "Mutating EgoBot" I use the Watson Conversation API to add intents and entities on the fly.
I believe you should use the standard trick:
instead of defining resposnses in the node of your diaglog, define an action on the output object of the node and let your applicatation take care of providing response (see https://console.bluemix.net/docs/services/conversation/develop-app.html#building-a-client-application)
I'm fairly new to nod-red oder nodejs in generel. But I think with time I got a decent understanding.
At the moment I'm using node-red-dashboard to give my home automation a nice touch and easy controlling interface.
All my devices communicate via MQTT and I organize my rooms (for example) with different tabs in node-red.
Maybe it's just a missunderstanding of mine, but how do I use the same mqtt-connection (or db connection, etc.) throughout different tabs? I've configured a new one for each tab and can see in the log, that individual connections are made for each tab.
The connection from another tab is not shown inside the nodes on another tab.
Maybe you can point me in the right direction.
Cheers,
Patrik
In the mqtt-broker configuration node's edit dialog, there is a select box where you can pick the 'scope' of the node. It defaults to the tab you're currently on, but if you change that to 'global', the config node will be available on all tabs.
Hopefully the title is clear, I couldn't find a better name but if someone can improve it please update it, thanks.
I would like the Firebase database to write on a node if a certain condition is met. For example, if one node receives an input from a client (say an angular app) then another node in the database should write certain data, something like a callback that is fired when a node receives some data.
I know there are 4 rule types (.read .write .validate .indexOn), what I am thinking of is some kind of .callback rule that is fired and writes on a node after some other node has received an input.
Obviously this can be achieved via a server side script but Firebase is about a server-less approach so I am trying to understand what are its current limits and what I can do with it.
Thanks for your responses
firebaser here
Running the multi-location update client-side or on a server-side process that you control are currently the only ways to accomplish this.
There is currently no way to trigger updates based on modifications to the database on Firebase servers. It is no big secret that we've been working on such functionality for a while now, but we have made no announcement as to when that will be available.
Also see Can I host a listener on Firebase?, which (I realize now) is probably a duplicate.
Is it possible, by BPMN rules, to use link events to communicate between different pools? Or the only possible way is through message flow?
The BPMN 2.0 specification elaborates on the usage of link events on pages 267 ff. (297 ff. in PDF).
While it does not explicitly state that link events must not be used to connect activities in different pools, some statements imply that doing so is at least not intended:
The spec stresses the role of link events as a substitute for sequence flows.
One of the examples is annotated as follows: "Note that the figure shows two different printed pages, not two Pools
in one diagram"
Furthermore, intermediate message events (see spec page 251/PDF: 281) are the obvious choice when modeling communication between pools without using message flows.
Is it possible to embed multiple GMail schemas in a single email? I'd like to provide users the ability to retry or cancel an action (the cancel operation would perform some cleaning stuff in the server app). However, if I try to embed more than one script, only the first one appears in the inbox (each script is correct and shows up properly when it is the only one).
Only one action is currently supported and if you include multiple actions, the first one will be used. The user experience for exposing multiple actions would be really different, so if/how to handle them is still being discussed.