Missing edges between the ECS-demo containers

[2opremio]

Steps to reproduce.

1. Launch the scope variant of the ECS demo (which uses scope:latest)

   git clone -b aws-ecs-scope git@github.com:weaveworks/guides.git
   cd guides/aws-ecs
   ./setup
   

   Which should output three urls let's call them u1, u2, u3.

2. Make sure that the Http Servers are communicating with the Data Producers:

   while true; do 
     for I in u1 u2 u3; do 
       curl $I
     done
   done

3. Open Scope in any of the three instances (e.g. u1:4040)

   The HttpServer and DataProducers ( the ecs-weave-ecs... containers) should be connected since they are communicating with each other. However they are not.
   

[2opremio]

In fact, I also expect an edge between all the weavescope containers since every probe is reporting to all the apps.

[tomwilkie]

@2opremio attaching the contents of /api/report and /api/topology/containers to bugs like this will massively help narrow it down.

[2opremio]

There you go https://gist.github.com/2opremio/9494a1f48b340a620526

[tomwilkie]

I've figured this out.

My bad.

[2opremio]

Great that you figured it out. Out of curiosity, can you elaborate on what's causing it?

[tomwilkie]

I thought I had it but I didn't. Sorry. Still working on it.

[peterbourgon]

Any update here? This is the only remaining release-blocker.

[tomwilkie]

The attached or fixes some issues but doesn't fix it 100%.

I've got two test cases: cross host communication over the weave network,
and cross host communication via docker port mapping. (1) works now, (2)
doesn't.

I don't know why it doesn't work yet.

Feel free to review the pr, I see no reason why it can't go in.

On Saturday, September 12, 2015, Peter Bourgon notifications@github.com
wrote:

Any update here? This is the only remaining release-blocker.

—
Reply to this email directly or view it on GitHub
#446 (comment).

[tomwilkie]

This is mostly fixes - pseudo nodes are working again, and short lived connections from containers to the internet are working.

But the short lived connection code doesn't deal with connections coming from the internet, as they go to the hosts IP, not the containers. We know the port mapping for containers, so we should be able to fix this. See #493