Bug 1537676

Summary:	[RFE] Control whether ntpd can be enabled / disabled on glusterfs pods and be able to specify ntpd servers
Product:	OpenShift Container Platform	Reporter:	Joel Rosental R. <jrosenta>
Component:	RFE	Assignee:	Duncan Hardie <dhardie>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.7.0	CC:	aos-bugs, bbennett, jokerman, jrosenta, madam, mmccomas, pweil, sarumuga, suchaudh
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-06-12 11:56:11 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:
Embargoed:

Description Joel Rosental R. 2018-01-23 16:51:22 UTC

1. Proposed title of this feature request
Control whether ntpd can be enabled / disabled on glusterfs pods
 
3. What is the nature and description of the request?
As a cluster admin I would like to choose whether ntpd is enabled / disabled in the glusterfs pods through a flag (which would need to be manually configured on the GlusterFS DaemonSet) , since there could be a possibility that in the hosts theirselves there is already a time sync mechanism in place, e.g: chronyd running.

Also in case it's strictly needed to run ntpd (as I understand there is no way to guarantee in this case that host has a time sync mechanism up and running), it would be good to be able to specify ntp servers ntpd should sync to.
 
4. Why does the customer need this? (List the business requirements here)
There can be some alerts at firewall level while ntpd running inside glusterfs pods try to sync with external ntpd servers.

5. How would the customer like to achieve this? (List the functional requirements here)
Be able to set a flag that enable/disable ntpd running into the pods, as well as an ENV variable where it's possible to specify to which ntpd servers sync to, e.g: internal ones instead external ones.


7. Is there already an existing RFE upstream or in Red Hat bugzilla?
Not found.

Comment 2 Sudarshan Chaudhari 2018-05-25 13:09:42 UTC

Hello, is there any update on this issue. 

Can we at least have some workaround till the feature comes in?

Also, it would be much helpful if we can have some ansible variable to define ntpd for gluster while deployment.

Thanks.

Comment 7 Kirsten Newcomer 2019-06-12 11:56:11 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.