yahoo-eng-team team mailing list archive

[Roman Podoliaka <rpodolyaka+bugs@xxxxxxxxxxxx>]

Public bug reported:

Now nova-novncproxy config options reside in [DEFAULT] group, which is
very confusing given the fact how they are named, e.g.:

    cfg.StrOpt('cert',
               default='self.pem',
               help='SSL certificate file'),
    cfg.StrOpt('key',
               help='SSL key file (if separate from cert)'),

one would probably expect these options to set SSL key/cert for other
places in Nova as well (e.g. API), but those are used solely in novnc
instead.

We could probably give noVNC options their own group in the config and
use deprecate_name/deprecate_group for backwards compatibility with
existing config files.

** Affects: nova
     Importance: Undecided
     Assignee: Roman Podoliaka (rpodolyaka)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Roman Podoliaka (rpodolyaka)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1494207

Title:
  novncproxy options in [DEFAULT] group are confusing

Status in OpenStack Compute (nova):
  New

Bug description:
  Now nova-novncproxy config options reside in [DEFAULT] group, which is
  very confusing given the fact how they are named, e.g.:

      cfg.StrOpt('cert',
                 default='self.pem',
                 help='SSL certificate file'),
      cfg.StrOpt('key',
                 help='SSL key file (if separate from cert)'),

  one would probably expect these options to set SSL key/cert for other
  places in Nova as well (e.g. API), but those are used solely in novnc
  instead.

  We could probably give noVNC options their own group in the config and
  use deprecate_name/deprecate_group for backwards compatibility with
  existing config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1494207/+subscriptions