[openstack-dev] Configuring default page-size on image-list call in nova
Hi All, Recently we had a bug where page-size parameter was not passed in from nova while making a call to glance for image list. This was addressed by https://review.openstack.org/#/c/43262/. As a result, I also thought that it might make sense to have a default page size configurable for image list call on nova end. The reason is, if we do not have page-size parameter set, then the page size is defaulted to 20 on glance client. This is not a configurable value on glance client. If there are huge number images(say 1000), then nova ends up making huge number of calls to glance(50, in this case). So, having a default page-size configurable on nova end would help to have more control over this value. This is captured in https://blueprints.launchpad.net/nova/+spec/default-page-size-for-image-list Can we get some discussions started over this? Thanks -- Sumanth N S ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] ./run_tests.sh fails with db type could not be determined error
Hi,
From sometime today, I am not any more able to run ./run_tests.sh. It gives
the following error,
*Running `tools/with_venv.sh python setup.py testr --testr-args='--subunit
'`*
*db type could not be determined*
*error: testr failed (3)*
*
*
*Ran 0 tests in 6.989s*
I tried recreating my virtual environment, running tests with/without site
packages but the result was same.
When I run tests with -d(debug) option, I see the below error.
*ERROR: unittest.loader.ModuleImportFailure.virt.xenapi.test_xenapi*
*--*
*ImportError: Failed to import test module: virt.xenapi.test_xenapi*
*Traceback (most recent call last):*
* File
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py,
line 252, in _find_tests*
*module = self._get_module_from_name(name)*
* File
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/loader.py,
line 230, in _get_module_from_name*
*__import__(name)*
* File /Users/sumansn/Work/nova/nova/tests/virt/xenapi/test_xenapi.py,
line 43, in module*
*from nova import test*
* File nova/test.py, line 52, in module*
*from nova.tests import conf_fixture*
* File nova/tests/__init__.py, line 39, in module*
*% os.environ.get('EVENTLET_NO_GREENDNS'))*
*ImportError: eventlet imported before nova/cmd/__init__ (env var set to
None)*
My python version is 2.7.3 and I am using a Mac OSx 10.7.5
Has anything changes recently that I have to account for? Any help would be
appreciated?
Thanks
--
Sumanth N S
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Guidelines for resource names in nova?
Hi All, Recently I have come across a bug in launchpad/nova which states that, while creating flavors, leading/trailing spaces around flavor names is currently allowed and expected not to be allowed. Bug reference - https://bugs.launchpad.net/nova/+bug/1206396 I want to extend this to other resources in nova also. I have following questions - 1. What are the other restrictions we should put on a resource's name, apart from extra spaces? 2. Should we define a guideline for names and other attributes while creating resources? -- Sumanth N S ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
