My assumption on the depreciation messages is that this is targeted at non-core OpenStack applications.
OpenStack developer pressure should be established within the projects, not by overwhelming production clouds with logs that something is depreciated. Equally, asking locally developed internal application developers to migrate when the official projects have not will be a tough meeting. Tim > -----Original Message----- > From: Russell Bryant [mailto:[email protected]] > Sent: 26 March 2014 18:52 > To: [email protected] > Subject: Re: [openstack-dev] [All][Keystone] Deprecation of the v2 API > > > Logging on half of the API calls is obviously bad, but logging a single time > seems reasonable. Deployers need to know it's deprecated, > too. If an API is going away, they have to make plays to test/deploy the new > thing. > > -- > Russell Bryant > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
