Ironic Client/UI features comparison
Comments
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
ActionIronic CLI or Ironic OSC pluginIronic-UIIronic API microversionNotesJulia's NotesPeter's Notes
2
Create a nodenode-createN/A
3
List nodesnode-listN/A
4
Get current boot devicenode-get-boot-deviceIn PikeN/A
https://bugs.launchpad.net/ironic-ui/+bug/1671567
5
Get console URLnode-get-consoleIn PikeN/A
https://review.openstack.org/#/c/437419/
6
Get supported boot devicesnode-get-supported-boot-devicesIn PikeN/A
https://bugs.launchpad.net/ironic-ui/+bug/1671567
7
Get node driver vendor passthru available methods.
node-get-vendor-passhtru-methods
Version 1.1Needs bug entry
baremetal node passthru list
8
Set node boot devicenode-set-boot-deviceIn PikeN/A
https://bugs.launchpad.net/ironic-ui/+bug/1671567
9
Set console modenode-set-console-modeIn PikeN/AEnables or Disables the console functionality, if supported.
baremetal node console enable/disable (bug/1655690)
https://review.openstack.org/#/c/437419/
10
Set node maintenancenode-set-maintenanceN/Abaremetal node maintenance set/unset
11
Set node power statenode-set-power-stateN/Abaremetal node power (bug/1663341)
12
Set node provision statenode-set-provision-stateN/Ahttp://docs.openstack.org/developer/ironic/_images/states.svg
baremetal node provide (bug/1648548)
13
Set node raid configurationnode-set-target-raid-configVersion 1.12baremetal node set --target-raid-config (bug/1648553)
14
View the nodenode-showN/Abaremetal node show
15
Update node propertiesnode-updateN/AGeneral interface for setting/updating values inside the node data structure via the API.
baremetal node set
16
Explicitly validate node configurationnode-validateIn Ocatabaremetal node validate
17
Call the node driver vendor passthru interfacenode-vendor-passthruN/Abaremetal node passthru call. Needs bug entry.
18
Create a portport-createSpecifically for a nodeN/Abaremetal port create (bug/1648563)
19
List ports on a nodenode-list-portsN/Abaremetal port list --node (bug/1648563)
20
List all portsport-listN/Abaremetal port list (bug/1648563)So, I could go either way, but portgroups might change that perspective in that one takes ports and binds them together. Then again, recent incidence of users misunderstanding what a port is in ironic has casued some confusion.We have chosen not to support working with ports indepedent of their parent node. Is this still a good assumption?
21
Show a portport-showN/Abaremetal port show (bug/1648563)
22
Update a portport-updateIn OcataN/AThis would be required to correct any issues for a deployment with nova where a port vif has been orphaned, or if local_link_connection information needs to be corrected in a tenant network separation deployment scenario.
baremetal port set (bug/1648563)
23
Create a port groupportgroup-createIn Pike
24
Delete a port groupportgroup-deleteIn Pike
25
List port groups on a nodeportgroup-listSpecifically for a node
26
List ports of a port proupportgroup-port-listIn Pike
27
Show details of a port groupportgroup-showIn Pike
28
Update a port groupportgroup-updateIn Pike
29
List available driversdriver-listN/Abaremetal driver list
30
Get properties for a driverdriver-propertiesN/A
31
Get driver raid propertiesdriver-raid-logical-disk-propertiesVersion 1.12
32
Show information about a driverdriver-showN/A[Anup] Ques: my patch for driver composition is showing half of driver info, is that enough?
33
Get a list of driver vendor passthru commands
driver-get-vendor-passthru-methods
N/A
34
Call a driver's vendor passthrudriver-vendor-passthruN/A
35
List Volume Targetsbaremetal volume target listTarget is something like the volume in cinder.
36
List Volume Connectorsbaremetal volume connector listA connector is like a port in ironic, and they are used to access targets.
37
Add Volume Targetsbaremetal volume target create
38
Add Volume Connectors
baremetal volume connector create
39
Update Volume Targets
baremetal volume target set/unset
40
Update Volume Connectors
baremetal volume connector set/unset
41
Delete Volume Targetsbaremetal volume target delete
42
Delete Volume Connectors
baremetal volume connector delete
43
Attach a virtual interfacenode-vif-attachNOTE: In pike, this feature was expanded to allow "hot plugging" of virtual interfaces.I think VIF attachments should be on our must do list for queens.
44
list a virtual interfacesnode-vif-list
45
delete a virtual interfacenode-vif-detachNOTE: In pike, this feature was expanded to allow "hot plugging" of virtual interfaces.
46
47
API FeaturesDoes functionality exist in Ironic CLI to control/update this?Support Present in UIIntroduced in API version?Notes
48
Port interfaces physical network objectYesversion 1.34
49
Node object storage_interfaceYesVersion 1.33Can be set to "cinder" for nodes supporting booting from a remote volume.
50
Volume Targets and ConnectorsYesVersion 1.32
51
Driver Composition node *_interfacesYes, part of node objectVersion 1.31
52
Driver composition driver updatesYesVersion 1.30Provides visibility into the calculated default drivers, what drivers are enabled, etc.
53
Injection of Non-Masking InterruptYesversion 1.29
54
Attach/detach of virtual interfaces for networkingYesversion 1.28I think we need to consider this a high priority for queens.
55
Soft power actionsYesIn PikeVersion 1.27
56
Portgroup mode and properties fields addedYes, via port objectIn PikeVersion 1.26
57
Allow unset of chassis_uuid from a nodeVersion 1.25
58
Expansion of portgroups to be available under nodes in the APIIn Pikeversion 1.24
59
API /v1/portgroups endpoint which provies the concept of port bonds.YesIn Pikeversion 1.23Needs bug entry
baremetal port group
60
Node ``resource_class`` fieldYes, part of the node objectIn Pikeversion 1.21This field is intended for nova use starting in Ocata, however operators will need to be able to update this field. (bug/1672709)
https://bugs.launchpad.net/ironic-ui/+bug/1672709
61
Node ``network_interface`` fieldYes, part of the node objectIn Pikeversion 1.20This field is used by tenant network separation. By default, nodes should end up being created with a ``flat`` network driver, however that network driver has no concept of switch fabric configuration. The ``neutron`` driver supports updating switch configuration. In order to use this, operators _also_ need to be able to view/update port level local_link_information details. (bug/1648566)
https://bugs.launchpad.net/ironic-ui/+bug/1648566
62
Add local_link_connection and pxe_enabledYes, Part of a port object.In Ocataversion 1.19Required to support tenant network separation. (bug/1648563)
https://bugs.launchpad.net/ironic-ui/+bug/1648563
63
``adopt`` verb for provision stateYesNot-applicable?version 1.17The adopt verb is intended for operators to be able to "add" a node that is "in-use" to ironic. It is part of the state machine workflow.
64
Filter nodes by driverYesversion 1.16This may be useful to display a list of nodes by driver. Needs bug entry.This can be done using the magic-search fuctionality in the node-list view.
65
Ability to initiate a manual cleaning operationYesIn Pikeversion 1.15This is via setting the node provision state, with a blob JSON attached that defines the explicit steps to be performed. Needs bug entry.
https://bugs.launchpad.net/ironic-ui/+bug/1648559
66
Ability to abort a cleaning operationYesIn Ocataversion 1.13bug/1648557
https://bugs.launchpad.net/ironic-ui/+bug/1648557
67
API functionality for raid configurationYesversion 1.12bug/1648553
https://bugs.launchpad.net/ironic-ui/+bug/1648553
68
New nodes ot ``enroll`` state by defaultYesYesversion 1.11
69
Node ``clean_step`` fieldYesIn Ocataversion 1.7This allows a user to see which step the node is presently in during the cleaning process.
https://bugs.launchpad.net/ironic-ui/+bug/1648550
70
Hardware introspection via ironic-inspector, ``inspect`` provision state.YesIn Ocataversion 1.6This step directs ironic to attempt to learn more about the hardware by performing "introspection" to learn about capabilities and hardware configuration. (bug/1648548)
https://bugs.launchpad.net/ironic-ui/+bug/1648548
71
``manageable`` state via ``manage`` provision state action.Yes, via provision state.Used, but only for enrollment?version 1.4Part of the state machine.
72
73
Bulk enrollment of nodes
74
Ability to specify a config-drive when setting provision state to active
75
Some node state transitions need to be added such as 'manageable-provide-clean failed'
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
As of the end of Pike
Copy of As of beginning of Pike