Review provision of configuration files from debian/*.conf

[James Page]

Swift upstream provide sample configuration files, which largely overlap with the conf files in debian/*.conf.

We should look in utopic + 1 at using upstream provided configuration rather than using package specific ones to avoid breaking changes (like mandatory bind_port definition as happened during juno).

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: swift 2.2.0~rc1-0ubuntu2
ProcVersionSignature: User Name 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
Date: Thu Oct 9 10:50:44 2014
Ec2AMI: ami-000000af
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
PackageArchitecture: all
SourcePackage: swift
UpgradeStatus: No upgrade log present (probably fresh install)

[Matt Kassawara (ionosphere80)]

James,

I contribute to the upstream OpenStack installation guide and generally expect packages to include current upstream example configuration files, particularly to handle addition/change/deprecation/removal of default options. They also provide a starting point for users to learn about available options. While working on the swift content in the installation guide, I found that the packages appear to include some rudimentary configuration files, often with defunct options. If your bug covers this issue, I'll track this bug rather than opening another one for my issue.

Matt