# Airshipctl Cluster Status https://github.com/airshipit/airshipctl/issues/370 ## Site ## Workload Clusters ______________________ ## PhasePlans status * Ability to identify relevant phases that are meaningful to status * Does it iterate and somehow know which ones to skip? ## Phase status * Tells me what is the state of the artifacts delivered by the phase. * Use Cases: * During deployment, if I am not waiting , I can use this to find out what happened or what is the state. * Status could be implemented by defining a new executor interface, phase status * What about Phases that do not make sense to have a Status * It could be non implemented for certain phases, .. * i.e. isogen or perhaps ephemeral phases. * How would the Phase Status work: * Consume the PhaseManifest (?? inventory object??) document. * What about using cli utils inventory object/?? might be a good source , and already has an interface to ask for status * What about things delivered via clusterctl, will not have them in the inventory object? * does multiple phases interacting with the same object cause race conditions/inconsistency. * From the contents then I can : * to determine what is part of the phase * determine what I can query for ??? * What about when Phases manipulate the same resources ? * What about clusterctl provider status ? * Do we integrate the executor with that mechanism * clusterctl creates a provider specific object? We can check if this has a status we can refer to , as part of the provider status. * What does the output look like ? * ... ________ Is status just a mechanism to retrieve - Latest PhaseManifests - PhaseManifest will include the status of the Phase - Ability to retrieve mltiple PhasesManifest/History/List of them .? Simplified: A more transactional version of this. Whiich just cares to. deliver data useful for auditing perhaps. - airshipctl phase history <name> Returns latest PhaseManifest(** InventoryObject)/Status :-) for the particular phase - airshipctl phase history <name> --all List of all PhaseManifest|Status for the particular phase. vs More about what we have been discussing. A way of understanding what is happenign with the documents that are associate with a particular phase. - airshipctl phase status <name> * gather inventory object for the phase * cli utils wouldl update the inventory object for status * deliver that information Equivalent to phase run perhaps? Too verbose We need to. explore something more succint.