Orion Bootnodes do not work properly

[eum602]

Orion bootnodes are not working properly.
Scenario 1:
Orion Node "A" points to Orion Node "a" as bootnode.
Orion Node "B" points to Orion Node "a" as bootnode.

If orion node "A" tries to send a message to orion node "B" then the message is NOT received by
If orion node "A" sends a message to orion bootnode "a" then it is received.
Node "B".

========================
Scenario 2:
Orion Node "A" points to Orion Node "a" and Orion Node "b" as bootnodes.

If Orion Node "A" sends a message to Orion bootnode "a" then the message is received.
If Orion Node "A" sends a message to Orion bootnode "b" then the message is NOT received.

======================
If explained scenarios are tested with different bootnodes other than the 4 bootnodes in the Lacchain architecture, then all works as expected.

[eum602]

Problem was partially solved by migrating bootnode keys to new virtual machines(with the same ip). The problem is still persisiting in one bootnode VM.

[eum602]

Follow the thread discussion with Hyperledger besu here

[eum602]

There are many logs that are apparently related to this issue on the following path: "/" ; those logs indicates that the is an insufficient memory RAM.

[eum602]

I suggest the following:
At the conceptual level:

• Each instance that wishes to make private transactions may do so as long as it additionally installs an orion node in a new VM.

Requirements:

• the Orion VM: 1CPU; 2GB RAM
• VM Besu: 2CPU; 8GB RAM
• Orion ports: 4040, 4444 (the latter should only listen to the ip of the besu node).

development in ansible:

• Create the deployment scripts to instantiate a new orion node.
• Modify the deployment scripts to instantiate a new besu node.
  • As input, the ip of the orion node could be requested so that during the besu deployment it points to the orion ip.
  • The other required input is the nodeKey.pub of the orion node.

Indicate in the readme the sequence of steps to:

• deploy orion
• display besu
• modify the orion firewall rule so that it listens on port 4444 to the besu intance, and 4040 port is opened to anyone.