[openstack-dev] [ironic] should we provide 'ironic node-list --chassis' and 'ironic port-list --node' commands?
ruby.loo at intel.com
Mon Aug 29 16:22:23 UTC 2016
While working on the openstackclient plugin commands for ironic, I was thinking about the equivalents for 'ironic chassis-node-list' (nodes that are part of specified chassis) and 'ironic-node-port-list' (ports that are part of specified node). It didn't make sense to me to have an 'openstack baremetal chassis node list', since a 'chassis' and a 'node' are two different objects in osc lingo and we already have 'openstack baremetal chassis xx' and 'openstack baremetal node yy' commands. Furthermore, our REST API supports 'GET /v1/nodes?chassis=c1' and 'GET /v1/ports?node=n1'.
So I proposed 'openstack baremetal node list --chassis' and 'openstack baremetal port list --node' . To implement this, I need to enhance our corresponding python APIs. The question I have is whether we want to only enhance the python API, or also provide 'ironic node-list --chassis' and 'ironic port-list --node' commands. The latter is being proposed  and coded at . Doing this would mean two different ironic CLIs to do the same thing, but also provide a more obvious 1:1 correspondence between ironic & osc commands, and between ironic CLI and python API.
It'd be great if we could decide in the next day or so, in order to get the osc-related commands into the client this week for the Newton release.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev