I support the move to deprecate but I don’t think the EC2API people should be responsible for the S3 compatibility. This would seem to need an S3API project (working with the SWIFT folk to do a smooth migration).
Tim From: Morgan Fainberg Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Saturday 6 February 2016 at 17:57 To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [keystone][ec2-api][swift] Moving EC2 Auth and S3Token to Externally supported So based on this conversation and the need to support the legal requirement of some deployers to totally strip the code from the install, I've taken another approach. The base controller will emit a 403 (Forbidden) if the core of the compat code is not available for import. If the legal demands (corp.legal) change for the org that requires the ease of removing the compat code changes, we will remove the fallback to the hard 403 response if the code is still in Keystone's tree. This type of fallback will be handled only for the aws compat code since the legal requirements have been relying on this , I do not expect this pattern to be expanded beyond this specific AWS compat code in keystone. The move to deprecate and move this into the hands of the ec2api team will continue to be discussed so we can hammer out details making sure we don't break apps relying on the aws compat apis. Long term I fully expect this to not be in Keystone's tree. --M
smime.p7s
Description: S/MIME cryptographic signature
__________________________________________________________________________ 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
