Re: [nova] Train: how to use newer API microversion
Alright, I made it work it seems. After I added the new endpoints (v2.1) and disabled the old ones (v2) I restarted nova-api service. This allowed me to use microversion 2.37 to use the option "--nic none", so that works as expected now. I just don't know yet if there are any clients that require v2 so for now I let them in "disabled" state. Thanks, Eugen Zitat von Eugen Block <eblock@nde.ag>:
If you (or your end users) rely on the legacy APIs, you can have both like this (192.0.2.40 is the example IP address of the API host; the /compute could be :some_port if you prefer that):
I started with disabling the old endpoints but then I couldn't use compute at all to create a new instance. There must be something still relying on the old endpoint but I can't find it right now. I'll give it another shot tomorrow. Thanks for your input.
Zitat von Radosław Piliszek <radoslaw.piliszek@gmail.com>:
On Thu, Mar 18, 2021 at 3:50 PM Eugen Block <eblock@nde.ag> wrote:
I also found that already, but it doesn't describe how I can move from v2 to v2.1 in order to use only the newer API. Do you have any information about that?
If you (or your end users) rely on the legacy APIs, you can have both like this (192.0.2.40 is the example IP address of the API host; the /compute could be :some_port if you prefer that):
+----------------------------------+-----------+--------------+----------------+---------+-----------+------------------------------------------------+ | ID | Region | Service Name | Service Type | Enabled | Interface | URL | +----------------------------------+-----------+--------------+----------------+---------+-----------+------------------------------------------------+ | xxx | RegionOne | nova | compute | True | public | http://192.0.2.40/compute/v2.1 | | xxx | RegionOne | nova_legacy | compute_legacy | True | public | http://192.0.2.40/compute/v2/$(project_id)s | +----------------------------------+-----------+--------------+----------------+---------+-----------+------------------------------------------------+
If you don't need the legacy APIs, you can delete their endpoints.
-yoctozepto
participants (1)
-
Eugen Block