[openstack-dev] [devstack] let's give a different warning message for different OS_PROJECT_NAME ?
amrith at tesora.com
Wed May 25 14:41:54 UTC 2016
> -----Original Message-----
> From: Sean Dague [mailto:sean at dague.net]
> Sent: Wednesday, May 25, 2016 6:06 AM
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [devstack] let's give a different warning
> message for different OS_PROJECT_NAME ?
> On 05/25/2016 04:05 AM, li.yuanzhen at zte.com.cn wrote:
> > Hi All,
> > A warning message leave me a doubt.
> > After having installed openstack by devstack, when I use the cmd
> > "source openrc", a warning message is
> > printed in the terminal that "WARNING: setting legacy
> > OS_TENANT_NAME to support cli tools."
> > and then when I execute the cmd "source openrc admin admin", it
> > give the same info.
> > at first, I think I make a failure in "source openrc" or
> > installing openstack, after read the openrc script,
> > I know this message will be printed no matter what openrc's
> > arguments are injected.
> > So I think, this message have an ambiguity for user. could we
> > <app:ds:ambiguity>ignore this info 'echo "WARNING: setting legacy
> > OS_TENANT_NAME to support cli tools." ' or make some different info
> > for different arguments, such as:
> > echo "WARNING: setting legacy
> > OS_TENANT_NAME=$OS_PROJECT_NAME to support cli tools."
> > what do you think?
> I think that's a good suggestion, please propose a patch and we should
> be able to get it in pretty quickly.
Would people be OK with listing all of the legacy parameters that are being set in the same format as a standard deprecation warning?
> Sean Dague
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev