Feature Overview
This feature enables console access to Bare Metal nodes via the Dashboard service, leveraging compatibility with the console functionality from the Compute service. This integration simplifies node management by providing consistent console interaction through a unified interface. The feature aligns with OpenStack's infrastructure management capabilities, improving operational efficiency for Bare Metal environments.

Goals
The goal is to provide users with seamless access to Bare Metal node consoles through the Dashboard service, ensuring compatibility with Compute service console features. This improves user experience by unifying console access methods for Bare Metal and Compute nodes, reducing operational complexity.

Who Benefits?

• Cloud Administrators benefit from a unified console interface across Bare Metal and Compute nodes, reducing time spent on managing separate console access tools.
• Operators who manage hybrid environments with both Bare Metal and virtualized infrastructure will see an improvement in workflow efficiency.

Requirements

Use Cases

• Primary Users: Cloud administrators and operators managing Bare Metal nodes.
• Scenarios:
  • Admins using the Dashboard to access Bare Metal node consoles for troubleshooting.
  • Operators who need to interact with nodes remotely during maintenance or diagnostics.
• User Interface: The feature will be available as part of the current OpenStack Dashboard (Horizon) user interface.

Out of Scope

• Advanced console customization options for Bare Metal nodes.
• Automated workflows triggered from console output.

Background and Strategic Fit
This feature provides critical functionality for organizations relying on both Bare Metal and virtualized environments. It enhances operational efficiency and consolidates infrastructure management tools under a single UI. For developers and testers, the primary focus is ensuring parity between Compute and Bare Metal services.

Assumptions

• Prerequisites: The Compute service console functionality is fully operational.
• Hardware Assumptions: Bare Metal nodes must support console access.
• Resource Assumptions: Adequate network connectivity between Dashboard service and Bare Metal nodes.

Customer Considerations

TBD

Documentation Considerations

• Impact: Updates to existing content and Release Notes are required.
• Key Concepts:
  • How to access consoles via the Dashboard.
  • Security best practices for managing node access.
• Reference Material: Link to Compute service console documentation for guidance on configuration and security (e.g., OpenStack Serial Console Documentation).

Interoperability Considerations

• Impacted Products:
  • Compute service (Nova)
  • Bare Metal service (Ironic)
  • OpenStack Dashboard (Horizon)
• Test Scenarios: Ensure console access works seamlessly in multi-node environments involving both Compute and Bare Metal nodes.

Questions

Resources

https://docs.openstack.org/ironic/latest/admin/console.html

Changes
The initial version of this RFE proposed serial consoles as the specific mode of interaction and use, however upstream discusison of this topic from the development team's recent interactions has yielded that serial console interaction is not advisable moving forward. The consensus seems to be yielding more towards focusing on just graphical console use with the existing high level interface design which resolves a number of unknowns. A overall specification change has been proposed upstream to help solidify these discussions, and if agreed upstream we can likely better design and scope this in a more tactical fashion. https://review.opendev.org/c/openstack/ironic-specs/+/933937