...
- VM2 ports were opened, but IP address is mapped to VM1 with alternate ports forwarding to VM2. Lincoln (Edge Lab) said:
"This rule is in place now. Like we discussed a long long time ago, the second VM is still using private IP address space, so the rules are allowing port mapping via NAT.So, the open-horizon.lfedge.iol.unh.edu:32348 mapps through to the VM2's internal IP address, same for port 32349. The other original ports open for that host name remain the same, passing through to VM1.
Hopefully this is not going to get too complicated. The idea was / is to map a single public IPv4 address (scarce resource) to both VMs, using different port sets, and allow your team to update / maintain each VM independently. Right now, VM1 still has this public IP address assigned directly, but when it's time to upgrade that one, we would 'move' it to be on the same private subnet as VM2."
- Instructions for loading data to (alternate) query node.
- Potential CFP submission to https://events.linuxfoundation.org/one-summit-north-america/program/cfp/#overviewor before December 3
"It would have impact if we could get our Sponsor User to talk about how they used our open source feature request process to collaborate with all of us to develop a feature that is then adopted by a commercial solution."
Action items
- Joe Pearson Load Open Horizon Agent data into new table