Hi Mark: It's been a little while since I looked at this last, but as I recall these values seem to be used and needed only by the trove taskmanager. If you have support for metering messages turned on, this account gets used to look up instance details when sending periodic metering messages to an AMQP exchange.
These aren't needed on the guest-agent, and that's probably the reason why a non-existing value of "radmin" seems to work. The fact that this exists in the guest configuration as well is probably a bug and should be cleaned up. Cheers, Nikhil On Tue, Jan 20, 2015 at 4:05 PM, Mark Kirkwood < mark.kirkw...@catalyst.net.nz> wrote: > I've been looking at how the 3 nova_proxy_admin_* settings are used. I'm > coming to the conclusion that I'm confused: > > E.g I note that a standard devstack (stable/juno branch) with trove > enabled sets these as follows: > > nova_proxy_admin_pass = > nova_proxy_admin_tenant_name = trove > nova_proxy_admin_user = radmin > > > However there is no 'radmin' user (or role) created in keystone, so the > settings above cannot possibly work (if they were needed/used). Some > experimentation involving removing these three settings from all of the > trove config files seems to support the idea that they are in fact not > needed, which has me somewhat puzzled. > > If someone could shed some light here that would be awesome! > > Thanks > > Mark > > > __________________________________________________________________________ > 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 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