using private ip when talking to the dashboard's not publicly-exposed ports
not updating api info if we get a malformed soap response
sending at most 50 logs per batch in the appcontroller, instead of all of them at once
using the login node's public ip address when sending logs, because the appdashboard there binds to the public ip (and not the private ip)
extracted number of logs per batch into a constant
extracted ip filenames that the loggers use to constants
properly handling HTTPErrors in AppControllerClient, by letting the caller specify if they are allowed and handling it accordingly, as opposed to just returning True
Merge remote-tracking branch 'org/testing' into dashboard-use-private-ip
keeping name of caught exception consistent in appcontroller client
not erasing the cache if there is a cache miss
Merge pull request #458 from shatterednirvana/dashboard-use-private-ip

Using private IP when waiting for Dashboard ports to open