Use python-swift3 on SUSE instead of swift-plugin-s3
Merge pull request #103 from saschpe/release/pebbles/master-s3-suse

Use python-swift3 on SUSE instead of swift-plugin-s3
Register endpoints with public name and FQDN when possible

When using SSL, the common name field in the certificates is checked,
and using IP addresses won't work with that.

Internally to the OpenStack setup, it is always fine to use the FQDN
from the node, so we use this in the internal and admin URLs of the
endpoints.

For the public URL, we prefer to use the public name if it is set. If it
it not set, then we use the public FQDN only if SSL is enabled;
otherwise, we prefer the IP address (like before) because we're not 100%
sure that the administrator will have completed a proper DNS setup where
the public FQDN generated by Crowbar will be announced externally.

Note that swift-proxy always uses SSL.
Merge pull request #104 from vuntz/use-public-name

Register endpoints with public name and FQDN when possible
Merge pull request #14 from crowbar/release/pebbles/master

pull changes from dell
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)
fix ssl for swift
lets try to keep in mind that self-signed certs wont work for now
tiny style fix
Stop installing python-keystone package

This is not needed since commit 2d62ccb, when we moved to using
keystoneclient.middleware.auth_token.
Add crowbar-status and crowbar-failed in schema

Otherwise, barclamp_mgmt_lib.rb will edit the schema and add them, which
will make the files differ from the ones in the package.

Part of https://bugzilla.novell.com/show_bug.cgi?id=776583
Set proposal_schema_version to 2 in crowbar.yml

This is needed when we have crowbar-status/crowbar-failed in the schema.
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.
Bump Barclamp proposal schema version to 2
Merge pull request #116 from dirkmueller/schema_bump

Schema bump
Merge pull request #113 from vuntz/add-missing-attributes

Add crowbar-status and crowbar-failed in schema [12/18]
typo
initial rhel support
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