The policy of giving projects vanity domains stopped about 5 years ago.
swift.openstack.org is a redirect to the canonical location -
docs.openstack.org/developer/swift. While we are not aiming to remove
the redirect any time in the forseeable future due to existing published
links pointing to it, we should at the very least stop adding more of
those links to the world.
Change-Id: Ia56ce22c65c1fac29a2d8fb367797a4d7929a9b4
The 'swiftinit' provider is a custom provider of the service type
that manages swift services using swift-init.
Use of the swiftinit service provider is optional, the default is
to use service providers specified in params file. This provider
also manages swift services starting at boot by adding or removing
a templated init or services file and making systemctl calls.
See README for more detail.
A wrapper defined type 'swift::service' has been created to simplify
use of the swiftinit provider without adding logic to every class.
this wrapper also aids in input validation and testing of the
swiftinit provider.
Two extra runs of apply_manifest have been added to the
basic_swift_spec acceptance test. The service_provider
is set to "swiftinit". The first run catches any errors upgrading
to the swiftinit service provider and the second run tests
idempotency.
This patch is an initial step towards using swift-init to manage
multiple swift services out of different configuration files such
as is needed to run a separate replication network.
Change-Id: I2f71c82c7a6c463f8c76a193409c0a17daa15bda
Before this fix the following services where missing:
root@swift-storage-01:~# swift-init status all|grep ^No
No container-updater running
No account-auditor running
No object-auditor running
No object-expirer running
No container-auditor running
No account-reaper running
No container-sync running
No object-updater running
After this commit:
root@swift-storage-01:/etc/init# swift-init status all|grep ^No
No proxy-server running
No object-expirer running
It's OK for the proxy-server to be stopped since it's a storage
.
You only need to manage one object-expirer per cluster, so this not
place to manage it either. See:
http://docs.openstack.org/developer/swift/overview_expiring_objects.html
This code removes the authentication code that is
not using keystone.
I could not get the code to work when things were configured to
use keystone and found that the tests still worked if I removed the
code.
In the current trunk PPA for oneiric (which is what
I am using for testing), the upstart files seem
to have a problem where they only will start the
swift servers if the file:
/etc/swift/<server_name>-server
exists. Raised as issue: 931893
in Launchpad.
This commit adds puppet code to deploy custom
upstart scripts that have fixed this issue.
