What happens if we provision our client, and later add brokers to the fabric? What if we remove brokers?
OpenDXL
Security Intelligence Sharing
Posts by ako
-
-
We're trying to determine what kind of logic we should use for provisioning our client, both for initial connection and for later disconnects or changes to the broker configuration on our DXL fabric.
As it is right now, we run through the provisioning process as part of our connection logic because our service is expected to start once and run indefinitely.
-
Our team has been making use of the Docker containers provided with a number of the solutions (in particular, the VirusTotal DXL Service), and we want to simplify bringing all of our services online after an event like a restart.
Is there a specific setting in any of the OpenDXL solutions that would let us automatically start something like the Docker container for the above VirusTotal service when the system boots?
-
Slight sidetrack... Are there any plans for a Node-based solution that doesn't require Node-RED?
-
A new video series is now available that walks through the steps to install and configure an OpenDXL environment.
Perfect timing, we were just getting ready to create a new test environment. Thanks!
-
Our team was recently informed that the OpenDXL Python Client now supports a command line interface that can be used for provisioning. This is huge news for us, because until now we were just doing everything manually.
My question is, what is the minimum version of the Python Client that supports the CLI? And are there any other features?
-
That was a huge help, thanks.
What kind of reconnect behavior can we expect if a client isn't able to immediately connect to another listed broker? For example, if the client has a network outage for several minutes.
-
I have an environment with multiple DXL brokers, and I'm not sure what kind of failover protection is already built-in to the OpenDXL Python Client.
If one of my clients is connected to one of these Brokers, and the broker goes offline without warning (power failure, for example), how can I make sure that my client will reconnect to another broker that is still online?