[openstack-dev] [devstack][keystone] Don't use devstack master branch with stable/kilo

2015-05-16 Thread Scott Drennan
Perhaps an obvious statement, but devstack master was working with
stable/kilo until recently, and as of today, it isn't any more (at least
for me).

The devstack commit "Use stevedore for keystone backends" on 2014-05-15
changes the way backends are set, and when I did a fresh install today I
ended up with keystone.conf entries like this:

[assignment]
driver = sql
...
[identity]
driver = sql
...
[token]
driver = sql


rather than fully specified module names (e.g. "driver =
keystone.identity.backends.sql.Identity")

This caused keystone to fail, with errors in /var/log/apache2/keystone.log
like this:

2015-05-16 21:16:25.786955 mod_wsgi (pid=9296): Exception occurred
processing WSGI script '/var/www/keystone/main'.
2015-05-16 21:16:25.787114 Traceback (most recent call last):
2015-05-16 21:16:25.787189   File "/var/www/keystone/main", line 25, in

2015-05-16 21:16:25.787409 application =
wsgi_server.initialize_application(name)
2015-05-16 21:16:25.787437   File
"/opt/stack/keystone/keystone/server/wsgi.py", line 51, in
initialize_application
2015-05-16 21:16:25.787600 startup_application_fn=loadapp)
2015-05-16 21:16:25.787625   File
"/opt/stack/keystone/keystone/server/common.py", line 41, in setup_backends
2015-05-16 21:16:25.787769 drivers = backends.load_backends()
2015-05-16 21:16:25.787795   File
"/opt/stack/keystone/keystone/backends.py", line 39, in load_backends
2015-05-16 21:16:25.787946 _IDENTITY_API = identity.Manager()
2015-05-16 21:16:25.789345   File
"/opt/stack/keystone/keystone/common/dependency.py", line 131, in
__wrapped_init__
2015-05-16 21:16:25.789519 init(self, *args, **kwargs)
2015-05-16 21:16:25.789544   File
"/opt/stack/keystone/keystone/common/dependency.py", line 193, in wrapper
2015-05-16 21:16:25.789570 self.__wrapped_init__(*args, **kwargs)
2015-05-16 21:16:25.789584   File
"/opt/stack/keystone/keystone/identity/core.py", line 412, in __init__
2015-05-16 21:16:25.790098 super(Manager,
self).__init__(CONF.identity.driver)
2015-05-16 21:16:25.790124   File
"/opt/stack/keystone/keystone/common/manager.py", line 70, in __init__
2015-05-16 21:16:25.790203 self.driver =
importutils.import_object(driver_name)
2015-05-16 21:16:25.790226   File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
38, in import_object
2015-05-16 21:16:25.790312 return import_class(import_str)(*args,
**kwargs)
2015-05-16 21:16:25.790335   File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line
27, in import_class
2015-05-16 21:16:25.790358 __import__(mod_str)
2015-05-16 21:16:25.790384 ValueError: Empty module name


After much head-scratching, since I'm not that familiar with keystone, I
figured out what was going on, corrected keystone.conf, and then went back
to devstack:stable/kilo, which behaves normally.  I don't think there's an
issue here, but wanted to share in case someone else hits the same problem.

cheers,
Scott
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron]Anyone looking at support for VLAN-aware VMs in Liberty?

2015-05-12 Thread Scott Drennan
On Friday, May 8, 2015, Erik Moe  wrote:

>   I have not been able to work with upstreaming of this for some time
> now. But now it looks like I may make another attempt. Who else is
> interested in this, as a user or to help contributing?
>
> I'm looking at it for Nuage Networks and can contribute in Liberty.

>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [neutron]Anyone looking at support for VLAN-aware VMs in Liberty?

2015-05-04 Thread Scott Drennan
VLAN-transparent or VLAN-trunking networks have landed in Kilo, but I don't
see any work on VLAN-aware VMs for Liberty.  There is a blueprint[1] and
specs[2] which was deferred from Kilo - is this something anyone is looking
at as a Liberty candidate?  I looked but didn't find any recent work - is
there somewhere else work on this is happening?  No-one has listed it on
the liberty summit topics[3] etherpad, which could mean it's
uncontroversial, but given history on this, I think that's unlikely.

cheers,
Scott

[1]: https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
[2]: https://review.openstack.org/#/c/94612
[3]: https://etherpad.openstack.org/p/liberty-neutron-summit-topics
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev