IdPv3.0.0a1 Load Testing Setup

[Nate Klingenstein]

I'll be playing around with load testing IdPv3.0.0a1 using an AWS environment.  Here's how:

1)  The Grinder nodes and IdP nodes are all registered with Salt(Salt master on the Grinder master) so that I can issue commands on all nodes of a given type simultaneously without knowing the nodes' addresses, which will change often since I'll be resizing hardware
2)  2 IdP nodes, described below
3)  Really big single-VM RedHat 389 LDAP Directory with 500,000 person entries
4)  Three big The Grinder Ubuntu 12.04 nodes managed by one master grinder node with console

IdP nodes:

1)  8GB SSD without fixed IOPS
2)  64-bit AMI Linux 2014.3, which smells like CentOS 6.5
3)  t1.micro while idle, resized to x3.loic before firing.  Effectively arbitrary amounts of CPU and RAM available.  I can also use moderate IdP hardware to simulate extremely heavy load, or constrain hardware in certain ways.
4)  Load balancing will be ELB 443 -> node 8443.  I will be using unauthenticated TLS between the node and the ELB to get the load without the trust.
5)  Grinder nodes and IdP nodes are both in us-west-2b so I can pulverize without network being a consideration
6)  It should be very easy to swap other servlet containers and JRE's in and out on the nodes, as well as tuning them.

If a committer wants shell and sudo and instructions on how to use the environment, please send me a note and your SSH public key off-list.  You'll need me to resize and start or stop nodes, but the rest should be doable by anyone.