Bug 1399061

Summary: Running the gluster container without systemd
Product: Red Hat Gluster Storage Reporter: Mohamed Ashiq <mliyazud>
Component: rhgs-server-containerAssignee: Humble Chirammal <hchiramm>
Status: CLOSED WONTFIX QA Contact: Anoop <annair>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: cns-3.4CC: hchiramm, madam, rcyriac, rhs-bugs, rtalur, sankarshan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-24 14:34:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mohamed Ashiq 2016-11-28 08:19:09 UTC
We had to run more than one process like rpc-bind and glusterd. Now as we have removed the dependency of rpcbind from glusterd in the container. We requirement of systemd is very minimum. We should be able to run gluster container without systemd.

Comment 2 Humble Chirammal 2016-11-28 08:40:39 UTC
As discussed we can work on this as well. One thing to note here is, how are we going to ship it if there is a possibility. Because, we may not be able to "sell" both versions, mostly we have to stick with one. Before that we need to qualify the new versions. However lets have a proper sanity testing from Dev side and take it upto next levels.

Comment 3 Mohamed Ashiq 2016-11-28 08:55:49 UTC
I feel We can stick to systemd-less images in future. As it will reduce the overhead of facing systemd related bugs. If I am able to do all the operation of RHGS-server-docker containers today on an image without systemd, I feel for long time we should stick to systemd-less image. I am gonna try this and update here.

Comment 6 Yaniv Kaul 2019-01-24 14:34:57 UTC
Unlikely to happen due to capacity.
Please reopen if you think we need to further discuss.