diff options
| author | Stephen Finucane <sfinucan@redhat.com> | 2019-08-16 01:19:59 +0100 |
|---|---|---|
| committer | Stephen Finucane <sfinucan@redhat.com> | 2019-12-23 14:20:28 +0000 |
| commit | 02eb9cffe6dd72b58bbcd660588e79a504e4d738 (patch) | |
| tree | d49a2197e300090dbc6c7030c2e99cd35f23739c /api-ref | |
| parent | 4cb8136e95f38f4fbbe8eec9395400fd5076e3fa (diff) | |
| download | nova-02eb9cffe6dd72b58bbcd660588e79a504e4d738.tar.gz | |
Remove 'nova-xvpvncproxy'
This legacy service is no longer used and was deprecated during the
Stein cycle [1]. It's time to say adios and remove them in their
entirety. This is pretty straightforward, with the sole exception of
schema for the 'remote-consoles' API, which has to continue supporting
requests for type 'xvpvnc' even if we can't fulfil those requests now.
[1] https://review.opendev.org/#/c/610076/
Part of blueprint remove-xvpvncproxy
Depends-On: https://review.opendev.org/695853
Change-Id: I2f7f2379d0cd54e4d0a91008ddb44858cfc5a4cf
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Diffstat (limited to 'api-ref')
| -rw-r--r-- | api-ref/source/parameters.yaml | 4 | ||||
| -rw-r--r-- | api-ref/source/servers-action-remote-consoles.inc | 3 | ||||
| -rw-r--r-- | api-ref/source/servers-remote-consoles.inc | 4 |
3 files changed, 3 insertions, 8 deletions
diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml index d21c3caf00..337aa5ec9f 100644 --- a/api-ref/source/parameters.yaml +++ b/api-ref/source/parameters.yaml @@ -5284,7 +5284,7 @@ os-getVNCConsole: type: object os-getVNCConsole-type: description: | - The type of VNC console. The valid values are ``novnc`` and ``xvpvnc``. + The type of VNC console. The only valid value is ``novnc``. in: body required: true type: string @@ -5833,7 +5833,7 @@ remote_console_protocol: type: string remote_console_type: description: | - The type of remote console. The valid values are ``novnc``, ``xvpvnc``, + The type of remote console. The valid values are ``novnc``, ``rdp-html5``, ``spice-html5``, ``serial``, and ``webmks``. The type ``webmks`` is added since Microversion ``2.8``. in: body diff --git a/api-ref/source/servers-action-remote-consoles.inc b/api-ref/source/servers-action-remote-consoles.inc index 6e0b7fc9c7..582365c2fc 100644 --- a/api-ref/source/servers-action-remote-consoles.inc +++ b/api-ref/source/servers-action-remote-consoles.inc @@ -175,9 +175,6 @@ Gets a VNC console for a server. Specify the ``os-getVNCConsole`` action in the request body. -The supported connection types are ``novnc``, ``xvpvnc``. Such as connect -with ``novnc``, set ``type`` parameter to ``novnc``. - Normal response codes: 200 Error response codes: badRequest(400), unauthorized(401), forbidden(403), itemNotFound(404), diff --git a/api-ref/source/servers-remote-consoles.inc b/api-ref/source/servers-remote-consoles.inc index 9aa11af822..c8515d3315 100644 --- a/api-ref/source/servers-remote-consoles.inc +++ b/api-ref/source/servers-remote-consoles.inc @@ -17,9 +17,7 @@ The API provides a unified request for creating a remote console. The user can get a URL to connect the console from this API. The URL includes the token which is used to get permission to access the console. Servers may support different console protocols. To return a remote console using a specific -protocol, such as RDP, set the ``protocol`` parameter to ``rdp``. For the same -protocol, there may be different connection types such as ``vnc protocol and -novnc type`` or ``vnc protocol and xvpvnc type``. +protocol, such as RDP, set the ``protocol`` parameter to ``rdp``. Normal response codes: 200 |