Previously bunsen only disabled SELinux for non-infrastructure machines. This prevented access as a storage server if the infrastructure box was also functioning as a storage server.
While addressing that problem it become clear that a more developer friendly way of identifying a machine's class(es) could be established. Such change was made preceding the addressing of the SELinux issue.
Previously bunsen only disabled SELinux for non-infrastructure machines. This prevented access as a storage server if the infrastructure box was also functioning as a storage server.
While addressing that problem it become clear that a more developer friendly way of identifying a machine's class(es) could be established. Such change was made preceding the addressing of the SELinux issue.