nova-novncproxy (noVNC) in OpenStack Cloud Administrator Guide - current

[Andrew Miles]

I have to run 'service nova-novncproxy restart'

and not

service novnc restart

-----------------------------------
Built: 2014-11-19T18:41:53 00:00
git SHA: f2468b21b86205d1c509cd9c07625bee36fb162e
URL: http://docs.openstack.org/admin-guide-cloud/content/nova-vncproxy-replaced-with-nova-novncproxy.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/common/section_compute-configure-vnc.xml
xml:id: nova-vncproxy-replaced-with-nova-novncproxy

[Michael Still (mikal)]

This naming "nova-novncproxy" would be consistent with the Ubuntu packages I have seen (nova compute is called nova-compute for example). Naming will of course depend on the packages being used. I think this bug is therefore valid.

[Andreas Jaeger (jaegerandi)]

See doc/install-guide/section_nova-controller-install.xml for full details on how it's done with different distros.
For Ubuntu the suggested change is correct, for RDO and SUSE, it's openstack-nova-novncproxy.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/137974

[Laurel Michaels (lmichaels)]

Hi Michael and Andreas,

Thanks for your help on this. A few miscellaneous issues:

***

There are 2 problems on cloud admin guide, page, not just one (like the bug says)

Regarding the section in the cloud admin guide that the bug points to -- from reading doc/install-guide/section_nova-controller-install.xml, it looks like we have 2 errors on the cloud admin guide page (not just the one in the bug):

First, the one in the bug (service novnc restart should be service nova-novncproxy restart)

Second, the cloud admin guide page includes this statement: apt-get install novnc, and I believe that should be apt-get install nova-novncproxy.

***

Syntax differences between distros

Regarding the "different syntaxes used by different distros" issue (nova-novncproxy for ubuntu and openstack-nova-novcnproxy for rhel/centos/fedora) -- I took a look at all the VNC console proxy sections that are under this main page in the cloud admin guide (the guide that this bug refers to):

http://docs.openstack.org/admin-guide-cloud/content/getting-started-with-vnc-proxy.html

They all use the ubuntu syntax for their examples. For that reason, I believe it's appropriate to keep that syntax when addressing this particular bug, so that's what I did.

If, at a later time, we decide to revisit all these sub-sections in the cloud admin guide, and talk about the other syntax for the other distros, that's fine too, but that should be a separate bug -- I believe it's out of the scope of this bug.

***

Anyway, thanks again for your help!

Laurel

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/137974
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=5494ca6e200548a9796d2f38a1632fec4657211e
Submitter: Jenkins
Branch: master

commit 5494ca6e200548a9796d2f38a1632fec4657211e
Author: Laurel Michaels <email address hidden>
Date: Sun Nov 30 15:12:12 2014 -0500

    fixed outdated reference to novnc

    The cloud admin guide contained these
    out-of-date commands:

    apt-get install novnc
    service novnc restart

    I changed them to the current syntax,
    which is:

    apt-get install nova-novncproxy
    service nova-novncproxy restart

    Change-Id: Ib4e2d79951f6a122535dd0fbe7134e6cca59b494
    Closes-Bug: 1394345

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.