I am not so sure that having multiple resource
types in the same file is supported as of 2.7.11
I am refactoring this code so that the upstart define
resides in its own file according to our standards.
So that it can be accessed by the swift proxy
from this address.
Previously, it was binding to eth0 and swift proxy
was trying to access it via localhost.
This commit adds an example of how to sync rings between
nodes.
The ringbuilder role exports resources representing the ring
databases that need to be synced.
The storage node can then just collect these resources
This commit adds puppet code to handle syncing of the ring
databases.
The class swift::ringserver is used to set up an rsync server
that serve out the ring databases.
The define swift::ringsync is used to rsync these ring databases
to the other hosts.
The swift ring db converts integers into floats with 2 decimal
points percisions. This was causing the ring resources to constantly
resync.
This commit munges weight in the type to the proper format.
This commit updates the spec tests so that they should work.
- the ssh module that they depend on had introduced a dependency on
the operatingsystem fact
- tests had not been updated to reflect using xinetd and not the service
to run the rsync daemon
- update travis-ci to include the xinetd module
Since rsync is now managed by xinetd, it is
necessary to remove the references to the rsync
service.
This was previously causing catalog compilation failures.
Also updates travisci and the unit tests
Previously, using the rsync sevices on Ubuntu
did not actually work.
After reading the init script, I decided that it
is annoyingly different from Redhat's implementation
so I have chosen to use xinetd to make the module more
consistent between the distros.
This commit adds the parameter proxy_local_net_ip to
the swift::proxy class for the all in one example.
This parameter had been changed to be required in a previous commit,
but the example had not been updated.
I changed the tests so that they check individual
lines of the resulting swift proxy file as opposed to
the entire file contents.
This was done so that tests can be associated with
only the parts of the resulting file they are related
to.
It is possible that the memcache server(s) may
reside on different machines than the swift
proxy.
This commit decouples the configurations of the
two services.
Previously, the binding address for all services
was set to localhost.
This is not going to be a commonly used value
for production deployments.
The defaults for address have been removes b/c
there isn't really a sensible default. This is
something that the users should have to set.
Previously, all of the storage server types
(account, container, proxy) were always
configured to be installed on the same node.
It often makes sense to only have the account and
container together, and to put the object server on
a different node. (or its possible that other
configurations make sense)
This commit refactors the swift module so that
each of the types of nodes can be built
independently of each other.
The spec tests now expect the modulepath
spec/fixtures/modules to contain links to all
of the modules that are required to run the
unit tests.
In order to run the tests, I need to create links
for these modules, but if I check in those links, it
will mess up the tests when they run in travis-ci.
Previously, swift::storage::xfs was not passing
the correct variable for mnt_base_dir to
swift::storage::mount. $mount_base_dir was incorrectly
specified.
This commit resolves this mistake and ensures that the correct
variable is passed.
Previously, the package for swauth of the swift
proxy was being added based on a variable that
was never set.
This commit updates that conditional to use the
correct variable.
Previously, a copy and paste error had resulted
in 3 definitions of the trunk ppa class.
Two of those were intended to be swift::repo::trunk
and swift::repo::release.
This commit corrects this error.
The default devices path for the storage class
was incorrectly set to /srv/nodes.
This commits updates it to /srv/node so that it is
consistent with the rest of manifests in this module.
Previously, all of the ports used by the storage
class were hardcoded.
This commits adds the following class parameters to
the swift::storage class to allow for configuration
of the ports used by a storage server:
- object_port
- container_port
- account_port
Removes the puppetmaster node declaration so that
this manifest can be imported from the openstack's
manifests/site.pp (so that the openstack project
and the swift project can use the same node
declarations when swift is added as a submodule to
the openstack project)
