A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Action | Ironic CLI or Ironic OSC plugin | Ironic-UI | Ironic API microversion | Notes | Julia's Notes | Peter's Notes | ||||||||||||||||||||
2 | Create a node | node-create | N/A | ||||||||||||||||||||||||
3 | List nodes | node-list | N/A | ||||||||||||||||||||||||
4 | Get current boot device | node-get-boot-device | In Pike | N/A | https://bugs.launchpad.net/ironic-ui/+bug/1671567 | ||||||||||||||||||||||
5 | Get console URL | node-get-console | In Pike | N/A | https://review.openstack.org/#/c/437419/ | ||||||||||||||||||||||
6 | Get supported boot devices | node-get-supported-boot-devices | In Pike | N/A | https://bugs.launchpad.net/ironic-ui/+bug/1671567 | ||||||||||||||||||||||
7 | Get node driver vendor passthru available methods. | node-get-vendor-passhtru-methods | Version 1.1 | Needs bug entry baremetal node passthru list | |||||||||||||||||||||||
8 | Set node boot device | node-set-boot-device | In Pike | N/A | https://bugs.launchpad.net/ironic-ui/+bug/1671567 | ||||||||||||||||||||||
9 | Set console mode | node-set-console-mode | In Pike | N/A | Enables or Disables the console functionality, if supported. baremetal node console enable/disable (bug/1655690) | https://review.openstack.org/#/c/437419/ | |||||||||||||||||||||
10 | Set node maintenance | node-set-maintenance | N/A | baremetal node maintenance set/unset | |||||||||||||||||||||||
11 | Set node power state | node-set-power-state | N/A | baremetal node power (bug/1663341) | |||||||||||||||||||||||
12 | Set node provision state | node-set-provision-state | N/A | http://docs.openstack.org/developer/ironic/_images/states.svg baremetal node provide (bug/1648548) | |||||||||||||||||||||||
13 | Set node raid configuration | node-set-target-raid-config | Version 1.12 | baremetal node set --target-raid-config (bug/1648553) | |||||||||||||||||||||||
14 | View the node | node-show | N/A | baremetal node show | |||||||||||||||||||||||
15 | Update node properties | node-update | N/A | General interface for setting/updating values inside the node data structure via the API. baremetal node set | |||||||||||||||||||||||
16 | Explicitly validate node configuration | node-validate | In Ocata | baremetal node validate | |||||||||||||||||||||||
17 | Call the node driver vendor passthru interface | node-vendor-passthru | N/A | baremetal node passthru call. Needs bug entry. | |||||||||||||||||||||||
18 | Create a port | port-create | Specifically for a node | N/A | baremetal port create (bug/1648563) | ||||||||||||||||||||||
19 | List ports on a node | node-list-ports | N/A | baremetal port list --node (bug/1648563) | |||||||||||||||||||||||
20 | List all ports | port-list | N/A | baremetal 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 port | port-show | N/A | baremetal port show (bug/1648563) | |||||||||||||||||||||||
22 | Update a port | port-update | In Ocata | N/A | This 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 group | portgroup-create | In Pike | ||||||||||||||||||||||||
24 | Delete a port group | portgroup-delete | In Pike | ||||||||||||||||||||||||
25 | List port groups on a node | portgroup-list | Specifically for a node | ||||||||||||||||||||||||
26 | List ports of a port proup | portgroup-port-list | In Pike | ||||||||||||||||||||||||
27 | Show details of a port group | portgroup-show | In Pike | ||||||||||||||||||||||||
28 | Update a port group | portgroup-update | In Pike | ||||||||||||||||||||||||
29 | List available drivers | driver-list | N/A | baremetal driver list | |||||||||||||||||||||||
30 | Get properties for a driver | driver-properties | N/A | ||||||||||||||||||||||||
31 | Get driver raid properties | driver-raid-logical-disk-properties | Version 1.12 | ||||||||||||||||||||||||
32 | Show information about a driver | driver-show | N/A | [Anup] Ques: my patch for driver composition is showing half of driver info, is that enough? [TheJulia]: I kind of think so, apparently there are also some bugs in info visibility that need to get sorted in the api. Best to focus on this later. | Anup: | ||||||||||||||||||||||
33 | Get a list of driver vendor passthru commands | driver-get-vendor-passthru-methods | N/A | ||||||||||||||||||||||||
34 | Call a driver's vendor passthru | driver-vendor-passthru | N/A | ||||||||||||||||||||||||
35 | List Volume Targets | baremetal volume target list | Target is something like the volume in cinder. | ||||||||||||||||||||||||
36 | List Volume Connectors | baremetal volume connector list | A connector is like a port in ironic, and they are used to access targets. | ||||||||||||||||||||||||
37 | Add Volume Targets | baremetal 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 Targets | baremetal volume target delete | |||||||||||||||||||||||||
42 | Delete Volume Connectors | baremetal volume connector delete | |||||||||||||||||||||||||
43 | Attach a virtual interface | node-vif-attach | NOTE: 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 interfaces | node-vif-list | |||||||||||||||||||||||||
45 | delete a virtual interface | node-vif-detach | NOTE: In pike, this feature was expanded to allow "hot plugging" of virtual interfaces. | ||||||||||||||||||||||||
46 | |||||||||||||||||||||||||||
47 | API Features | Does functionality exist in Ironic CLI to control/update this? | Support Present in UI | Introduced in API version? | Notes | ||||||||||||||||||||||
48 | Port interfaces physical network object | Yes | version 1.34 | ||||||||||||||||||||||||
49 | Node object storage_interface | Yes | Version 1.33 | Can be set to "cinder" for nodes supporting booting from a remote volume. | |||||||||||||||||||||||
50 | Volume Targets and Connectors | Yes | Version 1.32 | ||||||||||||||||||||||||
51 | Driver Composition node *_interfaces | Yes, part of node object | Version 1.31 | ||||||||||||||||||||||||
52 | Driver composition driver updates | Yes | Version 1.30 | Provides visibility into the calculated default drivers, what drivers are enabled, etc. | |||||||||||||||||||||||
53 | Injection of Non-Masking Interrupt | Yes | version 1.29 | ||||||||||||||||||||||||
54 | Attach/detach of virtual interfaces for networking | Yes | version 1.28 | I think we need to consider this a high priority for queens. | |||||||||||||||||||||||
55 | Soft power actions | Yes | In Pike | Version 1.27 | |||||||||||||||||||||||
56 | Portgroup mode and properties fields added | Yes, via port object | In Pike | Version 1.26 | |||||||||||||||||||||||
57 | Allow unset of chassis_uuid from a node | Version 1.25 | |||||||||||||||||||||||||
58 | Expansion of portgroups to be available under nodes in the API | In Pike | version 1.24 | ||||||||||||||||||||||||
59 | API /v1/portgroups endpoint which provies the concept of port bonds. | Yes | In Pike | version 1.23 | Needs bug entry baremetal port group | ||||||||||||||||||||||
60 | Node ``resource_class`` field | Yes, part of the node object | In Pike | version 1.21 | This 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`` field | Yes, part of the node object | In Pike | version 1.20 | This 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_enabled | Yes, Part of a port object. | In Ocata | version 1.19 | Required to support tenant network separation. (bug/1648563) | https://bugs.launchpad.net/ironic-ui/+bug/1648563 | |||||||||||||||||||||
63 | ``adopt`` verb for provision state | Yes | Not-applicable? | version 1.17 | The 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 driver | Yes | version 1.16 | This 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 operation | Yes | In Pike | version 1.15 | This 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 operation | Yes | In Ocata | version 1.13 | bug/1648557 | https://bugs.launchpad.net/ironic-ui/+bug/1648557 | |||||||||||||||||||||
67 | API functionality for raid configuration | Yes | version 1.12 | bug/1648553 | https://bugs.launchpad.net/ironic-ui/+bug/1648553 | ||||||||||||||||||||||
68 | New nodes ot ``enroll`` state by default | Yes | Yes | version 1.11 | |||||||||||||||||||||||
69 | Node ``clean_step`` field | Yes | In Ocata | version 1.7 | This 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. | Yes | In Ocata | version 1.6 | This 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.4 | Part 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 |