Be clear about hypevisors.search used in a few CLIs
The following CLIs are doing a pattern match on the hypervisor
hostname when getting servers:
1. nova host-evacuate
2. nova host-evacuate-live (terrible name)
3. nova host-servers-migrate
4. nova host-meta (terrible name)
The fact that the hypervisor host(s) are looked up using
a pattern match is not clear in the help string for the host
argument.
This makes the help more clear and adds a warning about being
specific if you only want to target a specific host for these
operations.
In a later change we may modify the behavior in these CLIs which
allow you to find hypervisors via pattern matching, but for now
we should at least update the help text so we can backport it.
Reviewed: https:/ /review. openstack. org/487513 /git.openstack. org/cgit/ openstack/ python- novaclient/ commit/ ?id=7024d84e258 199d51607e176bb 4d8ad5e44f6991
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7024d84e258199d 51607e176bb4d8a d5e44f6991
Author: Matt Riedemann <email address hidden>
Date: Wed Jul 26 12:44:34 2017 -0400
Be clear about hypevisors.search used in a few CLIs
The following CLIs are doing a pattern match on the hypervisor
hostname when getting servers:
1. nova host-evacuate migrate
2. nova host-evacuate-live (terrible name)
3. nova host-servers-
4. nova host-meta (terrible name)
The fact that the hypervisor host(s) are looked up using
a pattern match is not clear in the help string for the host
argument.
This makes the help more clear and adds a warning about being
specific if you only want to target a specific host for these
operations.
In a later change we may modify the behavior in these CLIs which
allow you to find hypervisors via pattern matching, but for now
we should at least update the help text so we can backport it.
Change-Id: Icec03326bb4d9f 898c04e10199038 167ce5e3cce
Partial-Bug: #1667794