Victoria Series Release Notes¶
4.0.0¶
Upgrade Notes¶
Python 2.7 support has been dropped. Last release of ironic-ui to support Python 2.7 is OpenStack Train. The minimum version of Python now supported by ironic-ui is Python 3.6.
Bug Fixes¶
Fixed
_construct_http_client() takes at least 1 argument
when creating an ironic client instance.
3.1.0¶
New Features¶
Adds support for selecting driver interfaces for dynamic drivers while creating nodes. The support for driver interfaces is not compatible with classic drivers. This feature is supported with Pike and further versions of ironic.
Adds support for injecting non-maskable interrupts into a node. A new action
Inject NMI
has been added to the node actions dropdown menu in theNode Details
page.
3.0.0¶
New Features¶
Support has been added for starting, stopping, and accessing the console associated with a node.
The action dropdown menu in the node-details panel has a new item
Enable|Disable console
.
The node-details/overview panel has a new
Console info
item in theGeneral
section. The value of this field is dependent on the console type.For
shellinabox
, the value is an anchor with the URL required to access the web console and titleshellinabox
. For others, the value is a string representation of theconsole_info
object returned by theget_console api
call.
The Node Details/Configuration tab now shows the node’s boot device.
Adds the ability to view and edit the node’s
resource_class
field on the node-details/configuration page.
Adds support for a user to be able to edit the
resource_class
field when enrolling/updating a node.
Adds support for editing portgroups from the node-details/configuration page. Each entry in the portgroups table has an associated
Edit portgroup
button that when clicked will launch a modal dialog that guides the user in making changes.
A backend mock has been added that enables better unit testing of the ironic-ui application by mocking the ironic API service. The mock utilizes angular $httpbackend handlers to intercept requests targeted at the ironic-ui server-side REST endpoints, and returns simulated responses.
A number of unit tests have been developed that illustrate the use of the backend mock functionality.
Although the backend mock is a work in progress, enough functionality already exists to support test development for the current set of in-progress features.
Adds support for viewing and managing the portgroups associated with an ironic node.
A portgroup table has been added to the node-details/configuration tab.
Each row in the table displays a single portgroup, and has column entries for its UUID, MAC address, name, and number of ports. A dropdown menu is also provided that contains actions that can be applied to the portgroup.
Detailed information for a portgroup is obtained by clicking the detail-toggle-selector (right-chevron) located in its table row. The additional information is displayed in a row expansion.
The port table in node-details/configuration tab has been modified as follows:
A column has been added that displays the UUID of the portgroup to which the port belongs.
The
Properties
column has been replaced with a column that displays only the boolean value of thepxe_enabled
property.Additional properties are displayed by clicking the detail-toggle-selector for that port in a similar manner to the portgroup table.
2.2.0¶
New Features¶
Support has been added for inspecting nodes. For a node that is in the
manageable
state, its action menu will include anInspect
button. Node action menus are located in the node-list and node-detail pages.
The current cleaning step is displayed in the Provisioning Status section of the node-details/overview page
The user is now able to abort a node cleaning operation. When cleaning is aborted the node is moved from the
CLEAN WAIT
state to theCLEAN FAIL
state. When appropriate an “Abort cleaning” action will be present in individual node action menu.
The node-details/configuration page has been extended to enable the user to edit ports after initial creation.
The user is now able to specify the pxe_enabled and local-link-connection attributes as part of defining/editing ports.
2.1.0¶
Prelude¶
This release adds support for editing nodes and moving those nodes between enroll, manageable, available and active states. It is now possible to enroll a node without all required fields for moving to manageable state being present due to the facility for editing the node once it has been created.
New Features¶
Edit nodes after creation
Move nodes between enroll, manageable, available and active states
Ability to enroll a node without all required fields for other states
2.0.0¶
Prelude¶
This release adds support for adding and deleting nodes. Support has also been added for adding and deleting ports. The panel will now be hidden if the baremetal service is not present in the scenario where the collection of running services differs between multiple keystone regions.
New Features¶
Add and delete nodes
Add and delete ports
Panel hidden if baremetal service or admin rights are not present
UX improvements across the interface
Breadcrumbs have been added
Known Issues¶
Currently it is not possible to edit a node via the UI once it has been enrolled. Therefore, the enrollment must be done accurately to ensure the node is enrolled accurately and can then be made available. At present, any errors made during enrollment can only be corrected by deleting the node and enrolling it again.