Hello,

with yum info audit I can confirm that the package audit is installed.
with rpm -ql audit I can see a list of files, including /usr/share/doc/audit-2.3.7/*
But those files are missing
ls: cannot access /usr/share/doc/audit-2.3.7: No such file or directory

CentOS 6.7
Can you help with that?
Thanks.

# fc29
dnf install -y docker docker-compose

# docker-1.13.1-62.git9cb56fd.fc29.src.rpm
# docker-compose-1.22.0-2.fc29.src.rpm

What's a good way to make this (only installing from a limited set of package repos) optional?

Based on the current README my expectation was that the certificate_file, certificate_key_file and certificate_chain_file directives needed to point to local (on the ansible control node) which would get installed by the role.

It turns out that the paths are entered in the vhosts.conf.
No files are deployed so the playbook needs to handle that outisde this role.

I believe it would be useful

The spring security code is left on feature branch.
Looking at ProductAppApplication.java, in the tutorial,

@GetMapping(path = "/products")
public String getProducts(Principal principal, Model model){
   model.addAttribute("principal",principal);
   model.addAttribute("products", productService.getProducts());
   return "products";
}

whereas in GitHub

@GetMapping(path = "/

Currently iptables is completely disabled for RHEL 6 because I don't like dealing with iptables. If someone could fix that, it would be just great.

I've been attempting to deploy OKD to BYO Infrastructure by setting

openshift_deployment_type: origin
deployment_type: origin

Currently running into the error:

Error reading manifest latest in registry.redhat.io/openshift/origin: unknown: Not Found

I'm assuming there's issues with my configuration but can't seem to find documentation on how to use casl-ansible for an OKD depl

certs = shared[Cert_List]
certs.num_tracked # number of certificates tracked from first line
2
len(certs) # number of requests stored - may be smaller than num_tracked
2
certs.requests

The official Galera deployment guidelines make a few recommendations that I'd love to see implemented into this playbook.

1. Each datacenter should have a unique gmcast.segment ID so that the nodes know who is closest and who is in each DC (Helps with replication optimization). It would be great to be able to define this in the host or group inventory.

2. Use the server private IP address in