[Bug 1129095] New: Make yast2_caasp kubeadm ntp screen more genericly available

http://bugzilla.opensuse.org/show_bug.cgi?id=1129095 Bug ID: 1129095 Summary: Make yast2_caasp kubeadm ntp screen more genericly available Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: jsrain@suse.com Reporter: rbrown@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- (Hi Jiri!) Kubic currently has a screen, implemented in yast2_caasp, for kubeadm Node configuration, which provides a screen for configuring NTP Servers https://openqa.opensuse.org/tests/876176#step/kubeadm_settings/1 When originally proposed, it was expected this screen would be extended to include other fields over time https://en.opensuse.org/Kubic:CaaSPInstallationComparision "[later] Certificates for velum and API server" The same document stated that the NTP server configuration needed to be available for the MicroOS or CaaSP Plain System system roles, but that doesn't seem to be how it was implimented in YaST, as the ntp dialogue is part of the inst_kubic_kubeadm_role Therefore, this is a bug that needs to be fixed. I see a few solutions Option A) would be to rename inst_kubic_kubeadm_role to something like inst_kubic_ntp_config, and I'll just plumb the additional dialogue into every system role with But that doesn't make much sense given the whole point of is for when a YaST module cant be used everywhere in the product Both the current Kubic installation media and the future MicroOS installation media want this ntp configuration screen on every system role. I can also see it being desired in other openSUSE distributions, as a lightweight alternative to the more complex timezone module. So, Option B) would be to remove inst_kubic_kubeadm_role from yast2_caasp (which removes yast2_caasp as a dependency in Kubic & MicroOS) and instead implement it as a module in yast2_installation, with a name something like "ntp_setup" I have a preference for Option B), Jiri what do you think? -- You are receiving this mail because: You are on the CC list for the bug.