[RFE] Revisit 'openstack baremetal node maintenance set|unset'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-ironicclient |
Invalid
|
Low
|
M V P Nitesh |
Bug Description
I'm not sure that our two OSC commands for node maintenance are 'right'. We have:
- openstack baremetal node maintenance set
- openstack baremetal node maintenance unset
Sam Betts prefers enable/disable, or on/off, because he thinks of it as 'maintenance mode'.
There is an existing openstack command that has maintenance:
$ openstack -h host set
usage: openstack host set [-h] [--enable | --disable]
Set host properties
positional arguments:
<host> The host to modify (name or ID)
optional arguments:
-h, --help show this help message and exit
--enable Enable the host
--disable Disable the host
--enable-
--disable-
Although I'm not totally convinced the host command is similar to ours. For one thing, there is no 'openstack host unset' command.
I think if we want an 'openstack baremetal node maintenance <action>', we ought to decide what set of verbs/actions work well with maintenance:
a. on/off
b. enable/disable (that host command would be a vote for this)
c. set/unset
On the other hand, I wonder whether we should just modify those via the existing 'openstack baremetal node set|unset' commands, eg:
- openstack baremetal node set --maintenance [<reason>]
- openstack baremetal node unset --maintenance
Changed in python-ironicclient: | |
importance: | Undecided → Low |
Changed in python-ironicclient: | |
assignee: | nobody → Himanshu Kumar (singh5himanshu) |
Changed in python-ironicclient: | |
status: | In Progress → Triaged |
Changed in python-ironicclient: | |
assignee: | nobody → M V P Nitesh (m-nitesh) |
summary: |
- Revisit 'openstack baremetal node maintenance set|unset' + [RFE] Revisit 'openstack baremetal node maintenance set|unset' |
I also noticed this osc command, has --disable and --disable-reason. (There's no corresponding 'unset' command). Which is a vote for 'openstack baremetal node set --maintenance I think.:
usage: openstack compute service set [-h] [--enable | --disable]
[ --disable- reason <reason>]
< host> <service>
Set service command
positional arguments:
<host> Name of host
<service> Name of service
optional arguments: -disable- reason <reason>
Reason for disabling the service (in quotas). Should
be used with --disable option.
-h, --help show this help message and exit
--enable Enable service
--disable Disable service
-