[tc][all] Follow up pain point discussion

Pierre Riteau pierre at stackhpc.com
Thu Dec 16 15:11:50 UTC 2021


On Sun, 12 Dec 2021 at 22:08, Sean Mooney <smooney at redhat.com> wrote:
>
> On Fri, 2021-12-10 at 22:02 +0100, Pierre Riteau wrote:
> > On Mon, 6 Dec 2021 at 11:59, Stephen Finucane <stephenfin at redhat.com> wrote:
> > > novaclient ✅ full feature parity  since 5.5.0
> > >
> > > We finally introduced a proper '--block-device' option for 'server create' in 5.5.0, which closed our remaining RFE. There have been bugfixes since but it's feature complete, if not bug free.
> >
> > What about `nova host-evacuate-live` and a few other commands
> > identified in doc/source/cli/data/nova.csv?
> this has deliberatlly not being ported to OSC and we never intend to add it.
>
> we advise people to impelemtnt this them selves as it purly a client side impleantion and discurage
> using the exsiting host-eveacuate-live as its error handeling if some live mirations fail is undefiend.
>
> you can do a better job yourself.
>
> >
> > aggregate-cache-images,,Request images be cached. (Supported by API
> > versions '2.81' - '2.latest') [hint: use '-- os-compute-api-version'
> > flag to show help message for proper version]
> > host-evacuate,,Evacuate all instances from failed host.
> > host-evacuate-live,,Live migrate all instances off the specified host
> > to other available hosts.
>
> all the host eveacutate apis were not ported for the same reasons as host-evacuate-live.
> this is something the nova team nolonger wants to maintain and we deliberatly chose to not port those to
> osc.
>
> > host-meta,,Set or Delete metadata on all instances of a host.
> again this is not something we want to maintain.
> its not part of the nova api and can be implented yourself in a few lines of bash.
>
> > host-servers-migrate,,Cold migrate all instances off the specified
> as with the other host-evacuate command this is condiers depercated and was intentionally not ported
> > host to other available hosts.
> > hypervisor-servers,,List servers belonging to specific hypervisors.
> openstack server list --all-projects --host <hostname>
>
> by the way all the host-evacuate,host-evacuate-live and host-servers-migrate commands do is call
> the list endpoint  as show aboove to get vms on a give host and loop over them calling evacuate, live migrate or cold migrate
> there is no error handeling and for hsot-server-migrate i dont think it  actully confirms the migration.
> it may but the dosc dont say one way our another. it certenly wont do the right thing in most caes if there is an error so you should not use it
> if you really care about the vms.
>
>
> > hypervisor-uptime,,Display the uptime of the specified hypervisor.
> the uptime of a hyperivor is part of a deprectated api that was mainly used by xen
> that is technially avaiable as part of the hyperviors api now but os-host has been deprecated for years
> and it will eventraully be removed.
>
> > instance-action,,Show an action.
> > instance-action-list,,List actions on a server.
>
> the instance action are aviable via
> openstack server event {list,show}
>
>
> > instance-usage-audit-log,,List/Get server usage audits
> >
> usage is aviabel via "openstack usage {list,show}"
>
>
> > .
> > migration-list,,Print a list of migrations.
> migration info is aviable at
>
> "openstack server migration {abort,confirm,force complete,list,rever,show}"
> and you can also confrim or revert a migrate via
> "openstack server migrate {conrim,revert}"
>
> > version-list,,List all API versions.
> > volume-update,,Update volume attachment.
> volume updates shoudl be done via cinder all nova proxy apis have been deprecated for 3+ year proably even longer so no clinet
> shoudl still be using those
>
> the equivalent woudl openstack volume migrate i belvie.
> the volume-update api is really swap volume i belive
> >
>

I didn't realise the host-evacuate-live command was not planned to be
reimplemented. Thanks for the details.



More information about the openstack-discuss mailing list