Configure and demonstrate MNI - Douglas federation

[surchs]

Once #127 is done, configure the FRP to provide connection to the DNP node:

• Talk to Gabe / Thomas about the setup plan
• Add the DNP node to our local federation node list. Configure port and hostname to use their DNP cloud machine
• Confirm we can federate MNI -> DNP

Steps agreed with Gabe + Thomas:

• DNP will connect DNP neurobagel node to DNP cloud machine
• DNP will expose DNP neurobagel node publicly from DNP cloud machine from public port
• DNP will restrict access to this port via openstack firewall to public IP of the BIC VM
• Neurobagel will list the public IP:Port of the DNP cloud machine as an internal node for federation

[surchs]

Waiting for Thomas to come back from vacation by March 11th. Then we will get an IP and port to federate with. Until then -> tracked

[surchs]

Also pinging @thomasbeaudry and @gdevenyi here to keep them up to date on our progress

[alyssadai]

We have confirmed that we can reach the DNP Neurobagel instance from the BIC internal node, and vice versa.

The local federation index for the f-API on the BIC internal node has also been updated to include the DNP Neurobagel instance, so you can now run federated queries which are forwarded to the DNP at https://federate-bic.neurobagel.org.

Because the query tool has not caught up with the recent changes to the n-/f-API response structures yet, we will wait for now to set up local federation at the DNP until the following are addressed and we release the APIs and query tool:

• Handle partial node query successes when all nodes are selected query-tool#60
• Enable pheno level session for response and query query-tool#78

[alyssadai]

Closing as the tasks specified for this issue are all complete!