Create a more typical application stack example

[peterbourgon]

The current example is great for playing around with Scope, but I think it would be a little confusing at a meetup or demo. Let's create a more typical example, with 2 load balancers, 3–5 application instances, and a database.

[tomwilkie]

I've got a branch with a few more application containers; just in the processes of adding load balancers.

[tomwilkie]

Here you go: e8da590

It has 2 go app and 3 elastic searches.

What needs doing:

• rewrite the curl load generator, so its not forking loads of processes.
• add some nginx or haproxy
• fix Scope doesn't see connections between the pyapp and goapp in the example #111

[peterbourgon]

If you make a PR as a branch on this repo, I'll contribute some commits to convert the curl load generator to a Go version.

[tomwilkie]

Ah I just pushed that straight to master - its in experimental.

I'd say go ahead with a go load gen, and push it to master.

[peterbourgon]

Oh, OK.

[peterbourgon]

This ticket is about creating a different example, with a fewer number of types of containers.

[tomwilkie]

No! More container types is better! A typical app has loads of services.

[peterbourgon]

We can have multiple examples. But I want an example that's immediately understandable for demos and meetups, where the point is to demonstrate individual features of Scope (and Weave).

[tomwilkie]

Isn't scope's job making complicated topologies easy to understand? ;-)

On Wednesday, 27 May 2015, Peter Bourgon notifications@github.com wrote:

We can have multiple examples. But I want an example that's immediately
understandable for demos and meetups.

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

[peterbourgon]

Isn't scope's job making complicated topologies easy to understand? ;-)

[tomwilkie]

The whole complicated container topology -> group by image is really quite compelling...

[peterbourgon]

We'll also use this for the tutorial doc.

[peterbourgon]

Consider it done.