yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

The actual bug, if we were going to go down that path, would be
eliminate this entirely. This is basically used to find template files:

ribos:~/.../openstack/nova/nova(master)> git grep basedir_def 
conf/cloudpipe.py:        default=paths.basedir_def('nova/cloudpipe/bootscript.template'),
conf/paths.py:def basedir_def(*args):
conf/virt.py:    default=paths.basedir_def('nova/virt/interfaces.template'),
conf/xvp.py:               default=paths.basedir_def('nova/console/xvp.conf.template'),


These could be more properly registered as python resources, and we could use the python infrastructure itself to find them.

** Changed in: nova
       Status: New => Opinion

-- 
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/1592535

Title:
  wrong default value for $pybasedir

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  In nova/conf/paths.py, I can read:

  path_opts = [
      cfg.StrOpt('pybasedir',
                 default=os.path.abspath(os.path.join(os.path.dirname(__file__),
                                                      '../../')),
                 help='Directory where the nova python module is installed'),

  This means that, wherever nova source code is installed to generate
  nova.conf is going to be the default value for pybasedir. This has all
  the chances in the world to be a wrong value. For example, if building
  from /home/zigo/sources/mitaka/nova/nova, we end up with:

  # Directory where the nova python module is installed (string value)
  #pybasedir = /home/zigo/sources/openstack/mitaka/nova/build-area/nova-13.0.0/debian/tmp/usr/lib/python2.7/dist-packages

  instead of:
  #pybasedir = /usr/lib/python2.7/dist-packages

  Unfortunately, this ends up in the package.

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