Plan for inclusion in Fedora?

[nixpanic]

What is the plan to include this in Fedora? When there is a review filed for this package, please pint me to it.

For inclusion in the CentOS Storage SIG, there is a string preference to have the package reviewed and included in Fedora.

[wrabcak]

Hi,

Yes, plan is to include it to Fedora. Better way is to create this package as sub-package of glusterfs so there is no need to new rpm package include process to Fedora. Then it should be tested that if glusterfs is installed on system also glusterfs-selinux is installed and glusterfs SELinux policy is installed with different priority than 100 (to check it use: #semaange -lfull | grep -v 100). If it wil lwork, then I'll be able to remove glusterfs SELinux policy from distribution selinux-policy rpm package.

THanks,
Lukas.

[nixpanic]

From my understanding, the decision through https://review.gluster.org/c/glusterfs/+/20181 was to create a stand-alone package.

Gluster deployments are mostly combined with multiple projects, and the (main) glusterfs repository should not need changes for SELinux requirements of other projects/components. Think of gluster-block, nfs-ganesha, glusterd2 and others. Placing all SELinux rules/policy in a single stand-alone project seems more practical.

@mchangir can you explain the plans for this repo?

[wrabcak]

Okay, thanks for clarification. Standalone package make more sense.

[mchangir]

@nixpanic I'm new to the github and upstream stuff. So, I don't have any plans for this repo yet. What should a typical plan include ?

[nixpanic]

On Wed, Aug 22, 2018 at 09:54:41PM -0700, mchangir wrote: @nixpanic I'm new to the github and upstream stuff. So, I don't have any plans for this repo yet. What should a typical plan include ?

This would include at least the following: 1. get the package in common distributions that contain Gluster 2. have users install the new package 3. plan for dropping the SELinux policy from the selinux-policy project There probably should be some automated tests as well. At least it needs to be made sure that the policy builds whenever there is a Pull-Request. How far is this policy from being completely functional? Once that is the case, we should get the processes started to get it included in the distributions.