Feature Overview
...
Goals
At ** the time of writing, in 2.10 deploying 4.15 if you configure NTP sources through CIM then deploy HCP with ACM, the ntp configuration is not applied to the resulting deployment.
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
Requirement | Notes | isMvp? |
---|---|---|
CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
NTP configuration added to a host in infraenv is also present on HCP post deployment | ntp config added to a host in CIM needs to also be applied to HCP | YES |
(Optional) Use Cases
This Section:
- deployment of HCP on top of an on-premise deployed with ACM
Questions to answer
- ...
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- it may not be possible to push that ntp config into the hcp deployment but this may have to be done as day 2 again ( https://issues.redhat.com/browse/MGMT-10962 )
Customer Considerations
- a customer would have to work around this by using a MachineConfig manifest (
https://docs.openshift.com/container-platform/4.15/hosted_control_planes/hcp-machine-config.html, https://github.com/openshift/assisted-service/blob/master/docs/user-guide/install-customization.md#configure-storage-on-nodes-using-machineconfig-manifests https://docs.openshift.com/container-platform/4.15/hosted_control_planes/hcp-machine-config.html )
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
this may not need much additional documentation once implemented, but sharing the workaround would be good
- relates to
-
RFE-5046 Ability to sync OS time from NTP and update HW clock at the time of installation of OpenShift
- Accepted