Use default 'log_name' in /etc/swift/proxy-server.conf

Swift's internal logging framework is buggy, i.e when setting something
different than the default ('swift'), you'll get a warning when the
daemon is started 'No handlers could be found for logger "swift-p"'.
This should also fix log messages ending up on the tty's, e.g.:

admin:~ #
Message from syslogd@d52-54-00-26-22-39 at Jul 11 13:16:56 ...
 �<131>swift-p ERROR with Account server
 192.168.125.11:6002/c113d48aacc445cf9694699f46adf8f5 re: Trying to get
 account info for /AUTH_6e48217cbf744995a23b2f0c448557af: Connection
 refused (txn: txf795266a95d048a9b89ab103febbc007) (client_ip:
 192.168.126.2)
Stop installing python-keystone package

This is not needed since commit 2d62ccb, when we moved to using
keystoneclient.middleware.auth_token.
Raise connection limit

With more than 2 storage nodes, it happens pretty
reliably that the connection limit of two is exceeded
during initial barclamp deploy.
Merge pull request #107 from saschpe/release/pebbles/master-proxy-logging

Use default 'log_name' in /etc/swift/proxy-server.conf
Merge pull request #109 from vuntz/no-python-keystone

Stop installing python-keystone package
Use --os-* arguments instead of -I/-K/etc. to be more explicit
Use internalURL endpoint for swift commands during the chef run

This is safer than using the publicURL.
Merge pull request #114 from dirkmueller/raise_defaults

Raise defaults
webui: Use sections to group options belonging together
webui: Change select tag from false/true to true/false

This is the usual order, so stay consistent.
Merge pull request #110 from vuntz/use-internalUrl

Use internalURL endpoint for commands during the chef run
Merge pull request #117 from vuntz/use-sections

webui: Use sections to group options belonging together
Merge pull request #118 from vuntz/webui-true-false

webui: Change select tag from false/true to true/false