I don't actually grok what this does that 'oslopolicy-checker' couldn't do, so perhaps we can deprecate this in the future. For now though, simply document the thing. While we're here, we make some additional related changes: - Remove references to the 'policy.yaml' file for services that don't use policy (i.e. everything except the API services and, due to a bug, the nova-compute service). - Update remaining references to the 'policy.yaml' file to include the 'policy.d/' directory - Update the help text for the '--api-name' and '--target' options of the 'nova-policy policy check' command to correct tense and better explain their purpose. Also, yes, 'nova-policy policy check' is dumb. Don't blame me :) Change-Id: I913b0de9ec40a615da7bf9981852edef4a88fecb Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Related-bug: #1675486
1.6 KiB
nova-spicehtml5proxy
nova-spicehtml5proxy
Synopsis
nova-spicehtml5proxy [<options>...]
Description
nova-spicehtml5proxy
is a server daemon that
serves the Nova SPICE HTML5 Websocket Proxy service, which provides a
websocket proxy that is compatible with OpenStack Nova SPICE HTML5
consoles.
Options
General options
Websockify options
Spice options
--spice-html5proxy_host SPICE_HTML5PROXY_HOST
IP address or a hostname on which the
nova-spicehtml5proxy
service listens for incoming requests.
This option depends on the [spice] html5proxy_base_url
option in nova.conf
. The nova-spicehtml5proxy
service must be listening on a host that is accessible from the HTML5
client.
--spice-html5proxy_port SPICE_HTML5PROXY_PORT
Port on which the nova-spicehtml5proxy
service listens
for incoming requests. This option depends on the
[spice] html5proxy_base_url
option in
nova.conf
. The nova-spicehtml5proxy
service
must be listening on a port that is accessible from the HTML5
client.
Debugger options
Files
/etc/nova/nova.conf
/etc/nova/rootwrap.conf
/etc/nova/rootwrap.d/
See Also
nova-novncproxy(1) <nova-novncproxy>
, nova-serialproxy(1) <nova-serialproxy>
Bugs
- Nova bugs are managed at Launchpad