feat(OKDInstallation): Implemented bootstrap of okd worker node, added features to allow both control plane and worker node to use the same bootstrap_okd_node score #198
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/okd-nodes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Quick review done, overall looks pretty good but deserves some improvements, mostly naming.
@@ -79,2 +71,3 @@topology: &HAClusterTopology,) -> Result<Outcome, InterpretError> {self.render_and_reboot().await?;OKDNodeInterpret::new(HostRole::Worker)On passe par le score et on call
.executedessus directement. On n'instance pas d'Interpret directement en dehors du get_interpret d'un score.Ca permet d'instrumenter les scores et suivre ce qui se passe comme il faut.
@@ -0,0 +26,4 @@};#[derive(Debug, Clone, Serialize, new)]pub struct OKDNodeScore {Le nom ne dit pas ce que ca fait. OKDNodeScore ce n'est pas un nom assez descriptif. Quelque chose comme PrepareOKDNodeInstallationScore ou AddNodeToOKDClusterScore. Bref, je n'ai aucune idee de ce que ca fait, ca m'obliger a aller lire le code ce qui ralentis tout ceux qui vont lire ce code dans le futur.
https://medium.com/@pabashani.herath/clean-code-naming-conventions-4cac223de3c6
Je l'ai modifié pour avoir le nom
OKDNodeInstallationScore, je croix que c'est mieux aligné avec l'info partagé en haut@@ -0,0 +264,4 @@// 4. Reboot the nodes to start the OS installation.self.reboot_targets(&nodes).await?;// TODO: Implement a step to wait for the control plane nodes to join the clusterFix this comment, not accurate in the context.
@@ -0,0 +54,4 @@}//TODO unsure if this is to be implemented here or notimpl OKDRoleProperties for StorageRole {For now we can completely delete the storage role, it is not used. We will use worker nodes for storage, and we will autodetect their storage capabilities and orchestrate at a higher level than the OKD role.
LGTM