On Thu, Jan 29, 2015 at 2:37 AM, Daniel P. Berrange <berra...@redhat.com> wrote: > On Wed, Jan 28, 2015 at 01:39:31PM -0800, Michael Still wrote: >> On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell <tim.b...@cern.ch> wrote: >> > There are currently 35% of openstack clouds from the survey using >> > this feature. I would therefore propose that this be reviewed with >> > the operators in detail before a rapid depreciation is performed. >> > To the best of my knowledge, the new package is not yet in use in >> > production. >> >> The patch itself doesn't actually propose a rapid removal. Its marked >> as being "removed in a future release". The reality is that this code >> has been largely abandoned for a long time... We're just trying to be >> more honest with signalling that to users. So I think we're on the >> same page here. >> >> > At CERN, we are highly dependent on this function and while it does >> > not provide 100% compatibility, it works pretty well. >> >> What happens when CERN upgrades to a modern boto and auth doesn't >> work? That's been known for at least a week or two and no one has >> stepped up to fix it. > > That's a failing of the Nova team that must be addressed. As maintainers > it is our job to produce software that meets the needs of our users. We > have 35% of users reporting they use this EC2 code, so fixing any problems > should be a high priority item & these bugs considered release blockers > for Kilo.
I agree that it is best for the ec2 API implementation in Kilo nova to work with modern botos. Thanks Daniel for volunteering to work on it. Michael -- Rackspace Australia _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
