I am reading the Indy walkthrough:
https://github.com/hyperledger/indy-sdk/blob/master/docs/getting-started/indy-walkthrough.md
and I am trying to figure out what is the Indy nodes pool?
And conceptually what is a pool?
And when we talk about Sovrin network which is the relationship between network, Sovrin pool, nodes, and ledger?
Indy node is application running on the machines participating in a Hyperledger Indy network.
Indy nodes pool is just an interconnected network of Indy nodes. This commonly refers Hyperledger Indy network you can run in docker for example. Network of Indy nodes is maintaining the state of ledger, verifying transactions.
Sovrin network is particular instance of Hyperledger Indy network. You can browse transactions on Sovrin network here. Note there's multiple Sovrin networks such as MainNet, TestNet, BuilderNet.
Related
I am quite new to MQTT implementations. I am managing to connect popular cloud based MQTT Brokers such thingsboard.io, Azure and AWS to send Sensor information to create dashboards for monitoring devices.
Problem
I have installed a local things-board broker to my local computer. But it is unable to reach other dashboards on the internet. Is it possible? Or is it only accessible within the local network?
It seems your doubt is more related to network connections. An MQTT broker will work in the same way, regardless it is working locally, in a fog server or in a cloud server. Obviously you will have to deal with access means: your clients/devices/applications must access the MQTT broker no matter where it is running. If you are running a local MQTT broker and it does not communicate directly with some cloud server, you can develop a specie of "gateway" only to send these data to the cloud or search for some tool that performs this task for you.
Below, you have some references regarding the working of MQTT and how to use it:
MQTT IoT Protocol complete tutorial - How it works with a demo
Using local MQTT broker for cloud and interprocess communication
MQTT Brokers/Servers and Cloud Hosting Guide
Creating an MQTT Broker With CloudMQTT
How to setup your own MQTT Broker
Could anyone explain what type of connections are between the nodes?
Are they anyhow encrypted? I cannot find anything in the official documentation.
Update:
http://developer.couchbase.com/documentation/server/current/security/security-comm-encryption.html
Depending on the version you are running and the deployment topology you have chosen with services, Couchbase Server has a number of connections between nodes. You can find the list here for the ports we use for internal communication between nodes under "node to node";
http://developer.couchbase.com/documentation/server/4.5/install/install-ports.html
Couchbase Server does not encrypt communication between nodes today. You can use other solutions like IPSec to do that. Couchbase Server does encrypt data access, web console and cluster to cluster communication with XDCR.
Is it possible to know what range of external IP the DataFlow workers on GCP are using? The goal is to set-up some kind of IP filtering on an external service, so that only our DataFlow jobs running on GCP can access the service.
The best solution would be to upgrade so that you can use SSL or other mechanisms of strong authentication.
You can use the --network= option to control the GCE Network that the worker VMs are assigned to. Take a look at the GCE docs on networking for details on how to set up a VPN (like the comment from Elmar suggested). You could also look at setting up a single machine in the network with a static, external IP and using it as a proxy for the other VMs in the network.
This is not a use pattern we have tested, so there may be issues with latency or throughput of traffic through the proxy/VPN. You will likely need to be careful to only send your traffic through this proxy so that you don’t accidentally hijack the traffic used by each worker to communicate with the Dataflow service.
I need to secure the replication data stream between two Neo4J nodes (eg. using SSL or TLS). Both are running in embedded mode in two JBoss instances.
Is it possible and how can I do that ?
Thanks
AFAIK Neo4j replication is not encrypted by itself. The most easy way would be connecting the cluster members using a VPN (e.g. using openvpn) and configure Neo4j to use the virtual network interface provided by the VPN.
An alternative might be stunnel.
Update:
there is a nice blog post on using openvpn for encrypting Neo4j cluster replication by John Russell. Please note that this uses Neo4j <= 1.8, in Neo4j 1.9.x there is no Zookeeper any more.
I am working with WebSphere MQ FTE. While reading a document I came across a sentence that the bridge agent connects to local queue manager through binding mode. What is meant by binding mode in WebSphere MQ?
WebSphere MQ was originally created to be a local communication stack that resided on the same server as the applications that used it. In this mode, applications talk to it using Inter Process Communication (IPC). This is where two processes on the same server intercommunicate using shared memory, semaphores and other local communication.
Eventually the MQ client was created and allowed applications to communicate with WebSphere MQ over the network. This meant that there were now two modes of communication with the queue manager. The term Client Mode naturally arose to refer to communications using the MQ client. The term Bindings Mode arose to differentiate client mode from native WMQ IPC connections.
So when you read that an FTE agent uses bindings mode connections, that means that it runs on the same server as a queue manager and that it communicates with the queue manager using shared memory instead of over the network.
Note that with WebSphere MQ File Transfer Edition the licensing refers to "Client" and "Server" bundles of the products. The Client package is the FTE agents without a copy of WebSphere MQ Server included. The Server package is the same FTE components bundled with a copy of WebSphere MQ Server and with the ability to connect in bindings mode.