[PKG-Openstack-devel] Bug#774114: closed by Thomas Goirand <zigo at debian.org> (Re: Bug#774114: novnc: Permit to use noVNC outside nova)
Daniel Dehennin
daniel.dehennin at baby-gnu.org
Tue Dec 30 14:14:43 UTC 2014
owner at bugs.debian.org (Debian Bug Tracking System) writes:
[...]
> If the issue is only the dependency on Nova, at the packaging level,
> then I don't see how depending on a Python lib can be a problem.
I agree that “unusable” is not the proper word, it will install a lot of
dependencies and create a “nova” user[1]:
LANG=C apt-get -s install novnc
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
ieee-data libjs-sphinxdoc libjs-swfobject libjs-underscore
[...]
Suggested packages:
python-amqp-doc python-amqplib-doc python-egenix-mxdatetime
[...]
Recommended packages:
javascript-common python-cliff-doc python-utidylib python-openid
python-scgi libjs-mochikit python-dev-all python-wheel
python-ndg-httpsclient python-sqlalchemy-ext
The following NEW packages will be installed:
ieee-data libjs-sphinxdoc libjs-swfobject libjs-underscore
libxmlsec1 libxmlsec1-openssl novnc python-amqp python-amqplib
python-anyjson python-babel python-babel-localedata python-boto
python-cinderclient python-cliff python-cmd2 python-colorama
python-daemon python-distlib python-dns python-ecdsa
python-eventlet python-extras python-feedparser python-fixtures
python-formencode python-glanceclient python-greenlet
python-html5lib python-iso8601 python-jinja2 python-json-patch
python-json-pointer python-jsonpatch python-jsonschema
python-keystoneclient python-kombu python-libxml2
python-lockfile python-lxml python-mako python-markupsafe
python-memcache python-migrate python-mimeparse python-mock
python-mysqldb python-netaddr python-neutronclient python-nova
python-novaclient python-novnc python-oslo.config
python-oslo.messaging python-oslo.rootwrap python-paramiko
python-paste python-pastedeploy python-pastedeploy-tpl
python-pbr python-pip python-posix-ipc python-prettytable
python-pycadf python-pyparsing python-pysaml2 python-repoze.lru
python-repoze.who python-requests python-routes
python-sqlalchemy python-stevedore python-subunit python-suds
python-tempita python-testrepository python-testscenarios
python-testtools python-tz python-urllib3 python-warlock
python-webob python-xattr python-yaml websockify xmlsec1
0 upgraded, 86 newly installed
I think they are not required for noVNC but for noVNC with nova.
[...]
> By the way, you may know that "noVNC" stands for "nova-VNC", so making
> it useful for something else than Nova would be going out of the defined
> path.
I was not aware of the “nova-VNC”, as a lot of other products use it[2].
My primary wish was to share the novnc integration[3] for all packages
and admins:
- move the nova stuffs (user creation), outside of novnc and
python-novnc, for example in something like nova-consoleproxy
- updates the dependencies in openstack packages if required
Does it sound ridiculous?
Regards.
Footnotes:
[1] http://anonscm.debian.org/cgit/openstack/novnc.git/tree/debian/novnc.postinst
[2] https://github.com/kanaka/noVNC/wiki/ProjectsCompanies-using-noVNC
[3] https://github.com/kanaka/noVNC/wiki/Integration
--
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 342 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20141230/aedd61c2/attachment.sig>
More information about the Openstack-devel
mailing list