settingsLogin | Registersettings

[openstack-dev] [trove] Confused about nova_proxy_admin_* settings

0 votes

I've been looking at how the 3 novaproxyadmin_* 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:

novaproxyadminpass =
nova
proxyadmintenantname = trove
nova
proxyadminuser = 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

asked Jan 21, 2015 in openstack-dev by Mark_Kirkwood (5,760 points)   3 8 13
retagged Jan 28, 2015 by admin

2 Responses

0 votes

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.kirkwood at catalyst.net.nz> wrote:

I've been looking at how the 3 novaproxyadmin_* 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:

novaproxyadminpass =
nova
proxyadmintenantname = trove
nova
proxyadminuser = 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-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL:

responded Jan 21, 2015 by Nikhil_Manchanda (2,360 points)   2 3
0 votes

Thanks Nikhil,

I figured I must have missed something that actually used the proxy - I
didn't have metering enabled in devstack. I'll enable it and (I guess)
it should fail until I give it correct proxy admin credentials...

Cheers

Mark

On 22/01/15 05:55, Nikhil Manchanda wrote:
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.kirkwood at catalyst.net.nz> wrote:

I've been looking at how the 3 novaproxyadmin_* 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:

novaproxyadminpass =
nova
proxyadmintenantname = trove
nova
proxyadminuser = 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-request at 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-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Jan 22, 2015 by Mark_Kirkwood (5,760 points)   3 8 13
...