...
Single node
This configuration creates a network of one: a single SHRINE node, backed by a single instance of i2b2, that accepts queries and exposes a web client. This is the configuration produced by SHRINE's install scripts when run against a stock i2b2 VM.
...
Firewall considerations
...
Firewall considerations
...
A hub-and-spoke network requires cert exchanges between the hub and each spoke. If there are N spokes, N cert exchanges are necessary.
Fully-meshed, each node can originate queries (Deprecated)
| Section |
|---|
| Column |
|---|
| 
|
| Column |
|---|
This configuration creates a fully-meshed network where each node can initate queries. It is similar to the single-node-network outlined above, but at each node, all the other nodes are listed in shrine.hub.downstreamNodes. The SHRINE team intends to stop supporting this topology in a future release. Do not create new fully meshed networks. |
|
shrine.conf
Assuming a 3-node netowrk with nodes A, B, and C:
...
Firewall considerations
...
Firewall considerations
...
