yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => kilo-3

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1417555

Title:
  Current AWS CLI and botocore do not work with EC2 API in nova

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  AWS CLI is a recommended Amazon's CLI and it uses botocore library instead of boto to access EC2 API:
  http://aws.amazon.com/cli/

  Amazon's URL for AWS EC2 API is: 
  https://ec2.amazonaws.com/

  OpenStack nova's EC2 API service URL is: 
  http://some.server.com:8773/services/Cloud

  AWS CLI works with the root URLs (without something trailing, like ../services/Cloud). This is so because of the following bug in botocore:
  https://github.com/boto/botocore/issues/420

  We did supply the fix here:
  https://github.com/Andrey-mp/botocore/commit/162bdc22de3ff3d6243459c132ca9bd01e02533f

  However, we do not control botocore and cannot predict when this fix is going to be applied or guarantee that in the future nothing alike happens again (in fact, older botocore didn't have this bug).
  Another problem is that there is a set of Tempest tests currently used to work against stackforge/ec2-api but which is about to be employed against nova's ec2-api. These Tempest tests use botocore too. And won't work with the nova's EC2-API until either botocore or nova is fixed.

  So we suggest to fix the situation in nova by changing the URL to http://some.server.com:8773/.
  It'll provide the solution for OpenStack independent of botocore bugs and fixes in this area, and will make the service URL more alike (compatible, sort of) with the AWS EC2 API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1417555/+subscriptions