7f98daeb5a
For whatever reason, the modules package recommends the client package: Package: openafs-modules-dkms Depends: dkms (>= 2.1.0.0), perl:any, libc6-dev Recommends: openafs-client (>= 1.8.0~pre5-1ubuntu1) However, if that gets installed before the modules are ready, the service tries to start and fails, but maybe fools systemd into thinking it started correctly; so our sanity checks seem to fail on new servers without a manual restart of the openafs client services. By ignoring this recommends, we should install the modules, then the client (which should start OK) in that order only. Change-Id: I6d69ac0bd2ade95fede33c5f82e7df218da9458b |
||
|---|---|---|
| .. | ||
| defaults | ||
| tasks | ||
| templates | ||
| vars | ||
| 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 Xenial with ARM64, with external 1.8 series packages
- CentOS 7 with external packages
Role Variables