--- tags: UI --- # Airship UI - Subcluster Support [TOC] ## As an operator I will use the Airship ui to : ### Infrastructure Management #### VM Document Management.... Does the UI have a role in visualizing or managing the document set that provides the definition for the VM's. * Help visualizing the VINO artifacts and their relationships to libvirt templates. * Libvirt template/flavor lifecycle (Creation/Editing/Deletion?) * Helm visualize the artifacts prduced by a vino cr, i.e. the apropriate vBMH's that a particular VINO cr might have produced. * Help validating the VINO CR + libvirt templates/flavor * Help producing the document perhaps coming been to articulate some default expectation or conventions or guidelines. * Help imposing/enforcing some sort of business rules.. #### VM as Node Instances Do we provide VM management cabilities such as : * Lifecycle of the VM/Node State : i.e. Reboot, PowerOFf,Power On,... * This would be applied utilizing BMH's manipulation + CAPI , etc. #### Cluster Visualization As an operator I want to understand : * How many subclusters do I have * For each subcluster: * what are composed of (how many nodes, etc) * what are the endpoints associated with it * I would like to know where they are deployed as far as rack/server/vm. * fire up an octant dashboard configured to use kubeconfig for that subcluster? :::warning How do we ensure that we can do this only if we have the appropriate priviliges. ::: ## As an tenant I will use the Airship ui to : ### Subcluster Dashboard interaction I should be able to start the ui, and given my priviliges access the subcluster dashboard. Including similar cluster visualization as described above for the operator. ### Monitoring integration ?? Besides bringing up the LMA Stack dashboards as needed, is this a plcae where we expose appropriate infrastructure telemetry to the tenant? ## Questions ### Do we need RBAC on AirshipUI to segregate between Tenant vs Operator use case or commands.