I think you need to do option 2 and print deprecation warnings, then the question becomes for how long.
I think there is a policy for this and that it is deprecate in N remove in N+1 Clients are a bit different so maybe keep it for ~6 months? Sam On 8 Nov 2013, at 10:49 am, Leandro Costantino <leandro.i.costant...@intel.com> wrote: > Hi all, > > Clients like python-novaclient/cinderclient/trove still support NOVA_*, > CINDER_*, TROVE_* variables for > backward compatibility support,while clients like > python-neutronclient/keystoneclient only supports OS_* env vars. > > > The following bug (#1061491, see review), mentions that it may be confusing > if novaclient for instance, > silently accept those variables without even being mentioned on the current > help/documentation neither warning the user at all. > (User has exported NOVA_USERNAME/CINDER_USERNAME/etc instead of OS_USERNAME > etc.) > > As Kevin suggested on the review, (https://review.openstack.org/#/c/55588/) > “we need to make sure that we have consensus that enough time has passed to > drop the old variables”. > > I would like to hear opinions about this. Some options that i can think of > are: > > 1) Remove NOVA_USERNAME, NOVA_PASSWORD and NOVA_PROJECT_ID support > from novaclient. Same for other clients allowing vars other than > OS_USERNAME, > OS_PASSWORD, OS_TENANT_ID for this specific options. > 2) Warn about deprecation if they are being used. > 3) Ignore this topic, keep everything as today and just close the > 'bug/suggestion'. > 4) Other? > > Best Regards > -Leandro > > PS: shall this message belong to another ML, please, let me know. > > > > > > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev