5eeeedbc8b
Over time we've had various different reasons for installing our own OpenAFS packages in various situations and we haven't kept the when: flags totally up to date. Currently, we need the 1.8.6-5 packages with the January 20201 timestamp fix installed everywhere; fix this. I think that on long-running servers, the have the PPA installed from prior iterations (I don't think we've ever *removed* it). So things like executors are still running with our packages, perhaps somewhat unintentionally. Update the comments a little to reflect what's going on. Change-Id: I6a58c23daf85cf8fa005e3dad84a665343a947bc |
||
|---|---|---|
| .. | ||
| defaults | ||
| files | ||
| tasks | ||
| templates | ||
| vars | ||
| README.rst | ||
README.rst
An ansible role to configure an OpenAFS client
Note
This role uses system packages where available, but for platforms or architectures where they are not available will require external builds. Defaults will pick external packages from OpenStack Infra builds, but you should evaluate if this is suitable for your environment.
This role configures the host to be an OpenAFS client. Because OpenAFS is very reliant on distribution internals, kernel versions and host architecture this role has limited platform support. Currently supported are
- Debian family with system packages available
- Ubuntu LTS family with external 1.8 series packages
- CentOS 7 and 8 with external packages
Role Variables